90-Day Plan
A structured set of goals, milestones, and learning objectives for new employees to achieve during their first three months in a role.
What Is a 90-Day Plan?
Key Takeaways
- ✓A 90-day plan sets clear goals, learning targets, and success criteria for a new employee's first three months.
- ✓It creates accountability for both the new hire and the manager by defining what "success" looks like early on.
- ✓70% of employees with a structured 90-day plan report feeling confident in their role by month 3 (LinkedIn, 2023).
- ✓The first 90 days are the critical window where new hires decide whether to stay or start looking elsewhere.
- ✓A 90-day plan typically covers three phases: learning (month 1), contributing (month 2), and owning (month 3).
A 90-day plan is a documented roadmap that outlines what a new employee should learn, accomplish, and demonstrate during their first three months. It serves two purposes: giving the new hire clarity on expectations, and giving the manager a framework for evaluating early performance. Without a 90-day plan, new hires operate in a fog. They don't know what's expected. They can't tell whether they're doing well or falling behind. They hesitate to ask because they don't want to seem incompetent. By the time the first formal review arrives (often at 6 months or a year), frustration has already built up on both sides. SHRM identifies the first 90 days as the period where new hires form their lasting impression of the organization. The Work Institute's 2023 Retention Report found that 25% of employees who leave within the first year cite a lack of clear expectations as a primary reason. A 90-day plan directly addresses that gap.
90-day plan vs 30-60-90 day plan
A 90-day plan is a general term for any structured plan covering the first three months. A 30-60-90 day plan is a specific format that breaks those three months into three distinct phases, each with different objectives. The 30-60-90 model is the most popular version of a 90-day plan and is covered in its own glossary entry. Not all 90-day plans follow the 30-60-90 structure. Some organizations use milestone-based plans tied to specific deliverables rather than time-based phases.
Who creates the 90-day plan?
In most cases, the hiring manager creates the initial plan before the new hire starts, then refines it collaboratively during the first week. For senior roles, the new hire might draft their own 90-day plan as part of the interview process or during the first few days, which the manager then reviews and adjusts. The best 90-day plans are co-created: the manager brings organizational context and role expectations, and the new hire brings their perspective on where they can add value fastest.
How to Structure a 90-Day Plan
A practical 90-day plan includes goals, activities, resources, and success measures for each month. Here's a framework that works across roles and industries.
| Element | Month 1: Learn | Month 2: Contribute | Month 3: Own |
|---|---|---|---|
| Primary focus | Absorb context, build relationships, understand systems | Start delivering on small projects with support | Take full ownership of key responsibilities |
| Knowledge goals | Understand product/service, team structure, key processes | Deep-dive into role-specific tools and workflows | Identify improvement opportunities and propose solutions |
| Relationship goals | Meet all team members and key cross-functional partners | Build working relationships with 5 to 10 stakeholders | Establish yourself as a reliable contributor and collaborator |
| Deliverables | Complete onboarding tasks, shadow team members, document learnings | Deliver 1 to 2 small projects or contributions independently | Own a full workstream or project and deliver measurable results |
| Check-in cadence | Weekly 1:1 with manager, daily buddy check-ins | Weekly 1:1 with manager, bi-weekly buddy meetings | Weekly 1:1 with manager, 90-day review meeting |
90-Day Plans by Role Type
A 90-day plan for a software engineer looks completely different from one for a sales representative or an HR manager. Here are role-specific examples.
Software engineer
Month 1: Set up development environment, review codebase architecture, complete 2 to 3 small bug fixes, shadow code reviews. Month 2: Own a feature or story from sprint planning through deployment, participate in on-call rotation (shadowing), submit first independent pull request for a medium-sized feature. Month 3: Lead a feature delivery end-to-end, contribute to architecture discussions, begin mentoring newer team members on the codebase. Success metric: independently delivering sprint commitments by Day 90.
Sales representative
Month 1: Complete product training, shadow 20+ sales calls, memorize the pitch deck and objection-handling playbook, meet all sales engineering and customer success partners. Month 2: Run 10+ discovery calls independently with coaching, submit first 5 proposals, build a pipeline of 15+ qualified leads. Month 3: Close first deal(s), manage a pipeline worth 3x monthly quota, deliver a presentation at team meeting on learnings. Success metric: pipeline generation at 80%+ of quota by Day 90.
HR manager
Month 1: Audit current HR processes, meet all department heads and understand their pain points, review compliance documentation, learn the HRIS and payroll systems. Month 2: Address 2 to 3 quick-win process improvements, draft or update 1 policy document, begin building relationships with external partners (legal counsel, benefits broker, recruitment agencies). Month 3: Present an HR roadmap for the next 12 months, own the next hiring cycle end-to-end, implement 1 measurable process improvement. Success metric: stakeholder satisfaction survey scores of 4+/5 by Day 90.
Writing Effective 90-Day Goals
Vague goals are worse than no goals at all. They create the illusion of clarity while leaving both parties free to interpret "success" differently. Here's how to write goals that actually work.
Use the SMART framework
Every goal in the 90-day plan should be Specific (what exactly will be done), Measurable (how will completion be verified), Achievable (is it realistic for a new hire), Relevant (does it align with the role and team priorities), and Time-bound (which month should it be completed by). Bad example: "Learn the product." Good example: "Complete all 6 product training modules and pass the product knowledge quiz with 80%+ by end of Month 1."
Balance learning goals with delivery goals
Month 1 should be heavily weighted toward learning (80% learning, 20% delivery). Month 2 shifts to a balanced split (50/50). Month 3 should emphasize delivery (20% learning, 80% delivery). New hires who are pushed to deliver too early burn out or make avoidable mistakes. New hires who are kept in learning mode too long feel unproductive and disengaged.
Include relationship goals
Technical skills and deliverables are easy to measure, but relationships determine long-term success. Include goals like "Meet with each department head for 30 minutes by end of Month 1" or "Identify your top 5 cross-functional partners and schedule recurring touchpoints by end of Month 2." New hires who build strong internal networks ramp faster and stay longer.
Manager's Role in the 90-Day Plan
The 90-day plan is only as good as the manager's commitment to it. Writing the plan takes 30 minutes. Supporting the new hire through it takes consistent effort over 3 months.
Before Day 1
Draft the 90-day plan and share it with the new hire during the pre-boarding phase. This gives them time to ask questions and mentally prepare. It also signals that the organization has thought carefully about their role and success.
Week 1
Walk through the plan together. Discuss each goal, adjust anything that doesn't make sense, and agree on how progress will be tracked. Clarify what "good" looks like for each deliverable. Set up the weekly 1:1 meeting cadence.
Ongoing
Reference the 90-day plan in every weekly 1:1. It should be a living document, not something filed and forgotten. If priorities change (they often do), update the plan together. Provide feedback in real time, not just at the 90-day mark. Small corrections in Week 2 prevent big problems in Month 3.
Day 90 review
Conduct a formal 90-day review meeting. Go through each goal and assess completion. Discuss what went well, what was challenging, and what support the new hire needs going forward. Create a transition plan from "new hire" to "full team member" with goals for the next quarter. If the 90-day period aligns with probation, this review may also determine confirmation of employment.
90-Day Plan Templates
A reusable template ensures consistency across hires and makes it easier for managers to create plans without starting from scratch.
- Section 1: Role summary (job title, reporting line, team, key responsibilities)
- Section 2: Month 1 goals with 4 to 6 specific, measurable objectives covering learning, relationships, and initial deliverables
- Section 3: Month 2 goals with 4 to 6 objectives covering contribution, skill development, and stakeholder engagement
- Section 4: Month 3 goals with 4 to 6 objectives covering ownership, performance targets, and future planning
- Section 5: Resources (key documents, training materials, system access, team contacts)
- Section 6: Check-in schedule (weekly 1:1s, mid-point review at Day 45, formal 90-day review)
- Section 7: Success criteria (what does "passing" the 90-day period look like?)
Common 90-Day Plan Mistakes
Even well-intentioned plans fail when they're designed poorly or executed inconsistently.
Setting unrealistic expectations
Loading Month 1 with delivery targets for a new hire who hasn't learned the systems yet guarantees failure and frustration. Month 1 should be 80% learning. A new hire can't close deals, ship features, or fix processes they don't yet understand.
Creating the plan and never referencing it again
A 90-day plan sitting in a Google Doc that nobody opens after Week 1 is worthless. Integrate it into weekly 1:1s. Pull it up on screen during every check-in. Track progress visually. When the plan is a living document, it works. When it's a one-time exercise, it doesn't.
Making it one-directional
Plans that are handed to the new hire without discussion miss half the value. The new hire has context from their interviews, their past experience, and their early observations. Let them contribute to the plan. Co-creation builds ownership and accountability.
Ignoring cultural and relational goals
Plans that only include task-based goals miss the fact that new hires also need to build social capital, understand team norms, and feel like they belong. A new hire who delivers on all their technical goals but has no relationships is likely to leave within 18 months.
Frequently Asked Questions
Is a 90-day plan only for new hires?
What happens if the new hire doesn't meet their 90-day goals?
Should the new hire write their own 90-day plan?
How detailed should a 90-day plan be?
Can a 90-day plan be adjusted mid-course?
Written by Adithyan RK