Prioritization questions ask how you decide what gets done first and, more revealingly, what does not get done at all. A strong answer shows the criterion you used, what you cut or delayed, who you told, and what happened next. This page gives the questions for your own workload, saying no, changing priorities and defending a call afterwards, with sample answers and the differences for people managers, product managers and project managers.
Table of Contents
- 13 Prioritization Interview Qu...
- How the interview is evaluated
- What prioritization questions ...
- How you prioritize your own wo...
- Deciding what not to do
- Saying no to someone senior
- When priorities change mid-pla...
- Defending the call afterwards
- Should you name a framework?
- How the question differs by ro...
- Choosing your stories
13 Prioritization Interview Questions and How to Answer Them
Question 1
When everything on your list feels urgent, how do you choose where to start?
What it tests
Whether you apply a criterion before you start, rather than working through whatever arrived last or whoever is loudest.
What a strong answer includes
Names the test you use to separate urgent from merely loud (someone outside the room waiting on a date, harm if it waits a day, a task that unblocks other people), shows you checking one assumption with the person who raised an item, and gives one real morning or week where that test pushed something visibly to the bottom of the pile.
Sample answer
I ask one question of each item: who is stuck, and for how long, if this waits until tomorrow. On the first morning of the school year, as the assistant principal responsible for operations, I had an unconfirmed bus route, eleven parent emails about class placements, a substitute needed for a teacher who had called in sick, and a request from the district for enrollment numbers. The bus route and the substitute had children waiting on them that morning, so they came first, and both were settled before first period. The enrollment figures were due Friday, so I blocked an hour on Wednesday. I answered the placement emails with one short note saying placements were fixed for two weeks and I would review requests after that, which closed most of the threads. Nothing that could wait got my first hour.
Question 2
Walk me through how you plan and prioritize a typical week.
What it tests
Whether your planning is a routine you actually run, with room for the interruptions your role guarantees, and whether it protects work that matters but never feels urgent.
What a strong answer includes
Describes a specific routine with a time and an input (when you plan, what you look at, how many things you commit to), says how much of the week you leave open for what you cannot predict, names the important but never urgent item you protect and how you protect it, and admits what gets pushed first when the week goes wrong.
Sample answer
I manage a hospital unit with about forty staff, and most of my week is interruptions, so I plan for them. On Monday before the morning huddle I look at three things: staffing gaps for the next fourteen days, anything with an outside date that week, and the one-to-ones I owe. I commit to no more than three things beyond keeping the unit staffed, and I keep the afternoons mostly open because that is when problems arrive. The thing I protect is one-to-ones with my charge nurses, because they never feel urgent and they are the first thing to vanish. I book them at the start of shifts rather than the end, when they would get canceled. When a week goes badly, the first thing I push is paperwork with a soft date, and I tell whoever is waiting on it that day instead of letting it slide quietly.
Question 3
You have three deadlines landing on the same day. What do you do?
What it tests
Whether you test which deadlines are really fixed and renegotiate early, rather than attempting all three and missing one without warning.
What a strong answer includes
Starts by checking which dates are truly fixed and what depends on each, moves or splits one of them by asking early rather than hoping, says who you told and when, and uses a real case in which you actually renegotiated a date, not one where you stayed late and everything happened to land.
Sample answer
I start by asking what depends on each date, because that tells me which ones can move. As a payroll coordinator I once had the monthly payroll run, a benefits file for our insurer and a headcount report for finance all due on the same Thursday. Payroll could not move, because people are paid on that date. The insurer accepted the file any time within a week, so the Thursday date was ours, not theirs. The headcount report was for a meeting the following Monday. On Monday I told the finance lead the report would arrive Friday morning, with the reason, and she was fine with it. I moved the benefits file to the next Tuesday after checking the window myself. Payroll ran on Thursday with nothing competing for my attention. The mistake I try not to make is treating every date I am given as equally fixed.
Question 4
Tell me about a request you turned down so the team could finish something more important.
What it tests
Whether you can refuse a reasonable request on a stated basis and keep the relationship with the person who asked.
What a strong answer includes
Makes the request sound worth doing, states the criterion that ranked it below the work you protected, describes the conversation with the person who asked (what you said, what you offered instead, when you would revisit it), and says what became of the request later.
Sample answer
I ran programs at a regional food bank, and in the spring a board member asked us to add a weekend distribution at a new church site. It was a good idea and the need was real. But we were six weeks from moving our partner pantries onto a new ordering system, and that move decided whether forty pantries could order at all over the summer. A new site would have taken my two coordinators off the move for most of those weeks. I met the board member in person rather than replying by email, said yes to the site and no to the timing, and showed her the one-page plan for the move with its dates. I offered to scope the site with the church in August and bring it to the September board meeting. The ordering system went live on time, and the weekend site opened in October.
Question 5
How do you tell your team you are stopping work they care about?
What it tests
Whether you can take work away from a team without losing its trust, by giving the real reason early and saying what happens to what they built.
What a strong answer includes
Gives the real reason in person as soon as you know it, says plainly whether the work is ending or only pausing so nobody waits for a restart that will not come, makes clear what happens to what they already built (reused, handed on, or archived where it can be found), and shows that you kept whatever you promised about it.
Sample answer
I managed the installation team at a city history museum. The director had given us a temporary exhibition on the river's old shipyards, and for four months my five technicians built the cases, the mounts and a full scale section of a wooden hull in our workshop. It was the most ambitious build they had done. Eight weeks before opening, the family that owned most of the objects withdrew the loan, and the director canceled the exhibition. I heard at four in the afternoon and told the team in the workshop before they went home, because I did not want them to hear it in the corridor the next morning. I gave them the real reason and said it was canceled, not postponed, so nobody spent the next year waiting for it to come back. Then I went through what would happen to what they had made. The hull section went into the children's gallery that spring, three of the cases were reused in the permanent galleries, and the rest were stored with their drawings for later shows. I asked the director to credit the team on the hull's label, and she did.
Question 6
How do you say no to a senior leader who wants their work done first?
What it tests
Whether you can put the cost of a senior request in terms that person cares about and let them make an informed call, rather than refusing outright or silently absorbing it.
What a strong answer includes
Says no plainly to doing the request on top of everything else, leaves the request as the leader framed it instead of shrinking it to fit, states what it would move in terms that person answers for (a date they promised, money, customers), makes clear the choice is theirs, and describes how you recorded the decision and who you told once they made it.
Sample answer
I was project manager for a general contractor building a six story apartment block. With the frame up, the developer's managing director asked us to fit out the ground floor café unit five weeks early, because a tenant wanted to open before the holidays and would sign a longer lease if we could. He wanted the full fit-out, and I did not try to talk him into a smaller version. I told him we could not do it and still hold the rest of the schedule, because the same electricians and finishers were booked on the upper floors. Then I put the cost in his terms: the café early would move the handover of floors two and three by four weeks, so twelve buyers he had promised March keys would get them in April, and his sales team would have to tell them. I gave him both schedules on one page and said the choice was his. He chose the café. I recorded the decision and the new residential date in that week's owner report, and the next morning I walked his sales manager through the new dates so the buyers heard from her first. The café opened in December, and floors two and three were handed over on the April date.
Question 7
Two people above you each say their project comes first. What do you do?
What it tests
Whether you bring a conflict between senior people to the people who can resolve it, instead of choosing alone or trying to satisfy both and failing both.
What a strong answer includes
Makes both requests concrete (what each needs, by when, and what it costs the other), takes the conflict to both people together, or to whoever sits above them, with a recommendation rather than a complaint, and says how the decision was recorded and passed on to the people doing the work.
Sample answer
I was project manager on a library renovation, reporting to our operations director, while the city's facilities manager had authority over the site. In the same week the city asked us to finish the children's area two weeks early for a reopening event, and my director wanted to move our finishing crew to another job that was behind. Both requests were reasonable, and one crew could not do both. I wrote down what each needed in crew days and what it would cost the other, and set up one call with both of them rather than choosing myself. My recommendation was to finish the children's area with the full crew, then release half the crew a week later. They agreed on the call, and I confirmed it in writing that afternoon. The area was ready for the event, and the other job had its crew nine days later than my director first wanted.
Question 8
Tell me about a time your priorities changed overnight. What happened to the work already in progress?
What it tests
Whether you can re-plan fast without losing track of what was already moving, and whether the people affected hear about the change from you.
What a strong answer includes
Describes what changed and how you found out, the order in which you re-sorted the work and the rule behind it, what you stopped, what you finished anyway because stopping cost more, and whom you called before they found out on their own. Ends with what you did about the work you paused.
Sample answer
I dispatched a regional delivery fleet of about twenty trucks. One evening two trucks failed inspection, and the next day's routes were built for twenty. By five the next morning I had re-sorted the stops with one rule: deliveries with a promised time window, and anything refrigerated, kept their slot, and everything else could move. That covered most of the load with eighteen trucks. Three trucks were already loaded, and I left them alone, because unloading and reloading would have cost more than the stops it saved. Twelve deliveries moved to the next day. I called those customers before eight rather than letting a driver break the news at the door, and gave each a new window. The following day's routes started with those twelve, so nobody was moved twice.
Question 9
Tell me about a prioritization call you got wrong.
What it tests
Whether you can look back at a trade-off honestly, name what you misjudged, and show what you changed in how you decide.
What a strong answer includes
States what you chose and your reasoning at the time, which should sound sensible, names the specific thing you did not weigh or did not check, owns the consequence without blaming the people who argued for the other option, and gives the concrete change you made along with a later decision where you used it.
Sample answer
I managed a neighborhood restaurant and had two projects for the spring: a new seasonal menu, and fixing the host stand, where the wait list lived on paper and walk-ins got lost on busy nights. I put the menu first because it was visible and the owner was excited about it. I never checked how many walk-ins we were losing, and when I finally counted over two Fridays, it was more tables than the new menu was likely to bring in. The mistake was ranking by what was visible rather than by what I had measured. I moved the host stand ahead of the last two menu items and had a simple digital wait list running in three weeks. Since then I count before I rank. When the owner wanted to add brunch the next year, I looked at weekend covers first, and we opened on Sundays only.
Question 10
How do you defend a trade-off when the thing you deprioritized causes a problem later?
What it tests
Whether you can stand behind a decision that was sound when you made it without getting defensive, and tell a bad outcome apart from a bad decision.
What a strong answer includes
Deals with the consequence before the explanation, restates the decision with the information you had at the time, explains the reasoning to the people affected without hiding behind it, and says whether you would decide the same way now and what, if anything, you changed.
Sample answer
I ran a community youth soccer league with three part-time staff. Before the fall season I put referee scheduling ahead of rebuilding our registration site, because the season before we had games with no referee and families waiting on the field. The registration site then crashed on opening night, and about a hundred families could not sign up. I fixed that first: we opened a phone and paper option the next morning and extended registration by a week. Then I wrote to parents and to the board explaining what happened and why the site had been second on the list, without pretending it was fine. I would make the same call again, because a game without a referee is worse than a slow sign-up. I changed one thing: the next year I paid for a load test before opening night, at a small fraction of the cost of a rebuild.
Question 11
Which prioritization framework do you use, and when does it stop helping?
What it tests
Whether a framework is a tool you have actually used to reach a decision, and whether you know where its usefulness ends.
What a strong answer includes
Names one tool you have genuinely used and a decision it helped you reach, explains in a sentence how you applied it rather than reciting what it stands for, and names a specific moment when it did not help, and what you did instead.
Sample answer
On events projects I use MoSCoW, sorting everything into must, should, could and won't. For a two-day trade conference I ran, it earned its place with the client in week one: we agreed that registration, the main stage and catering were musts, and a mobile app was a could. When the budget tightened in week eight, we cut the app in one conversation, because the decision had already been made in principle. Where it stopped helping was among the musts. When the venue's audiovisual quote came in high, everything left was a must, and the categories said nothing about which must to compromise on. That became a conversation with the client about which session they could least afford to go wrong, and we reduced the equipment in the breakout rooms instead of on the main stage.
Question 12
How do you prioritize a product backlog when every request has a sponsor?
What it tests
Whether you rank requests against a goal everyone can see rather than by who is asking, and whether the sponsors of low-ranked requests hear the reason from you.
What a strong answer includes
Anchors the ranking in one stated goal for the period, shows how requests were compared against it using evidence you gathered, makes the ranking visible so sponsors can challenge it, and describes the conversation with at least one sponsor whose request did not make the cut and what would move it up.
Sample answer
When I took over a scheduling app used by small clinics, the backlog had about sixty items and nearly every one had a name next to it from sales, support or the founders. I agreed one goal for the half with my manager: fewer clinics leaving in their first three months. I went through the backlog against that goal, using support tickets and cancellation notes as evidence, and published the ranking in a shared document with a one-line reason for each position. Three items that nobody had championed moved to the top, including a reminder setting clinics kept asking support about. The head of sales had a reporting feature near the bottom, and I told him myself before he saw the document, with the reason and the evidence that would move it up. Early cancellations fell over the half, and the reporting feature went into the next one after he brought two customers who needed it.
Question 13
A project's scope keeps growing but the date and budget are fixed. How do you decide what gives?
What it tests
Whether you treat scope as the variable when time and money are fixed, and make every addition visible as a trade instead of absorbing it.
What a strong answer includes
Shows a mechanism for additions (each new request names what it replaces, or it waits for a later phase), says who approves the trade, gives a concrete addition you traded out or deferred, and explains how the sponsor saw the running total of changes rather than meeting it at the end.
Sample answer
I managed the refit of fourteen stores for a retail chain, with a fixed budget and a fixed finish before the holiday season. By the fourth store, regional managers had asked for new signage, extra fitting rooms and a change to the stockroom shelving. Each request was sensible, and together they would have broken the budget. I set one rule with the program sponsor: any new item named something it replaced, or it moved to a second phase after the holidays. I kept a one-page change log the sponsor saw every Friday, with the running cost of every addition. The fitting rooms were traded against a flooring upgrade the stores did not need, the signage moved to phase two, and the shelving went in because it was cheap and saved handling time. All fourteen stores finished on time and inside the budget, and phase two was approved in January from the same log.
How the interview is evaluated
What prioritization questions are testing
A prioritization question looks like a question about being organized. It is really a question about judgment under a constraint: there is more to do than time, people or money allow, and something has to give. A list of what you did first shows that you were busy. A method shows how you decided, and the evidence for a method is the thing you chose not to do.
Build every prioritization answer from four parts:
- The criterion. The test you used to rank the work, stated before the ranking, so the choice does not look like instinct or favoritism.
- The cut. What you dropped, delayed or shrank, named specifically. An answer where nothing was cut is a story about working hard.
- The communication. Who heard about the cut, from you, and when, including the people who wanted the work you dropped.
- The consequence. What happened to the work you protected and to the work you cut, including any cost you paid.
The questions below are grouped by the situation they describe. Prioritization is one competency inside the wider set of manager behavioral interview questions, and a full behavioral round will mix it with leadership, feedback and conflict stories. For how the whole loop fits together, see the guide to management interviews.
How you prioritize your own work
Question forms:
- When everything on your list feels urgent, how do you choose where to start?
- Walk me through how you plan and prioritize a typical week.
- You have three deadlines landing on the same day. What do you do?
These are the questions any candidate may hear, whatever the role and whether or not they manage anyone. They sound like an invitation to describe your system, and that is the trap. A to-do list, a calendar and an urgent versus important grid are all fine things to own, but none of them is an answer on its own. The answer is the rule you apply to what is on the list, and a real day or week in which that rule made you put something off.
Prepare one routine you genuinely follow and one moment in which it was tested. Keep the routine short enough to say in two sentences, then spend the rest of the answer on the example.
Failure modes: listing tools and techniques with no decision attached; "I just work longer hours", which describes absorbing a priority problem rather than solving it; and an example where every deadline was met and nothing was renegotiated, which leaves no evidence of judgment.
Follow-ups to expect: "What did you leave until later that week?", "What happens when your manager adds something on a Wednesday?", and "Who do you tell when a date is going to slip?"
Deciding what not to do
Question forms:
- Tell me about a request you turned down so the team could finish something more important.
- How do you tell your team you are stopping work they care about?
This is the center of the competency, because saying yes to one thing only means something when it costs something else. The strongest stories involve a request that was genuinely good. Turning down a bad idea shows little; turning down a good one at the wrong time shows that you can rank.
Two conversations belong in these answers. The first is with the person who asked: what you said, what you offered, and when you would look at it again. The second, for a manager, is with your own team, particularly when the work being stopped is work they chose or care about. When the work is ending rather than pausing, say so the first time; a team left waiting for a restart that never comes loses more trust than one told the truth once. Then say what happens to what they built.
Failure modes: keeping everything alive at half speed so nobody has to hear no; cutting work silently and letting people discover it; and describing the refusal but never saying what became of the request.
Follow-ups to expect: "How did they take it?", "Did the request come back?", and "What would have made you say yes?"
Saying no to someone senior
Question forms:
- How do you say no to a senior leader who wants their work done first?
- Two people above you each say their project comes first. What do you do?
The no in these answers is to doing the senior request on top of everything else, not to the request itself. You do not have to shrink it to make it acceptable. It works when the cost is stated in terms the other person answers for: the date they promised, the customers waiting on it, the budget they own. Say what the request would move, and be clear that the decision is theirs if it is theirs. A leader who hears the cost and still chooses their request has not overruled you. They have made the call you asked them to make, and your part is to record it and tell the people it moves.
When two senior people each claim first place, the useful move is to stop being the person who secretly decides between them. Put both requests side by side with what each costs the other, and get both people, or the person above them, to make the call with a recommendation from you.
Failure modes: doing both quietly and missing both; choosing between two senior people alone and leaving one of them to find out; and a story in which the senior person was simply unreasonable.
Follow-ups to expect: "What if they had insisted?", "Did you escalate, and how did your manager react?", and "How did you tell the people doing the work?" When the disagreement is less about priority and more about bringing someone round, the stakeholder management interview questions page covers influence over people you do not manage.
When priorities change mid-plan
Question forms:
- Tell me about a time your priorities changed overnight. What happened to the work already in progress?
- A variant you may hear: "Describe a time your plan was overtaken by events."
Changing priorities is where a method earns its keep. When the plan breaks, you need a rule quick enough to apply before the day starts, and you need to know what was already in motion. Some of it should stop immediately, and some of it costs more to stop than to finish. A strong answer shows both judgments.
Failure modes: re-planning everything from scratch and losing work that was nearly done; treating the new priority as the only priority; and changing the plan without telling the people it moved.
Follow-ups to expect: "What did you stop that you later wished you had finished?", "How did the people affected hear about it?", and "What did you do with the paused work?"
Defending the call afterwards
Question forms:
- Tell me about a prioritization call you got wrong.
- How do you defend a trade-off when the thing you deprioritized causes a problem later?
Every real trade-off leaves something undone, and sometimes the thing left undone goes wrong. Prepare to separate two cases. A bad decision is one where you missed information you could have had, and the honest answer names what you did not check and what you now check. A bad outcome from a sound decision is one you can stand behind, provided you dealt with the consequence first and explained the reasoning to the people it affected.
For a wrong call, tell it in three steps: what you chose and why it made sense at the time, the specific thing you missed, and the concrete change in how you decide, with a later decision that used it. "I would communicate more" is not a change. "I now count before I rank" is.
Failure modes: explaining the decision before fixing the problem; blaming the people who argued for the other option; and a wrong call so small that it shows nothing.
Should you name a framework?
Question form:
- Which prioritization framework do you use, and when does it stop helping?
Frameworks are tools you can reference, and naming one you have really used can make your reasoning easier to follow. Two you may meet in product and project work are RICE, described by Intercom as scoring each idea on reach, impact, confidence and effort, and MoSCoW, which the Agile Business Consortium describes as sorting requirements into must have, should have, could have and won't have this time for a fixed timebox. The urgent versus important grid serves the same purpose for personal workload.
The risk is an answer that explains the framework and never reaches a decision. Keep the framework to one sentence, then describe what it helped you decide and what you cut because of it. Knowing where a framework stops helping, for example when every remaining item is a must or when scores are being argued rather than estimated, shows that you use it as a tool rather than a script. If you do not use a named framework, say so and describe the rule you do use; that is a complete answer.
How the question differs by role
The four parts hold for everyone. What changes is which part carries the weight and what the constraint is.
- People managers: the constraint is the team's capacity, and communication carries the weight. Prepare stories about stopping work your team cared about, protecting them from requests that arrive mid-plan, and telling them the truth when priorities change. For how deciding what to fix first shows up in a role where it is a daily task, see the operations manager interview questions.
- Product managers: the constraint is what the team can build, and the criterion carries the weight. Prepare a backlog story in which you ranked against a stated goal with evidence, and a story in which you said no to a sponsor and told them why. In a product interview you may also get a case version, such as choosing between features for a product you do not know; state the goal first, then compare the options against it.
- Project and program managers: when the date and budget are fixed, scope is the variable, and the cut carries the weight. Prepare a story about additions arriving mid-project and the mechanism you used to trade them, with the sponsor seeing the running total.
- Individual contributors: the constraint is your own time, and the criterion carries the weight. Prepare the "how do you prioritize your work" answer with a real week and one date you renegotiated.
Choosing your stories
Three stories cover this page if you choose them for range: one where you cut or turned down something good, one where you said no to someone senior or settled a clash between two senior people, and one where the plan changed and you re-sorted the work. Add a fourth where the call went wrong, told with what you changed since. A story can do double duty, but check that each one names the thing you dropped, because that is the part that turns a busy week into evidence of judgment.
Write down the four parts for each story, then rehearse them out loud with a follow-up asked straight after: "Which piece of work lost out, and how did the person who wanted it find out?" A manager mock interview built for your role can ask that follow-up and gives feedback on each answer, so a story with no cut in it shows up before the real interview does.
Sources
Practice these questions out loud
Reading a list is silent rehearsal. Run a mock interview for your target role and get feedback on every answer.
Start a mock interview
About the author
Mock Interview Pro team · Interview coaching and practice
Mock Interview Pro runs mock interviews and practice sessions with per-answer feedback, so you can rehearse questions like these out loud before the real interview.
