Patterns
Pressure reveals patterns.
Not what organisations say about themselves.
What they actually do under load.
Communication rises as reliability falls
When systems begin to slip, organisations rarely fix the reliability problem first. They increase communication.
More meetings. More updates. More alignment work. The communication load expands precisely because the system no longer reliably carries intent.
The question is never "are we communicating enough?" It is "what is communication compensating for?"
Get that wrong and you will spend the year in meetings about meetings.
Decisions degrade under load
A decision can leave the room perfectly clear. Everyone understands the direction. The priorities are agreed.
Weeks later, different versions are running. Not because people disagreed. Because the structure that was supposed to hold the decision begins to strain under load.
When load doubles and the deadline halves, the described version doesn't run. Something else does.
The signal isn't in how decisions are explained. It's in whether the organisation can still hold them when pressure enters.
Effort fills the gaps the architecture can't hold
Every organisation has playbooks. Workflows. Process documentation. People have been trained. Systems have been built.
But when load spikes, work stops flowing through the system and starts flowing through individuals.
The same loop keeps running. More process won't fix a structural gap. What compounds is what holds under load.
Everything else resets.
Boundaries dissolve under pressure
The boundary was clear when it was drawn. Everyone understood the scope. The ownership was agreed. The edges were defined.
Three weeks later, the edges have moved. Not because anyone decided to move them. Because systems don't hold boundaries under load. They absorb them.
More gets added. Scope expands. The person who owned it is now coordinating six conversations they weren't supposed to be in.
Nobody chose this. The architecture allowed it.
That's where boundaries stop holding.
Teams experience different organisations
Ask each person in a leadership team separately: what operating environment is your team in? Five people. Four different answers.
They aren't disagreeing about strategy. They aren't even experiencing the same organisation.
Under pressure, that doesn't surface as debate. It surfaces as drift. People make decisions from different starting points. Work duplicates. Priorities collide.
No amount of communication fixes a team operating in four different rooms.
Organisations run on defaults, not decisions
Most organisations believe they run on decisions. They don't.
When pressure increases, decisions fade. The system falls back to whatever behaviour it has learned will keep work moving. Who absorbs the problem. Which priority quietly wins. What gets bypassed when the deadline compresses.
Strategy describes how the organisation intends to behave.
Defaults reveal how it actually will.