Binder

The WHY problem

"People will do just about anything, work any hours, if they know that the work they do is meaningful."

That line comes from an operator trying to explain why PE-backed companies lose their best people. The narrative collapses. The pastor is drunk and spending time at the casino. Nobody’s describing Hawaii anymore. They’re describing the details of trimming sails and reading the compass.

Same failure in PM. Marty Cagan’s distinction between product and IT mindset isn’t primarily about methodology. It’s about belief. IT staff are mercenary — they’re executing requirements. Product staff are missionary — they believe in what they’re building. The difference isn’t the process. It’s the WHY.

Same failure in the Afghanistan debrief. The post-mortems focused on training quality, equipment, corruption. What wasn’t addressable: troops fighting for their clan, not for Afghanistan. The WHY was wrong before the first training session began. No investment in the HOW fixes a broken WHY.

Creating the WHY

Paul O’Neill walked into Alcoa and set an unrealistically high safety goal — zero work days lost. Everyone thought he was crazy. What he understood was the leverage point. The goal wasn’t about safety. It was about giving people something they could believe in.

"Until I said the target was zero, we didn't have a problem. Part of the role of leadership is to create a crisis."

The crisis creates the WHY. Without it, you’re just describing the compass.

The Japanese concept “un-son” — cloud-grandchild — is the long-game version of the same idea. Japanese businesses over 100 years old explicitly ask: what will this mean for future generations as distant as clouds? That WHY — continuity, obligation, community — turns out to be more durable than any financial target.