You're deciding whether to open a new location. You ask: Can we support it operationally? Is there demand? What's the financial model? Those are good questions. But you never ask the underlying question that would reshape your whole analysis: Are we opening this location because we've outgrown our current capacity, or because we're bored with the current market? One answer means you should open. The other means you should fix the existing market first. You're answering the wrong question really well, which means you're probably getting the wrong answer.
The Question Beneath the Question
Most business decisions fail not because leaders answer questions poorly, but because they answer the wrong questions.
You want to hire an operations manager. The question you ask: What skills should this person have? What's the salary range? Good questions. But the question you didn't ask: Are we actually constrained by operations, or is this hire fixing a symptom while the real problem (unclear systems) stays hidden?
You want to add a new service line. The question: Is there market demand? Can we deliver it? Those are market questions. The question beneath: Are we adding this because customers are asking for it, or because we want to appear more sophisticated? One means you're solving a customer problem. The other means you're solving a narrative problem. Both might lead to the same service. But the second one will probably fail.
NFIB research on owner-led businesses found that decision quality improves 40% when businesses implement structured questioning frameworks. The framework forces you to ask the underlying question first. Not what to decide. Why to decide.
Where Assumptions Hide in Plain Sight
Every decision rests on assumptions. The problem is that you don't see them as assumptions. You see them as facts.
You decide to open a second location. The assumption underneath: your service model is location-agnostic. You've never tested this. You've never explicitly asked whether your success in Location A was because of your model or because of specific customers, culture fit, or local conditions.
Assumptions live in the unspoken layer of your thinking. They're so obvious to you that you don't bother to state them. They're "just how it works." That's exactly when they're dangerous. The decisions that fail most spectacularly are usually the ones where a core assumption was wrong—and you never even knew to question it.
Reframing for Clarity
The solution is brutal honesty about what you actually know versus what you're assuming. Take a decision you're about to make. Write down: What do I know for sure about this? Now write: What am I assuming? The gap between those two lists is your assumption inventory.
Now ask the underlying question. What would change if one of these assumptions was wrong? If your location expansion assumption about transferability was wrong, you'd open an unprofitable location. That's a $200K problem. If your new service assumption about profitability was wrong, you'd spend months building something that loses money. That's a $50K problem.
The real severity of being wrong about each assumption is different. That matters. You invest in testing the assumptions with the highest downside first.
Building a Decision Discipline
Create a simple framework for decisions above a certain threshold (say, $50K or 100 hours of work): (1) State the decision. (2) Answer the underlying question—why are we doing this? (3) List the core assumptions. (4) Identify which assumptions matter most. (5) For the highest-impact assumptions, state how you'd test them before committing. (6) Decide: commit fully, commit with contingency, test first, or don't do it.
This takes 2–3 hours. For a decision that might cost you $200K or more, that's the best 3 hours you'll spend. The hardest part isn't the framework. It's the honesty. You have to admit: I don't know if my assumption is true. I'm betting on it. That's uncomfortable. It's also the exact feeling that tells you the framework is working.
What makes a decision question different from a business question?
A business question asks about execution—"What should this cost?" A decision question asks about purpose—"Why are we doing this?" Decision questions come first. They reshape which business questions matter.
How do assumptions hide in plain sight?
They hide because they feel obvious. They're patterns your brain has seen before. You don't consciously think "I'm assuming X"—you just feel that X is true. The more obvious something feels, the more likely it's an unexamined assumption.
When should you reframe the question instead of answering the question you asked?
When the answer to your original question would inform a wrong decision. If you're asking "how do we expand" without asking "should we expand," you'll get excellent expansion advice for a bad expansion. Reframe first.
