Skip to main content

The power of "What" over "Why"

Leadership isn't about having all the answers—it's about asking the right questions. I was reminded about this while listening to Shannon Minifie, CEO of Box of Crayons, on the Coaching for Leaders podcast (Episode 760), where she explored how the quality of our questions shapes the quality of our leadership.

The problem with "Why"

As leaders, we're trained to dig deep, to understand root causes. "Why did this happen?" "Why didn't you finish that project?" These questions feel investigative and thorough. But here's what Minifie points out: "why" questions often put people on the defensive.

When someone hears "Why did you do that?" their brain doesn't hear curiosity—it hears judgment. They start building walls instead of opening doors. The conversation shifts from exploration to explanation, from possibility to justification.

The "What" alternative

This connects directly to Michael Bungay Stanier's work in The Coaching Habit, which offers seven essential questions that keep conversations forward-focused. The shift from "why" to "what" is subtle but transformative.

Instead of asking:

  • "Why did this fail?" try "What happened here?"
  • "Why didn't you meet the deadline?" becomes "What got in the way?"
  • "Why do you think that?" transforms into "What's making you think that?"

Notice the difference? "What" questions invite reflection without accusation. They create space for honest conversation rather than defensive posturing.

Curiosity as a leadership muscle

The real lesson here isn't just about word choice—it's about cultivating genuine curiosity. When we approach situations with authentic curiosity rather than disguised criticism, we:

  • Build psychological safety: Team members feel comfortable sharing challenges and mistakes
  • Uncover better information: People share what actually happened, not sanitized versions
  • Foster problem-solving: The focus shifts to solutions rather than blame
  • Develop our people: Questions that make people think help them grow

The ripple effect

When you consistently ask "what" instead of "why," you're not just changing your vocabulary—you're changing your team's culture. You're signaling that mistakes are learning opportunities, that challenges are meant to be discussed openly, and that your role is to support growth, not assign blame.

Leadership curiosity isn't passive. It's an active choice to set aside judgment, stay genuinely interested, and create the conditions where people can do their best thinking.

What question will you ask differently today?

More information

The Kind of Curiosity Leaders Miss – Coaching for Leaders

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...

Cache stampede: when our cache turned against us

While investigating some performance issues, we ran into an ASP.NET Core API that cached a fairly expensive aggregation query for 60 seconds. Under normal load, that was fine: one request rebuilds the cache, everyone else reads from it. Under peak load, dozens of requests would arrive in that same expiry window, all see a cache miss, and all fire the same expensive query in parallel. The database didn't like that. That was the moment when our caching layer stopped helping and started hurting. A burst of requests comes in at the same time, all miss the cache, and all go hammer the database or the downstream API at once. That's a cache stampede . The cache was supposed to protect our backend, and for a few hundred milliseconds it did the opposite. Why this happens IMemoryCache.GetOrCreate (and its async sibling) looks like it protects you, but it doesn't add any locking on its own. Look at the naive version: public async Task<Report> GetReportAsync(string key) ...

A complex system designed from scratch never works

A few years ago, I worked as an architect on a big mainframe rewrite. I still count it as one of my failures. Not because the technology was wrong, but because I couldn't convince the management team to simplify the approach. Years later, the organization is still struggling to get the new system up and running. I left the project at the time, because I couldn't put my name behind an approach that would take very long and cost a lot of money without a working system to show for it along the way. Gall’s Law That memory keeps coming back to me, because it's a textbook case of Gall's Law playing out in real life. Gall's Law , from John Gall's Systemantics , states it plainly: A complex system that works is invariably found to have evolved from a simple system that worked. A complex system designed from scratch never works, and it cannot be patched to make it work. You have to start over with a simple system that works. What does that mean in practice,...