How to Answer Managed Competing Priorities

STAR method answers “Tell me about a time you managed competing priorities” by showing the situation, task, action, result and one deliberate trade-off. MIT guidance assigns 60% of the response to Action, while Structured interviews assess job-related judgment, communication and follow-through against proficiency benchmarks.

How should you answer “Tell me about a time you managed competing priorities”?

To answer “Tell Me About a Time You Managed Competing Priorities”, choose one truthful story, name the competing work, show the trade-off, explain your ranking rule and stakeholder communication, then state the result.

Say:

“I chose [priority A] over [priority B] because [impact, urgency, risk or cost of delay]. I told [stakeholder] what would move, protected [outcome] and delivered [result].”

Then expand the example with the STAR method: Situation, Task, Action and Result. MIT’s guidance places the greatest emphasis on the Action section, where your judgement, communication and execution become visible (MIT guidance).

• Situation: “I was [role] when [two demands] collided, with [deadline or risk] attached.”
• Task: “I was responsible for [outcome], so I had to decide what to protect and what to move.”
• Action: “I ranked the work by [method]. I explained the order to [stakeholder], reduced or delegated [work] and checked progress at [review point].”
• Result: “We achieved [specific outcome]. [The delayed work] moved to [later date or reduced scope].”

Use this bridge line:

“The key decision was to delay [work] so I could protect [higher-value outcome], and I told [stakeholder] before the deadline changed.”

The answer must prove a decision. A crowded workload is not enough. Interview guidance suggests keeping the answer to about two minutes and explaining the deliberate trade-offs behind the decision.

Keep ownership accurate. If your manager made the final call, say:

“My manager made the final decision, but I gathered the options, recommended [choice] and managed [my contribution].”

Prepare for the next question with interview follow-up questions and strong response patterns. Never invent a result or claim someone else’s work.

What is the interviewer really checking in this question?

A strong answer can demonstrate four signals: judgement, a repeatable prioritisation method, stakeholder communication and follow-through. (CoPilot Interview)

Make those signals audible with one test:

“I chose X because…, I told Y…, I delivered Z…, and I checked the result by…”

That sentence exposes gaps quickly. If you cannot name the reason, the person informed, the completed work or the evidence checked, your example is still describing activity rather than judgement.

Structured interviews use consistent questions and proficiency benchmarks. OPM describes behavioural-description interviews as evidence about what a candidate did, particularly for complex professional and managerial work. The interviewer is not mainly measuring charm. They are comparing your evidence with requirements identified through the role’s job analysis. (OPM on structured interviews)

This prompt is a behavioural-description interview question. It asks what you actually managed. A situational interview question would ask what you would do if two deadlines collided. Do not answer the past-tense question with a hypothetical policy.

The 1988 structured-interview research links reliable assessment with job analysis, standardised questions, anchored rating scales and consistent administration. (1988 structured-interview research) STAR gives your evidence a clear shape. A higher score may not result. Map each detail to the role’s proficiency benchmarks instead.

Which story should you choose when two examples fit?

Interview-preparation guidance suggests choosing a story that makes a deliberate delay, decline or scope reduction visible, because competing-priorities questions are intended to explore judgement rather than busyness (example guidance). The usual advice is fair: choose a specific example, explain your action and finish with a concrete result. That approach still fails when the biggest result hides the actual choice.

Choose the smaller story if its trade-off is clearer. A large-impact example might show that a launch succeeded, but not whether you ranked the work, accepted risk or simply inherited a good plan. A modest example might show that you delayed a report, protected a customer commitment and reset expectations early. That gives stronger evidence of judgement, communication and follow-through. Useful prioritisation criteria include impact, urgency, cost of delay, reversibility and effort, rather than outcome size alone.

Ask aloud: “What did I delay, delegate, reduce, escalate or refuse, and what evidence shows that choice was reasonable?” Pick the story with the clearest answer.

No workplace example is required. Use academic, volunteer, caring, society or personal-project evidence when you held genuine responsibility and can explain the outcome. Interview guidance generally favours truthful, specific and adaptable stories over overly polished accounts.

If your manager owned the decision, say: “My manager made the final call, but I gathered the options, recommended [choice] and managed [my part].” That is accurate ownership, not borrowed authority.

