STAR Method Time-Management Examples (2026) — 3 Worked Answers

Ready to get organised?

Get my action plan - Free • 30 seconds • No signup required

The Real Question Is About Prioritisation

"Tell me about a time you had to manage competing priorities" gets asked in 70%+ of mid-level interviews. The interviewer isn't testing whether you can work hard. They're testing whether you can decide what to drop.

The two most common failures: "I just worked late and got everything done" (signals you'll burn out) or "I asked my manager what to prioritise" (signals you can't decide for yourself).

The STAR method (Situation, Task, Action, Result) lets you show the trade-off you made. Three worked answers below. For the parent framework, see the STAR method interview examples guide.

The Time-Management STAR Template

• Situation: the specific moment the priorities collided. Date, deadlines, what was at stake.
• Task: what you owned across the competing items.
• Action: the prioritisation rule you applied, then the explicit trade-off (what got done, what got dropped or deferred, who you told).
• Result: outcome on the prioritised work and what happened to the deprioritised work.

The rule: your Action must include the moment you said "I will not do X right now." If everything got done, it's not a prioritisation story. It's a productivity story, and a weaker answer.

Example 1 — Three Deadlines, Same Day (Mid-Level IC)

Situation: On a Wednesday I had three Friday deadlines: a client proposal worth £80k, an internal compliance report, and a peer-review for a colleague's promotion submission.

Task: Own the outcome on all three. None could slip without a real cost.

Action: I ranked them by reversibility, not urgency. The client proposal couldn't be rebooked, the compliance report had a one-week grace window, and the peer-review had a hard deadline but only required 45 minutes. I worked the proposal Wednesday-Thursday morning, did the peer-review Thursday afternoon, then emailed my compliance lead at 4pm Thursday explicitly requesting the grace extension with a Tuesday delivery commitment. She agreed.

Result: The proposal won the client. The peer-review was filed on time and my colleague got promoted. The compliance report shipped Tuesday with full quality. No one was surprised by the sequence because I told them in advance.

Example 2 — Manager Drops Urgent Work Mid-Sprint (Engineering / PM Role)

Situation: Three days into a two-week sprint, my manager added an urgent customer-escalation request that would take roughly four days of my time. My existing sprint commitment was already at capacity.

Task: Decide what to drop from the sprint, and own the conversation with stakeholders.

Action: I didn't accept the new work silently. I drafted a 5-bullet message: the new ask, my current sprint scope, three options (drop A, drop B, or split into two sprints with the urgent work in this one). I sent it to my manager and the two stakeholders for the deprioritised work, and asked for a 15-minute call the same day. We picked the split option: urgent escalation this sprint, original work A in next sprint, original work B reframed as a smaller scope.

Result: The customer escalation was resolved in five days. Both deprioritised stakeholders were unsurprised because they'd been in the call. I've used the same 5-bullet structure for every priority renegotiation since.

Example 3 — First Week of New Role (Early-Career)

Situation: In my first week as a graduate analyst, my new manager dropped four tasks on me at once: onboarding admin, a data-pull for a client, a research summary for an internal partner, and shadowing two senior calls.

Task: Get the high-value items done, complete onboarding, and not look like I was struggling.

Action: I asked my manager for a 10-minute slot at the end of day two to confirm priorities, but before that I'd already drafted a ranking: client data-pull (external deadline), shadowing calls (time-fixed), research summary (internal deadline), onboarding admin (no deadline, can run in evenings). She agreed and added a fifth task. I batched the onboarding admin to two evening sessions of an hour each, did the data-pull on day three, attended the calls in their slots, and delivered the research summary on day five.

Result: Everything landed on time including the bonus task. My manager mentioned the priority-check approach in my first 30-day review as the reason she trusted me with a real client by week three.

Common STAR Time-Management Mistakes

1. "I just worked late". Reads as poor judgement and pre-empts burnout questions.

2. "I asked my manager what to do". Fine as a confirmation step, weak as the only Action.

3. Vague trade-off. You must name what got dropped or deferred and what happened to it.

4. No notification step. Strong prioritisers tell people before the deadline slips, not after.

For more behavioural variants and the full template, the STAR method interview examples guide walks through 12 worked answers.

[Try the free STAR coach — paste your raw story, get a clean STAR draft in 30 seconds](/interview-prep)

FAQs

Should I mention a framework like Eisenhower or MoSCoW?

Optional. Mentioning a framework can signal structured thinking, but only if your Action actually maps to it. A generic name-drop without method is worse than no name-drop.

What if I genuinely got everything done?

Pick a different story. The question is about trade-offs, not about being efficient.

Can I use a study-deadline story for a graduate role?

Yes. Finals week with competing module deadlines is a fine example as long as you name the trade-off clearly.