Whose work grew this year while your praise stood still? Find someone you talked up a year ago and haven't really engaged since. Look at what they're actually doing now. Then do what you can to share what they've become, specifically and in public if you can. The test of recognition is simple... whether the picture you have of someone has kept up with where they are now. Done honestly, it closes the gap between what you say you value and what your attention actually tracks.

Trust compounds in a fictional locker room the same way it compounds in your office, through small deposits repeated until people change what they expect from each other.

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.

Sometimes, the reason the problem persists isn't that leadership doesn't see it. It's that fixing it requires someone powerful to give something up. To accept a constraint. To close off an option they've been keeping quietly open. When that's the case, no framing fixes it completely. What good framing can do is make the cost of doing nothing explicit enough that the conversation has to happen, even when it's uncomfortable.

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.