Why You Believe What You Believe
some thoughts on the philosophy of leadership
I’ve watched this happen dozens of times. Someone makes a confident claim about strategy or process or direction, and someone else asks, “why?” They’re not asking to be difficult - they actually want to know. And nobody has an answer.
That little pause, right before the justification that doesn’t always show up, is what philosophical unpreparedness looks like in real life. It isn’t about intelligence and it isn’t about experience. It’s about not having a framework. Most leaders were never taught to trace their positions back to the assumptions underneath them, so when the pressure is high, they don’t have anything to guide them.
Name the Thing
I’ve spent a good chunk of the last year arguing that quality is a systemic property and not a testing output. That can sound like a preference about practices, but it’s not. It’s a statement about what quality actually is, and you have to figure out what that is before you can decide how to pursue it.
I’ve learned that once I name what a thing is, everything around it tends to get a lot clearer. If you believe quality is a testing output, you hire testers, you build QA gates, and you measure defect escape rates. If you believe quality is a systemic property, you redesign feedback loops, you rethink how teams are structured, and you start measuring deployment confidence and flow instead. Same word, completely different application.
Philosophical clarity sharpens how you think, and it changes what you build.
Most leadership teams have never run an exercise like this on the things that matter most to them. What is a customer? What does developer experience actually mean? What does “done” look like? They’re running on inherited defaults that nobody chose on purpose and nobody ever actually agreed with. This creates friction that’s difficult, and miserable, to diagnose, because the arguments look tactical when the actual disagreement is foundational.
Whose Eyes Do You Trust?
The second place this shows up is in how leaders decide what’s true. What are the standards they use to decide what counts as enough evidence to act?
Different leaders in the same building often apply totally different thresholds. Peter needs to see it with his own eyes. Melissa only trusts the dashboard. And Nick just goes with whoever felt like a good idea in the last meeting. Nobody named the standard, so nobody can argue about it. They just keep disagreeing about conclusions while the real disagreement stays buried.
Like most leadership topics, all of this is true in any relationship and how we deal with the people in our lives. I’ve learned in my own relationships that once I notice something is off and actually name it, I usually understand it. When we name things together, that understanding increases.
The 10% Test
Pick any position your organization presents as a value or a commitment. Now ask whether you’d hold onto it if it cost you 10% of revenue.
If the answer is no, it isn’t a commitment. It’s probably just marketing or buzzwords.
I’ve watched leaders mix these two things up for their entire careers, and I suppose it makes sense why. Brand positioning and a real ethical commitment look the same as long as nothing’s on the line. The difference only shows up under pressure, and by the time the pressure can be felt, it may be too late to figure out which one you actually have.
The leaders who don’t mix them up tend to have one thing in common. They’ve already done the work of naming their commitments out loud, they know why those commitments exist, and they’ve tested them to understand how they work.
Ten Seconds
There’s an article in HBR this week that calls all of this philosophical proficiency, which they define as the ability to surface, question, and reason about the foundational assumptions behind your decisions. They argue it’s becoming as essential to leadership as financial literacy. I think they’re right, and I’d push it a step further. It’s already separating the good leaders from the ones who are continually struggling.
The leaders I’ve seen struggle most at senior levels weren’t failing on execution. They were failing on credibility. And almost every time, it traced back to the same thing: they couldn’t answer “the why” behind their own positions when someone leaned on them. They had opinions, but they didn’t have grounded positions. Anyone who’s spent time in those rooms can tell the difference in about ten seconds.
AI is going to raise the stakes on this quickly. Every AI tool you bring in carries somebody else’s philosophical assumptions built into it. Somebody decided what that system treats as knowledge, what it optimizes for, and what it won’t do. Whether any of that lines up with what you actually believe is a question most leaders haven’t thought to ask. The ones who notice when it doesn’t will be the ones who already know what they believe.
Start Here
You won’t find philosophical clarity from reading philosophy. You get it by leaning into hard questions in real situations, getting things wrong, and slowly getting more precise. The starting point is simple. Pick something central to how your organization runs and ask what it actually is. Then ask whether your leadership team would give you the same answer.
The gap between what they say and what they assume is where the fun starts.
If you want to talk through what this looks like in your team, I’d like to chat with you (schedule time here).