How to Answer Competing Priorities Interview Questions When Something Had to Wait
By Daniel Okafor
Prepare a truthful competing-priorities interview answer when work had to wait, with a decision worksheet, worked answer, and follow-up practice.
Interview Strategy | Published 2026-10-19
Explain the decision, the work you protected, and the honest cost of what waited.
A useful competing-priorities interview answer explains the commitments that collided, the constraint, the consequences of delay, the candidate's recommendation and authority, and the result for both protected and deferred work. Use a specific past event for a behavioural question, distinguish agreed deferral from recovery after a mistake, and include only outcomes you can support.
A strong answer to a competing-priorities question does not depend on claiming you delivered everything. It depends on making a clear choice when two commitments could not both be met as promised. Show what collided, why one piece of work came first, who had authority to agree, and what happened to the work that waited. That is where the evidence sits. “I worked harder and got everything done” may be true, but when a deadline moved or scope changed, smoothing over the cost hides the judgement the question can reveal. A useful answer accounts for both sides of the trade-off. This guide will help you prepare for questions such as “Tell me about a time you managed competing priorities” and “How did you handle two urgent requests?” The aim is a concise, supportable story, not a perfect ending. First, distinguish a past example from a proposed approach “Tell me about a time” asks for an event. “What would you do if” asks for a proposed response. They may involve similar choices, but the evidence is different. The US Office of Personnel Management's structured-interview guidance distinguishes questions about past behaviour from questions about a possible future situation and connects structured questions to job-relevant competencies. For a past example, explain what you knew and did then. If you now see a better way to handle it, place that in your reflection rather than rewriting the event. For a proposed situation, name the information you would seek, the criteria you would use, and who could make the decision. Keep the two kinds of answer separate: a considered plan is not evidence of a past success. The preparation method below helps you organise your evidence. It is a guide for your own answer, not a universal employer scoring rubric. Choose a story with an actual collision Two deadlines close together do not automatically make a useful story. The important detail is the constraint that made a choice necessary. For example, two tasks may need the same specialist before one deadline. A customer issue may interrupt a scheduled internal review. An analysis may depend on information that will arrive after the meeting it is meant to support. In each case, explain what could not happen at once and why the sequence mattered. Look for a story where you can identify the commitments, the reason they conflicted, and your part in the response. A modest example with clear evidence is often easier to explain than a large project where you only saw the final decision. Before you settle on one, ask: Can I name both commitments and the constraint between them? Do I know what actually happened when each piece of work was delayed? Can I separate my recommendation from someone else's approval? Can I describe the outcome for the work that waited? If you cannot answer the last question, check records you are permitted to use or choose another story. Do not supply a happy ending from memory's blank spaces. Keep confidential work details in approved systems; a personal preparation note can use a general description. Reconstruct the decision before polishing the answer Write a short decision note before you shape a spoken response. Its purpose is to recover the reasoning and expose any facts you still need to check. Question What to recover from your experience What was promised? The deliverable, requester, timing, and purpose of each commitment. What was constrained? Your available time, a shared resource, a dependency, or a necessary review. What would delay change? A blocked decision, interrupted service, avoidable rework, or a rescheduled internal activity. What alternatives existed? Change the order, narrow scope, share the work, move the date, or seek a decision. Who could agree? What you could change yourself and what required the owner or manager. What happened afterwards? The protected outcome, the cost of the deferral, and any recovery or follow-through. These prompts are for preparation, not six paragraphs to recite. If you cannot explain why one request mattered more at that moment, “I prioritised by impact” is only a label. Consider an internal presentation and a file needed for a customer implementation the next morning. The presentation can still matter; its review may be movable with agreement, while the implementation team cannot begin without the file. That distinction explains the sequence. Calling the presentation unimportant would claim more than the decision requires. Explain the trade-off and the alternative you rejected The listener needs enough context to understand why you chose one path. You do not need to list every option, but include the alternative that makes your recommendation clear. If you reduced scope, explain what the smaller deliverable still allowed someone to do. If you asked for help, say what could be handed over safely and what needed your attention. If you escalated, name the decision you needed and the consequence of each choice. “I kept management informed” leaves the key reasoning out. For example, a recommendation might sound like this: “I could complete the customer handover before implementation began, or finish the full internal presentation. I recommended protecting the handover, sending a short written update that afternoon, and moving the presentation review. My manager agreed to that order.” The example makes the boundary clear: the candidate recommends, the manager approves. Use that distinction whenever you did not own both deadlines. Extra hours may be part of your actual response, but they do not explain the decision by themselves. Say what the extra time solved and what changed in the workload. If the capacity problem remained, include it in the account. Build the answer around the decision Harvard's interviewing guide recommends a specific example, a clear account of your role, and an explanation of the situation, action, and result. The outline below adds responsibility and reflection as prompts for this particular question; those additions are an editorial adaptation. Situation: Two commitments collided because of a specific constraint. Responsibility: State what you owned and where your authority ended. Action: Explain what you clarified, recommended, agreed, and communicated. Result: Account for the work you protected and the work you delayed. Reflection: Name a specific improvement, if the example calls for one. Use the outline to organise notes, then speak from the facts rather than memorising a paragraph. Give enough context to make the collision clear and spend most of your time on the choice and its consequences. If the interviewer gives you a format or time limit, follow it. Otherwise, keep the first account concise and have the supporting detail ready for follow-up questions. Worked example: two requests, one agreed deferral Consider a project coordinator preparing a customer handover and an internal reporting presentation. Both are requested for Thursday afternoon. The coordinator needs to check the handover details and assemble the presentation. A vague answer might be: “I had several deadlines, so I organised my workload, communicated with stakeholders, and delivered the important work on time.” The listener still cannot tell what “important” means, who agreed to a change, or what happened to the other request. Here is a more developed illustrative answer: “I was preparing a customer handover and an internal reporting presentation for the same afternoon. I could not complete both properly in the time available. I owned the preparation, but moving the presentation review needed my manager's agreement. “I checked what each deadline supported. The implementation team needed the handover before it could begin the following morning. The presentation supported an internal review that could be rearranged. I recommended completing the handover first, sending a short written reporting update that afternoon, and moving the presentation review to Friday. “After my manager agreed, I confirmed the revised plan with the people expecting the presentation. I completed the handover checks and sent the reporting update. The implementation team received what it needed, and the presentation review took place on Friday. The internal team had to reschedule; the written update was an interim response, not a substitute for the full presentation. “Afterwards, I added a check for overlapping review dates when planning this recurring work. I would still raise the capacity conflict earlier if it happened again.” The example explains why the handover came first, who approved the change, and what the deferral cost. It also makes room for follow-through without pretending the original commitments were both met. In your own answer, use outcomes you can support. A saved customer, revenue figure, or efficiency percentage adds nothing unless it is true and relevant. If you recognised the conflict too late Not every story ends with a planned move agreed in advance. You may have underestimated the work, missed a dependency, or raised the conflict after there was little room to respond. The answer can still show judgement if it separates the cause from the recovery. For example: “I underestimated the checking needed for one deliverable and did not flag the collision soon enough. By the time I raised it, the internal review had to move. I explained the shortfall, agreed which work to finish first, and gave the affected colleague a revised date I could support.” Continue with what actually happened and what you changed. You might estimate review time separately, check dependencies before promising a date, or agree an earlier checkpoint with your manager. Say whether you later used that change and what you observed. If you have not tested it, describe it as your next step. Take responsibility for your part without claiming sole responsibility for a shared failure. Be specific about what was yours to notice, say, or do. If several people lacked a shared view of capacity, explain that rather than assigning the whole problem to “unreasonable stakeholders.” If the question asks for a successful example and this story mainly demonstrates recovery from a mistake, use another truthful example when you have one. A good match between the question and the evidence is more useful than forcing one story to answer every prompt. Adjust the emphasis to your level of responsibility Your role changes which part of the decision you can claim. An early-career candidate may not have had permission to move a deadline. The evidence could be noticing the conflict, gathering the facts, proposing an order, and carrying out the agreed plan. Do not present yourself as the final decision-maker if someone else approved it. A specialist might explain a technical dependency or identify a minimum usable output. Make clear why the sequence preserved necessary checks or let the next team proceed. A manager should account for how the decision affected other people's commitments. Moving a task off your own list is not a complete result if it quietly leaves someone else with an unworkable deadline. Include the capacity used, the promises changed, and how you checked that the revised plan could work. These are preparation prompts, not universal hiring criteria. In work involving safety, regulated duties, or incident response, explain the procedures and authority that applied. A general urgency-versus-impact exercise does not replace them. Prepare for the follow-up that tests your reasoning Once the sequence is clear, practise the questions that could expose a missing part of the story: Why did that deadline take precedence? Explain the consequence or dependency, not the requester's seniority alone. Who disagreed? Describe the concern and your response. If nobody objected, say so. What did the delayed work cost? Name the rescheduling, reduced scope, or other effect you know about. What would you change? Choose a step you could improve, such as identifying shared resources earlier. What would have made you reverse the order? Separate what you knew then from what you can see now. When you do not remember an exact number, give the outcome you can support. “The review moved to Friday” is clearer than an invented claim that everyone became more productive. A preparation exercise you can complete now Choose one real collision and write a line for each of these: the two commitments, the constraint, the consequence of delay, your recommendation, the agreement, and the result for each piece of work. Mark the part you personally did. Read the note aloud once. Wherever you say “I communicated,” add what you communicated. Wherever you say “I prioritised,” add the criterion. Wherever you say “we delivered,” check that a listener can distinguish your contribution from the team's work. Keep source facts in a place you are permitted to use. If you already prepare in AskMyCareer, its Interview Story Bank and career evidence tools can help organise reusable stories from a saved career graph. Check the facts and edit generated wording before relying on it; a plain note works for this exercise too. The answer is ready when another person can explain why one task went first, what happened to the other, and what you were responsible for. If those points are clear and accurate, the story has substance even when something had to wait.