Organizations that can’t identify the people who know stuff that no one has asked them to explain, or can’t help those people learn how to communicate what they know, are ceding control of their organizational knowledge and institutional memory to whatever the next hire brings with them.

The working part is the naming. An injury that stays hidden is indistinguishable from personality. The moment it’s made visible, it becomes a fact about you rather than who you are.

We’re stuck with two options. Keep the decision open and pay for it with bursts of energy, or plan ahead and pay for it in missed predictions and wasted effort. Most leaders and orgs pick a lane, and the failure they can't manage is the one that hides in their strength.

Want to know what your culture actually is? Don't read the values page. Don't check at the annual meeting... the annual meeting knows it's being watched. Watch what people do when they think nobody's checking. Every organization has a way it runs naturally, and that default is the real culture.

You can't learn what an organization values by watching it on a good day. Everybody can look generous when nothing's at stake. You learn it by watching what gets cut first when things get tight. That first cut is the most honest act an institution ever takes. Put down the annual reports and letters to fans. Grab the layoff list. That's the unquestionable truth.

Belief is a practice you keep, especially after it's torn. A value that has never been tested and broken is a guess... a wish. Nobody bets on it when it matters, because nobody knows what it costs. The taped sign carries information the new sign couldn’t: everyone in that room knows exactly what failure looked like, and chose to believe again anyway.

I’m beginning to think that we shouldn’t worry so much about whether people like us. In business and life it seems like it’s healthier to focus on whether they have enough evidence that they’re willing to rely on us (for things we’re capable of) when that reliance could cost them something.

Building a team around one star is brittle and failure-prone by design, not by bad luck. A star is temporary. Stars transfer, retire, burn out, or leave for an avocado farm, so the club that rests its results on them is running on a clock it can’t see. The problem shows up while the star is still there. Every team skill the star replaces just rots on the vine. By the time the star is gone, the team has spent months destroying the crop it will depend on.

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.

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.

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.