The structure beneath the symptoms
Most delivery problems have already been diagnosed. Usually more than once, by people who were not wrong.
I have posted pieces of this thinking here before, in bits. I finally sat down and wrote the whole argument out properly.
Here is the short version.
When delivery is slow or unpredictable, someone runs a review. It says the teams need clearer priorities, or more ownership, or a tighter process. You bring in the framework, run the workshops, restructure the squads. For a quarter it feels different. Then it settles back exactly where it was.
The usual explanation is that the change did not go deep enough, or people did not commit. So the next intervention is bigger. And it fails the same way.
The real reason is simpler. The diagnosis described a symptom, and the fix treated it as the cause.
Delivery behaviour shows up at the team level, so that is where we look for the cause. But the cause usually sits a level or two above it, in how authority, priority, visibility, constraints and load are arranged. A team that escalates everything and waits is not passive. It is behaving rationally inside a structure that taught it deciding is more dangerous than waiting. No ownership course survives contact with that structure.
This is also why engagement surveys cannot find it. They measure how people feel about their conditions. A feeling tells you something is wrong. It cannot tell you what, and it cannot separate two situations that feel identical for opposite reasons.
In the paper I show two areas of the same company. Same leadership, same culture, diagnosed in the same week. One was healthy. The other was in a four-pattern collapse. The difference was not the people. It was how each area was built.
Here you can find the full details:
Comments