What simple structure should you say out loud?

The STAR method can keep an answer about competing priorities focused on the decision; one commonly cited structure uses roughly 20% Situation, 10% Task, 60% Action and 10% Result.

Situation:
“I was [role] when [two demands] collided, with [deadline or risk] attached.”

Use one specific, truthful setting. For example: “I was working on a customer-facing service when a production issue and a planned release competed for the same capacity.” This is a template, not a claim about your experience. Role-based examples can help candidates adapt prioritisation stories to SaaS, sales, marketing, customer service and engineering contexts.

Task:
“I was responsible for [outcome], so I had to decide what would happen first and what would move.”

Name the decision boundary. For example, you might have needed to protect month-end close, prepare a board pack, complete a compliance audit or meet an SLA. These are prompts for your own story. Do not combine them into one event unless that is what happened.

Action:
“I used urgent versus important because [reason], then checked the cost of delay and confirmed the order with [stakeholder].”

Four commonly discussed prioritisation methods compare urgent with important work, impact with effort, MoSCoW categories and cost of delay. Name a method only when it explains your choice. The decision and trade-off matter more than the label.

Continue with the control you applied: “I delegated [task], reduced [scope], escalated [conflict] and told [stakeholder] what would move.” A feature flag, delayed API endpoint or revised audit task can illustrate this sentence, but each is an example template unless it describes your real work.

Result:
“We achieved [measurable or observable outcome]. I moved [work] to [later point] or reduced its scope, and I learned [specific lesson].”

Make the consequence visible. Structured interviews use job-related questions and proficiency benchmarks, so connect the result to the role rather than listing tools or frameworks (OPM guidance on structured interviews). That is the answer: what you chose, why you chose it, what moved and what happened.

What should early-career, experienced and career-changer candidates say?

MIT recommends preparing three to five truthful stories, then adapting each story to the responsibility you actually held. Keep each example below 120 words. Borrow the structure, not the wording.

Early-career example

“During a university society event, I had coursework due while our speaker cancelled three days before the event. I listed the deadlines, separated essential work from optional work and divided the event tasks between four volunteers. I protected the coursework submission first, then confirmed a replacement speaker and simplified the running order. The event ran as planned, and I submitted my coursework on time. I learned to agree task ownership early rather than carry every task myself.”

This works for coursework, volunteering or a society event. Name what you personally organised. Do not imply formal authority you did not have.

Experienced example

“In a SaaS role, a customer issue appeared during a product launch week, while an internal audit and board pack were also due. I ranked the customer risk first, kept the launch scope intact and moved the board pack review by one day. I told the finance lead and product manager before their deadlines changed, delegated the evidence gathering and recorded the decision. The customer issue was resolved, the launch proceeded and the audit evidence stayed complete. The board pack went out the following day.”

Examples from marketing, engineering and operations can illustrate the same pattern: competing work, a deliberate movement of one commitment and clear communication (role-based examples). Your level changes the expected ownership. Interview guidance may distinguish prioritisation expectations for mid-level, senior and staff candidates, so experienced answers can address wider consequences rather than only a personal to-do list (prioritisation guidance).

Career-changer example

“While working in retail, I managed a busy Saturday rota, a supplier delivery and a customer complaint involving a team member. I asked a colleague to receive the delivery, handled the complaint privately and updated the duty manager with the remaining risk. I checked that the rota still covered the busiest period and followed up with the customer. The outcome was fewer handoffs, a clear decision record and no repeat escalation.”

Retail, caring, freelance, study and community projects all count when the responsibility was real. Do not invent revenue, percentages or performance data. Observable outcomes are valid.

Candid failure version

“I ranked that incorrectly, missed [deliverable], owned it early and changed the review point.”

Add what failed, who you told and what changed afterwards. A missed deadline can show learning when you explain the control you added, rather than hiding the mistake.

How should you adapt the answer to the role?

OPM’s job-related structured interviews make role-specific evidence the useful adaptation: match your trade-off to the work’s risk, customer and decision owner. (OPM guidance on structured interviews)

