6 steps
- Write the competing tasks down with their deadlines and who asked.
- For each, ask: what happens if it is late by a day? By a week?
- Rate impact: revenue, customers, safety, a team blocked.
- If two people's requests conflict, ask them, or your shared manager, to decide the order.
- Commit to an order and block time for the first item.
- Tell the people whose task moved, with a new date.
Example
| Task | If late | Impact | Decision |
|---|---|---|---|
| Client bug fix | Client can't bill today | High | Do first |
| Board slides for Friday | Can wait two days | High | Schedule Wednesday |
| Colleague's data request | Minor delay | Low | Offer Thursday or delegate |
Interview answer: "How do you handle competing priorities?"
"I list the tasks with their deadlines and impact, sort them by urgency and importance, and if two stakeholders conflict I ask them or my manager to agree on the order. Then I communicate new dates. Last quarter, that let me ship a client fix the same day and still deliver the board report on time."
PMI's guidance separates the same two axes: priority (importance) is not the same as urgency (PMI).
Cronos, by Gambit Studio, puts competing tasks side by side on iPhone or iPad in four quadrants by urgency and importance, which is often all it takes to see which one wins.