The question behind the question

One of the most useful habits I've developed over the years is listening for the question that hasn't quite been asked.

A learner asks where to find a document. A facilitator checks whether a session has been confirmed. A client wants to know whether an invoice has been sent.

On the surface, they're all straightforward questions. And they all deserve straightforward answers. But often they're really asking something else.

What's underneath the question

Listen closely and the questions change shape. "Can I rely on this programme?" "Has somebody thought this through?" "Am I going to have to chase this?"

Nobody says those things out loud. But they're there, underneath almost every query a programme receives.

A learner asking where to find a document usually isn't worried about the document. They're checking that the programme is organised enough that they can stop worrying about it.

A facilitator confirming a session usually isn't doubtful about the diary. They're checking that someone is holding the bigger picture so they can concentrate on their part of it.

A client asking about an invoice usually isn't questioning the process. They're checking that the professional relationship is as well run behind the scenes as it is in the room.

People aren't only looking for information. They're looking for confidence and in the end, that's what they were looking for all along.

Answering the question and the concern

This is where good programme management goes slightly further than expected.

Answering the question is important. It's the baseline. "Yes, the document is in the shared drive, here's the link." But giving someone confidence that everything is under control is often what they're really looking for.

That might mean answering the question before it's asked, because the information has already been sent. It might mean answering with a little more context than was requested, so the person can see the shape of what's coming next. It might mean simply being quick, warm and consistent enough that the question never carries an edge of doubt.

Sometimes the most confident answer is the one nobody asks you for: raising a problem yourself, before they discover it. Volunteering bad news early can't be faked, which is exactly why it carries so much weight.

None of this requires dramatic effort. It requires noticing that the question on the surface is rarely the whole of what's being asked.

When to act, and what it's for

In a previous post I wrote about the difference between responding and reacting - about knowing when to act, when to wait and when not to step in at all. Listening for the unasked question is the other half of that judgement. One tells you when to act. The other tells you what the action is really for.

A habit, not a technique

I won't pretend there's a checklist for this. It isn't a technique you can apply in the moment. It's a habit that develops slowly, the way most judgement does.

It starts with assuming there's more to a question than its words. It grows as you get to know your learners, your facilitators and your clients well enough to hear the difference between curiosity and concern. And it matures into something almost quiet: the ability to answer the question that was asked and the one that wasn't, at the same time.

You won't always guess right, and sometimes you'll hear a concern that isn't there. But listening for it is still the better bet than never hearing it at all. When that happens consistently, something changes in a programme. People stop bracing themselves. They start to assume things will work, because so far, they have.

That's not information. That's confidence.