For SaaS or engineering, say: “I protected the customer-impacting API endpoint, used a feature flag and delayed the lower-risk endpoint.” Then add who received the update and what the release achieved. For operations or finance, frame month-end close, compliance audits or board packs around control, deadline and risk. Do not describe activity alone.

For sales or customer success, explain how you handled an urgent SLA issue while protecting a high-value prospect. State the service trade-off plainly. Role-based examples can help candidates adjust the level of detail for different functions, including remote and hybrid work. (DailyRemote’s role-based examples)

For a manager role, show delegation, coaching and escalation. Explain how the team understood the revised order. Prioritisation expectations can vary by career level, so senior candidates may need to explain wider consequences and their ownership of the decision. (Resland’s prioritisation examples)

In remote or hybrid work, mention the written update, decision owner, time-zone risk and handoff plan. Use LinkedIn Interview Prep, Glassdoor Interview Reviews, Salary.com, Big Interview, CoPilot Interview or the Resland story bank as prompts only. Never recite their scripts.

How do you practise saying the answer in two minutes?

Interview guidance suggests an answer of about two minutes, while a commonly used STAR structure assigns 60% of the response to Action; rehearse the decision and execution aloud rather than over-polishing the background.

The map below is an author-created application of MIT’s percentages to CoPilot Interview’s two-minute target. The second-by-second split is a practical approximation. It is not a timing instruction from MIT.

Beat	Time target	What to say aloud
Situation	24 seconds	Name the role, setting and competing demands.
Task	12 seconds	State your responsibility and the decision you faced.
Action	72 seconds	Explain the ranking rule, trade-off, communication and execution.
Result	12 seconds	Give the outcome, what changed and what you learned.
Stop signal	At roughly two minutes	Stop adding background and invite a follow-up.

MIT’s published STAR guidance recommends 20% for Situation, 10% for Task, 60% for Action and 10% for Result (MIT STAR guidance).

The Action block needs evidence, not extra context. Replace “I had a lot going on” with: “The launch, refund defect and partner deadline competed for the same four days.” Name the ranking rule. Name the work you moved. Name the person you told.

Run this rehearsal loop:

1. Prompt: Say, “Tell me about a time you managed competing priorities.”
2. Answer: Speak without notes.
3. Replay: Listen for a missing choice, trade-off or result.
4. Score: Mark judgement, method, stakeholder communication and follow-through.
5. Revise: Change one sentence and record the answer again.

Use these response starters for likely probes:

• “Why did you rank them that way?” “I ranked them by risk and cost of delay because…”
• “What did you delay?” “I moved [work] to [date] after confirming…”
• “Who disagreed?” “[Name] preferred [option], so I compared…”
• “What would you change?” “I would set an earlier review point by…”
• “How did you measure success?” “I checked success through [metric or observable change]…”

Structured interviews commonly use standardised lead and probe questions, so practise follow-ups as seriously as the opening answer.

FAQ

What if nothing was delayed?
Say what you ordered, protected or reduced. For example: “I completed both deliverables, but I used delegation to protect the customer deadline and reduced the internal report to its essential sections.” Prioritisation still requires a choice about time, attention, scope or risk.

What if my manager made the decision?
Separate authority from contribution. Say: “My manager made the final call, but I gathered the options, recommended [choice] and managed [your part] through delivery.” Do not claim ownership of a decision you did not make.

What if I chose incorrectly?
Explain the information available, the decision, the failure and your repair. Use: “I ranked [work] first because [reason]. That proved wrong when [impact]. I told [stakeholder] early, reset the plan and added [review point or escalation] to prevent a repeat.”

How do I quantify a non-financial result?
Use an observable change. You could say, “The result was fewer handoffs, a clear decision record and no repeat escalation.” Name the evidence you genuinely have. Do not invent revenue, time saved or satisfaction data.

What if two senior stakeholders disagreed?
Show how you made the conflict visible. Say: “I documented the competing outcomes, compared the consequences and asked the shared manager to confirm the order. I then sent both stakeholders the agreed sequence and ownership.”

What should an entry-level candidate use?
Use a truthful example from coursework, volunteering, a society event, caring responsibilities or a personal project. State your responsibility clearly: “This was not a workplace example, but I had to protect the final submission while resolving a team issue.” Interview guidance suggests preparing three to five truthful stories for behavioural interviews.

