# Managing Conflicting Priorities: How to Decide What Comes First Canonical URL: https://headwayskills.com/knowledge/time-management/managing-conflicting-priorities/ Markdown URL: https://headwayskills.com/knowledge/time-management/managing-conflicting-priorities.md Entity type: Article Last updated: 2026-07-07 Language: en Primary audience: professionals improving time management at work Owner: Headway Skills Contact: https://headwayskills.com/contact/ ## Short answer Two requests, both urgent, one of you. Practical ways to rank the work, renegotiate a deadline, and hand the decision back to the person who owns it. ## Key facts - Title: Managing Conflicting Priorities: How to Decide What Comes First - Category: Time Management - Primary skill: Time Management - Related skills: Working with Your Manager, Communication - Primary keyword: managing conflicting priorities - Source page: https://headwayskills.com/knowledge/time-management/managing-conflicting-priorities/ ## What this page covers - Two requests, both urgent, one of you. Practical ways to rank the work, renegotiate a deadline, and hand the decision back to the person who owns it. - Practical guidance for managing conflicting priorities - How this topic connects to Time Management ## Detailed explanation Two people have asked you for something, both said Friday, and both are sure theirs is the one that matters. Managing conflicting priorities means separating urgency from importance, confirming which piece of work actually outranks the other, and renegotiating the rest openly instead of absorbing the collision in silence. Most of these conflicts are not a scheduling failure on your part — they are an unresolved decision that belongs to whoever handed out the work. It rarely feels that way at the time. It feels like evidence that you are not organized enough, or fast enough, or senior enough to keep up, which is why so many people go quiet and try to solve it privately with a longer evening. The questions below are the ones people actually ask once they get there. ## What counts as conflicting priorities — and is it your fault you have them? Conflicting priorities are two or more pieces of committed work that cannot all be finished in the time available — which is different from a long to-do list. A long list is a volume problem you can work through; a conflict is a choice somebody has to make. Teamly and Epicflow both trace them to sources outside the individual: fixed constraints, requirements that changed after the work was assigned, stakeholders whose needs genuinely compete, and external events nobody scheduled. If you diagnose the situation as a personal discipline problem, you reach for the wrong fix — working faster, staying later — and the conflict comes back next week with different names on it. Diagnosed correctly, it points at a decision to be surfaced rather than a habit to be repaired. ## How do you decide what comes first when everything looks important? The most-cited tool across this topic is Eisenhower's Urgent/Important Principle, which Mind Tools recommends for deciding whether something genuinely has to happen now. Its usefulness is in a distinction most of us collapse under pressure: urgency is a property of a deadline, importance is a property of consequence. When everything on your list looks equally critical, it usually means you are looking at two urgent things rather than two important ones. A practical way in: for each task, ask what actually happens if it slips by two days. Not how it feels — what breaks, who is blocked, what the organization loses. Rank by that answer, and let the deadlines set the order inside the ranking rather than driving it. The limitation: this works once you know the relative importance — which is often exactly what you are missing, because it lives with whoever assigned the work. ## What do you do when two people both say their work is the urgent one? You hand the conflict back. Office Dynamics, writing for assistants who support several leaders at once, gives the clearest version of this: ask the group to agree the order among themselves and then tell you, and set up a regular short huddle where the week's priorities get settled collectively. The point is not passivity: you are not the right person to arbitrate between two people who both outrank you. Ask a Manager has fielded this for years, and the recurring failure mode in those letters is not conflict — it is silence. The employee guesses, picks one, and is later held accountable by the other for a decision they were never authorized to make. So say it out loud, and say it early. Name both commitments, state plainly what you can deliver in the time you have, and ask which one takes the slot. That is one uncomfortable sentence in exchange for a decision you can point back to later. ## How do you renegotiate a deadline without looking like you can't handle the job? Mind Tools frames this as a negotiation rather than a confession, and suggests aiming for an outcome both sides can live with. It offers two concrete moves. You can push the date back. Or you can deliver the work in smaller pieces — the more useful of the two, and the one people forget: a partial delivery on the original date often satisfies a requester who needed something to start from rather than the finished thing. Timing does most of the work here. A deadline reopened on Monday reads as planning. The same conversation on Thursday afternoon reads as a problem being dropped on someone. Nothing about the request changes — only how much room the other person has to respond. Arrive with a proposed sequence rather than an open question. "I can have the draft to you Wednesday and the full version Monday, unless you'd rather I flip the order" gives the other person something to approve. "I'm swamped" gives them a problem to solve. ## What if your manager just says "do both"? Sometimes that is fair and the two things really do fit. More often the tradeoff has not been made visible yet, because "I have a lot on" tells a manager nothing they can act on. Make the cost concrete. Not that you are overloaded, but what specifically would have to move: which piece of work slips, by how long, and who notices. A manager who hears "both, then" to a vague complaint will usually answer differently when the sentence is "I can do both if the client summary waits until Thursday — is that acceptable?" You are not refusing; you are asking them to spend something, which is what a priority decision is. Escalate when the two requesters are peers who will not resolve it between them, or when the consequence of guessing wrong is larger than the awkwardness of asking. Below that, decide and move. ## Can you say no at work — and how, without damaging the relationship? Yes, and it gets easier once you have delivered enough to have some credit in the account. The part that protects the relationship is having a real reason and giving it: that it is not yours to authorize, that it cannot be done in the time, that someone else is better placed, that you need a day to decide. A no with a reason attached is heard as judgment. A bare no is heard as refusal. A conditional yes is frequently the better move anyway — yes to this, if that moves — because it keeps you in the problem rather than outside it. If the awkward part is not the ranking but the saying, that is worth noticing. It is a common reason capable people stay stuck between two deadlines, and it is learnable rather than a limit on your character. If you are not sure whether the sticking point is your organization or those conversations, it is worth [seeing where your habits stand](https://assessment.headwayskills.com/) before you fix the wrong one. ## How do you stop new work from becoming a conflict in the first place? Almost every guide on this topic starts after the collision exists. The more useful moment is earlier, when you accept the work. Four things are worth pinning down before you say yes: who is actually asking, what exactly is being asked for, when it is genuinely needed rather than "ASAP," and what counts as finished. This is not bureaucracy. A large share of apparent priority conflicts are really ambiguity conflicts — two tasks look equally urgent precisely because neither was specified well enough to compare. Mind Tools adds the other half: manage expectations in the same conversation where the work is offered — state what you are already carrying and agree a completion date against it, rather than accepting first and discovering the clash later. And if you routinely take work from several people, Monster suggests asking each of them to rank their own requests on a shared urgency scale up front, which settles much of this before anyone collides. ## How do you answer "how do you handle conflicting priorities?" in an interview? It is a standard behavioral question, and both Indeed and RemoteRocketship publish sample answers built around a specific past situation rather than a general philosophy. What the interviewer is testing is narrower than it looks: they want evidence of a decision process and of communication with the people affected. They are not checking whether you managed to finish everything. So pick one real collision and walk through it in order: what the two demands were, how you worked out which mattered more, who you checked that with, and what you ultimately delivered and what you moved. Naming what slipped is a strength, not an admission — it shows you made a choice instead of quietly dropping something. Read back over those answers and the calendar barely appears in any of them. Nearly every one turns on something said to another person: a question asked before accepting, a sequence proposed, a deadline reopened, a tradeoff made visible. ## What makes this easier the next time it happens That is where the real difficulty sits, and it is a set of behaviors rather than a temperament — which means it responds to practice. **Time Management** is the obvious one, but the part that matters here is not the folder system. It is the front door and the ranking rule: pinning down who is asking, what is actually wanted, when it is truly due and what "done" means, before the work is on your plate. Alongside that: separating important from urgent, and knowing your legitimate reasons for declining, so a no is something you can explain rather than dread. **Working with Your Manager** is what turns a stuck week into a resolved one. Aligning on priorities, agreeing how much you are expected to decide alone before you check, and raising a conflict early with a proposed sequence attached — all of it reads as partnership rather than complaint. Most managers would far rather hear about a collision on Monday than a missed deadline on Friday. **Communication** decides whether any of it lands. A tradeoff is a conversation, not an email — the medium matters when someone might be disappointed. Leading with the constraint rather than burying it under apology, being specific about what will move, disagreeing with a request without making it personal: this is what separates "reliable, and told me early" from "difficult." None of the three is a fixed trait, and none is unusual. They sit inside **a wider group of twelve skills that turn up in almost any job**, and a free Job Skills Test measures all of them — so rather than guessing which of the three above is costing you, you can [find your weakest link](https://assessment.headwayskills.com/) and start there. ## Where that leaves you Some of this may already describe how you work. You might already ask when something is genuinely needed, or quietly push back on an "ASAP" that isn't one. The rest is not a different personality; it is a small number of moves you can add without becoming louder or more difficult than you are. The demands also tend not to get simpler: as you take on more, the number of people with a claim on your week grows, which is an argument for building the habit now, while the stakes are small, rather than under real pressure. And you have already done the less obvious thing — you went looking for a method rather than just working later into the evening. What is left is a question about you specifically, not about the situation: which of these you are already strong at, and which one is quietly costing you. That is not something to guess at. The Job Skills Test is a **free** self-assessment of your work skills: about seven minutes of questions, and it shows you where you stand across all twelve, including the three above. It will not have the difficult conversation for you. It will tell you which one you have been avoiding, and which skill to put your effort into first. **[Take the test](https://assessment.headwayskills.com/)** Free, and your results appear the moment you finish. ## Who this is for - Professionals building practical workplace skills - Readers looking for specific, usable work advice - Managers, educators, and coaches supporting career readiness ## Common questions ### What is this guide about? Two requests, both urgent, one of you. Practical ways to rank the work, renegotiate a deadline, and hand the decision back to the person who owns it. ### Which Headway skill does this connect to? This guide connects primarily to Time Management. It also relates to Working with Your Manager, Communication. ### What is the recommended next step? Use the free Work Skills Test to reflect on which work skill to improve next. ## Related pages - https://headwayskills.com/knowledge.md - https://headwayskills.com/knowledge/time-management.md - https://headwayskills.com/knowledge/working-with-your-manager.md - https://headwayskills.com/knowledge/communication.md - https://headwayskills.com/work-skills-test.md ## Citation guidance Use the canonical page when citing this content: https://headwayskills.com/knowledge/time-management/managing-conflicting-priorities/ Preferred summary: "Two requests, both urgent, one of you. Practical ways to rank the work, renegotiate a deadline, and hand the decision back to the person who owns it." ## Change log - 2026-07-07: Content collection version published.