What a 30-60-90 day plan actually is
A 30-60-90 day plan is the most structured way to onboard into a new role — or to demonstrate strategic thinking in a final-round interview. It splits your first three months into phases: Learn (days 0-30), Contribute (30-60), and Drive (60-90).
The plan is not a contract. It's a forcing function. Writing it makes you commit to specific outcomes early, surface alignment with your manager fast, and avoid the most common new-hire failure mode: drifting through onboarding for two months and then realizing you don't know what you're supposed to be doing.
How to use the generated plan
If you're starting a new job
- Draft in week 1. Generate, edit, send to your manager before your first 1:1 ends. Frame it as "here's my best-guess plan based on what I know so far — what would you change?"
- Revise in week 3. Once you've met the team and read the docs, you'll know which items were misguided. Cut what doesn't matter, add what does.
- Review weekly. Check items off in your 1:1. The visible progress matters as much as the work itself — managers want to see momentum.
If you're interviewing
- Tailor to what you learned. Use what you've heard in earlier rounds. Reference real people, real systems, real priorities the company mentioned.
- Present it as hypotheses, not commitments. "Here's how I'd approach the first 30 days — subject to learning the actual priorities once I'm in." This signals humility and judgment.
- Three slides, not thirty. One slide per phase. The interviewer will ask follow-up questions; leave room for that.
The 30-60-90 framework in one sentence per phase
Days 0-30 (Learn): Meet everyone who touches your work, understand the systems, ask the question "why" five times in every conversation.
Days 30-60 (Contribute): Ship your first meaningful piece of work. Small enough to finish, visible enough to matter.
Days 60-90 (Drive): Propose something. Lead a project. Show you can take ownership without being asked.
Common mistakes
- Too many items. 5-8 items per phase is plenty. 20 items reads as performative.
- Vague verbs. "Learn the codebase" is not a goal. "Read and annotate the top 3 services by traffic, present takeaways at week 3 standup" is.
- No metrics. Even early-phase items should have a definition of done.
- Pure tactics, no strategy. By day 60, your plan should include at least one item that demonstrates judgment, not just execution.
- Set and forget. A 30-60-90 plan written on day 1 and never revisited is just paper. The value is in re-grounding yourself against it weekly.