The most expensive failure mode in the Four S’s and the one that looks most like good management.
In the Four S framework, I made a claim that generated more replies than anything else in the piece: that the sequence – Signal, State, Structure, Support – matters as much as the questions themselves, and that running them out of order produces recognizable failure patterns. The one leaders wrote to me about most was the first: Structure before Signal. Several described their own organizations in the process of describing the pattern.
So this piece slows down on that single failure mode, because it deserves the attention. It is the most expensive of the four, the most contagious, and the hardest to catch – precisely because from the inside, and often from the board’s seat, it looks exactly like good management.
What Process Theater Is
Process theater is structure built in service of a question nobody pressure-tested. The operating rhythms are impeccable: the sprint cadence hums, the OKRs cascade, the dashboards refresh, the rituals run on time. Every container is well-designed. What’s missing is the audit underneath – whether the truth those containers were built to carry is still true, or was ever verified in the first place.
The result is an organization that is highly organized and poorly oriented. Motion is constant. Progress is ambiguous. And because the machinery is visibly excellent, questioning the direction starts to feel like questioning the competence of everyone running it, so nobody does.
I want to be precise here, because this is not an argument against process. Structure is the third S for a reason; I’ve spent much of my career building operating infrastructure and I’d build it again. The failure is not structure. The failure is structure deployed as a substitute for the harder, quieter work of finding the signal – process as an answer to a question no one finished asking.
Why Smart Organizations Do This
The uncomfortable part first: process theater is not a stupidity problem. It’s a regulation problem wearing a management costume.
Uncertainty is physiologically expensive. When a leadership team doesn’t actually know whether the strategy is right – when the signal is murky and admitting so feels dangerous – building structure is the most socially rewarded way to discharge that discomfort. A new operating cadence is doing something. It’s visible, presentable, and immune to the accusation of passivity. The body gets the relief of motion; the calendar gets the appearance of rigor; the unanswered question gets buried under a beautifully formatted quarterly planning doc.
This is the somatic mechanic underneath the pattern: structure can function as a collective soothing behavior. The rituals genuinely lower the room’s anxiety – that’s why they’re adopted so eagerly and defended so fiercely. But they lower it by managing the feeling of uncertainty rather than resolving the uncertainty itself. The organization becomes calm and lost at the same time.
AI has made this failure mode dramatically cheaper to enter and more expensive to stay in. When tooling can spin up dashboards, tickets, summaries, and cadences almost for free, the cost of building structure approaches zero, while the cost of building structure around the wrong signal compounds faster than ever, because the machinery executes so efficiently. Amplification, again: the tools scale whatever they’re pointed at, including a mistake.
The Tells
You can’t diagnose process theater from the org chart or the metrics. By design, both look healthy. You diagnose it from patterns. Here’s what I watch for in rooms:
Decisions have ceremonies but no owners. There is a meeting where the decision is discussed, a doc where it is recorded, and a review where it is revisited. And no single person whose body carries the yes. Everything is processed; nothing is decided.
Rituals survive their reasons. Ask why a recurring meeting exists and the honest answer is a history lesson, not a purpose. The container has outlived the truth it was built for, and nobody feels licensed to close it.
Planning consumes more energy than the plan produces. The quarterly process is a season, not an event. Teams emerge from it depleted, with artifacts everyone signed and few believe.
Disagreement gets routed into process instead of resolved. When two leaders see the signal differently, the organization responds by adding a workstream, a working group, or a framework – anything but the direct conversation. Structure becomes the place conflict goes to be stored, not settled.
The energy inverts. This is the somatic tell, and the most reliable one. Healthy structure releases energy – a good cadence means people spend less on coordination and more on the work. Theater absorbs it. If your best people leave planning cycles flatter than they entered, the structure is feeding on the organization rather than feeding it.
None of these tells is damning alone. Three together, and you’re almost certainly maintaining machinery around an unexamined premise.
The Reversal: Signal Audit Before Structural Investment
The fix is not to tear down the process – dramatic structure-burning is usually just theater in a different costume. The fix is to restore the sequence.
Before the next structural investment – the reorg, the new cadence, the tooling rollout – run the Signal question first, and run it honestly: If I strip away what I want to be true and what we’ve told the board is true, what remains? In practice, I ask leadership teams to do this in three moves:
Name the premise each major structure protects. Every standing meeting, cadence, and ritual was built to carry some truth. Write that truth down in one sentence, in the present tense. If the sentence is hard to write, you’ve found your first candidate.
Test the premise against the body, then the data. Read the sentence aloud in the room and notice what happens – the collective wince, the too-quick agreement, the glance exchange. The body registers a dead premise before the dashboard does. Then verify with whatever evidence would actually settle it.
Retire or recommit out loud. Structures whose premises hold get explicitly recommitted, which restores their authority. Structures whose premises have died get closed with a named ending, which returns their energy to the system. The worst outcome is the middle path: rituals kept alive on politeness.
Teams are consistently surprised by how much capacity this returns. Because pretending is heavy and process theater runs on a low-grade, organization-wide pretense that everyone is carrying and nobody is naming.
What Right-Order Structure Feels Like
When structure comes after signal, you can feel the difference in the room. The cadence is lighter, because it’s carrying something true and doesn’t need ceremony to justify itself. Meetings end early sometimes, because the container serves the work rather than the reverse. People defend the structure without being defensive about it – they can tell you, in one present-tense sentence, what it’s for.
That’s the quiet test I’d leave you with. Pick your most sacred process, the one it would feel almost rude to question. Ask what unarguable truth it exists to carry. If the answer comes clean and current, recommit to it with confidence. If the answer is a history lesson, you’ve just found the most valuable meeting on next week’s calendar.
Signal first. Then build. The order is the discipline.
This piece is part of an ongoing series on the Four S framework: Signal, State, Structure, Support. The framework anchors my keynote, “Coherence Across Complexity: Leading at the Pace of the Body in the Age of AI.” For engagements and speaking, contact us here →.
About the Author