What answers should you avoid, and how should you repair them?

Interview guidance cautions that busyness alone is not evidence of prioritisation; make the trade-off explicit (competing-priorities guidance).

Weak: “I just worked longer hours and got everything done.”

Repair: “I protected the critical deliverable, delegated [task] and reset [deadline].”

Avoid “I am very organised.” Avoid naming the Eisenhower matrix, MoSCoW or cost-of-delay analysis without showing the decision it produced. Avoid stories where somebody else acted and you merely observed. Many prioritisation interviews assess whether candidates can explain visible trade-offs.

If every priority was completed, explain the order. State the resource trade-off, accepted risk or reduced scope. Completing everything does not mean nothing was prioritised.

When two senior stakeholders disagree, say: “I surfaced the conflict, compared the consequences and asked the shared manager to confirm the order.” Then explain what you executed.

General interview practice is not legal, HR-compliance or financial advice. Seek qualified advice for a sensitive employment matter.

Razen Rehearsal Sandbox: The two-minute competing-priorities interview answer

You are in a final interview for an operations manager role at Northstar Software. The panel asks about a time you managed a customer refund defect, a product launch and a partner deadline, all competing for the same four days; your answer must show what you chose to move, not just that you worked late.

Setting. A 45-minute final interview in a meeting room. You sit opposite Helen, the hiring manager, and Marcus, the finance director who joined to test judgement and cost awareness.

Cast

• Jordan, Candidate explaining a past decision. At stake: Needs to prove sound judgement without overstating their authority.
• Helen, Hiring manager testing prioritisation. At stake: Needs evidence Jordan can make and communicate hard choices.
• Marcus, Finance director probing trade-offs. At stake: Needs to know Jordan protects customer and financial risk.

The Wrong Way

Jordan: One example was when a refund defect, a product launch and a partner deadline all landed in the same week. I had to keep everything moving.

(Starts quickly; hands clasped tightly, eyes moving between both interviewers.)

Helen: What did you do first?

(Leans forward and leaves a short gap after the question.)

Jordan: I mapped everything out, worked longer hours and kept all three stakeholders updated. I made sure nothing slipped.

(Speeds up; gives a small nod after each claim.)

Marcus: So did any of the work move?

(Tilts his head; voice stays flat and precise.)

Jordan: Not really. We delivered the launch, fixed the refunds and hit the partner date. It was intense, but the team pulled together.

(Smiles briefly; shoulders rise on “not really.”)

Helen: How did you decide which risk mattered most?

(Sets her pen down and holds steady eye contact.)

Jordan: I looked at urgency and impact, then I focused on whatever was loudest that day. I also took on some work from the team to help.

(Adds detail without answering directly; fingers tap once against the table.)

Marcus: What did you delay, reduce or refuse?

(Waits silently; one eyebrow lifts.)

Jordan: Nothing, in the end. I suppose I could have escalated sooner, but the result was positive.

(Drops volume on “nothing”; looks down at the last word.)

Why it fails. The failure starts with Jordan’s line, “I made sure nothing slipped,” then becomes clear in “Nothing, in the end.” That answer presents busyness as prioritisation and hides the resource or risk choice the panel needs to assess. The claim that Jordan focused on whatever was loudest also replaces a repeatable ranking rule with reactivity.

The Right Way

Jordan: One example was when a refund defect, a product launch and a partner deadline competed for the same four days. I owned the customer-risk response and the launch handoff.

(Speaks at a measured pace; places both hands flat on the table.)

Helen: What decision did you have to make?

(Nods once and keeps her gaze on Jordan.)

Jordan: I ranked the work by customer harm and cost of delay. I protected the refund fix, kept the launch handoff, and moved the partner report by two days.

(Pauses between each priority; raises one finger for each choice.)

Marcus: Why was the partner report the work that moved?

(Leans back slightly; voice sharpens on “why.”)

Jordan: It affected one partner, but the existing report still covered the key figures. The refund defect affected 38 customers, so delaying that risk was not reasonable.

(Looks directly at Marcus; keeps the number plain and unembellished.)

Helen: How did you handle the stakeholder whose deadline changed?

