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

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.

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         ...