They say
What to say when an employee says “No one told me it was a priority.”
When an employee says nobody told them it was a priority, examine what you actually communicated and how the work ranked against competing commitments. Correct any ambiguity, then agree how priority conflicts will be raised.
Your response
“Let’s look at what I actually communicated. If I didn’t make the priority and trade-offs clear, that’s mine to correct. We also need a better way for you to flag competing priorities before work is missed.”
First, check this
Did you clearly rank this work against the employee’s other commitments, or did you call it important while saying the same about everything else?
Why this works
Calling work important is not the same as ranking it against other commitments. The manager must check whether the employee received a usable priority decision. The employee also has a responsibility to raise conflicts before work is missed. This keeps the page about priority signalling; a claim that the requirements themselves changed belongs to the next conversation.
Don’t say
“It should have been obvious.”
If they push back again
“Everything you give me is marked urgent.”
You could say
That’s fair, and it’s mine to fix. From now on I’ll rank new work against what you already have. If I forget, ask me which comes first.
After the conversation
- Set up a simple ranked list of the employee’s current work and update it whenever you add something new.
- Agree on how the employee should flag a clash between priorities, and reply to those flags within a day.
- If the priority was yours to make clear, tell the people affected by the missed work that the gap was on your side.
Questions managers ask
How do I communicate priorities so nothing gets missed?
Put the work in order instead of labeling it. Calling a task important means little when everything else is important too, so rank it, say what can slip if there’s a conflict, and repeat the order whenever you add something. A short written list works better than a passing mention in a busy meeting.
What if I did say it was a priority but buried it in a long message?
You told them, in a way that was easy to miss. Accept your share of the miss, and next time put priorities first, on their own, with a date. It’s still fair to expect the employee to read carefully and ask when they’re unsure.
Should employees ask before assuming what’s most important?
When two pieces of work genuinely clash and the stakes are real, they should ask. Tell your team you want a quick question rather than a guess, and make it easy by answering promptly. If getting an answer from you takes three days, people will reasonably keep guessing.