How to slow down, find what’s truly urgent, and choose the answer that actually fits
Decisions feel urgent when people are waiting, the timeline is tight, and you can already see how many things could go wrong if the next move isn’t handled well.
You’re in a meeting that was supposed to be a quick project update. Then someone raises an issue: a deadline is closer than expected, a stakeholder wants an answer, and a few details are still unclear. Now everyone is talking through what needs to happen next.
Someone says, “We probably need to make a call on this.” Another person adds, “I think we need to know today.” Before you’ve had time to think it through, you feel the pressure to respond.
You start sorting through options in your head. You’re trying to protect the timeline, avoid creating more work for the team, keep the stakeholder satisfied, and make sure no one misses something important. No one says it directly, but it feels like someone needs to make this easier, and it might need to be you.
So the question in your mind becomes: What’s the answer?
But that may not be the best first question.
When pressure rises, it can make the decision look simpler and more urgent than it really is. It can seem like you only have two choices: give an answer right away, or become the reason things slow down. But most high-pressure decisions have more options than that.
Strong decision-making under pressure doesn’t always start with having the answer. Sometimes it starts with slowing down long enough to understand what’s actually urgent, who should be involved, and what kind of answer the situation really needs.
That pause can change the decision in front of you. It can also change the role you’re about to step into.
Decisions feel urgent when pressure takes over
Most leaders don’t rush into decisions because they’re careless. They rush because it feels like waiting even a few minutes could make things worse. A deadline gets mentioned, a stakeholder is waiting, someone is frustrated, the team needs direction, and a senior leader wants to know what’s happening.
Suddenly, the decision isn’t just about the decision anymore. Responsiveness is on the line. So is trust. No one wants to become the bottleneck, and the team still needs to keep moving. If people already see you as someone who can handle complexity, you may also feel pressure to make the situation easier for everyone else.
That’s a lot to bring into one decision.
If you’re someone people rely on, the pressure can build fast. You may not even realize you’ve moved from thinking through the situation to trying to relieve the tension around it. That’s where decision-making gets tricky.
Pressure can make a decision feel urgent before you’ve had time to ask whether it actually is. A request can start to feel like a responsibility. Someone else’s impatience can start to feel like your timeline. A complicated situation can start to feel like it needs a simple answer right now.
This is especially true for leaders who are perceptive, conscientious, and quick to see downstream impact. You can often spot the problem behind the problem, including how one missed decision can create extra work, confusion, or friction later. So when something comes to you with urgency around it, your mind may start solving before you’ve had time to separate what’s truly needed from what’s pressing on you.
That doesn’t mean you’re doing anything wrong. You’ve trained yourself to be useful under pressure. But being useful under pressure isn’t the same as letting pressure set the terms of the decision.
Sometimes the strongest leadership move isn’t to answer faster. It’s to slow down just enough to see what the moment actually needs.
Pressure can make the decision look bigger than it is.
Pressure doesn’t just make a decision feel urgent. It can also make the decision feel larger, more personal, and more final than it really is. That’s one reason high-pressure decisions can be so hard to think through clearly.
At first, you may be asking, “What should we do?” Then the questions start multiplying. What if I choose wrong? Could this slow the team down? Will the stakeholder lose confidence? If I say yes, will I regret it later? If I say no, will I look unhelpful? Would asking for more time make people think I can’t handle it?
Now the decision isn’t just about the work in front of you. It’s tangled up with reputation, relationships, timing, trust, and what other people may think of your judgment. That’s when the decision can start to look bigger than it is.
A request for input starts to feel like full ownership. The need for a next step starts to feel like a final answer. A timing issue starts to feel like a test of your commitment. Someone else’s impatience starts to feel like proof that you’re already behind.
When that happens, it’s easy to respond to the size of the pressure instead of the size of the decision. You might say yes because you don’t want to create friction. An answer may come out before you have enough information, or responsibility may land with you when another person needs to be involved. A temporary next step can start to feel like a permanent commitment.
This is why slowing down matters. Not because every decision needs more time, because some decisions really do need to happen quickly. Slowing down gives you a chance to right-size the decision before you respond.
It helps you see whether you’re being asked for a final call, a recommendation, a next step, a tradeoff, or simply a response that keeps the conversation moving. Because sometimes the decision in front of you isn’t as big as the pressure around it.
The first move is to slow down
Slowing down can sound unrealistic when people are waiting on you. In a real workplace moment, you may not have a full afternoon to think, gather every detail, or talk through every possible consequence. Sometimes the timeline is tight, and the work reallly does need to keep moving.
But slowing down doesn’t have to mean stepping away for hours or delaying the decision until everything feels certain. It can be as simple as taking a beat before you answer, asking one better question, or asking for what you need to know before you commit. The point isn’t to stall. The point is to stop the pressure from choosing the answer for you.
That’s where The Not-So-Fast Decision Check comes in.
It’s a simple three-question framework for moments when a decision feels urgent and you can feel yourself rushing toward an answer:
- What is truly urgent here?
- Whose decision is this?
- What answer actually fits?
Those questions are intentionally simple because high-pressure moments don’t leave much room for a complicated process. You don’t need a 12-step model when people are staring at you in a meeting or waiting for your reply in a message thread. You need a way to slow the mental scramble long enough to see what the situation is asking from you.
The first question helps you separate the actual time-sensitive need from the pressure around it. The second question helps you check whether the decision belongs with you, someone else, or a group of people. The third question helps you avoid defaulting to a yes-or-no answer when the situation may need something more precise.
This is where many capable leaders get caught. They’re good at making things easier for other people, so they move quickly into problem-solving. Before they know it, they’ve taken on the decision, the timeline, the tradeoff, and the emotional relief everyone else wanted from the conversation.
The Not-So-Fast Decision Check interrupts that pattern. Not dramatically. Not with a long pause that makes everyone uncomfortable. Just enough to ask, “What’s actually happening here?” before you decide what role you’re going to play.
That small pause can change the next move. Maybe the situation does need a decision right now. Maybe it needs a recommendation, but not a final answer. Perhaps the real issue is that someone else needs to weigh in . Or maybe the best response is, “I can answer part of this now, but we need to separate what’s urgent from what still needs more thought.”
That’s not indecision. It’s better leadership under pressure.
Ask, “What is truly urgent here?”
The first question in The Not-So-Fast Decision Check is: What is truly urgent here?
This matters because pressure can make the entire situation feel urgent, even when only one piece needs attention now. A stakeholder may need an update today, but they may not need a final recommendation today. The team may need direction before the meeting ends, but the full decision may need one more person’s input. Someone may feel anxious about the uncertainty, but that doesn’t automatically mean everything has to be solved on the spot.
When a decision feels urgent, it helps to separate three kinds of urgency: true urgency, emotional urgency, and social urgency. These aren’t labels you need to memorize. They’re a practical way to figure out what’s actually driving the pressure before you respond.
True urgency
True urgency means something time-sensitive needs attention. There’s an actual deadline, risk, dependency, customer impact, or consequence if no one acts soon. The work may stall, a handoff may be missed, or a commitment may be affected.
When true urgency is present, the next move may be to act quickly. You may need to make the best decision you can with the information available. But even then, slowing down matters because you still need to understand what part of the situation needs action now.
For example, maybe the stakeholder really does need an answer by the end of the day. That doesn’t mean they need every detail solved. The true urgency may be that they need to know whether the team is still on track, what’s at risk, or when a fuller recommendation will be ready.
Emotional urgency
Emotional urgency is different. The situation feels urgent because someone is anxious, frustrated, disappointed, impatient, or uncomfortable with uncertainty. The pressure is coming from the emotional charge around the decision, not necessarily from the actual timeline.
This kind of urgency can be especially persuasive if you’re sensitive to tone, tension, or other people’s reactions. You may sense someone’s stress and feel pulled to make it better. Before you know it, you’re answering quickly because the room feels uncomfortable, not because the decision truly needs to be made right now.
Emotional urgency doesn’t mean the concern should be dismissed. It means the emotion needs to be separated from the decision. A useful response might be, “I hear that we need to move this forward. Before we decide, let’s confirm what has to happen today versus what can wait until we have the missing information.”
Social urgency
Social urgency comes from visibility, hierarchy, reputation, and expectations. You may feel pressure to answer because a senior leader is involved, because people see you as reliable, or because you don’t want to seem slow, difficult, or unprepared.
This kind of urgency often shows up as a fear of what your response will signal. If you ask for more time, will people think you can’t handle it? If you say no, will they think you’re not committed? If you point out a tradeoff, will you seem like you’re creating friction?
That pressure can make a rushed answer look like the safest answer. But speed isn’t the only way to show leadership. Sometimes the stronger move is to respond with confidence and a boundary around the decision, such as, “I can give you a quick reaction now, but I don’t want to treat that as the final recommendation. I’ll come back by 3:00 with a more useful answer.”
In the example meeting from the opening, “We need to know today” may include all three kinds of urgency. There may be a true timing issue because the stakeholder needs an update. There may be emotional urgency because people are nervous about the deadline. Social urgency may also be present because you don’t want to look like the person slowing things down.
The question “What is truly urgent here?” helps you sort through all of that. You’re not trying to prove the pressure is wrong. You’re trying to find the part that needs action now, so you don’t treat the whole situation like an emergency.
That distinction matters.
Once you know what’s truly urgent, the decision often gets smaller and more workable. You may realize the next move is to give a directional answer, confirm a timeline, ask for one missing piece of information, or name what can be decided now versus later. You’re still being responsive, but you’re no longer treating the whole situation as an emergency.
This is also where slowing down becomes practical. You’re not pausing to overthink. You’re pausing to find the part of the decision that actually needs movement now, so you can respond to that part without taking on more than the moment requires.
Ask, “Whose decision is this?”
Once you’ve sorted out what’s truly urgent, the second question in The Not-So-Fast Decision Check is: Whose decision is this?
This question matters because pressure has a way of making nearby decisions feel like your decisions. If you’re in the conversation, if you understand the issue, or if people are used to looking to you for direction, it’s easy to assume you should be the one to answer. But being close to a decision doesn’t always mean you’re the person who should make it.
Sometimes you own the decision. Sometimes you’re there to recommend, advise, execute, or point out the tradeoff. Other times, the decision belongs to someone with more authority, more context, or more accountability for the outcome.
This is especially important if you tend to step in when things feel messy. You may see what needs to happen before other people do, which can make it tempting to solve the problem yourself. But when you decide too quickly, you may unintentionally take over something that needed another person’s input or approval.
Check the role you’re being asked to play
Before you answer, ask yourself what role you’re actually in.
Are you being asked to make the final call? Are people asking for a recommendation? Do they need your expertise, your approval, your capacity, or your reassurance? Those are different asks, and they don’t require the same response.
For example, if the stakeholder needs an update today, you may be able to recommend what to say. But the decision to shift budget, change scope, or move a deadline may belong to someone else. In that case, answering too fast could put you in the wrong seat.
That doesn’t mean you leave people hanging. It means you help move the conversation forward without taking over a decision that should involve someone else.
You might say, “I can recommend the next step for today’s update, but the decision to change scope needs to sit with Alex.” Or, “I can speak to the team impact, but Jordan owns the final call on the timeline.”
Look at who owns the outcome
A useful way to answer “Whose decision is this?” is to ask who will live with the consequences.
Who has the authority to say yes? Who has the context you don’t have? Which person or team will be accountable if the choice creates cost, delay, risk, or extra work? If the answer points to someone else, your next move may be to involve them instead of deciding for them.
This question can also reveal when the decision needs shared ownership. Maybe you can decide one part, but another part requires approval. Perhaps you can recommend a path, but leadership needs to choose the tradeoff. Or maybe the team can move forward today, but the longer-term decision needs input from finance, legal, operations, or another stakeholder.
The point isn’t to avoid responsibility. It’s to place the decision where it belongs.
That’s a meaningful distinction for leaders who are used to being helpful. You can stay involved without becoming the default decision-maker for everything near you. You can contribute your judgment without absorbing authority that belongs somewhere else.
In the meeting example, the answer to “Whose decision is this?” might be, “I can recommend the update we send today, but I can’t decide whether the whole timeline changes.” That gives you a more accurate role. You’re not stepping away. You’re helping the group separate recommendation, authority, and execution before someone treats them as the same thing.
Ask, “What answer actually fits?”
The third question in The Not-So-Fast Decision Check is: What answer actually fits?
After you’ve sorted out what’s truly urgent and whose decision it is, you’re in a much better position to respond. You’re no longer answering the pressure around the decision. You’re answering the decision itself.
Pressure can make it seem like you need to give one clean answer right away. Yes, we can do it. No, we can’t. I’ll handle it. I’ll decide. Or I’ll get back to you. But many high-pressure decisions don’t call for a simple yes or no. They call for a response that matches the situation more precisely.
The answer may be partial
Sometimes the best answer is yes to one part and no to another. You might be able to give the stakeholder an update today, but not a final recommendation. Your team may be able to take the first step this week, but not absorb the full request without moving something else.
That might sound like, “We can give them a directional update today, but we shouldn’t commit to the full timeline until we confirm the resource impact.” Or, “I can take A and B, but C needs to wait or move to someone else.”
That kind of answer keeps things moving without pretending everything fits. It also helps people see the decision more accurately. Instead of treating the request as one big yes or no, you’re breaking it into pieces that can be handled honestly.
The answer may be conditional
A pressured moment can make a request sound fixed, but many decisions have conditions built into them. You can say yes if the timeline changes. You can say yes if another priority moves. Agreement may depend on budget, approval, staffing, risk tolerance, or a tradeoff that hasn’t been discussed yet.
This is where a more accurate answer might sound like, “Yes, we can do that if the launch date moves by one week.” Another version could be, “I’m comfortable recommending this if finance confirms the budget impact first.”
You’re not being difficult. You’re making the terms of the decision visible before people assume agreement.
The answer may be not yet
Not every delay is avoidance. Sometimes “not yet” is the answer that protects the quality of the decision.
You might not have enough information. The right person may not be in the room. A tradeoff may need to be discussed before anyone commits. In that case, a useful response could be, “Not yet. The next step is to confirm the impact on the team before we decide,” or, “I wouldn’t make that call today. I’d recommend we come back with two options by tomorrow.”
This still gives direction. It just doesn’t force a final answer before the decision is ready.
The answer may be not mine
Sometimes the answer that fits is, “I can help, but I shouldn’t be the one to decide.” That can feel uncomfortable if you’re used to being responsive, but it’s often exactly what the situation needs.
You might say, “I can outline the tradeoffs, but Alex needs to make the final call.” Or, “I can recommend the next step, but this decision belongs with the team that owns the budget.”
That keeps you involved in the right way. It also prevents your input from being treated as approval, especially when you don’t own the authority or the outcome.
The answer may be a next step
Sometimes the answer isn’t a decision at all. It’s the next move that makes a better decision possible.
That might sound like, “The next step is to confirm whether the stakeholder needs a final answer today or just an update.” Or, “Before we decide, we need to know what would have to move if this becomes the priority.”
This kind of response is often more useful than a rushed answer. It gives the group something to do, keeps momentum, and avoids locking everyone into a decision before the right pieces are on the table.
The point isn’t to make every answer complicated. It’s to avoid shrinking the decision into yes or no when the situation calls for something more specific. A better answer may be partial, conditional, temporary, collaborative, or simply not yours to make.
That’s how you keep pressure from deciding for you. You don’t have to rush into the fastest answer. You need the answer that actually fits.
Better decisions start with better questions
When everything feels urgent, it’s easy to think your value comes from having the answer right away. People are waiting, the situation feels tense, and you don’t want to be the reason progress slows down. So you move fast, even when part of you knows the decision needs more thought.
Better decision-making starts earlier than the answer. It starts in the moment when you slow down enough to ask, What is truly urgent here? Whose decision is this? What answer actually fits? Those questions don’t make the pressure disappear, but they do help you stop treating every pressured moment like it requires an immediate yes or no.
That’s the purpose of The Not-So-Fast Decision Check. It gives you a simple way to pause before pressure turns into overcommitment, unnecessary ownership, or a rushed answer you’ll have to unwind later. You’re not stepping out of leadership. You’re stepping into the part of leadership that knows how to respond with judgment instead of reflex.
In practice, this might mean giving a directional answer instead of a final one. It might mean saying yes to one part of the request and no to the rest. Maybe it means bringing the right person into the decision before everyone treats your input as approval. Or it may mean saying, “I can help move this forward, but we need to decide what’s changing to make room for it.”
That’s what slowing down makes possible.
You don’t have to become slow to be thoughtful. You don’t have to answer instantly to be trusted. And you don’t have to treat every urgent-feeling decision as if it belongs fully to you.
The next time a decision feels urgent, try not to start with, “What’s my answer?” Start with The Not-So-Fast Decision Check. Ask what’s truly urgent, whose decision it is, and what answer actually fits.
Those three questions can help you find the next right response before the pressure decides for you.
Need support with a high-pressure decision?
Some decisions are hard to sort through on your own, especially when the stakes feel high, the pressure is building, and the answer affects other people.
If you’re navigating a complex decision at work and want a calmer, more strategic way to think it through, a High-Stakes Decision Session can help.
Together, we’ll slow the situation down enough to sort through urgency, ownership, tradeoffs, and response options so you can move forward with more confidence and less second-guessing.
This is especially helpful when:
- you feel pressure to answer quickly
- the decision affects multiple stakeholders
- you’re stuck between competing priorities
- you keep replaying the decision in your head
- the answer isn’t as simple as yes or no