THE CENTRAL IDEA
Enterprise coordination connects interdependent work while preserving appropriate local decision authority.
Why a senior team is more than a meeting
The upper echelons literature directs attention to the people through whom strategic choices are interpreted and enacted. For our proposed coordination dimension, that starting point raises a practical question: when responsibilities span several functions, how does a choice become a coherent set of commitments? The question concerns observable coordination work rather than an assumption that a group becomes integrated simply because its members share senior titles.
Coordination should be distinguished from centralization. An executive can clarify dependencies and then leave a team free to act within them. Another executive can attend every meeting without resolving ownership or contradictory instructions. A self-report needs examples that discriminate between these possibilities. The number of cross-functional meetings is therefore an inadequate substitute for understanding what happened at the boundary between two pieces of work.
A launch with incompatible promises
Imagine a product launch in which marketing promises a date, engineering plans a limited release, support expects a full customer rollout, and finance has assumed immediate revenue. Each plan may look coherent inside its own function. The enterprise problem is the mismatch between them. A coordination conversation should identify the shared commitment, the assumptions attached to it, and the person authorized to resolve the conflict.
A practical map has four columns: decision, dependency, information, and owner. The map is useful only if it changes a handoff or a decision. In the fictional launch, it might reveal that a limited release needs a different communication plan and a revised revenue assumption. The exercise should finish with a specific update, not with an aspiration that everyone will communicate better. Review whether the affected teams understand the update in compatible terms.
Study the boundary, not the executive aura
The proposed index describes how often a participant endorses coordination practices. It should not become a general score for enterprise leadership. A role with fewer dependencies may produce fewer opportunities to demonstrate the practice. Likewise, a heavily centralized organization may require coordination behaviors that are unnecessary elsewhere. Reports should invite the participant to identify the dependency structure and the decisions they could actually influence during the reference period.
An empirical study could follow selected cross-functional commitments over time, recording unresolved dependencies before and after coordination episodes. Researchers would need to distinguish genuine resolution from shifting the problem to another team. Accounts from several affected functions could reveal whether one participant’s impression of clarity is shared. The study should treat disagreement as information about the system and the measurement, rather than assuming the most senior participant supplies the definitive account.
Points to carry forward
- Make shared dependencies and decision ownership explicit.
- Reserve joint discussion for issues that require joint action.
Where the evidence stops
A self-report cannot establish the quality of coordination across an entire organization.
The cited literature informs our original framework. Read the current evidence status and intended use alongside this guide.
REFERENCES / FOLLOW THE ORIGINAL EVIDENCE