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

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.

.NET 8–Keyed/Named Services

A feature that a lot of IoC container libraries support but that was missing in the default DI container provided by Microsoft is the support for Keyed or Named Services. This feature allows you to register the same type multiple times using different names, allowing you to resolve a specific instance based on the circumstances. Although there is some controversy if supporting this feature is a good idea or not, it certainly can be handy. To support this feature a new interface IKeyedServiceProvider got introduced in .NET 8 providing 2 new methods on our ServiceProvider instance: object? GetKeyedService(Type serviceType, object? serviceKey); object GetRequiredKeyedService(Type serviceType, object? serviceKey); To use it, we need to register our service using one of the new extension methods: Resolving the service can be done either through the FromKeyedServices attribute: or by injecting the IKeyedServiceProvider interface and calling the GetRequiredKeyedServic...

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