The operating model is the strategy
Why organizational structure, decision rights and cross-functional coordination increasingly determine whether strategic priorities translate into performance.
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
Why organizational structure, decision rights and cross-functional coordination increasingly determine whether strategic priorities translate into performance.
Read articleHow readiness, stakeholder alignment and behavioral change determine whether new operating models are adopted or quietly resisted.
Read articleFocus
True readiness depends on leadership attention, operating capacity, role clarity and the ability to absorb disruption.
A functioning system links strategic priorities with measurable outcomes, management routines and clear ownership.
Strategic challenges
The challenge is turning collective intent into consistent choices when trade-offs affect leaders differently.
The challenge is separating declared enthusiasm from the real constraints that determine whether mobilization can hold.
POV
Unless roles, interfaces and decision rights change with structure, most reorganizations relocate old problems.
Performance systems need selectivity: measures should sharpen accountability, not replace judgment with dashboards.
Strategic impact
Explicit interfaces and shared priorities reduce handoff failures, duplication and unresolved trade-offs.
Shared understanding of choices and trade-offs reduces friction between sponsorship, execution and daily adoption.
What we observe
Centralization can move work while preserving slow approvals, unclear service expectations and weak responsiveness.
Formal matrices fail when committees, hierarchy and informal vetoes continue to override delegated authority.