how to answer how do you prioritise your work

by Wistkey · 5 august 2026 · 6 min read

a list of productivity apps is not a strong answer to "how do you prioritise your work?" the interviewer wants to hear how you make decisions when several tasks matter at once. give them a clear method, then prove that you have used it.

this question tests more than organisation. it shows whether you understand what matters to the role, notice risks before they become problems and keep other people informed when priorities change. your answer should make your judgement visible.

use impact, deadline, dependency, communicate

build your answer around four checks:

• impact — which task matters most to the customer, team or business outcome?
• deadline — what has a fixed due time, and what would happen if it slipped?
• dependency — is someone else waiting for your work before they can begin?
• communicate — who needs to know about the order, a trade-off or a possible delay?

this is stronger than saying you do the most urgent task first. urgency can be noisy. a request that arrived five minutes ago is not automatically more important than work that protects a customer, unlocks a colleague or prevents a serious risk.

start with your method, not your morning routine

open with one direct sentence: "i prioritise by comparing impact, deadlines and dependencies, then i confirm any trade-offs with the people affected." that gives the interviewer a useful headline before you add detail.

you can mention a task list, calendar or project board, but keep the tool in a supporting role. the important part is the decision you make with the information in front of you. explain how you review the plan when new work arrives rather than pretending the first plan never changes.

prove it with one example

after your headline, use a short example. the star method will keep it focused: set up the competing demands, explain your responsibility, spend most of the answer on your decisions, then finish with the result.

choose an example where at least two real priorities competed. perhaps you had a customer deadline while a colleague needed information, or coursework was due during a volunteering event. a busy week by itself is not evidence. the useful part is how you compared the work and what you did next.

make your own contribution unmistakable. say "i checked", "i reordered" and "i told" rather than hiding every action inside "we". you can still show teamwork by explaining whom you consulted and how your decision helped them.

a sample answer you can adapt

"i prioritise by looking at impact, fixed deadlines and whether anyone else is blocked by my work. in my last role, i had to finish a customer report on the same afternoon that an urgent data request arrived from another team. i checked the report deadline and found that the account manager needed my final figures by 2 pm, while the other team needed only one section of their request to start their work. i sent that section first, agreed when they would receive the rest, then completed and checked the customer report. both teams had what they needed at the promised time, and i updated my task board so everyone could see the status. that experience reinforced the value of making trade-offs visible instead of silently trying to do everything at once."

do not memorise that wording. replace it with a situation you can discuss honestly. a genuine example is easier to deliver naturally and easier to defend when the interviewer asks a follow-up question.

show what happens when priorities change

good prioritisation is not stubbornly following a list. explain that you reassess when the facts change. if a safety issue, customer problem or immovable deadline appears, you check its effect, adjust the order and tell the people whose work will move.

avoid promising that you simply stay late until everything is done. that skips the judgement the question is testing. a better answer shows that you raise conflicts early, offer options and agree what success looks like when time or capacity is limited.

adapt the answer to the role

read the job description and borrow its priorities, not its sentences. in customer service, you might balance customer harm, response targets and accurate records. in a project role, you might focus on delivery milestones, dependencies and risk. in healthcare or other safety-critical work, follow the role's established escalation and safety procedures rather than inventing your own hierarchy.

if you have little paid experience, use study, caring responsibilities, volunteering or a group project. the interviewer needs evidence of your decisions, not a particular job title. choose a moment with a clear constraint and a result you can explain without exaggeration.

practise the answer in two lengths

prepare a short version that takes about a minute and a fuller version with more detail. say both aloud. listen for the point where your setup becomes longer than your action, then trim it. your decision process should be the centre of the answer.

finish with the result and what you learned. then stop. a clean ending sounds more assured than adding another method, app or example because the silence feels uncomfortable. if pressure makes you rush, use the same pause-and-plan habits from our guide to answering questions about stress and pressure.