Skip to main content

The one question that transforms every coaching session

As rewarding coaching can be, as challenging it is. While reading the 'How to be a more effective coach?' post by JD Meier, he shared one 'bonus' question that really created a breakthrough in how I tackle these coaching conversations.

What would make this conversation wildly valuable for you today?

This one question makes all the difference as it shifts the focus from you to them, immediately.

Why this question works so well

It transfers ownership immediately

The moment you ask this question, something profound happens. The conversation stops being about your agenda and becomes entirely about theirs. You're not trying to fix, advise, or direct. Instead, you're creating a container for their most important work to emerge.

This transfer of ownership is crucial because:

  • People are more invested in solutions they help create
  • People often know what they need better than we do
  • It honors their autonomy and expertise in their own lives
  • It removes the pressure on you to have all the answers

It cuts through surface-level concerns

Most people come to coaching sessions with what they think they should talk about, not necessarily what they need to talk about. This question bypasses that entirely. It gives them permission to dig deeper, to surface what's really on their mind, and to prioritize their most pressing needs.

The word "wildly" is particularly important here—it suggests they can think bigger, be more ambitious, and not settle for incremental improvements.

It creates psychological safety

By asking what would make the conversation valuable for them, you're sending a clear message: this space is theirs. You're not here to judge, evaluate, or impose your own framework. You're here to serve their growth in whatever way they need most.

Beyond the question: creating a mindset

While the specific wording of this question is powerful, what matters more is the mindset behind it. Ask yourself:

  • Am I truly curious about what this person needs?
  • Am I willing to let go of my own agenda?
  • Do I trust that they know what's best for them?
  • Am I comfortable with not knowing where the conversation will go?

There's something vulnerable about asking this question. It requires you to step back and admit that you don't know all the answers. But this vulnerability is precisely what makes it so powerful.

When you ask "What would make this conversation wildly valuable for you today?" you're not just asking about today's conversation—you're modeling what it looks like to prioritize someone else's needs, to be genuinely curious, and to trust in their capacity for growth.

More information

How To Be a More Effective Coach | JD Meier

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