This question comes up in almost every interview for roles that involve a workload — which is most of them. What interviewers are listening for is not a list of productivity tools. They want evidence that you can make sound judgements about what matters most, communicate those judgements to stakeholders, and actually follow through.
Why interviewers ask this question
Poor prioritisation is one of the most common causes of underperformance in professional roles. When someone fails to deliver, it's often not because they worked too slowly — it's because they worked on the wrong things. Interviewers want to know your approach to avoiding that problem.
They're also probing for:
- Judgment — can you tell the difference between urgent and important?
- Communication — when you can't do everything, do you tell someone?
- Reliability — do you have a system, or do you just react to whatever shouts loudest?
Useful prioritisation frameworks
You don't need to name-drop a framework in your answer, but knowing them helps you think clearly and give a specific, structured response.
Importance vs urgency (Eisenhower Matrix). The most durable tool. Separate what's genuinely important (long-term value, consequences if missed) from what feels urgent (someone is asking now). Most people live in the urgent-not-important quadrant. The best performers protect time for important-not-urgent work.
MoSCoW method. Used in project management: Must Have, Should Have, Could Have, Won't Have. Good for getting clarity on scope when you have competing requests from multiple stakeholders.
Impact vs effort. When picking between tasks of similar urgency, favour high-impact, low-effort work first. A five-minute task that unblocks a colleague has enormous leverage.
Pick the one that genuinely reflects how you work and build your answer around it.
How to structure your answer
Use three parts: your system → a real example → how you handle shifting priorities.
Describe how you actually organise your work day-to-day (not aspirationally). Then give a specific instance of competing priorities and how you resolved it. Finish by acknowledging that priorities shift, and show that you handle that by communicating proactively rather than just quietly switching tasks.
Sample answers
General professional role
"I start each week by listing everything I have on, then sorting by two dimensions: what the consequences are if it's late, and what's time-sensitive because someone else is waiting on me. High-stakes, deadline-sensitive items go first. I protect the first two hours of each day for heads-down work on those — no meetings, no messages if I can help it.
When something new lands mid-week, I ask myself: does this displace anything on my current list? If yes, I flag it to my manager or the person who asked rather than just absorbing it quietly and delivering everything late. That conversation is usually quick — often the new thing can wait a few days, or something on the existing list can.
A concrete example: last quarter I had a board presentation to prepare, an urgent client deliverable due two days before, and a teammate who needed help with a project I'd been involved in. I blocked two days for the client work, let my colleague know I could review their draft on the Thursday rather than immediately, and got the board pack done on the Friday with a day to spare. None of it slipped because I was explicit about the sequencing upfront."
Senior or manager-level role
"At a team level, I use a version of importance-urgency sorting. I try to protect the team's time for the work that moves the needle — not just what happens to be shouting loudest. I've found that a lot of reactive work can actually wait 24 hours without consequence, but it crowds out the strategic work that's harder to recover from if it slips.
In practice: each Monday we spend 15 minutes as a team aligning on the week's priorities. It's a brief sync but it means everyone knows what the blockers are, what's been promoted in urgency, and what we've consciously deprioritised. When something genuinely changes mid-week — which it does — I make the call on what drops or gets delegated, and I tell the relevant stakeholder immediately rather than hoping I can absorb it.
The biggest priority mistake I see is treating everything as equally urgent. Part of my job is making that call so the team doesn't have to — and so we're spending our limited time where it actually matters."