2.8 Recognize the impedance mismatch
Book 3 · The Orchestrated OrganizationChapter 2 · section 8 of 10
An organization is not ready when its people are using new tools. It is ready when its surrounding processes can support the system’s speed and authority. Watch for these warning signs:
- Security reviews happen only at the end of a project.
- Operations learns about a new agent from an incident.
- Finance cannot reconcile automated decisions or runtime costs.
- Audit cannot reconstruct which instructions, memory, skills, data, or permissions shaped a decision.
- Customer service is the first place a system’s failure becomes visible.
- A system changes its behavior, but the organization cannot identify what changed.
Every one of those signs means the technical system and the organization are running at different speeds, or working from different assumptions about authority. The response is not always to automate more, either; sometimes the system needs less authority, better tests, more review capacity, or a clearer owner.
Contents
- 2.1 Block: hierarchy vs. intelligence
- 2.2 JPMorgan Chase: connectivity as the moat
- 2.3 Titles: what the market is doing right now
- 2.4 Start with an honest assessment
- 2.5 Help developers become orchestrators
- 2.6 Start new projects differently
- 2.7 Design the team: composition, size, and specialists
- 2.8 Recognize the impedance mismatch
- 2.9 Plan the transition in ninety days
- 2.10 The human cost is part of the plan