The company cannot pause while it changes
The new structure looks convincing. Leadership agrees that the current model will not support the next stage.
Now the company must implement it while continuing to close customers, ship products, support the team and manage runway.
This is where transformations become difficult.
A reorganization, systems migration, post-acquisition integration or operating-model redesign is not a side project. It changes who makes decisions, how work moves, which systems people trust and what leaders are accountable for.
If nobody owns the complete change, the transformation becomes additional work layered on top of the old company. People attend new meetings while following old processes. The project appears active, but the operating reality barely changes.
Start with the business result
“Complete the reorganization” is an activity.
The result may be:
- Reduce the time required to make customer-impacting decisions.
- Integrate two companies without losing customers or key employees.
- Improve margin by removing duplicated work and systems.
- Create an operating model that can support the next revenue stage.
- Move to a new system without interrupting finance or customer delivery.
- Clarify accountability after a funding round or leadership change.
McKinsey’s research on operating-model redesign argues that leaders should begin with the value the redesign must create, not boxes and reporting lines.
Define:
- What must become measurably better?
- Why must it change now?
- What cannot be disrupted?
- Which behaviors and decisions must change?
- What will the company stop doing?
- What must be true when the mandate ends?
The result becomes the standard for every structural decision.
Diagnose the current operating reality
Do not design the future company from the org chart alone.
Map how the work actually happens:
- Where do strategic initiatives begin?
- Where do they wait?
- Which decisions return to senior leadership?
- Which teams depend on one another?
- Where is information duplicated or lost?
- Which unofficial leaders make the system work?
- Which customers or operations carry the highest transition risk?
- Which old processes persist because they solve a real need?
A transformation built on the formal model can accidentally remove the informal mechanisms keeping the company functional.
Give the change one accountable owner
A steering committee can provide input and governance. It cannot own day-to-day execution.
One senior operator should own:
- The transformation plan
- Dependencies and sequencing
- Decisions and escalation
- Leadership alignment
- Communication
- Operational continuity
- Measures and risk
- Capability transfer
The owner needs authority across the functions affected by the change. Otherwise they become a project reporter who documents problems without resolving them.
Sequence the change around risk
Not every change should happen at once.
Separate the program into:
- Decisions: What must leadership decide before work begins?
- Foundations: Which ownership, data or system conditions must exist first?
- Transitions: Which teams, workflows or customers move when?
- Stabilization: How will the company detect and repair failure?
- Transfer: Who owns the new model after the transformation?
Prioritize changes that unlock other work. Protect customer delivery, payroll, financial reporting, security and contractual commitments.
A systems migration may require data governance and process decisions before configuration. A reorganization may require decision rights before reporting lines change. An acquisition integration may need customer and employee communication before tools are consolidated.
Design the work—not only the structure
McKinsey’s updated operating-model research emphasizes that redesign should address how work gets done, decision rights, cross-functional processes and technology—not only the org chart.
For every major workflow, define:
- The outcome
- The owner
- The teams involved
- The decisions required
- The system of record
- The handoffs
- The escalation path
- The measures
- The new behavior expected
People need to understand how Monday morning will be different, not only where their role appears in a presentation.
Build leadership alignment through decisions
Leadership alignment is not general agreement that the transformation is important.
It means leaders agree on the choices the new model requires:
- Which priorities receive resources
- Which authority moves
- Which work stops
- Which roles change
- Which performance measures matter
- Which trade-offs are acceptable
- How leaders will behave when the new model creates friction
Unresolved disagreements surface later as inconsistent instructions to the team.
Involve the people who must operate the change
Transformation cannot be delegated entirely to communications or consultants.
The people closest to the work understand dependencies leadership may not see. Involving them helps the company:
- Identify operational risk
- Test the proposed workflow
- Preserve useful local knowledge
- Improve adoption
- Build internal owners
- Detect where the design will fail in practice
Participation does not mean every decision is made by consensus. The mandate owner remains accountable.
Measure adoption and operating performance
A completed rollout does not prove the company transformed.
Track whether:
- Decisions move faster
- Owners act with the intended authority
- Cross-functional work hits milestones
- Teams use the agreed systems
- Duplicate processes disappear
- Customer delivery remains stable
- The expected financial or strategic benefit appears
- Old workarounds return
The measures should connect the change to the business result defined at the beginning.
Common failure patterns
The transformation is added to everyone’s existing job
The work loses to immediate operating demands. Give the mandate dedicated senior ownership and explicit resources.
Leadership changes the design outside the process
The organization receives conflicting signals and waits for the next reversal.
Communication replaces implementation
Town halls and documents explain the change but do not alter decisions, workflows or systems.
Software leads the transformation
A new platform encodes unresolved ownership and process problems.
The company declares victory at launch
The hardest stage begins when people must operate the new model under pressure.
When a fractional Transformation Lead fits
A fractional or interim Transformation Lead may fit when:
- The change is consequential but time-bound.
- The company needs experience it does not require permanently.
- The work crosses several leaders and functions.
- The CEO cannot personally manage the complete program.
- A neutral operator must resolve trade-offs.
- The internal team needs to learn and inherit the model.
A Fractional COO may be more appropriate when the transformation is inseparable from broader company operations. A Business Systems Lead may fit when the primary mandate is a systems migration with defined organizational implications.
What a useful mandate sounds like
“Lead the reorg” is too narrow.
A stronger mandate is:
Redesign and implement the operating model required for the company’s next stage, preserving customer delivery while clarifying decision rights, cross-functional workflows, leadership accountability and the systems that support them.
The mandate should define the business result, authority, affected teams, sequence, risk, resources and transition owner.
What the company should retain
- A working operating model
- Clear decision rights and ownership
- Documented workflows and systems
- Leaders aligned around the new model
- Measures tied to the intended value
- Internal owners capable of sustaining it
- A record of decisions and lessons
- Less dependence on external support
The transformation succeeds when the new company works—not when the project ends.