-
1
1. Diagnose the problem before you draw an org chart
Every reorg traces to one of three drivers: growth (the business has outgrown the current structure, a new segment or product needs its own motion, or a geography needs real coverage), performance (the current org is missing number because the design is wrong, not because the people are), or efficiency (the org has drifted into too many layers, too wide a span, or too many hand-offs for the stage you are at). Write down which driver explains the most pain and the specific evidence behind it. A reorg aimed at the wrong driver fixes the wrong thing: you redesign for growth when the real issue is performance, and six months later you are back where you started with a shaken team. Pick one primary driver, name the one or two secondary ones you will tolerate solving, and refuse to pile on scope from there.
- Pull attainment, pipeline velocity, win rate, and ramp data by segment and rep for the last four to eight quarters
- Interview the top and bottom third of managers to hear where they feel the current org fights them
- Write a one-page problem statement that names the driver, the evidence, and the outcome you expect from the change
Tip: If the honest answer is more than one driver, you are planning a redesign disguised as a reorg. Scope down or stage the work across two cycles rather than trying to solve everything in one cutover.
-
2
2. Document the current org and the metrics that go with it
Before you design the future, map the present. Build a full picture of the current org that includes every role, the person in it, their manager, their span of control, their segment or territory, their quota, their attainment history, and the comp plan on top. Pair it with the metrics that matter for the decision: productivity per rep, cost of sale, ramp time, voluntary and involuntary attrition, and the ratio of quota-carrying heads to overhead. The point is not to produce a slideware chart. It is to have the data in hand when a manager pushes back and says a change will hurt their team. Reorgs that skip this step end up relitigating facts in every review, and the plan ships late and politically bruised.
- Export the full roster with role, manager, span, segment, quota, attainment, and tenure into a working sheet
- Compute productivity per rep (bookings over cost), average ramp, and attrition rate by team and segment
- Freeze the snapshot and share it with the exec sponsor and HR partner before any future-state design begins
-
3
3. Design the future org around role, span, and territory
Work the future org from three decisions, in this order. First, roles: what roles exist, what each one is accountable for, where the hand-offs are, and which roles are being added, merged, or retired. Second, span of control: how many direct reports each manager carries, which the research consistently puts at six to eight for a hands-on sales manager and up to ten for a coaching-light front-line role. Third, territory or segment: how coverage is divided and how accounts flow between roles. Do not start from names. Start from the shape. Draft two versions, a conservative one that solves the diagnosed problem with the fewest structural changes, and an aggressive one that solves it with a cleaner future state. Make the exec sponsor choose between real options, not between the plan and no plan.
- Define each role with a one-paragraph charter, a quota or metric, and the hand-offs in and out
- Set a target span of control per manager level and flag every box that violates it
- Draft conservative and aggressive versions and compute productivity, cost, and coverage for each
Tip: Design the org you need twelve to eighteen months from now, not the one that matches today's headcount exactly. Reorgs that solve for the current snapshot age out before the dust settles.
-
4
4. Run impact analysis on every affected person
This is the step that separates a plan from a working plan. For every person whose role, manager, segment, territory, or comp will change, document four things: what is changing, how their expected earnings move, whether their career trajectory improves or stalls, and the retention risk if they leave. Rank the list by retention risk, not by seniority. Build a specific remediation per high-risk case, which may be a comp true-up, a transition bonus, a quota grandfather, a title change, or an explicit career path commitment. If more than ten percent of quota-carriers show material downside with no remediation, the plan is not ready. Model the aggregate too: total comp exposure, severance liability for roles being retired, and the cost of the retention package in year one.
- Build a per-person change record with role delta, comp delta, manager delta, and retention risk score
- Prepare a specific remediation plan for every rep flagged medium or high risk
- Share the aggregate cost model with finance and legal so comp exposure and severance are approved before launch
Tip: Reorg plans that look good in aggregate often hide two or three individuals who will walk on announcement day. Pressure-test the plan by naming the ten people most likely to leave and asking whether the design still works without them.
-
5
5. Communicate 1:1 before anything goes public
Every person whose role, manager, or comp changes gets a prepared one-on-one with their new manager (or the departing one, if that is cleaner) before any all-hands, Slack post, or shared document goes out. Give managers a packet: what is changing for this person, why, what stays the same, how comp and in-flight deals will be handled, and the escalation path if something feels wrong. Lead with continuity before change. Sequence the conversations tightly, usually one to two business days, so the news does not leak before the field hears it from the right person. Reorgs do not fail because of the structure. They fail because people learned about their new life from a shared file, and the trust tax lasts for a year. Protect that moment with everything you have.
- Build a per-person brief for managers covering the change, the rationale, the comp impact, and the FAQ
- Rehearse the hardest three conversations with the HR partner before the real ones happen
- Hold all 1:1s inside a one to two day window and move the all-hands immediately after the last conversation
Tip: Give managers a decision tree for the five questions every rep will ask. Freelance answers in 1:1s create inconsistencies that eat the first month of transition.
-
6
6. Cut over on a fixed date
Pick one date and move everything on it. Change org trees in HRIS, repoint quotas in the comp system, reassign CRM ownership and routing rules, update dashboards, swap manager relationships, and ship the one-page per-person summary. Soft launches, where the chart changes but the systems do not, teach the team that the plan is optional and leave three parallel truths running in CRM, HRIS, and reality. Snapshot the pre-cutover state (ownership, pipeline, quota, manager) for every affected person and keep it searchable for 90 days. If a credit dispute or a quota question comes up in month two, you need the pre-cutover record to resolve it mechanically rather than by memory.
- Encode new roles, managers, and territories in HRIS, CRM, and the comp system on the same day
- Snapshot the pre-cutover state for every rep so any dispute can be resolved against a known baseline
- Send a one-page per-person summary on cutover day with new role, new manager, new quota, retained deals, and the escalation contact
-
7
7. Support reps through the 90-day transition
The first 90 days after cutover are where reorgs are won or lost. Stand up a transition cadence that is heavier than normal: weekly 1:1s between every rep and their new manager for the first six weeks, a biweekly pulse survey with three or four questions, a visible exception tracker for deal transitions and comp questions, and a named point of contact (usually the sales ops or chief of staff) who owns escalations. Managers absorb the hardest moments: a rep whose top account moved, a new direct report who is skeptical of the new boss, a comp plan that feels unfair until it is explained. Give them air cover and a predictable rhythm. Teams that invest in the first 90 days see sentiment stabilize by week six. Teams that assume cutover is the finish line see attrition spike at day 45.
- Lock weekly 1:1s between every affected rep and their new manager for six weeks, then move to biweekly
- Run a biweekly pulse (three questions, under two minutes) and share the trend line with sales leadership
- Hold a weekly exception review for 60 days to close out deal transitions, comp questions, and territory disputes
Tip: The right support signal is boring predictability, not heroics. If the first 60 days feel like a daily firefight, the structural plan is still wrong and no amount of 1:1 time will fix it.
-
8
8. Measure outcomes against the rationale at 90 and 180 days
Reorgs are usually declared successful at cutover and never measured again, which is how the same problem shows up in the next planning cycle wearing a new jersey. Set the measurement up front, tied directly to the diagnostic driver. If the driver was growth, measure new-segment pipeline, win rate, and productivity against the pre-cutover baseline. If it was performance, measure attainment projection and ramp time against plan. If it was efficiency, measure cost per booked dollar and manager span against the design target. Review at 90 days with sales leadership, HR, and finance, and again at 180 days with a sample of managers and reps in the room. Decide explicitly whether the reorg solved the problem, created new ones, needs a follow-on move, or should carry into the next annual plan with adjustments.
- Define the three to five outcome metrics tied to the diagnostic driver before the cutover goes live
- Hold a structured 90-day review with a written outcome and a decision on whether to adjust, hold, or extend
- Hold a 180-day review with the field in the room and feed the lessons into the next planning cycle
