Skip to main content

Permission to experiment granted

In my post yesterday about shifting from "why" to "what" questions, I explored how this simple change can transform leadership conversations. Today, I want to focus on one specific question that came up in a related Coaching for Leaders podcast episode with Elizabeth Lotardo:

What have you already tried?

What makes this question so powerful?

When someone comes to you with a problem and you ask, "What have you already tried?" you're sending several key messages simultaneously:

You expect initiative. You're not surprised that they've already taken action—you assume it. This presumption of capability builds confidence.

Experimentation is valued. By asking what they've tried, not what they've done, you're acknowledging that not everything works on the first attempt. And that's okay.

Their attempts matter. Even if their experiments didn't solve the problem, the learning from those attempts is valuable information worth discussing.

The psychological safety connection

This question creates psychological safety in a way few others can. It tells your team member:

"I don't expect you to have all the answers before you start. I expect you to try, learn, and iterate."

Contrast this with common alternatives:

  • "Have you tried X?" (implies they should have thought of your solution)
  • "What do you think you should do?" (puts pressure on them to have the right answer)
  • "Why didn't this work?" (focuses on failure rather than learning)

"What have you already tried?" honors their agency while opening space for collaborative problem-solving.

The immediate impact

Here's what I've noticed when I consistently ask this question:

People come to me earlier in their problem-solving process, not just when they're stuck. They're not afraid to share their failed experiments because they know those attempts are part of the conversation, not evidence of incompetence.

The conversation naturally shifts from me solving their problem to us building on what they've learned. I might say, "Interesting that approach X didn't work—what did that tell you?" or "You've tried A and B—what feels like the next logical experiment?"

Asking this question consistently helps you (re)shape your organizational culture.

Your homework

So, when someone brings you a challenge, resist the urge to immediately offer solutions or ask what they think they should do. Instead, try: "What have you already tried?"

Then listen. Really listen to what they've learned. Build from there.

You might be surprised at how much problem-solving has already happened—and how much permission this simple question gives your team to keep experimenting.

More information

Stop Solving Your Team’s Problems – Coaching for Leaders

The power of "What" over "Why"

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