Six months after a change effort is when you find out whether it actually worked. Not during the rollout, when attention is high and the new way of working is still novel. Six months later, when the next crisis has arrived and the champion who drove the initiative has moved on to something else. That's when you find out whether the improvement was built into the structure or just held in place by effort.

What most organizations do under pressure is fix things near the surface. The urgency is real, and fixes at the execution and systems level produce visible results fast. The problem is that a fix at the wrong level doesn't just fail to solve the problem. It spends capital, creates change fatigue, and gives the skeptics more evidence that nothing ever really changes. The willingness to attempt the harder fix, the one at the right level, gets weaker every time the wrong one is

What makes organizational diagnosis so hard? The place where the pain is visible and the place where the pain originates are almost never the same.

The team that needs to move fast is stuck in an approval process built for work that needs to be stable. The team that needs to think carefully before acting is being pushed into sprint cycles built for work that benefits from moving fast. Each of them is working against the structure rather than with it. Under normal load that's a manageable annoyance. Under higher load it's the thing that's breaking everything. Understanding this changes how you read what you're seeing.

Load doesn't damage everything equally. It finds the weak points first. And it doesn't show up the same way in every team. The difference between what’s cracking and what isn't is where the diagnosis begins.

Every organization I've walked into with a retention problem has the same look on their face when I ask where people are leaving. Then they point to the exit. Attrition isn't a people problem. It's a symptom. Who stays, who leaves, and when, is at the performance layer of the company. That layer is the end of a chain, not the beginning of it.

If a system keeps producing the same problem, what's it actually doing? The answer, more often than most leaders expect, is that it's protecting something. That's a loaded way to put it, so let's get specific about what it means. Organizations aren't conscious, so they can’t make decisions to protect things. But they do develop patterns over time, and those patterns tend to persist, even when they're also causing visible harm.

Recognizing that feeling of "here we go again" is one of the most useful signals an organization or team can produce. But we don't treat it that way because repetition feels like failure. If the problem came back, someone didn't fix it right or didn't follow through. So the response to the repetition is usually the same as the response to the first one, just with more frustration behind it. Added threats or incentives. A more detailed plan. And usually, a similar result.