Why transformation stalls after the strategy is approved
How readiness, stakeholder alignment and behavioral change determine whether new operating models are adopted or quietly resisted.
Read articleCross-functional coordination breaks down where shared outcomes meet fragmented authority
Cross-functional work rarely fails because specialists cannot cooperate. It fails when an outcome is shared but authority, budgets and performance measures remain divided. Each function can make a defensible local decision while the end-to-end result deteriorates. More meetings then add information without resolving who may trade one priority against another.
Start with the outcome and its dependency chain. Map the hand-offs, decisions and resources that determine customer value, speed or risk. For each, distinguish input from consent, decision rights from execution and escalation from routine coordination. If two leaders can veto but neither can decide, the design has created negotiation as an operating process.
Make interdependence visible through shared measures. Functional cost and service targets still matter, but they should sit beside cycle time, first-time quality, customer outcome and total economic impact. Track queues and rework at boundaries, not only activity inside teams. Shared data turns friction into a constraint that an accountable owner can address.
Govern only the conflicts that require joint judgment. Establish a small forum with named decision owners, explicit tolerances and pre-agreed rules for capacity, risk and priority trade-offs. Push reversible decisions close to the work; escalate only choices whose impact crosses boundaries. The 2026 Orange Book similarly links clear roles with appropriate delegation, aggregation and escalation.
Finally, align consequences. Resource allocation, objectives and recognition must reflect the enterprise outcome, or collaboration remains voluntary when pressure rises. Review recurring exceptions as evidence that authority or process is wrong, then redesign the interface. Coordination becomes reliable when people can resolve dependencies through the operating system�not through personal influence or heroic intervention.
Related macro
Articles
How readiness, stakeholder alignment and behavioral change determine whether new operating models are adopted or quietly resisted.
Read articleHow companies can balance enterprise integration with regional autonomy through clearer governance, roles and leadership systems.
Read articleFocus
Adoption depends on how interests, incentives and operating realities are reconciled across affected groups.
Behavior is shaped less by stated values than by the routines, incentives and informal norms people experience daily.
Strategic challenges
The challenge is redesigning work without treating structure as a substitute for end-to-end operating choices.
The challenge is separating necessary differentiation from structural burden that no longer serves strategy or control.
POV
Preserving familiar boundaries often institutionalizes duplication, delay and weak accountability across the enterprise.
Treating resistance as a people problem often conceals unclear trade-offs, weak sponsorship and weak accountability.
Strategic impact
Clear visibility on capacity, dependencies and local conditions enables mobilization to follow operational reality.
Evidence across performance, work and behavior separates systemic issues from local symptoms and isolated complaints.
What we observe
Meetings can be full while ownership, evidence standards, escalation logic and decision follow-through remain undefined.
Centralization can move work while preserving slow approvals, unclear service expectations and weak responsiveness.