The Pattern Beneath the Problem

 

Recurring organisational problems are usually different expressions of one underlying pattern - and pattern recognition collapses an apparent problem list into a single mechanism.


A founder describes the problem this way:

"My COO has been here two years. She's capable. But she keeps escalating things she should be able to decide. I find myself making the same call she should have made - usually a week later than I wanted. My head of product does the same thing. Different style, same outcome. And the leadership meetings have started to drift. We agree on things and then nothing quite happens for ten days. I'm spending too much time pulling the team through their own decisions."

Five complaints. Read as separate problems, the response list is long:

— coach the COO on decision-making

— review the head of product's mandate

— redesign the leadership meeting structure

— introduce clearer decision rights

— consider whether the team has the right people

All plausible. None of them likely to work.

Because under the five complaints sits one mechanism.

The founder is describing two senior leaders who escalate things they could own. A leadership meeting where decisions soften after the room. And a recurring sense that the founder is closing loops other people opened.

Each is a different surface symptom. They share a structural source.

The COO is not under-deciding because she lacks capability. She is reading the structure. She has noticed - accurately - that decisions she makes alone tend to come back. The head of product has noticed the same thing in a different register. The meeting drift after agreement is the same signal at the team level.

What the senior layer is reading is this: real ownership has not yet moved.

The founder is still the place where weight finally settles. The leaders below can feel it. So they shape their behaviour around it.

That is why coaching the COO will not work. There is nothing wrong with the COO's decision-making. The pattern that is slowing her down is sitting one level up.

The pattern is the founder's. The team is mirroring it.

This is what changes the level of the diagnosis.

Five conversations become one. Five interventions become one. The work is no longer about distributed accountability, meeting design, decision frameworks, or hiring profile.

It is about the operational pattern that is teaching the entire senior layer to wait.

Once that pattern is named and starts losing organising power, the COO does not need new coaching. She starts deciding. The head of product does not need a new mandate. He starts owning. The leadership meetings do not need a redesign. Things start happening after agreement, rather than ten days later.

Not because the team changed.

Because the structure stopped broadcasting the same instruction.

The founder did not have five problems. He had one pattern producing five surface readings of the same thing.

That is what pattern recognition does. It collapses an apparent problem list into a single mechanism. And once the mechanism is visible, the intervention becomes precise rather than scattered.

Most recurring organisational problems are not separate.

They are different expressions of the same underlying pattern.

← Back to Insights

Next
Next

Dependency Architecture