Cooperation Before Consolidation
Coordinate distinct institutions without forcing them into one hierarchy
- Difficulty
- Advanced
- Time to result
- ~ongoing to results
- Steps
- 6
- Confidence
- 97%
Cooperation Before Consolidation treats fragmented execution as a coordination problem rather than automatically solving it with a merger or an additional executive layer. Carter argues that defense, intelligence, diplomacy, law enforcement, and disaster response have distinct missions that cannot simply be pushed into one hierarchy. The practical model is a tiered council system: working-level participants resolve routine matters, senior leaders address harder conflicts, and only issues requiring unique authority reach the president or chief executive. Each escalation should arrive in decision-ready form. This preserves specialist institutions while creating a reliable mechanism for common action. The framework applies to governments, companies, alliances, and multi-partner programs where no participant can command all the others.
Origin
Extracted from Masters in Business through Ash Carter's critique of bureaucratic consolidation and his description of the National Security Council coordination model.
Core principles
- 01Preserve genuinely different institutional capabilities
- 02Treat coordination as a management problem
- 03Resolve issues at the lowest competent level
- 04Escalate only decisions requiring higher authority
- 05Do not confuse a tidy org chart with effective collaboration
How to run it
- 1
Map the institutional system
Identify every organization needed for the shared mission, its legal or practical mandate, and the authority it controls.
Pro tip Include informal influence and external stakeholders as well as formal reporting lines.
Watch out Leaving a critical institution outside the process will recreate fragmentation.
- 2
Protect necessary distinctions
Determine which capabilities, cultures, and responsibilities should remain separate because they serve genuinely different purposes.
Pro tip Ask whether combining functions would weaken expertise or accountability.
Watch out Structural simplicity is not automatically operational effectiveness.
- 3
Build coordination layers
Create recurring forums at working, senior, and executive levels so problems can be resolved by people with the appropriate knowledge and authority.
Pro tip Use a stable cadence and consistent membership.
Watch out Ad hoc meetings encourage delayed escalation and repeated debate.
- 4
Assign decision rights
Specify what each forum may decide, what requires consensus, and what must be escalated.
Pro tip Document decision rights before a crisis exposes ambiguity.
Watch out Coordination fails when participants believe another institution cannot legitimately influence them.
- 5
Resolve issues low in the system
Have junior and senior groups settle all matters within their authority before involving the final executive.
Pro tip Escalate a concise record of agreements as well as disagreements.
Watch out Sending every dispute upward will overload the only person who can arbitrate.
- 6
Prepare executive decisions
Convert unresolved conflicts into clear options, trade-offs, and recommendations for the authority who can direct all participants.
Pro tip Frame the exact decision required instead of presenting an open-ended briefing.
Watch out Do not consume executive time on issues the coordinating groups have not seriously attempted to solve.
In the wild
A company faces cyber incidents involving security, legal, communications, operations, and customer support. Rather than merging the teams, it creates an operating group for routine incidents, a senior council for major trade-offs, and a narrow escalation path to the CEO for decisions only the CEO can impose across functions.
→ Specialist teams retain their expertise while incidents receive coordinated and timely decisions.
Carter describes junior-level and cabinet-level meetings that work through foreign-policy issues before using presidential time. Only disputes that participants cannot resolve because they lack authority over one another are elevated to the president.
→ Distinct agencies can collaborate without being placed inside a single consolidated department.
Common mistakes
Adding another layer on top
Creating a new office without changing how institutions cooperate can add bureaucracy while leaving the original coordination failure intact.
Escalating everything
If working groups do not resolve routine matters, the final executive becomes a bottleneck.
Forcing incompatible functions together
A merger can weaken specialist missions when the real need is a dependable way for those missions to interact.
Is it for you?
Best for
It is best for cross-agency, cross-functional, or partnership work where participants must collaborate but should not be placed inside one organization.
Not ideal for
It is not ideal when duplicated units perform the same function and a straightforward consolidation would remove genuine redundancy.
From the transcript
“The managerial question is cooperation, not consolidation.”
“how do I get different things that I cannot mush together?”
“The National Security councils be basically intended to put decisions in management form that are ready for the President to make a decision”
From the episode
Ash Carter Discusses the Business of Defense
Ash Carter