The Reorg That Doesn't Stick: Why Structural Changes Fail to Change How Work Actually Moves

Reorganizations are among the most resource-intensive interventions available to senior leaders. They consume months of planning attention, generate genuine organizational anxiety, and carry real costs in productivity lost during the transition period. Yet a pattern repeats with enough consistency to warrant serious examination: the org chart changes, the boxes and lines are redrawn, announcements go out, and then, within six to twelve months, leadership observes that the same friction points exist in roughly the same places. Decisions still stall. Cross-functional work still accumulates delays. The same conversations about ownership and priority happen in new meeting rooms with slightly different attendees.

The explanation is rarely that the structural logic was wrong. More often, the redesign addressed the layer that is visible on a slide deck while leaving untouched the layer where work actually lives.

What a Reporting Line Does and Does Not Do

A reporting relationship establishes authority, accountability chain, and career context. It answers the question of who is responsible to whom. What it does not answer is how work moves between people, how decisions get made when two functions touch the same problem, or how information travels from the point of origination to the point where it is needed.

Those questions are answered by workflows, not org charts. Workflows describe the actual sequence of steps, handoffs, approvals, and communications that produce an outcome. In most organizations, workflows are not formally documented. They are instead embedded in individual habit, team convention, and institutional memory. When the org chart changes, those embedded patterns do not automatically update. People continue routing requests to the person they previously routed them to. They continue escalating through the hierarchy they previously knew. The new structure sits on top of the old operating logic, and the old operating logic wins, because it is specific and practiced while the new structure is abstract and unfamiliar.

Why This Gap Is Consistently Underestimated

Reorganization planning typically concentrates on the design rationale: why the new structure better aligns with strategy, which spans of control are appropriate, how role definitions will shift. These are legitimate and necessary questions. The gap appears at the implementation stage, where the assumption is often that the new structure will generate its own operating patterns through normal use.

That assumption treats organizations as self-correcting systems, which they are, but only slowly and imprecisely. Self-correction in organizations happens through repeated trial and error, informal negotiation, and gradual norm formation. That process takes time, generates confusion costs during the interval, and frequently lands on operating patterns that are functional but suboptimal because they were shaped by whoever was most assertive in filling the ambiguity rather than by deliberate design.

Directors who have led or inherited reorganizations will recognize the symptom: a period of genuine disruption, followed by stabilization that looks like success, followed by the realization that the new structure has produced its own informal workarounds that serve the same structural gaps the reorganization was intended to close.

The Design Work That Precedes Structure

A more durable approach treats workflow redesign as a prerequisite to structural change, not a consequence of it. Before finalizing a new org chart, it is worth mapping the ten to fifteen workflows that account for the majority of cross-functional coordination friction in the current structure. These are typically not hard to identify. They are the workflows that generate the most escalations, the most complaints about clarity, and the most visible delays.

For each of those workflows, the relevant questions are: Who initiates the work? Who contributes at each stage? Where do handoffs occur, and what information travels with them? Where do approvals happen, and are those approval points designed around decision type or organizational hierarchy? Where does the workflow currently break down, and why?

Answering those questions before designing the new structure allows the structure to be shaped partly around the workflows it needs to support, rather than requiring the workflows to adapt to a structure that was designed without them in mind. In practice, this often reveals that some reporting changes under consideration would solve one workflow problem while creating a different one, and that insight is far less costly to act on during planning than after implementation.

Making the Workflow Layer Explicit After Structure Changes

For leaders who are managing the aftermath of a reorganization that is already in place, the intervention point is the same even if the sequence is reversed. The most productive question is not whether the structure was designed correctly, but whether the workflows beneath the new structure have been explicitly defined or left to emerge informally.

A practical diagnostic is to identify the five workflows that are generating the most post-reorg friction and trace them step by step as they currently operate, not as they were intended to operate. The gap between the two is usually informative. It often reveals that people are routing work through pre-reorganization relationships because the new structure did not specify how the corresponding handoffs should work. It may reveal that approval steps were not reassigned when authority shifted, so work is traveling to people who no longer hold the relevant authority and then being redirected, adding delay at every cycle.

Once those gaps are identified, defining them explicitly, even in simple documentation, significantly accelerates the stabilization that would otherwise happen through months of informal negotiation. The documentation does not need to be comprehensive or formal. It needs to be specific enough that a person new to the workflow can follow it without needing to ask which of two plausible paths is correct.

The Broader Principle for Structural Interventions

The pattern generalizes beyond reorganizations. Any structural intervention, whether it is a new governance body, a revised decision authority matrix, or a reconstituted leadership team, operates at the level of formal design. The formal design creates conditions and incentives, but it does not move work. Work moves through the specific, habitual, informal channels that people have established over time.

Directors who understand this distinction approach structural change as a two-part problem. The first part is designing the structure. The second part, which is at least as consequential and substantially less glamorous, is designing the operating layer that will make the structure functional in practice.

Organizations that invest disproportionately in the first part and treat the second as self-generating tend to find themselves redesigning the structure again in eighteen months, frustrated that good thinking on paper did not produce the results the thinking predicted. The structure was not the problem. The operating layer beneath it was never built.