How to Make a Decision When You Don't Have Enough Information

The Trap Is Waiting

At some point in your career, you've sat in a meeting, or at your desk, or on a call, and the question has been on the table: what do we do? And the honest answer was: I don't know enough yet.

So you waited. You asked for more data. You scheduled a follow-up. You said "let's revisit this when we have more clarity." And maybe that was the right call. But I'd bet, more often than not, it wasn't. More often, you were buying time because the discomfort of uncertainty felt worse than the cost of delay.

That cost is real, even when it's invisible.

The Information You're Waiting For Probably Isn't Coming

Here's the thing about "more information." There is always more information available if you look long enough. There's another stakeholder you could ask. Another analysis you could run. Another week you could wait to see how the situation develops. The problem is that the window in which a decision is actually useful tends to close faster than the information you're waiting for arrives.

I've watched managers wait for perfect data on a hiring decision until the candidate accepted another offer. I've watched teams wait for market clarity on a product decision until a competitor made the move first and the moment was gone. The information eventually showed up. It just didn't matter anymore.

Waiting isn't neutral. It's a choice, and it has consequences.

What You're Actually Doing When You Stall

I want to be honest about what's happening psychologically when we stall for information. Most of the time, it's not a rational assessment of what we need. It's risk aversion dressed up as process. We are afraid of being wrong. We are afraid of being the person who made the call and had it go sideways. And so we unconsciously construct a need for "more information" because it gives us cover.

The data isn't actually going to change your mind in most cases. You already know what you're inclined to do. You just want someone or something to absorb the responsibility if it goes wrong.

That's understandable. It's also a failure of leadership.

Build a Frame Before You Need One

The best decision-makers I've worked with share one habit: they think about decisions before they're in them. They establish, in advance, what "enough information" actually means for a given type of decision. Not in a formal, documented way necessarily, but in their heads. They've asked the question: at what threshold am I comfortable moving?

This matters because when you're in the middle of a decision under pressure, you're not thinking clearly about what you actually need. You're reacting. Having a frame already built means you can evaluate where you are against something real, not against your anxiety.

A simple version of this: before a project starts, decide what you'd need to know to pull the plug or change direction. Write it down. When the moment comes, you check the list, not your gut.

The Two Questions That Actually Matter

When you're stuck in a decision without enough information, there are really only two questions worth answering.

The first is: what is the cost of waiting? Not abstractly. Concretely. What does delay cost in dollars, in time, in opportunity, in team morale? If the cost of waiting one more week is low, then waiting might be defensible. If the cost of waiting one more week is a deal that closes without you, or a team member who leaves because you couldn't make a call on their promotion, or a competitor who ships first, then you have your answer. You move.

The second is: what is the cost of being wrong? If the decision is reversible, the calculus changes dramatically. Most operational decisions are more reversible than people treat them. You can hire and course-correct. You can launch a feature and iterate. You can restructure a process and adjust. Irreversible decisions, the ones where being wrong has catastrophic or permanent consequences, deserve more caution and more information-gathering. But most decisions aren't irreversible, and treating every decision like it is paralyzes organizations.

Ask both questions honestly. The answers usually point somewhere.

Move, Then Watch

One of the most useful reframes I've found is this: the decision isn't the end of the process, it's the beginning of the next one. You make the call. Then you watch what happens. Then you adjust.

Good decision-makers aren't people who are always right. They're people who make reasonable calls under uncertainty, watch the results with clear eyes, and correct fast when they're off. The manager who makes five imperfect decisions and corrects four of them moves faster and gets better outcomes than the manager who waits for certainty and makes two perfect ones.

Speed plus correction beats perfection plus paralysis almost every time.

What to Do Right Now

If you have a decision sitting open right now, here's a process worth running.

Name the actual decision. Not the conversation around it, not the conditions you're monitoring. The specific choice you have to make.

Write down what you know. Not what you wish you knew, not what would be nice to have. What you actually know right now.

Answer the two questions: what does waiting cost, and how reversible is being wrong?

Set a deadline. If you don't have a decision by a specific date, the default is X. Having a default forces clarity.

Make the call. Document your reasoning briefly, not to protect yourself politically, but so you can learn from it later.

That's the whole process. It doesn't require a committee or a framework or a consultant. It requires discipline and a little bit of courage.

The Managers Who Get This Right

The best operators I've seen are not people with better information than everyone else. They're people who've made peace with uncertainty. They know they're going to be wrong sometimes. They've built enough trust with their teams that being wrong isn't catastrophic. They correct, they learn, they move.

They also create cultures where their teams make decisions, too. Because when a manager stalls, their whole team stalls. The paralysis moves downward. When a manager models confident, thoughtful decision-making under uncertainty, the team learns it. That compounds over time.

The Courage Part

I'm not going to pretend this is all analytical. Part of it is just courage. Making a call when you can't see the whole board is uncomfortable, and no framework fully eliminates that discomfort. But discomfort is not the same as danger, and waiting until you're comfortable is waiting too long.

The information will probably never be complete. The picture will probably never be fully clear. At some point, you look at what you have, you answer the two questions, and you move.

That's the job.