'Walk us through your first 90 days' is the senior-move question that punishes both kinds of confidence: the candidate who promises transformation by week six reads as someone who has never actually inherited a team, and the candidate who offers ninety days of pure listening reads as someone hiding from commitment. The panel is pricing your judgement about the ratio — what you can genuinely know from outside, what you'd verify first, and when you'd start moving.
The working skeleton is 30/60/90 — learn, decide, move — but the marks live in the texture: naming the assumptions your plan rests on, anchoring each phase to something checkable, and building in the moment where your plan changes because the building taught you something. A plan that cannot be wrong is not a plan; it is a speech.
Below are four fully worked walkthroughs at different altitudes — operations, marketing, head-of-function, and a transformation brief — each marked against the four criteria aurate uses in live sessions, plus the challenge questions panels attach and the credibility rules that separate a plan from a promise.
Practise these questions out loud with a live AI interviewer — free. Start with Try Me
How the marking guidance works
Each model answer below is marked against the four criteria a live aurate session scores:
See how a full session is scored
aurate is a practice tool. Marking guidance describes what strong practice answers show — it isn't an employability assessment.
Why it's asked: For operations roles the panel wants the plan anchored in the physical reality of the job — sites visited, shifts worked, numbers reconciled — before any redesign talk. The strong answer sequences credibility-building before change and names the one early move that buys trust.
My first thirty days are spent where the service actually happens. Eleven nurseries — I'd work a full day in each, not a walkthrough: opening shift in some, closing in others, because settings look different at 7:45am and 6pm. Three things I'm reading on those days: staffing reality against rota (agency reliance tells you more than any report), the state of the safeguarding and ratio paperwork under time pressure, and what managers fix locally without telling anyone — that last one is where the operational truth lives.
One early move inside the first month, deliberately small and visible: whatever the most-complained-about piece of head-office admin is — and every group has one — I fix or kill it. It buys the credibility the rest of the plan spends.
Days thirty to sixty: decisions from what I've seen. I'd expect — and I hold this as an assumption, not a finding — that two or three settings drive most of the agency spend, and that occupancy and staffing aren't being planned in the same conversation. By day sixty the managers and I have agreed the three numbers every setting runs on, reviewed the same way monthly.
Days sixty to ninety: the first structural fix goes live — likely a shared bank-staff pool across the closest clusters, because it attacks the agency line without touching ratios — and I bring you a costed view of what year one looks like.
What I won't do in ninety days: restructure management or announce a curriculum change. I'd be moving on scaffolding I don't have yet, and this sector punishes leaders who arrive loud.
Marking guide
Why it's asked: Marketing 90-day answers fail by promising creative transformation before understanding what already converts. Panels want evidence-first instincts — what you'd measure and read before you change a single message — plus one early proof-point that shows pace without recklessness.
First month: I'd resist the rebrand instinct entirely and audit what already works. Three reads in parallel — where the trade sales actually come from (the taproom, the wholesalers, the supermarket listings — the mix decides everything downstream), what the last two years of activity genuinely cost and returned, wherever that's knowable, and twelve customer conversations: six landlords who stock us, six who stopped. The ex-stockists are the audit — people who leave tell you the truth people who stay soften.
Early move, weeks three to four: one owned channel brought up to competent — usually the mailing list, because it's cheap, measurable, and nobody's darling. It shows pace without betting the brand on my first month's guesses.
Days thirty to sixty: the choice the audit sets up. My assumption from outside — flagged as exactly that — is that the brand spends thinly across too many small activities. By day sixty I'd bring you a one-page plan that kills the bottom half of the activity list and concentrates the freed budget on the two channels the evidence backs, each with a number attached that we agree in advance counts as working.
Days sixty to ninety: the first concentrated campaign runs — trade-focused, because the audit will almost certainly say our next pound converts better through stockists than direct — and we review it against the pre-agreed number, not against enthusiasm.
The honest edge: ninety days is too short to prove a marketing strategy. What it can prove is the operating pattern you're hiring — evidence before spend, concentration over sprawl, and numbers agreed before campaigns rather than after.
Marking guide
A plan reads well on paper — the challenge round is the test
Two walkthroughs in, the pattern is visible: assumptions named, triggers stated, subtraction included. What panels then do is attack it — access, goodwill, budget — and an aurate session rehearses exactly that defence live, marking you on the same four criteria used across this page. Two free sessions. No credit card.
Try it freeWhy it's asked: At head-of level the plan's centre of gravity moves from process to people: the panel wants to hear how you'd read a team you didn't build, handle the inherited situations every function carries, and earn followership before exercising authority. Plans that skip straight to structure read as dangerous.
The first month is people before process — because in support, the team IS the product. One-to-ones with all fourteen people in the first fortnight, same three questions each: what should I protect, what should I fix first, and what do you do that nobody sees? The pattern across fourteen answers is the real org chart. Alongside that, I'd take my own ticket shifts — genuinely take them, in the queue, badge on — because reading dashboards about a queue you've never sat in is how support leaders end up managing fiction.
What I'm listening for specifically: the inherited situations. Every support function has them — the workaround that became a process, the customer no one will name as unprofitable, the strong performer holding a broken rota together by goodwill. By day thirty I'd know which of those is urgent.
Days thirty to sixty: the decisions. Two I'd expect — held as assumptions until the month teaches me otherwise: the escalation path to engineering needs a real contract (support usually bleeds exactly there), and the metrics likely over-reward speed and under-measure resolution, which quietly trains people to close rather than fix. By day sixty the team has agreed the three numbers we run on and — more important — the one we've stopped worshipping.
Days sixty to ninety: the first structural change, made WITH the seniors rather than announced — likely the rota redesign if the goodwill-dependency is what I find, because you fix the thing that breaks people before the thing that breaks metrics.
And the commitment I'd make you now: no restructure announcements inside ninety days. If the team hears my name and thinks 'reorg', I've spent my first quarter making everyone update their CV instead of their tickets.
Marking guide
Why it's asked: The panel's favourite counterpunch: it attacks the plan's optimism and demands subtraction in one move. Strong candidates concede the constraint honestly, show the plan's load-bearing parts survive it, and produce a real stop-list — because stopping things is the scarcest senior skill.
You're right on both counts, so let me take them in order.
On access: the plan's first month assumes the divisional accountants will open their workings to me, and mid-transformation, some won't — I've lived that. So the load-bearing version needs only what nobody can withhold: the ledger itself, the close timetable, and my own attendance at the month-end I'd sit through in week two, wherever it's rockiest. Everything else in month one is enrichment; those three are the plan.
On goodwill: I'd assume LESS than the plan sounds like it assumes. A transformation lead arriving mid-programme is read as either rescue or threat, and which one gets decided in my first three conversations — so those are with the two divisional FDs most burned by the programme so far, and my opener is asking what the programme has cost their teams, not what they've cost the programme.
Now the stop-list, because it's the better half of your question. Three candidates I'd examine in month one, expecting to stop at least two: the parallel reporting — divisions almost certainly still run their old packs alongside the new ones 'temporarily', which doubles work and lets everyone keep their favourite truth; any workstream that exists to hit a milestone nobody can trace to a benefit — mid-programme transformations always grow one or two; and the weekly all-hands programme call, if it's become theatre — a written note plus fortnightly decisions-only sessions usually returns four hours a week to people who are already drowning.
Stopping those isn't housekeeping. It's the message: this phase values your time, and the programme serves the business — not the other way round.
Marking guide
Why it's asked: Learn, decide, move is the whole frame: thirty days of evidence with a stated end-trigger, thirty of decisions agreed with the people who own them, thirty of visible motion. Over-engineering — week-by-week Gantt detail, deliverables per fortnight — reads as naive, because it pretends the building won't change the plan. Phases carry objects and numbers; weeks stay unclaimed.
Why it's asked: At final-round and offer-stage conversations for management roles, arriving with a one-page plan — clearly labelled as assumptions to be corrected — signals seriousness even when nobody asked. The label is the craft: 'here's my outside-in read, and half the value is you telling me where it's wrong' invites collaboration instead of marking. Never send it cold before a first interview; that reads as presumption.
Why it's asked: Panels hear 'quick wins' from every candidate and believe almost none of them. The credible version is one small, reversible, named move — chosen because it's cheap to be wrong about — rather than a promised harvest. Interviewers who've actually inherited teams know the first quarter's real wins are usually subtractions and repairs, and they mark accordingly.
Why it's asked: The plan that gets hired is derived from the role's actual scorecard: the problem stated twice in the advert, the metric the hiring manager owns, the thing the last incumbent didn't do. If the interview process hasn't revealed those yet, the strong move is asking — 'what does a great first six months look like from your seat?' — and visibly wiring the answer into your ninety days on the spot.
Why it's asked: Some final rounds make the plan a set-piece — ten minutes, slides, panel Q&A. Everything on this page still applies, plus presentation mechanics: brief decoded aloud, assumptions on the slides, and a defence ready for the budget and access challenges. Our interview presentation guide covers that format's own rules; build the plan here, deliver it there.
Three phases with objects in them: a learning month with named evidence sources and an end-trigger, a decision month producing two or three agreed priorities, and a movement month with one visible change landing. Add the assumptions it rests on and one thing you would stop — those two elements separate plans from speeches.
Spoken: ninety seconds to two minutes, phase by phase, with one concrete object per phase. As a document: one page. Week-by-week detail signals you haven't led a first quarter before — real plans hold shape at the phase level precisely because the building will redraw the weeks.
Yes — it is often the strongest line in the answer. A stated not-doing list (no restructure announcements, no strategy rewrite before the audit) shows you understand what new leaders cost organisations, and it pre-empts the panel's fear that you'll arrive loud. Subtraction reads as seniority.
Certainty. Plans built without inside access that nonetheless promise specific outcomes by specific dates read as either naive or rehearsed. The fix is structural: name the assumptions, schedule their verification, and show where the plan bends when the building corrects you. Confidence about method, humility about facts.
Increasingly — team-lead and specialist interviews borrow it because it tests judgement cheaply. The altitude changes but the skeleton holds: what you'd learn, what you'd decide, what you'd change, what you'd leave alone. At any level, the marked behaviours are the same: evidence before action, and visible respect for what already works.
Two free sessions. No credit card.