(Glances at her notes, then looks back up.)

Jordan: I told the partner that day, gave a new Friday delivery date and explained what would stay in the report. I asked my analyst to own the launch checklist while I reviewed the refund fix.

(Uses open palms for the explanation, then points briefly to the delegation.)

Marcus: And the result?

(Relaxes his shoulders but keeps the question testing.)

Jordan: We corrected the refunds before the launch, the launch went ahead, and the partner received the report two days late with no surprise. The lesson was to state the cost of delay before promising every deadline.

(Slows on “two days late”; finishes with steady eye contact.)

Why it lands. Jordan names a visible trade-off: the partner report moved two days so customer harm and the launch handoff stayed protected. The result is smaller than claiming every deadline held, but the panel can hear the ranking rule, stakeholder communication, delegation and follow-through. The cost is real: Jordan admits a late delivery instead of polishing the story into a flawless success.

<aside class="razen-coach-card" data-razen-scenario="the-two-minute-competing-priorities-interview-answer"> <p class="razen-coach-card__title"><strong>Practice this live.</strong></p> <p><a class="razen-coach-card__button" href="https://razenai.com/coach?scenario=the-two-minute-competing-priorities-interview-answer&amp;article=how-to-answer-tell-me-about-a-time-you-managed-competing-priorities-2&amp;utm_source=razen_blog&amp;utm_medium=rehearsal_sandbox&amp;utm_campaign=how-to-answer-tell-me-about-a-time-you-managed-competing-priorities-2">Click here to boot up the Razen AI voice coach for this exact scenario.</a></p> </aside>

Delivery playbook

Tone shifts

• Start factual and compact during the four-day setup; shift to firmer emphasis on “I protected the refund fix.”
• When Marcus challenges the delayed report, lower the pace rather than becoming defensive; let the customer-risk reason carry the answer.
• Use a matter-of-fact tone for “two days late,” because hiding the cost would weaken the evidence of judgement.

Pause placement

• Pause for 2 seconds after “competed for the same four days” so the panel can register the collision.
• Pause for 1 second after “moved the partner report by two days” before explaining why.
• Pause for 2 seconds after “two days late” before stating the lesson; do not rush past the cost.

Physiological cues

• Before answering, exhale through the nose and lower both feet flat; suppress the quick smile that appears when admitting the missed deadline.
• Count the three priorities on three fingers below the table, then return both hands to stillness before naming the ranking rule.
• Keep your gaze on Marcus for the customer-harm explanation, then include Helen when describing the stakeholder update.

Recovery moves

• If you say, “I kept everything moving,” correct it immediately: “Let me make the trade-off clearer. I protected the refund fix and moved the partner report by two days.”
• If Marcus asks what moved and your mind goes blank, say: “The partner report moved. The existing report covered the key figures, while the refund defect affected 38 customers.”
• If you claim every deadline held, repair it with: “That wording is too broad. The partner deadline moved, and I told them the same day rather than hiding the change.”

Watch it explained

Frequently asked questions

How long should my answer be?

Aim for about two minutes as a rule of thumb, then stop and invite a follow-up. MIT’s STAR guidance gives the Action section 60% of the response, with Situation, Task and Result taking 20%, 10% and 10% (Using the STAR method for your next behavioral…). Treat those proportions as speaking guidance, not a script you must recite.

What if I have no workplace example?

Use a truthful academic, volunteer, caring, society or personal-project example. Explain the competing demands, your responsibility, the decision you made and the result. Say, “This was not a workplace example, but it shows how I prioritised under pressure.” Do not inflate the story or claim authority you did not have.

What if my prioritisation decision was wrong?

Own the error without turning the answer into an apology. Say what information you had, why the decision seemed reasonable, what failed, when you told stakeholders and what you changed. A strong repair includes a review point, earlier escalation, narrower scope or a clearer cost-of-delay check.

Should I name the Eisenhower matrix or MoSCoW?

Name a framework only when it explains your decision naturally. You could say, “I used urgent versus important to separate the customer risk from the internal request.” Impact versus effort, MoSCoW and cost-of-delay analysis also work. The interviewer needs to hear the choice and trade-off, not a memorised label.