Skip to main content
Steady at the Top
← All articles

How to tell whether your reorganization solved anything

Evaluate a reorganization by comparing the original operating bottlenecks with the same work under the new structure. Check whether decisions move, handoffs improve, and employees can identify who owns the next action. Completion of the organization chart is a milestone, not evidence that the business problem improved.

A bottleneck comparison review is a working assessment of whether a structural change improved the specific constraint used to justify it. For the review, distinguish unavailable handoff facts from disagreement over their meaning, using Daft and Lengel’s (1986) account of organizational information processing as the research reference. The method is a practical diagnostic, not a standardized research scale.

Your review needs a before-and-after comparison, a credible account of other changes, and a willingness to revise the design. A profitable quarter may coincide with a poor structure. An improved structure may initially operate in a difficult market. Keep those explanations separate.

Use industrial/organizational psychology, the psychology of work and organizations, to inspect the reorganization through work performed. Ask who now makes the disputed decision and whether the original handoff obstruction has changed.

Recover the original case for change

Find the business case, meeting record, or announcement that described the problem. Extract the concrete claims. Perhaps customer exceptions waited for several functions, product launches lacked a decision owner, or regional teams duplicated work. Preserve the wording before interpreting the current result.

If the original rationale was vague, acknowledge that limitation. You can reconstruct an operating baseline from records, but do not pretend you specified it in advance. Distinguish what leadership promised from what the review now proposes to measure.

A reorganization changes reporting relationships and authority. An implementation review checks whether that design was put in place. An effectiveness review checks whether the design improved the intended work. Both matter, but they answer different questions.

Use How to lead executive exits and restructuring with care to situate the review within the broader restructuring process. If employment terms or duties require changes following the review, involve employment counsel and the appropriate people function. This article offers general management guidance, not legal advice.

The bottleneck comparison review method

1. Specify the constraint and its consequence

Write one sentence for each original bottleneck. “Account exceptions waited for approval because nobody could reconcile commercial and delivery priorities” is useful. “We needed better collaboration” leaves too much room to declare success without evidence.

Identify the practical consequence: delay, repeated rework, confused accountability, customer disruption, or avoidable escalation. Use the actual work rather than a generic score. A measure matters when it reflects the problem the change was meant to address.

Define the relevant population. Are you reviewing all customer exceptions, only larger requests, or one region? Use the same boundary for the before-and-after comparison where possible. Otherwise, an apparent improvement may reflect a different mix of work.

Choose a review period suited to the operating cycle. A quarterly decision cannot be evaluated after a week. Avoid selecting a convenient date solely because leadership wants to announce completion. State which events the review must observe before reaching a conclusion.

2. Reconstruct a defensible baseline

Use existing workflow records, decision logs, and delivery evidence. Compare similar cases when possible. A single memorable disaster is a poor baseline for every subsequent routine event. Record missing data rather than filling the gap with confident estimates.

Measure elapsed time and the reason for waiting separately. Faster decisions may reflect a simpler workload, while unchanged total time may conceal improvement in the internal handoff. The trace should let you identify where the time moved.

Include role clarity as an observable question. Ask people who would own a specific decision and compare their answers. Agreement on a survey item is less useful if the same colleagues name different owners when faced with a real exception.

Avoid overclaiming precision. A small set of reconstructed cases can still reveal a recurring problem. Explain the limits of the comparison and use the result to guide the next test rather than treating it as proof of universal improvement.

3. Observe the new process in use

Follow current cases through the redesigned arrangement. Check who makes the decision, who contributes evidence, and where exceptions go. Compare the observed process with the intended design. Workarounds can make a weak design appear functional while exhausting a few people.

Ask whether the CEO still resolves routine disputes the new structure was supposed to handle. If your intervention remains essential, identify the unresolved boundary. A reporting line has not transferred authority when everyone still waits for your personal view.

Look for displaced costs. A faster commercial approval may create more delivery rework. A centralized team may reduce duplication while making local customer response harder. Evaluate the whole consequence relevant to the original decision.

Use Morrison’s 2014 review to examine the review channel: can people describe continuing workarounds without being expected to endorse the reorganization? Give people a protected way to report workarounds and contradictions. Do not require a positive review from those who must operate the design.

