The Question Behind the Question

A leader once came to a conversation with a fairly ordinary tactical problem: a hiring decision between two strong candidates, and a request for help thinking it through. Twenty minutes in, the conversation had quietly moved somewhere else entirely. The real question wasn't which candidate was better on paper. It was whether this leader trusted themselves to make a senior hire at all, after a previous one hadn't worked out and nobody had ever actually talked about why.

The hiring decision was real. It also wasn't the thing that needed solving most.

I've seen this shape often enough to think it isn't unusual at all, it's closer to the norm. Someone brings a specific, well-defined problem. A few layers under it sits something less specific and considerably more important, usually unspoken, sometimes not even fully known to the person carrying it until the conversation gets there.

Why the surface question is so often not the real one

A tactical question is easy to bring to someone. It has a clean shape, a clear ask, and doesn't require admitting to anything uncomfortable. 'Should I hire this person' is a question about a candidate. 'Do I still trust my own judgement after the last hire went wrong' is a question about the person asking, and that's a much harder sentence for most people to say out loud, even to themselves.

This isn't evasion or dishonesty. Most people genuinely don't know, at the point they ask, that there's a second question sitting underneath the first. The tactical question is the one they can see clearly. The real one is usually visible only from a few steps back, and a single person rarely has the distance to see their own situation from there while they're standing inside it.

Why this matters beyond a one-on-one conversation

This pattern shows up constantly in ordinary management too, not just in structured one-on-one conversations. A team member asks for help prioritising their workload, and the real issue is that they don't trust their manager to back them if they say no to something. Someone asks for guidance on a difficult client email, and the real issue is that they're afraid of being blamed if the relationship goes sideways regardless of what the email says. Answer only the surface question in either case, and the advice usually works, technically. It also leaves the actual problem fully intact, waiting to resurface in a slightly different costume next quarter.

What actually helps

The shift isn't about cleverly guessing what the 'real' question is and announcing it. That tends to land as presumptuous, and it's often wrong besides. What works better is something quieter: staying with the surface question a little longer than feels natural, and treating it as genuinely worth understanding fully, rather than as something to solve quickly and move past. More often than expected, the real question simply surfaces on its own, in the other person's own words, once they've had enough room to get there without being rushed past it.

This is, in some ways, the simplest and least dramatic skill in this entire series, and also the one most consistently in short supply. Most conversations, even well-intentioned ones, are organised around getting to an answer efficiently. The answer to the wrong question is still the wrong answer, no matter how efficiently it arrives.

Organisations can build a small amount of this into how managers operate, without needing anyone to become a trained listener overnight. A simple habit, when someone brings a problem, asking one extra question before offering a solution ('what would actually change for you if this got solved') surfaces the real shape of the ask more often than it seems like it should. Tracked loosely across a team, even something as simple as noticing how often a 'solved' problem actually stays solved versus quietly returning in a new form tells a manager whether they've been answering surface questions or real ones.

If you're reading this and recognising a problem that keeps returning despite being 'solved' more than once, the question worth sitting with isn't 'how do I solve this better next time'. It's narrower: when you first brought this up, or someone first brought it to you, was there a question underneath the one that got asked?

At an organisational level the question becomes a count: how many of the problems your managers consider closed are actually closed, and how many have simply gone quiet for a while before returning in a different shape. Neither question requires a new framework to answer, only a willingness to stay in the conversation a little longer than feels efficient.

Deepak Narayan is an independent leadership coach and consultant at Rivi Consulting.