To measure reorganization success, compare the outcome that prompted the redesign with a baseline from before it. Trace one piece of work through the new structure to see which decision or handoff changed. Then check what happened to quality. A customer who gets an account three days sooner but has to call back to fix it has experienced both sides of the redesign.
Jump to the copyable reorganization scorecard or see a completed 90-day review.
What would a successful reorganization change?
Start with the decision that justified the disruption. Suppose a company merges its sales support and activation teams because customers wait while routine applications move between managers. “Combine the teams by April” tells you when the boxes on the org chart should move. It says little about what an applicant should experience in May.
Give the redesign a testable promise: “If the onboarding lead can approve routine applications, customers should wait fewer working days for activation.” Name the person who can change the approval rule and the person who sees the customer outcome. Ask both to trace the same recent case. If they disagree about who could have approved it, you have already found something worth checking at day 30.
Set the target and comparison window before reading the results. McKinsey’s Getting organizational redesign right recommends defining short- and long-term measures when setting the redesign’s objectives. The review schedule below is a practical way to apply that principle to one workflow.
Which metrics show whether a reorganization is working?
For the onboarding merger, use three measures. Each answers a different question that leadership will face when it decides whether another team should adopt the design.
- Customer outcome — median onboarding time. Count working days from receipt of a complete routine application to activation. Use the same start event, end event, and working-day calendar in both periods. Also check the open queue: faster completions can hide older applications that nobody has finished.
- Change in the work — approval handoffs. Count each transfer of approval responsibility on a routine case and take the median across cases. Ask staff whether they still seek informal sign-off in chat. A workflow log can lose a handoff while the customer still waits for it.
- Quality check — reopened cases. Divide the number of activated cases reopened at least once within 14 days by all activated cases with a full 14 days of follow-up. Count each case once. Keep the definition of “reopened” consistent.
Choose measures that fit the reason for your redesign. If a merger was meant to reduce duplicate purchasing, measure duplicate orders and the time staff spend resolving them. Adoption of a common purchasing system is useful supporting evidence. For choosing measures across several initiatives, see organizational transformation metrics.
Reorganization success scorecard
Copy this worksheet into the review agenda. Complete one measure record for each outcome, workflow change, and quality check. Agree in advance who will make the decision if the measures point in different directions.
Review details
Redesign and workflow: [what changed, for whom]
Intended outcome: [what should improve]
Decision owner: [name]
Next review: [date]
Measure record
Measure and data source: [name and source]
Counting rule: [eligible cases, unit, start and end]
Baseline: [period, case count, value]
Target: [value and deadline]
Current result: [period, case count, value]
Measure owner: [person who can verify it]
Decision record
What changed in the work: [evidence from cases]
What else might explain the result: [volume, staffing, or case mix]
Decision and reason: [extend, adjust, or test longer]
Action owner and follow-up date: [name and date]
What to review at 30, 60, and 90 days
Day 30: Did the work change? Walk through one ordinary case and one exception with the people who handled them. Identify the last person who could say yes, how long the request waited, and what happened when that person was unavailable. If the old manager still approves every case, give the new lead explicit authority before judging the design. This is one way to spot silos that survive a reorganization.
Day 60: Are customers seeing a difference? Compare like cases across periods. Record how many arrived, how many finished, and whether the team received more complex work. Look at a few long-running cases as well as the median. A shorter queue after a quiet month calls for a different interpretation than a shorter queue under the usual workload.
Day 90: What should leadership keep or revise? Read the three measures together. Identify one decision the evidence supports, one uncertainty that matters, and who will resolve it by when. Adapt the cadence to the work: a quarterly procurement process may have completed only one cycle by day 90.
Worked example: faster onboarding, more reopened cases
In this illustrative team merger, the onboarding lead gained authority to approve routine cases. The pilot team compares 100 routine activations before the merger with 100 after it. Each case has had at least 14 days to reopen. The figures are hypothetical.
| Measure | Before | Target | Day 90 |
|---|---|---|---|
| Median onboarding time | 10 days | ≤7 days | 7 days |
| Median approval handoffs | 3 | 1 | 1 |
| Reopened within 14 days | 4% | ≤4% | 9% |
The team met its speed and handoff targets. It also reopened nine cases per hundred, up from four. That five-percentage-point increase tells the operations lead where to investigate. It does not establish that removing approvals caused five extra cases to reopen.
Decision at day 90: Keep the pilot running and hold expansion for one review cycle. Within two weeks, the operations lead will review all nine reopened cases with the activation team, compare their reasons with those from the baseline period, and check whether the mix of applicants changed. If missing verification explains a recurring error, test a check at activation and measure the next eligible cohort. If reopening mostly reflects address changes after activation, separate those from correctable processing errors and recalculate both periods using the same rule.
A review minute can be that specific: “We retained the lead’s approval authority. Expansion is pending a review of nine reopened cases. The operations lead will return with the case reasons and a recommendation on 14 June.” A named decision, owner, and date give the next meeting a starting point.
How do you evaluate a reorganization without a reliable baseline?
Try reconstructing a small comparison from dated applications, approval logs, or support tickets. Select consecutive eligible cases from a stated period. Record the inclusion rule, missing fields, and sample size. If the old system recorded application submission and the new one only records completion, identify a milestone both systems captured before comparing elapsed times.
When earlier records cannot support a fair comparison, mark the baseline as unavailable. Start a prospective series using a stable counting rule. You can still report whether the team meets today’s service target, trace who makes decisions, and identify recurring delays. A comparable team that has yet to reorganize can add context if it handles similar work under similar conditions.
At the next leadership review, bring one completed scorecard and one case that challenges the headline result. Ask the decision owner what they will change for the next customer. If the team still depends on the same approvals, incentives, or workarounds, revisit why organizational change fails before extending the design.