You cannot learn the job and prove yourself in sequence — the calendar makes you run both at once, and the date in the question tells you exactly when the learning has to stop.
Most answers to "what would you do in your first weeks?" are a list of good intentions: listen, build trust, understand the culture. All true, all unrankable, and none of them survives contact with a date.
A credible answer runs three things in parallel from day one. You learn, but time-boxed and with named people in it. You make one visible commitment small enough that you will certainly keep it. And you hold the existing work steady so nothing breaks while your attention is elsewhere.
Then you do the arithmetic. If a roadmap is due in six weeks, the learning track closes at week three — finished or not — because weeks four and five belong to writing it and being told it is wrong. The date sequences the plan for you. Your job is to say so out loud.
Pin the deliverable, then place your activities. Three meters respond: what you know, what the team trusts you with, and delivery risk against the pinned date. Then swap the scenario and watch the same blocks produce a different curve.
learn time-boxed, with names in it · commit one promise small enough to keep · hold the work already in flight · change structural moves · deliver the pinned date
an outsider with a badge
watched, politely
manageable
week 0 · before you start
run the twelve weeks
scenario — this keeps your blocks, so you can compare
the fixed date in the prompt
activities — pick one, then pick a week (two fit in a week)
place in week
Pick an activity above, then choose a week.
Read the date out of the prompt first. Everything else is downstream of it.
the prompt says: "the exec team wants a revised roadmap in six weeks"
D = week 6 the fixed date — not negotiable in the answer
L = ceil(D / 2) = 3 listening closes here, finished or not
D-2 = week 4 the draft circulates, so you can still be told you're wrong
D-1 = week 5 harden it against what came back
D = week 6 deliver
which gives the shape of the answer:
weeks 1-3 learn: 9 one-to-ones, 2 skip-levels, one customer call,
and I read Q3 and Q4 myself rather than being briefed
weeks 1-3 hold: the two releases already in flight keep their dates;
Priya keeps running them and reports to me weekly
week 3 commit: one promise small enough to keep — a written Friday
update to the team and to my boss, starting this week
weeks 4-5 draft, circulate, get challenged, rewrite
week 6 deliverThe three tracks, in the order you should say them:
Then close with the sentence that turns intentions into a plan: "So by week three I stop asking questions and start writing, and by week four the draft is in front of you with time left to be wrong."
| the situation | lead with | the trade-off you're accepting |
|---|---|---|
| A respected predecessor; nothing on fire | The learning track, and an explicit "no structural changes before week six" | You move slower than the date would like. You are buying consent, and you should say that is what you are buying. |
| A failing team; missed commitments, attrition | Holding the line, plus one visible change early — with what you'd reverse if you're wrong | You will move before you are certain. Say so, and say how you'd detect and correct the error. |
| No date given in the prompt | Invent one and justify it: "the board meets quarterly, so I'd work to week ten" | 30/60/90 is a default, not an answer. A date you chose is better than a template you borrowed. |
| You've been asked to fix something specific | Confirming the real ask before planning against the stated one | One clarifying question costs you thirty seconds and can save the whole answer. |
"You've just joined as engineering manager of a nine-person platform team. The previous manager was well liked and left three weeks ago; the team was never told why. Your VP wants a revised migration plan in six weeks. One of your reports applied for your job."
Start with the arithmetic out loud: six weeks means listening closes at week three, the draft circulates at week four, and week six is delivery. Then the three tracks. Learning: nine one-to-ones plus two skip-levels in the first ten working days, one call with the largest internal consumer of the platform, and I read the last two quarters of incident data myself. Holding: the migration keeps its current cadence and its current owner — I don't touch it in weeks one to three, I just attend and listen. Committing: a written Friday note to the team and the VP from week one, and one unblock they've been waiting on, delivered by week two.
Then name the hazards rather than hoping they don't come up. The internal candidate gets the first meeting: I'd tell them I know they applied, that I want them here, what I'd need from them, and what I'd back them on — and I'd expect to have earned nothing yet. On the silence about the departure: I'd tell the team what I can and can't say, so the vacuum stops manufacturing its own explanation. And I'd ask the VP in week one what makes this a success at week six — because "revised plan" may really mean "tell me whether this migration is still worth finishing."
Close on the constraint you're choosing: no structural changes before week six. This team liked the last manager. Moving people before I can explain what she was optimising for reads as a verdict on her, not a decision about them — so any change I make comes after the roadmap, with the evidence attached. Had the team been failing instead, that constraint inverts: waiting would be the risk, and the change would come in week three with a stated way to reverse it.