The importance of Why
On working out the why for yourself, the fiction you sometimes build instead, and why a leader hands out the real one.
Why is the most useful question I own, and most of the time I never have to ask it out loud.
For most things the why just lands, almost immediately, no thinking involved. Hand me the task and the reason underneath it usually shows up with it. I don’t interrogate anyone. I don’t hold up the work waiting for a justification. It’s the same instinct that makes me take a thing apart instead of just using it: pull enough things apart and eventually the whys start arriving pre-assembled.
The rest I absorb and carry. No why on arrival, so it rides in the back of my head while I get on with the work, and the reason surfaces later. A day, a week, somewhere in the middle of something unrelated. I’ve learned to let those come in their own time.
But speed has a failure mode, and I have to own it. A why that arrives on its own isn’t understanding, it’s a pattern match, built from the facts I can see, and the facts I can’t see are usually the ones that made the call. I’ve assumed a rule was laziness when it was legal. I’ve read a decision as politics when it was arithmetic from a spreadsheet I’d never seen. The dangerous part is that a why I invented feels exactly like a why I understood. Same certainty, same weight, no warning light. The only tool that catches it is embarrassingly simple. Say your version out loud to someone who actually knows, and find out which kind you’re holding.
And then there are the leftovers, the ones that never resolve. The rule with no logic I can reconstruct. The call that seems to argue with itself. The “because that’s how it is.” Those nag. The reasoning won’t come, the itch won’t quit, and I’ll keep pulling long after I’ve been told to drop it. That’s the bill: not that I need a reason for everything, but that the things that don’t add up will not leave me alone until someone hands me the why.
And it isn’t just me. Everyone is like this, whether they admit it or not. People resist what they don’t understand the reason for. Hand someone a rule with no why attached and they’ll fight it, ignore it, or quietly work around it. Hand them the same rule with the why made plain and most of them will carry it for you. The rule didn’t change. The understanding did.
That changed how I lead more than anything else I’ve learned. If people run on the why, then handing it out is the job. Be open about what you’re doing, honest about why, transparent about what’s still undecided, on everything you’re allowed to be. And when a why genuinely isn’t yours to share, because some aren’t, say that instead: there’s a reason, and I can’t give it to you yet. That’s still honest, and people can carry it. What you can’t do is leave the space blank, because nobody leaves a blank. They do exactly what I do. They build a why out of the facts they can see, and the one they build is almost always worse than the truth. Silence doesn’t read as neutral. It reads as bad news. And the flip side is the cheapest motivation there is: people who can see why the work matters push harder for it, willingly, than any perk or slogan ever got out of anyone. People work hard for a reason. They drag their feet for a mystery.
Underneath all of it, the why is the thing that keeps me in the work at all. Strip the reason out and it’s just tasks. Put it back and it’s a reason to show up. That’s the one why I can’t afford to lose the answer to.
So you’d think the rule would be simple: no why, no action. It isn’t, and it can’t be.
When push comes to shove, you do what needs doing, whether or not anyone explained it. Some calls get made without you. Some deadlines don’t care what you understand. I’ve executed plenty of decisions I didn’t have the reasoning for, and a few I didn’t agree with, because the work had to happen and it was mine to do.
But.
The why is the grease on the bearings. The icing on the cake. It doesn’t change what gets done, it changes how the doing goes. The same task, handed over with the reason attached, goes down smoother and lands better and gets done willingly instead of grudgingly. People move faster when they can see where they’re pushing and why. Friction drops. The thing that would have ground turns instead.
So I’ve made my peace with it. I chase the why for myself, because that’s the only way I actually understand anything, and I check the ones I build, because certainty isn’t proof I got it right. I hand the why to other people every chance I get, because it’s the cheapest force multiplier there is. And when there’s no time for either, I do the thing anyway, and go find the why after.
The why was never a requirement. It’s the lubricant. Get the job done first. But if you can pass someone the reason on the way past, do it, because everything moves easier when people know why.