Check Understanding When Every Task Feels Urgent

An employee tells you every task on their list is urgent. You have five minutes before your next meeting, and the easy move is to nod along and let them handle it however they want. That does not solve anything. A list of five urgent items usually contains different deadlines, different consequences if something slips, and requests from people with very different amounts of authority. Sorting that list is not only a skill you are teaching the employee. It is a decision you need to make with them, before the wrong task gets finished first.

Why This Conversation Goes Wrong

Most managers handle this one of two ways, and both fail. The first is to say something like "just use your best judgment" and walk away. That sounds like you are building independence, but you are actually handing off a decision the employee does not have enough information to make. They do not know which director's request is genuinely time sensitive this week and which one is routine. You do.

The second failure is the opposite. The manager grabs the list, reorders it themselves, and hands it back without asking a single question. That fixes the immediate problem but teaches the employee nothing. Next week they will bring you the same tangle of urgent items, because they never learned what made one item more urgent than another. The goal is not to pick the order for them forever. It is to show them the questions that produce the order, so eventually they can answer those questions on their own and only escalate the genuine conflicts.

There is also a quieter version of this problem. An employee who feels like everything is urgent is often carrying a conflict that only you can resolve, such as two people at different levels both expecting to be first. Asking them to sort that out alone is not delegation. It is avoidance dressed up as trust.

How to Prepare Before You Sit Down

Do not have this conversation from memory. Ask the employee to bring the actual requests, including the date each one is due and the name of the person waiting on it. A due date without a name attached is easy to inflate. A name attached to a date is much harder to argue with.

Before the meeting, think through two things yourself. First, what actually happens if each item moves by a day. A dashboard that supports a Thursday meeting has a real deadline. A request that has been sitting for two weeks with no follow up probably does not. Second, whether any of these requests came from someone whose authority the employee is likely to overestimate or underestimate. A senior title attached to a request often gets treated as automatically first in line, even when the actual deadline is soft. You want to walk in already knowing where that assumption is going to show up.

What to Say When You Meet

Manager Rosa sat down with Eli and started with the list itself. She said, "You told me the dashboard, the interview packet, the vendor reply, and the forecast are all urgent. Let's go through each one. When does the dashboard actually get used?"

Eli answered, "The operations meeting is Thursday morning. The forecast is due Friday, and the vendor is waiting on an answer from us today."

Rosa said, "Then reply to the vendor before noon, finish the dashboard by Wednesday afternoon, and set the interview packet aside for now. I will let recruiting know we need a few more days. Does that order make sense to you?"

Eli replied, "Honestly, I thought the packet had to come first, since it came from a director."

That last line is the real payoff of the conversation. Rosa now knows exactly where Eli's mental model breaks down, and she can fix it directly. She said, "A request from a director matters, but a title alone does not outrank a same day answer to a vendor. Next time you have two deadlines pulling against each other, send them both to me with your proposed order. I will tell you within the hour if I see it differently."

Notice what Rosa did not do. She did not ask Eli to guess again, and she did not just hand back a corrected list without explanation. She named the actual rule, date, consequence, and who is waiting, and gave Eli a concrete way to escalate the next real conflict instead of silently guessing at it.

Mistakes to Avoid

A few habits turn this conversation into a wasted five minutes instead of a real fix. Skipping the question of what happens if a task slips is one of them. Without that question, every item on the list sounds equally urgent, because urgency is being asserted instead of tested.

Reordering the list without asking why the employee had it wrong in the first place is another. You lose the chance to correct the actual reasoning error, which means the same mistake shows up again next month with a different set of tasks.

Treating this as a one time fix is a third mistake. If you resolve today's conflict but never set up a signal for the next one, you will have this exact conversation again in two weeks, and the employee will still be guessing in between.

Finally, watch for the manager who resolves the list but never checks whether the order actually held. If you tell someone to reply to the vendor first and finish the dashboard second, follow up and see if that is what happened. If it did not, you need to know why, and so does the employee.

How to Practice and Score It

This conversation is easy to get wrong live, because it happens under time pressure and the employee is usually a little anxious about disappointing someone. That makes it a good one to rehearse before you need it for real. DealSpeak lets you run through this exact scenario with an AI counterpart playing the employee, then scores how well you pulled out date, consequence, and owner for each item, whether you actually resolved the conflict instead of pushing it back, and whether you gave the employee a clear rule for the next time competing deadlines show up.

You can find this scenario along with other manager conversations in HR and Leadership practice conversations. If you want to see how a related pattern plays out in a different setting, Explore the Gap Between Stated Values and Meeting Behavior looks at what happens when stated priorities and actual behavior in the room do not match. And if the issue with your team is less about competing deadlines and more about a leader who inserts themselves into everything, Help a Leader Separate Visibility From Useful Involvement covers that pattern directly.

At the end of the week, pull up the order you agreed on and compare it to what actually got done. Mark which items were genuinely time bound and which ones only sounded urgent when the employee first brought them to you. Ask them to explain one choice back to you using date, consequence, and owner. If they can do that under pressure, the method has actually stuck.

What Changes When You Do This Well

A priority conflict between five tasks is not a test of the employee's willpower. It is a question about deadlines, consequences, and authority, and only you have all three answers. Once you give the employee a clear way to escalate the next real conflict, most of these conversations get shorter, and the ones that remain are the ones actually worth your time.