How do you prioritize your work? A framework-based answer

Why interviewers ask this question

Most roles involve more work than time. Hiring managers want to know you will spend your hours on the right things without being told every morning. They are also checking whether you can communicate trade-offs clearly, because poor prioritization that goes unannounced causes missed deadlines and broken trust.

The question appears in interviews for individual contributors, managers, and senior leaders alike. The expected depth of your answer scales with the seniority of the role, but the core logic is the same at every level.

Three frameworks you can use

Pick one framework, learn it well, and apply it consistently in your answer. Mixing three frameworks in one response sounds rehearsed and confusing. Below are the three most commonly recognized options in 2026.

• Eisenhower Matrix: Sort tasks into four quadrants by urgency and importance. Do urgent-and-important tasks now. Schedule important-but-not-urgent tasks. Delegate urgent-but-not-important tasks. Drop the rest. This works well for roles with high email and meeting volume.
• MoSCoW method: Label each task Must have, Should have, Could have, or Won't have for this period. Common in product and project management roles. It forces explicit trade-offs and is easy to explain to non-technical stakeholders.
• Impact-effort matrix: Plot tasks on a two-by-two grid of impact versus effort. Start with high-impact, low-effort tasks to build momentum. Deprioritize low-impact, high-effort tasks. Useful in engineering, marketing, and operations roles.

A step-by-step method that works across frameworks

Regardless of which framework you name, your answer should describe a repeatable process. Here is a four-step method you can adapt to any role.

1. List everything on your plate. Write it down rather than keeping it in your head. This takes two to five minutes and prevents tasks from being forgotten.
2. Score each item by impact and deadline. Ask: what happens if this is late? Who is blocked? What is the business cost? A task that blocks three colleagues is higher priority than one that only affects you.
3. Communicate your order to your manager or stakeholders before you start. A quick message like 'I am planning to finish X today and move Y to Thursday, does that work for you?' prevents surprises.
4. Reassess when something new arrives. New requests do not automatically go to the top of the list. Ask the requester for the deadline and the consequence of delay, then slot it in accordingly.

A concrete example answer you can adapt

Use the STAR format: Situation, Task, Action, Result. Here is a full example for a project coordinator role. Adapt the details to your own experience.

Situation: 'In my last role at a mid-size logistics company, I was managing three client onboarding projects simultaneously when a fourth urgent request came in from our largest account.'

Task: 'I needed to decide what to delay without damaging any client relationship or missing a contractual deadline.'

Action: 'I listed all open deliverables and scored each one by deadline and the cost of being late. Two items had hard contractual dates, so those stayed at the top. I identified one internal reporting task that could move by two days without any external impact. I messaged my manager with the proposed change before acting, and she approved it in ten minutes.'

Result: 'All four clients received their deliverables on time. The internal report was delivered two days late with no consequence. My manager later used the same scoring approach with the wider team.'

Notice that the example is specific: it names the number of projects, the type of role, the stakeholder consulted, and the outcome. Vague examples like 'I had a lot going on and I figured it out' do not land.

Common mistakes to avoid

Even candidates with strong prioritization skills lose points by answering this question poorly. Watch for these patterns.

• Saying you do everything at once. Multitasking is not prioritization. It signals you have not thought about trade-offs.
• Claiming you never miss deadlines. Interviewers know this is not true. A better answer acknowledges that trade-offs exist and explains how you manage them.
• Forgetting to mention communication. Prioritization without stakeholder alignment is just personal preference. Always include the step where you tell someone.
• Using a framework name without explaining it. Saying 'I use the Eisenhower Matrix' means nothing if you cannot describe what goes in each quadrant.
• Giving an example with no measurable outcome. End your STAR story with a result, even a small one.

How to practice before the interview

Practicing out loud is the single most effective preparation method. Reading your answer silently feels smooth but speaking it reveals filler words, unclear transitions, and timing issues.

Time yourself. A good answer to this question runs between 90 seconds and two and a half minutes. Under 60 seconds is too thin. Over three minutes loses the interviewer.

Break-In Bad's interview assistant listens to the interviewer's questions in real time and surfaces relevant talking points only you can see, even on a shared screen. If you blank on which framework to mention or forget a step in your example, the assistant can prompt you without the interviewer knowing. It works on video calls and in-person interviews where you have a device nearby.