What is a 30-60-90 day plan?
A 30-60-90 day plan is a structured onboarding framework that breaks a new employee's first three months into three phases: Learn (days 1–30), Contribute (days 31–60), and Lead (days 61–90). Each phase has different goals, activities, and success indicators — shifting from observation to contribution to ownership.
Used well, it turns onboarding from "winging it" into a structured, measurable process. Used poorly, it's a checkbox that neither side refers to after week one.
What's in the download
The template includes three sheets:
- Overview template: The primary 3-phase table with goals, activities, and success indicators. Editable for any role.
- Relationship map: A structured list of stakeholders to meet in the first 30 days, organized by type (team, cross-functional, external).
- Weekly check-in log: A simple table for tracking weekly progress against the plan, with a column for what changed and what needs re-prioritization.
How to fill in the template
Step 1: Set the context before writing goals
Before writing anything in the template, answer: what does success look like at 90 days? What are the top 3 priorities this role exists to own? What are the most important relationships for this person to build? The goals in each phase flow from these answers, not from a generic template.
Step 2: Write goals for each phase
Days 1–30 goals should be almost entirely about learning — not contribution. Pressure to deliver in the first month produces shortcuts that cause problems later. The best 30-day goal is: "Understand the team's situation well enough to contribute confidently in month two."
Days 31–60 goals should be about one or two meaningful contributions — not a full project portfolio. Quality over breadth. The best 60-day mark looks like: one thing shipped, one relationship built, one process understood deeply.
Days 61–90 goals should have an ownership flavor — a recommendation, a plan, or leading a decision. This is the signal that onboarding is working: the new person is adding judgment, not just labor.
Step 3: Define success indicators for each phase
Success indicators are how you'll know each phase went well. They don't need to be metrics — they can be behavioral ("can explain the team's top priorities without notes") or output-based ("first project shipped with fewer than X revision cycles"). Write at least one per phase.
Step 4: Identify risks and mitigation
What would slow the plan down? Common risks: key stakeholders unavailable, unclear ownership of a decision, documentation doesn't exist. Write one or two risks per phase and a mitigation plan — this makes the plan honest and shows you've thought critically about execution, not just intent.
4 examples by role type
New engineering manager
Days 1–30: Meet every report 1:1, understand each person's development goals and current challenges. Read all the architecture docs, post-mortems, and incident reviews. Learn the on-call rotation and have sat in on one incident response.
Days 31–60: Run the first team retrospective. Deliver one process improvement (shorter sprint ceremonies, cleaner ticket hygiene, etc.). Have given substantive feedback to at least 3 reports.
Days 61–90: Own the team's quarterly planning process. Have written a 6-month development plan for each report. The team's delivery predictability has improved.
New head of marketing
Days 1–30: Audit all existing channels: website traffic, paid performance, email, content. Understand the sales pipeline and where marketing is credited. Meet every sales rep and understand their main objections.
Days 31–60: Identify the highest-leverage growth lever. Propose a revised marketing strategy with a 6-month roadmap. Run the first campaign with the new hypothesis.
Days 61–90: Have revised the attribution model. Pipeline influence from marketing has a clear measurement framework. The team's roadmap is public and aligned with sales.
New product manager
Days 1–30: Talk to 10 customers. Understand the current roadmap and the reasoning behind each item. Map all the stakeholder relationships and decision rights.
Days 31–60: Own the next sprint planning end-to-end. Ship one small feature and run the retrospective. Have identified the most underserved customer segment.
Days 61–90: Presented a revised 6-month roadmap to leadership. Have a clear framework for prioritization that the team and stakeholders understand. Running the next quarterly planning cycle independently.
New employee (individual contributor)
Days 1–30: Understand how the team works: standups, code review process, documentation standards. Have shipped one small, well-scoped task. Know who to ask for each type of question.
Days 31–60: Own a project end-to-end (planning, execution, review). Have given feedback in at least one code or design review. Running weekly tasks independently without checking in on process.
Days 61–90: Have identified one area to improve (process, tooling, documentation) and proposed or implemented it. Can onboard the next new hire on the basics. Operating without regular check-ins.