4. Separate the design from simultaneous changes

List other changes that could explain the result: staffing, demand, software, customer mix, leadership, or the scope of work. A before-and-after comparison alone cannot isolate the contribution of the new structure. State the competing explanations.

Ask what evidence would distinguish them. If both reorganized and unchanged units improved after a demand reduction, lower demand may account for part of the result. If a newly assigned decision owner resolves a recurring dispute, the authority change has a clearer connection.

Avoid statistical language the evidence cannot support. You can say the observed handoff improved in the reviewed cases. You should not claim the reorganization caused all improvement unless your design and evidence justify that conclusion.

Use How to review decision quality without creating more bureaucracy to review the decision process itself. A sound evaluation can conclude that the original choice was reasonable under uncertainty while the current design needs adjustment. That conclusion is more useful than rewriting history around the latest outcome.

5. Decide what to retain, repair, or reverse

Retain elements supported by operating evidence. Repair specific gaps where the principle works but the boundary remains unclear. Consider reversal when the design creates costs that outweigh its demonstrated benefit. Avoid treating any revision as an admission that leadership cannot decide.

For each change, name an owner, the expected effect, and the next observation point. Keep the response proportionate. One broken handoff may need a clarified decision rule rather than another company-wide restructuring.

Tell employees what the review found. Include the useful changes, remaining problems, and action owners. Do not publish an abstract success score while leaving the people doing the work unable to see how their feedback affected the decision.

Consult Kramer’s 1999 review when reviewing the credibility of management’s follow-through after people report that the new structure still obstructs their work. In this review, credibility comes from admitting the gaps you will repair and returning with evidence that the repair occurred.

A hypothetical result that needs a qualified verdict

A company reorganizes customer delivery around account teams. The stated problem was slow resolution of cross-functional exceptions. After implementation, exceptions reach a decision faster, but delivery managers spend more time correcting promises made without capacity review.

A presentation calling the reorganization successful would omit the displaced cost. A presentation calling it a failure would overlook the improved decision path. The review identifies both and changes the approval boundary for commitments that affect delivery capacity.

The company keeps the account-team structure and tests the revised boundary on the next set of relevant cases. It records what remains uncertain. This is a hypothetical example of a qualified verdict, not evidence that account teams suit every business.

The private-life composite

A founder returns from a weekend away and spends the first evening resolving disputes between leaders who now report through the new structure. Their partner asks whether the reorganization was meant to reduce those calls. The founder realizes the announced completion date became the only success measure.

This composite shows how the private cost of an operating gap can become normal. The review should count the recurring rescue work and identify why the new design still requires it. Your personal availability should not hide an unresolved decision boundary.

If the pressure of implementing and reviewing the reorganization leaves symptoms that persist or disrupt daily life, consult a licensed clinician instead of interpreting them through the organization chart. The operating review should address authority and workflow while qualified professionals address individual clinical concerns.

Keep personnel narratives out of the verdict

Do not explain every problem through the executive who left. Check How to let a departing executive say goodbye with dignity when the organization needs to mark a departure respectfully. A farewell and an effectiveness review serve different purposes. Neither should become a vehicle for unsupported claims about the former leader.

Use How to decide when it is time to let an executive go if unresolved leadership performance remains part of the diagnosis. The review can show that clearer structure did not fix a behavior. Address that behavior through the appropriate process rather than launching another redesign to avoid the conversation.

Before closing the review, ask a frontline employee to describe one practical difference. The answer should concern work: a known owner, a shorter handoff, a usable exception route. If the only change they can name is a new reporting line, inspect the operating result again.

Keep the baseline and current trace together. Future leaders should be able to see why the structure changed, what improved, and what remained unresolved. That record prevents the next redesign from beginning with the same untested claims.

A useful verdict is specific enough to act on: this bottleneck improved in these cases, this cost moved elsewhere, and this owner will make the next correction. The reorganization earns its place by improving work that matters.

Check whether the workaround disappeared

Ask who still bridges the old boundary informally. If one respected employee continues translating between functions after hours, the structure may rely on the same hidden arrangement. Record the work that person performs and decide whether it needs formal ownership. Improvement should remain credible when that person takes leave.

Sources

Steady at the Top