When “why” shows up late, it shows up expensive.
Unasked questions compound.
I’ve learned this the hard way.
At work, “why” isn’t curiosity. It’s underwriting.
If I can’t explain something after five “whys,” I don’t understand it.
I understand the pitch.
I understand the diagram.
I may even understand the roadmap.
But that doesn’t mean I understand the system.
I’ve seen fragility get funded because the demo worked and the assumptions weren’t interrogated.
Until something breaks.
Then “why” shows up — in an outage bridge, an exam, or a board meeting — asking questions no one rehearsed:
Why does it behave this way?
Why can’t we reverse it?
Why does this edge case exist?
Why didn’t we see this coming?
That’s not inquiry. That’s exposure.
The most expensive systems I’ve seen weren’t built wrong.
They were built before anyone paused long enough to ask why.
Not why it works.
Why it exists.
Why it’s structured this way.
Why failure will look the way it will.
The assumptions hardened into the architecture.
I ask early.
Not to slow things down — but to surface fragility while it’s still cheap to fix.
Because “we didn’t know” is forgivable.
“We never asked” is not.