A 30-60-90 day plan gives you a practical way to turn a new job into clear learning goals, relationships, and early results. This guide explains what to include, provides a reusable template, and shows how to review your progress with your manager each week.
Overview
A 30-60-90 day plan is a short-term roadmap for your first three months in a new role, internal transfer, internship, or expanded assignment. It is not a rigid contract or a list of everything you hope to accomplish. Instead, it helps you sequence your work: first understand the role and context, then contribute with increasing independence, and finally take ownership of meaningful priorities.
The strongest plans connect four areas:
- Learning: What systems, processes, customers, products, and expectations do you need to understand?
- Relationships: Which colleagues, partners, customers, or stakeholders should you meet?
- Delivery: What useful work can you complete safely and credibly?
- Evidence: How will you document progress, questions, accomplishments, and changing priorities?
Before writing your plan, ask your manager what success should look like at 30, 60, and 90 days. A plan based only on your assumptions may prioritize visible activity over the work your team actually needs. Treat the document as a starting point that becomes more precise as you learn the role.
What to include in each phase
| Phase | Primary focus | Useful outputs |
|---|---|---|
| Days 1-30 | Learn, observe, and build context | Onboarding checklist, stakeholder map, questions, process notes |
| Days 31-60 | Contribute and improve | Completed work, draft recommendations, reliable routines, early wins |
| Days 61-90 | Own priorities and plan ahead | Measurable results, improved process, next-quarter priorities |
Checklist by scenario
Reusable 30-60-90 day plan template
Copy the structure below into a document, task manager, or shared workspace. Replace the prompts with details from your role.
Role: [Job title or assignment]
Start date: [Date]
Manager: [Name]
Top team priorities: [Priority 1], [Priority 2], [Priority 3]
Success measures: [How progress will be recognized or measured]
Days 1-30: Learn and connect
- Complete required onboarding and gain access to essential systems.
- Review team goals, current projects, documentation, and performance expectations.
- Meet key colleagues and learn how work moves across the team.
- Observe recurring meetings and identify decisions, dependencies, and risks.
- Complete one or two low-risk tasks to learn the workflow.
- Record open questions and confirm which ones require immediate attention.
Milestone: I can explain the team’s priorities, my responsibilities, key workflows, and the questions that need further clarification.
Days 31-60: Contribute and improve
- Take ownership of defined tasks or a manageable project area.
- Deliver work against agreed standards, deadlines, and review steps.
- Identify one practical improvement based on what you have observed.
- Ask for feedback on quality, communication, and prioritization.
- Document repeatable steps, decisions, or lessons that will help the team.
Milestone: I can complete core responsibilities with appropriate support and have evidence of useful contributions.
Days 61-90: Own and plan forward
- Lead an agreed project, recurring responsibility, or improvement effort.
- Use relevant measures to show progress, quality, timeliness, or impact.
- Resolve routine issues independently and escalate material risks early.
- Propose priorities and development goals for the next quarter.
- Review the first 90 days with your manager and agree on the next set of expectations.
Milestone: I understand how my work supports broader goals and have a documented plan for continued performance and growth.
Milestone examples by career stage
Student or intern: Learn the team’s tools, complete a supervised assignment, ask informed questions, and present what you learned. Your plan should emphasize learning quality and dependable follow-through rather than trying to redesign established processes immediately.
Entry-level employee: Master core workflows, deliver recurring tasks accurately, build relationships with teammates, and identify a small improvement after you understand the existing process.
Career changer: Translate prior skills into the new context, close knowledge gaps, and confirm unfamiliar terminology, systems, and decision-making norms. Avoid assuming that a method that worked in your previous field will transfer without adjustment.
Experienced individual contributor: Establish credibility with stakeholders, take ownership of a defined outcome, and clarify how your expertise complements the team’s current capabilities.
New manager: Learn the team’s strengths, workload, goals, and communication preferences before making major changes. Set expectations for one-to-ones, decision-making, feedback, and escalation.
For remote or hybrid roles, include specific plans for communication windows, collaboration tools, documentation, meeting participation, and visibility of completed work. A useful remote-work plan makes work discoverable without requiring constant status messages.
Questions for your manager
- What would make my first 30, 60, and 90 days successful?
- Which outcomes matter more than activity or volume?
- What should I learn first, and which topics can wait?
- Who are the most important partners or stakeholders for this role?
- What decisions can I make independently, and when should I ask for approval?
- Which deadlines, risks, or commitments should I know about immediately?
- How do you prefer progress updates: a meeting, written summary, dashboard, or another format?
- What feedback would you like me to request or receive during onboarding?
- Are there existing processes I should follow before suggesting changes?
Use the answers to turn broad expectations into observable milestones. For example, replace “learn the product” with “complete product training, shadow two customer calls, and explain the main workflow in the next team review.”
Weekly check-in table
| Week | Completed | Evidence or result | Questions and risks | Next priority |
|---|---|---|---|---|
| 1 | [Tasks completed] | [Notes, access, meetings] | [Unknowns or blockers] | [Immediate focus] |
| 2 | [Tasks completed] | [Work delivered] | [Decisions needed] | [Next focus] |
| 3-4 | [Tasks completed] | [Learning and early contribution] | [Risks or dependencies] | [30-day review actions] |
| 5-8 | [Tasks completed] | [Quality, speed, or stakeholder feedback] | [Trade-offs] | [60-day priorities] |
| 9-12 | [Tasks completed] | [Outcomes and ownership] | [Open decisions] | [Next-quarter plan] |
What to double-check
Review your plan with your manager before treating it as final. Check that each goal has a clear owner, a realistic time frame, and a definition of done. “Build relationships” is a useful intention, but “meet the product, sales, and support leads and record how each team works with ours” is easier to complete and discuss.
Also confirm the following:
- Priority: Does the plan reflect current team needs rather than an idealized job description?
- Scope: Are you avoiding commitments that depend on people, data, or access you do not control?
- Measures: Can you show progress through completed deliverables, feedback, quality checks, cycle time, or another relevant indicator?
- Dependencies: Have you identified approvals, training, systems, or colleagues needed to proceed?
- Communication: Does the plan state when and how you will report progress?
- Development: Does it include a skill or capability you want to strengthen, not just immediate tasks?
Keep a simple accomplishment log throughout the 90 days. Record the situation, your action, the result, and any feedback. This creates useful material for performance conversations and future promotion planning; see the promotion readiness checklist for a related evidence-building workflow.
Common mistakes
- Trying to change everything immediately: Learn why a process exists before recommending a replacement.
- Confusing busyness with progress: Meetings and training matter, but connect them to decisions, skills, or deliverables.
- Writing goals that are too vague: Add an observable action, outcome, or review point.
- Making promises before understanding constraints: Use language such as “assess,” “draft,” or “propose” when the final result depends on discovery.
- Ignoring relationship work: A technically strong plan can fail if it does not account for stakeholders, handoffs, and communication norms.
- Keeping the plan private: Share the relevant version with your manager and use check-ins to adjust it.
- Treating day 90 as an ending: The purpose is to establish sustainable performance and the next set of priorities, not to finish onboarding permanently.
When to revisit
Review your 30-60-90 day plan weekly during the first month, then at least every two weeks as your responsibilities stabilize. Revisit it immediately when the team changes direction, a project is delayed, a manager changes, a major tool or workflow is introduced, or your scope expands.
At each review, mark goals as complete, in progress, paused, or no longer relevant. Add the reason for any change so the document reflects judgment rather than missed work. Before a formal check-in, prepare three short points: what you completed, what you learned, and what you need next. If your role is remote or hybrid, send a concise written update in the team’s preferred collaboration tool so decisions and priorities remain easy to find.
To put the plan into action today, schedule a manager conversation, copy the template into your preferred workspace, list your first five questions, and choose one measurable milestone for each phase. Set a weekly reminder to update the check-in table. A useful new job plan should become more accurate over time—and should help you and your manager make better decisions about priorities, development, and career growth.