The question behind the question
Founders rarely arrive with the right question. They arrive with the symptom.
“We need to redo our messaging.”
That is how a project usually starts. It is a reasonable request, and it is almost never the actual problem. Messaging is what a founder can see. It is the surface where the discomfort shows up. Underneath it, one of five or six other things is usually going on, and none of them get fixed by new headlines.
Finding the question behind the question is not a clever framing exercise. It is the difference between spending three months on the wrong work and spending three weeks on the right work.
It is also the cheapest part of any engagement. Reframing costs a conversation. Building the wrong thing costs a quarter. Yet the reframe is the step most often skipped, because it feels like delay when everyone in the room is impatient to start.
How do you tell a symptom from a problem?
A symptom is where you noticed it. A problem is where it started. The gap between them is usually one or two steps upstream, and there are a few reliable tells.
The question names a deliverable. “We need a new landing page.” “We need a rebrand.” A real question names an outcome instead: we need people who land here to understand what this is in five seconds.
Everyone already agrees on the answer. If the room is aligned before any evidence exists, you are being asked to validate, not investigate. Alignment that early is a warning sign, not a green light.
It has been fixed before. If this is the second or third time you have solved this exact thing, you have been treating the symptom. Recurrence is the clearest evidence that the diagnosis was wrong.
It arrives with a deadline attached to the solution. “We need the new site live by September.” Deadlines are fine. Deadlines on a specific answer, before the problem is understood, mean the decision has already been made and the research is decoration.
The brief tells you where it hurts. It rarely tells you why.
Four prompts that get underneath it
These are the questions we ask in a first conversation, before anything is scoped. They are simple on purpose. Simple questions are harder to deflect.
1. What made you notice this now? Not what is wrong, but what changed. The trigger tells you where to look. A drop after a pricing change is a different problem than a slow drift over eighteen months, even when the metric moves identically.
2. What would have to be true for this to be the problem? This is the one that does the most work. Say the belief out loud, then check it. If “our messaging is unclear” were true, new visitors would bounce and returning ones would convert. If both groups behave the same, messaging is not it.
3. Who is happiest with you right now, and why? Founders investigate the unhappy customers and skip the delighted ones. The delighted ones are where the positioning is hiding. They will describe your product in words you have never used in your marketing.
4. What decision does this unlock? If the answer is “we would know more,” stop. Every question worth researching has a decision waiting on the other side. If nothing changes based on the finding, it is curiosity, and curiosity does not need a budget.
None of these require a methodology or a tool. They require someone in the room willing to slow down for twenty minutes while everyone else is ready to move. That is usually the hardest part, and it is worth insisting on.
What this looks like in practice
A subscription brand came to us convinced they had a pricing problem. Cancellations were up, and exit surveys said “too expensive.” The obvious move was a discount test.
We asked what would have to be true. If price were the problem, cancellations would cluster among the lightest users and the most price-sensitive segments. They did not. They clustered among people who had used one specific feature and hit a wall with it.
Seven of ten cancellations mentioned something missing, not something costly. “Too expensive” was shorthand for “not worth it yet.” The real question was never “what should we charge.” It was “what is the one thing that makes this worth keeping.”
That reframe cost one conversation and a week of reading. A discount test would have cost a quarter and taught them nothing.
Notice what did the work there. Not a new dataset. Not a bigger sample. A single question asked before anything was commissioned, and a willingness to check the belief the brief was built on.
When the brief is actually right
Sometimes it is. A founder who has already done this work arrives with a sharp, falsifiable question and a decision attached, and the right move is to answer it directly and quickly.
You can tell within one conversation. Ask what they expect the answer to be, and what they would do if it came back the opposite way. If both answers are specific and different from each other, the question is real. If the second answer is vague, the question is not load-bearing yet, and no amount of rigor will make it so.
Ask one more time
The practice is unglamorous. When you land on an answer that feels right, ask why once more. The first answer is usually the one you brought with you. The second is closer. The third is often the one worth building around.
Most people stop at the first because it is comfortable and it confirms the plan. The insight lives one question past comfortable.
A. Sterling LLC, consumer insights and strategy. Washington, DC. info@asterlingllc.com