30/60/90 Day Plan
A 30/60/90 day plan for a new hire β outcomes per phase, owners, check-ins.
More from Recruiting
What you get
A 30/60/90 day plan for a new hire in a personalised, text-based format. You get a 3-phase plan with outcomes, owners, and check-ins.
Who it's for
- New team leaders
- Hiring managers
- Recruitment specialists
- HR generalists
Use cases
- Onboarding a new software engineer
- Creating a plan for a marketing intern
- Setting goals for a sales team member
- Developing a personalised plan for a data analyst
- Outlining objectives for a customer support agent
FAQ
what is a 30 60 90 day plan
A 30/60/90 day plan is a structured approach to onboarding new hires, outlining specific goals, owners, and check-ins for each phase. It typically consists of three phases, each with its own set of objectives and milestones.
how long is the 30 60 90 day plan
The plan is divided into three phases, each with a specific duration: 30 days, 60 days, and 90 days. You'll get a plan with outcomes, owners, and check-ins for each phase.
what format is the plan in
The 30/60/90 day plan is delivered in a text-based format, outlining specific goals, owners, and check-ins for each phase. You'll get a personalised plan tailored to your new hire's role and context.
how much does the 30 60 90 day plan cost
The 30/60/90 day plan costs Β£1.00. You'll get a comprehensive, personalised plan to help your new hire succeed in their role.
Sample output
**Day 1β30** * Goal: Paired on payment service extraction PR and shipped one bug fix to production end-to-end. * Goal: Completed a technical design document for a small feature. * Goal: Implemented a test for an existing endpoint. * Owner: New hire pairs with Lena for onboarding and guidance. **Day 1β30** * Owners: Lena (onboarding buddy), Alex (technical lead for payments service extraction). * Owners: Michael (manager for regular check-ins). * Check-ins: 30-min weekly with Michael, 30-min Friday with Lena. * Check-ins: Ad-hoc meetings with Alex for design document review. **Day 1β30** * Check-ins: Submit a self-assessment of progress and goals for the next sprint. * Check-ins: Receive feedback on design document and test implementation. * Check-ins: Discuss and align on priorities for the next sprint. * Check-ins: Review PRs and provide constructive feedback to teammates. **Day 31β60** * Goal: Led a small feature development and shipped to production. * Goal: Completed a code review for a teammate's PR. * Goal: Paired with Alex on a complex payment service extraction task. * Goal: Implemented monitoring for a critical endpoint. **Day 31β60** * Owners: Alex (technical lead for payments service extraction), Lena (onboarding buddy). * Owners: Michael (manager for regular check-ins), Rachel (devops for monitoring guidance). * Check-ins: 30-min bi-weekly with Michael, 30-min weekly with Alex. * Check-ins: Ad-hoc meetings with Rachel for monitoring implementation review. **Day 31β60** * Check-ins: Submit a self-assessment of progress and goals for the next sprint. * Check-ins: Receive feedback on feature development and code review. * Check-ins: Discuss and align on priorities for the next sprint. * Check-ins: Review team's PRs and provide constructive feedback. **Day 61β90** * Goal: Owned a significant component of the payments service extraction. * Goal: Completed a performance optimization for a critical endpoint. * Goal: Mentored a junior engineer on a small feature development. * Goal: Developed a technical roadmap for a future feature. **Day 61β90** * Owners: Alex (technical lead for payments service extraction), Michael (manager). * Owners: Rachel (devops for monitoring guidance), junior engineer (mentee). * Check-ins: 30-min monthly with Michael, 30-min bi-weekly with Alex. * Check-ins: Ad-hoc meetings with Rachel for performance optimization review. **Day 61β90** * Check-ins: Submit a self-assessment of progress and goals for the next quarter. * Check-ins: Receive feedback on performance optimization and technical roadmap. * Check-ins: Discuss and align on priorities for the next quarter. * Check-ins: Review team's technical roadmaps and
Last updated: 2026-06-28