Making Decisions Under Uncertainty

As a manager working across teams, you often face decisions where the information you need is scattered, incomplete, or changing. Maybe you need to choose a sha

Level: Manager
Setting: Cross-team
Core skill: Deciding with imperfect info
Common pitfall: Analysis paralysis
Practice to try: A decision + review loop

What this looks like in real work

As a manager working across teams, you often face decisions where the information you need is scattered, incomplete, or changing. Maybe you need to choose a shared process for handling customer requests, but each team has different data and priorities. Or you must commit to a project timeline without knowing whether another department will free up the specialists you need. The pressure to decide is real, but the clarity you want is not there yet. This is the everyday reality of cross-team leadership: you are asked to move forward while key details remain fuzzy.

In these moments, the temptation is to wait for more data, more alignment, or a clearer signal. But waiting has its own cost. Other teams may stall, work may pile up, and people may start making their own assumptions. The decision does not get easier with time; it just gets more urgent. Recognising that uncertainty is the normal condition, not a temporary glitch, helps you shift from hoping for perfect information to working with what you have. That shift is the first step toward deciding well under uncertainty.

Why it trips people up

Uncertainty feels risky, and most managers are trained to reduce risk. So when information is missing, the instinct is to gather more, analyse longer, and consult more people. This can feel responsible and thorough. But in cross-team work, the information you need often sits with people who are busy, have different goals, or simply do not know yet. The more you wait, the more you may be waiting for something that will never arrive in a neat package. Meanwhile, other teams are watching for your signal to act.

Another trap is confusing uncertainty with a lack of authority. You might think you cannot decide until everyone agrees, but cross-team decisions rarely come with full consensus. If you wait for unanimous support, you will delay indefinitely. The real skill is to decide with the information you have, while staying open to adjusting later. That requires separating the decision from the outcome: you can make a good decision process even when the result is uncertain. Managers who struggle here often mistake patience for progress, and the work slows down for everyone.

The mistake that quietly hurts

Analysis paralysis rarely looks like doing nothing. It looks like one more meeting, one more data request, one more round of feedback. Each step seems reasonable, but together they create a pattern of delay. The quiet harm is that other teams start to route around you. They make their own decisions, set their own priorities, and stop waiting for your input. By the time you feel ready, the window for shaping the work has narrowed. You are no longer leading the decision; you are reacting to it.

This mistake also erodes trust. When you repeatedly ask for more information without committing, people begin to see you as indecisive. They may stop bringing you problems because they assume you will not act. Over time, your influence shrinks, not because you lack authority, but because you have not used it. The irony is that the pursuit of certainty often creates more uncertainty for everyone else. The fix is not to decide recklessly, but to decide deliberately with what you have, and to build in a way to revisit the choice.

A practice you can repeat

Try a simple decision and review loop. First, set a clear decision date. When a cross-team issue arises, ask yourself: what is the latest point at which we can decide without causing real harm? Put that date on the calendar. Then, before that date, gather only the information that could change your choice. Not everything, just the few facts that would make you pick a different path. Write down your current best option and the main reason you might be wrong.

On the decision date, make the call, even if you are not fully certain. State what you are deciding, what you are assuming, and when you will review it. Then schedule the review. At the review, ask: what actually happened? What did we learn? Do we stay the course, adjust, or reverse? This loop turns uncertainty into a manageable cycle. You are not pretending to know everything; you are committing to learn and adapt. Over time, this builds confidence because you see that decisions can be revisited without drama. It also gives other teams a predictable rhythm, which reduces their anxiety and keeps work moving.

What to say and do

When you need to move forward without full information, your words matter. Start by naming the uncertainty openly. You might say: "We don't have all the data yet, but waiting any longer will slow down three teams. I'm going to decide based on what we know today, and we'll review in two weeks." This sets expectations and gives people a reason to trust the process. It also signals that you are not ignoring the gaps, just choosing to act despite them.

Next, make the decision concrete and give people a role. Try: "Here's the call: we'll go with option A for now. I need each team to flag any blocker that would make this unworkable within the next five days." This invites input without reopening the whole debate. Finally, when you review, be explicit about what you learned. Say: "The assumption about response time was wrong, so we're adjusting the plan. The overall direction still holds." This normalises adjustment and shows that reviewing is not a sign of failure. These phrases help you lead through uncertainty without pretending it away.

When the stakes get higher

Higher stakes do not mean you should wait for perfect information. They mean you should be more deliberate about how you decide. When a cross-team decision could affect many people or a critical deadline, you still need a decision date, but you may want to widen your circle of input before that date. Ask a few trusted colleagues from different teams what they see as the biggest risk. You are not seeking consensus; you are testing your assumptions. Then decide, and communicate the reasoning clearly.

You can also build in a shorter review cycle. If the stakes are high, you might review in days rather than weeks. That does not mean you are indecisive; it means you are watching closely. The key is to avoid letting the higher stakes become an excuse for endless analysis. In fact, high-stakes situations often demand faster decisions because delay itself creates new risks. Your job is to balance speed with a clear plan to correct course. When you do that, people see that you can hold both caution and action together, which builds confidence even when the path is unclear.

Questions new leaders ask

Q: How do I know when I have enough information to decide? A: You rarely feel certain. Instead, ask: what is the cost of waiting another week? If waiting creates more problems than deciding with gaps, you have enough. Also, identify the one or two facts that would truly change your choice. If you cannot get them soon, decide without them.

Q: What if I make the wrong call? A: You will sometimes be wrong. That is why you build a review loop. A wrong decision that is reviewed and adjusted quickly is far less damaging than a delayed decision that stalls everyone. Focus on making the process sound, not on being perfect.

Q: How do I get other teams to accept a decision they disagree with? A: You do not need full agreement. You need clarity. Explain what you decided, why, and when you will revisit it. Invite them to surface blockers, not to relitigate the choice. Over time, a consistent decision and review rhythm earns trust, even from those who initially disagreed.