“We need to decide whether to open in Kenya.” Three conversations later, the actual question is whether two founders still want the same company.
This is not evasion. Leaders present the question they can articulate, which is usually the operational one. The question underneath it is harder to name and harder to raise, particularly in a room where everyone reports to somebody.
This is a placeholder article. The structure, length and rhythm reflect how finished pieces will read; the argument is illustrative.
Why the stated question is usually downstream
Operational questions are safe. They have inputs, they can be analysed, and analysing them feels like progress. Structural questions — about ownership, about direction, about whether the leadership team is the right one — have none of those properties.
So the business builds a model for the Kenya decision. The model is excellent. It answers a question that was never really the constraint.
Getting underneath it
Three questions tend to surface the real one:
- If this decision went either way, what would still be unresolved?
- Who in this business would be surprised by the answer we are heading towards?
- What is the thing nobody has said in this room?
The third is the useful one, and it is precisely the question an internal participant cannot ask. Independence is not a credential. It is permission to say the thing.
Half of what we are paid for is asking the question everybody in the room already knows needs asking.
Then answer the stated question anyway
None of this is licence to ignore the brief. The Kenya decision still has to be made, and made well. But it is made differently — and often more quickly — once the thing underneath it has been named.
