The Check Valve

How Organizational Architecture Quietly Destroys Strategic Optionality

On June 4, 1942, at 10:22 am near Midway, American dive bombers fell upon three Japanese aircraft carriers while they were in the middle of rearming. The Japanese planes had originally been armed for one mission when scouts reported a different target, and the order had come to switch. With fueled aircraft and heavy ordnance caught in the rearming cycle, it took only six minutes for Akagi, Kaga, and Sōryū to be turned into blazing infernos. The carriers were destroyed because the plan suddenly required a level of rapid reconfiguration the system could no longer deliver.

That’s the fast version of the problem. A strategy is only as good as the system’s ability to reverse direction.

There is also a slower version.

I once worked inside an innovation group organized as a portfolio of loosely related, technically demanding projects. Each project was a small big bet and required deep specialists. Deep specialists create enormous value inside one domain, but become very hard to redeploy elsewhere. Their narrow expertise was essential for the portfolio architecture. Once that structure was chosen, the subsequent hiring decisions were largely locked in.

The effects were twofold. First, the specialists had little incentive to reveal unflattering information about their own projects, so critical data for portfolio decisions was lost. That’s the polite version of Upton Sinclair’s observation that it is difficult to get a man to understand something when his salary depends upon his not understanding it. Second, when a project lost its viability, ending it meant firing capable people who had performed loyally and admirably. That hurdle was too high, so even projects that should have been shut down retained resources. The portfolio could no longer be trimmed and slowly became cluttered with zombified projects: still moving, still consuming brain capacity, and still somehow lurking in the background of every review meeting. The final bill was predictable, painful, and arrived much later: the entire department eventually had to be restructured.

This is what I call a check valve. It permits flow in one direction and blocks it in the other. Resources flowed into each project, and the structure prevented them from flowing back out. When the structure was chosen, the flow direction was fixed.

The real tragedy was that no one made bad decisions. The department hired exceptional talent and executed with real competence. The loss of strategic freedom was created by a structure that could only be operated by accumulating people the organization could never afford to let go, and by accumulating an information deficit the organization could never afford to bring to light. The architecture ensured that every subsequent good hiring and project decision became a permanent reduction in optionality.

Strategic freedom is lost long before the zombie apocalypse becomes visible. Not in the crisis, the failed project, the staffing decision, or even the plan. Strategy fails in the architecture.

Boardroom / Team Drill

Pick one major initiative and ask: if we had to shut this down, shrink it, or redirect it six months from now, what would make that decision practically or morally impossible? That answer is the check valve.

Personal Drill

Pick one commitment in your own work and ask: what am I continuing, not because it is still right, but because stopping it has become too expensive, awkward, or embarrassing?