The question nobody asks before making a decision is this: what would have to be true for this to be the right call?
Most teams skip straight to weighing options, gathering more data, or polling the room. They focus on collecting information. The real skill is knowing which question cuts through all of it. One well-formed question will save you from a dozen spreadsheets and three months of regret. This post is about that question, why it keeps getting skipped, and how to use it before your next big decision.
Why does the question nobody asks before making a decision get skipped?
Because it feels slower. And in most organisations, decisiveness is rewarded more than accuracy.
When a board is waiting, a grant deadline is closing, or a staff member is asking what to do next, asking “what would have to be true for this to be right?” feels like stalling. It feels like the opposite of leadership.
It isn’t. It’s the difference between a decision you can defend in twelve months and one you’ll quietly walk back.
The other reason it gets skipped: it surfaces uncertainty. Most decision-makers would rather feel confident than be correct. Naming the conditions that need to hold true forces you to admit which ones you can’t verify yet. That’s uncomfortable. It’s also where every good decision starts.
What’s wrong with gathering more information?
Nothing, until it becomes a substitute for thinking.
A pattern that comes up frequently in non-profit decision-making: “I have data, but I don’t know how to use it.” The instinct, almost always, is to gather more. More survey responses. More dashboards. Another report. The belief is that clarity lives somewhere on the other side of one more data pull.
It rarely does.
More information without a sharper question produces more noise, not more signal. You end up with three reports that disagree, no framework for weighing them, and a decision that defaults to whoever is loudest in the room. The question is the filter. Without it, the data has nowhere to land.
How does this question actually work in practice?
It works by inverting the usual flow. Instead of asking “what does the data say?” you ask “what would the data need to say for option A to be the right choice?”
Then you check.
Here’s a small example. A non-profit is deciding whether to open a second location. The board is split. Someone pulls foot-traffic estimates, someone else pulls donor maps, a third person makes the case from anecdotes. Nobody agrees.
Now apply the question. What would have to be true for a second location to be the right call?
Demand in the new area would need to exceed unmet demand at the current location.
The new site couldn’t cannibalise donors or volunteers from the existing one.
Operating costs would need to stay within a defined percentage of program spend.
There would need to be at least one local partner willing to share infrastructure.
Now the data has a job. Each item on that list is testable. You’re no longer drowning in reports. You’re answering four specific questions. And if even two of them come back negative, you have your answer, without another six months of debate.
When should you ask it?
Before you start gathering data. Not after.
This is the part most people get backwards. They collect first, then look for patterns, then try to retrofit a decision. By that point, sunk cost has already shaped the answer. You’ve spent three weeks on the analysis. Somebody is going to act on it, even if the conclusion is shaky.
Asking the question first does two useful things. It tells you what data you actually need (which is almost always less than you think). And it tells you what data is irrelevant, which protects your time and your team’s attention.
If you can’t articulate what would change your mind, you’re not ready to gather information yet. You’re ready to think.
What does this look like for a small non-profit?
It looks like fewer decisions made on anecdote, and more decisions made on conditions you can actually check.
Most small non-profits don’t lack data. They lack a way to interrogate it. Donation records, program attendance, volunteer hours, intake forms, social engagement, all of it sits in some system somewhere. The problem isn’t volume. It’s that nobody has asked a sharp enough question to make the data answerable.
Try this the next time a real decision is on the table:
Write down the decision in one sentence.
Write down what would have to be true for the answer to be yes.
Write down what would have to be true for the answer to be no.
For each item, mark whether you can check it with data you already have, data you could get, or data you’ll never have.
Start with the cheapest checks first.
You’ll often find the decision answers itself somewhere between step three and step five. Not because the data is magical, but because the question finally was.
What we keep getting wrong about decision-making
We treat decisions as moments. They’re not. They’re the visible end of a thinking process that started much earlier, with a question.
The quality of your decisions is almost entirely set by the quality of the question you asked at the beginning. Better data won’t rescue a vague question. More meetings won’t either. Senior advisors won’t, though they may help you ask a sharper one.
The organizations that punch above their weight, the ones doing more with less and serving their communities in meaningful ways, aren’t the ones with the most information. They’re the ones who have learned to ask the question nobody asks before making a decision, and to keep asking it, even when the room is impatient for an answer.
That habit is small. It costs nothing. It compounds for years.
Frequently asked questions
What if I genuinely don’t know what would have to be true?
That’s useful information. It means the decision isn’t ready to be made, or that you don’t yet understand the problem well enough to act on it. Sit with the question for a day, talk it through with one trusted person, and write down what comes up. The answer doesn’t have to be perfect. It just has to be specific enough to test.
How is this different from a pros and cons list?
A pros and cons list catalogs what you already think. This question forces you to define what would change your mind. That’s the key shift. You’re not measuring sentiment, you’re naming testable conditions. One produces opinions, the other produces decisions you can defend.
Doesn’t this slow everything down?
It feels slower for the first ten minutes and saves you weeks later. Most decision delays come from circling the same debate without resolution, not from thinking carefully up front. Asking the question early replaces a long, frustrating debate with a short, specific one.
Can this work for small, everyday decisions too?
Yes, though it’s overkill for most of them. Save it for decisions where the cost of being wrong is meaningful: hiring, program design, technology investments, partnership commitments. For those, a five-minute version of this exercise is worth more than another committee meeting.