Making Hard Decisions Without All the Facts

There's a decision that's been sitting unmade for weeks — changing jobs, ending a relationship, investing in a project, accepting an offer — and the excuse is always the same: "I need more information before I decide." A week goes by, one more data point shows up, and the decision still doesn't get made. The problem isn't that information is missing. It's that no amount of information ever removes the uncertainty from a decision that actually matters, and waiting for it to disappear isn't a neutral pause — it's already, in practice, deciding not to act.

Someone postponing a decision usually experiences it as a state of waiting, not as an action with consequences of its own. But while the new job offer goes unaccepted, someone else takes it. While the closing conversation doesn't happen, the relationship keeps running on the same wear and tear as always. While the project stays unfunded, the window to do it keeps shrinking. Not deciding doesn't stop time — it spends that time in favor of whichever option was already in motion before the question was even raised. The cost of silence applies here with the same logic: what doesn't get decided also acts, just in favor of the status quo.

Ontological coaching starts from a premise that's uncomfortable for anyone chasing certainty: language doesn't just describe the world, it also generates it. A decision isn't the result of a calculation that produces a correct answer once there's enough data — that works for picking a vendor by price, not for deciding whether to leave a job. A decision that matters is a declaration: a speech act that doesn't describe a prior reality, but creates a new one by the mere fact of being spoken. Before saying "I accept" or "I'm done with this," both options coexisted, open. After saying it, one closes and the other starts to exist as a line of action.

Underneath "I need more information" there's almost always a deeper automatic judgment: "if I have enough data, I'll feel sure, and if I feel sure, I won't be able to get this wrong or be judged for this decision." The problem is that total certainty doesn't exist for any decision involving an uncertain future — not even with all the information in the world does the risk of it turning out differently than expected disappear. Chasing that certainty isn't prudence — it's often the same emotionality that shows up in procrastination, the fear of being judged by others or by yourself if the decision turns out to be a mistake. A change of observer here isn't getting more data: it's noticing that "I can't decide" often means "I don't want to take responsibility for a decision that might go wrong," which is a different problem, and a far more workable one.

Deciding isn't waiting to feel sure. It's a declaration that closes the deliberation and opens an action, using the information you have today.

The concrete work has three steps. First, separate which information is essential — without which the decision would change substantially — from which is merely reassuring — it doesn't change the decision, it just calms the anxiety of making it. Second, put a deadline on the deliberation itself, like a request you make to yourself with a due date, not an open-ended search with no end. Third, accept that almost no decision is a final, irreversible verdict: most can be corrected with a later action if new information calls for it, so the standard isn't "decide perfectly" but "decide on time and adjust along the way." Declaring the decision and designing the first concrete action that follows — the conversation, the email, the first step of the project — is what actually unblocks what no additional data point was ever going to unblock.