The 30-60-90 Day Plan: Complete Guide With Templates and Examples
What a 30-60-90 day plan is, what to include, and how to create one. Includes filled-in examples for new hires, managers, and sales roles.
The 30-60-90 Day Plan
Complete guide with templates, examples, and goals for every phase
At a previous company, I handed every new hire a laptop, said "ask if you need anything," and went back to work. By month two, they were frustrated. By month four, several were gone. Not because they were bad hires. Because I had given them no roadmap.
A 30-60-90 day plan fixes that. It is the simplest tool I know for turning a confused new hire into a productive team member, and for helping a new manager or salesperson figure out where to focus before they get overwhelmed. It is one of the frameworks I built into FirstHR because structured transitions produce better outcomes than winging it, and that pattern holds across every company size and role type.
This guide covers everything: what a 30-60-90 day plan actually is, the four main types, what to put in each phase, filled-in examples for three scenarios, how to create one step by step, what to look for when a candidate brings one to an interview, how to adapt it for remote employees, and the mistakes that make these plans useless.
What Is a 30-60-90 Day Plan
A 30-60-90 day plan is a structured document that breaks the first three months of a new role into three phases, each with distinct goals and expectations. The 90-day window echoes "The First 90 Days" by Michael Watkins, which SHRM calls his seminal book on leadership transitions.
The core idea is simple: rather than expecting someone to figure out their first three months on the fly, you give them (and yourself) a shared map. Everyone knows what success looks like at day 30, day 60, and day 90. Check-ins happen on schedule, and you adjust the plan as you go.
Each phase builds on the previous one. You cannot contribute effectively without first learning. You cannot own something you have not yet contributed to. The sequence is intentional, and skipping phases is the most common reason these plans fail.
A weak start costs you quickly. Research reported by SHRM (2017) shows that up to 20% of employee turnover occurs within the first 45 days of employment, which falls inside the window this framework exists to structure.
What Is the 30-60-90 Rule?
The 30-60-90 rule is the same framework under a different name: learn first, contribute second, own third, with a checkpoint at the end of each thirty-day block. People who say "rule" usually mean the sequence is not optional. People who say "plan" usually mean the written document.
The practical version for a manager fits in one line: do not ask for output in month one, and do not accept dependence in month three. If someone is still shadowing at day 75, the plan slipped somewhere in phase two, and the place to fix it is the day-60 review rather than a surprise at day 90.
Types of 30-60-90 Day Plans
The 30-60-90 framework applies in four main contexts. The structure is the same across all of them. What changes is who creates it and what the goals focus on.
The most common confusion: people treat "30-60-90 day plan" as exclusively an onboarding tool. It is not. New managers use it to establish themselves without alienating their team. Salespeople use it to hit revenue targets faster. Candidates use it to stand out in interviews. The framework works in all four contexts because the underlying logic is universal: a structured transition beats improvising.
This guide is written for small businesses without an HR department, so it sticks to the practical details of running the process when you are doing everything yourself, including where compliance deadlines and paperwork fit into the plan.
What to Include in Each Phase
Every phase of a strong 30-60-90 plan addresses the same three questions, just at different levels of depth and independence:
- Learning goals: What do they need to know or understand by the end of this phase?
- Performance goals: What do they need to deliver or accomplish?
- Relationship goals: Who do they need to meet and build trust with?
Each goal needs a success metric. "Understand the product" is not a goal. "Pass the product certification quiz with 80%+ score" is a goal. The difference is evaluability: can you look at it on day 30 and say definitively "yes" or "no"?
You also need:
- Check-in schedule: Daily 15-minute syncs in week one, twice weekly in weeks 2-4, weekly in months 2-3, formal reviews at days 30, 60, and 90.
- Resources and training: What tools, courses, or people does the person need access to? List them so nobody has to ask later.
- Known constraints: What will make this hard? A product launch in month two, a team vacation, a major deadline? Flag them early so goals can be calibrated accordingly.
If the role carries real training, sequence it across the phases instead of dumping all of it into week one. A 30-60-90 training plan puts compliance and systems in the first thirty days, supervised practice in the second, and saves the deeper material for the last thirty, when the person has done enough of the job for it to land.
30-60-90 Goals by Phase
These are the types of goals that work at each phase. Adapt them to the specific role. The categories stay the same; the specifics change based on what the job actually requires.
Notice the progression. Day-30 goals are about absorbing and building trust. Day-60 goals are about applying and proving competence. Day-90 goals are about leading and being trusted without supervision. Each set of goals prepares the person for the next phase rather than jumping straight to independence.
The goals in every phase fall into three categories. Learning goals cover what the person needs to understand: systems, processes, key customers, team dynamics. Performance goals cover what they need to deliver: outputs, metrics, tangible work products. Relationship goals cover who they need to connect with: direct team, cross-functional stakeholders, key customers or partners.
Leaving a category out tilts the plan. A plan with only performance goals ignores the fact that relationships determine whether those performance goals are even achievable. A plan with only learning goals gives no accountability for output. Keep all three categories in every phase, and shift the balance toward performance as the phases progress.
The most useful goals have a specific number attached. Not "build relationships with the team" but "complete 1:1s with all 6 team members by day 30." Not "learn the product" but "pass product knowledge quiz with 85%+ and demo the product end-to-end without assistance."
Quantified goals are not micromanagement. They give the person a clear target to self-assess against. When someone knows they need to complete 6 specific conversations by day 30, they can track their own progress. When the goal is just "get to know people," there is no way to know if they are on track.
Filled-In Examples for Three Scenarios
Below are three complete, filled-in 30-60-90 day plans for the most common use cases. Adapt the goals to your specific role and company context. The structure is what matters; the specifics should reflect your reality.
One note on format before the examples. They use a table structure because it makes the goals scannable at a glance. In practice, your plan can be a table, a simple list, or a structured document. What matters is that every phase has clear goals and clear metrics, and that both manager and employee can reference it without effort. Pick the format your team will actually use.
Example 1: New Employee (General Hire)
This plan works for most individual contributor roles: customer success, operations, marketing, admin, and similar functions. The goals are intentionally broad so you can adapt the specifics to your role.
The key features of this plan: phase one is weighted toward learning and relationship-building, and its success metrics measure learning (calls shadowed, certification passed) rather than output. Phase two introduces independent work but still includes a relationship goal. Phase three shifts the balance fully toward ownership and independent output.
| Phase | Learning Goal | Performance Goal | Relationship Goal | Success Metric |
|---|---|---|---|---|
| Days 1-30 | Complete orientation, compliance paperwork, and product training | Explain the product end to end to a colleague | Meet everyone you will work with weekly | Shadow 5 customer calls; pass the product certification |
| Days 31-60 | Learn the escalation path and the tools behind it | Own 3 accounts and handle tier-1 tickets solo | Build one working relationship outside your team | Solo call rating averaging 3.8 or better; 1 process fix proposed |
| Days 61-90 | Understand how the role feeds this quarter's priorities | Lead a small project from start to finish | Train the next new hire on your core tool | Project delivered independently; 90-day review completed |
Notice that each phase carries exactly three goals and one short line of success metrics. This is not a hard rule, but it is a useful default. Three goals give the new hire enough to focus on without overwhelming them. A short, checkable metrics line per phase makes the review conversation simple: did they hit it or not?
Example 2: New Manager or Team Lead
This plan is for someone transitioning into a leadership role, either as a first-time manager or as an experienced manager new to this team. The key rule: observe before changing anything. Managers who restructure in week two break trust before they have earned it.
The manager plan looks different from the individual contributor plan in one important way: the goals are organized around people, operations, and strategy rather than learning, performance, and relationships.
The people-first structure reflects the reality of management. In month one, a new manager's primary job is to understand their team and build enough trust to lead effectively, not to learn the product or master their individual skills. The rest of the plan builds on that trust.
| Phase | People Goal | Operational Goal | Strategic Goal | Success Metric |
|---|---|---|---|---|
| Days 1-30 | Meet every direct report 1:1 | Map the team's current projects and blockers | Shadow existing processes before changing anything | Complete 1:1s with all 8 reports; map all active projects |
| Days 31-60 | Build working relationships with peer managers | Run team meetings independently | Make your first hire or process decision | Team meeting satisfaction score 4+/5; one decision made with documentation |
| Days 61-90 | Give every report a development goal for next quarter | Resolve one legacy team problem | Own team OKRs and present results to leadership | OKRs set and approved; presentation delivered |
Example 3: Sales Role Ramp
Sales plans are more metrics-driven than plans for other roles. The success metrics are usually revenue targets and pipeline activity numbers. Calibrate the day-90 quota target based on your typical sales cycle length: if your average deal takes 90 days to close, 50% of quota by day 90 is realistic; if your cycle is 30 days, you might target 80%.
The sales plan deliberately delays revenue goals until phase two. This surprises some managers who want to see revenue from day one. The logic is sound: a rep who tries to sell before they truly understand the product will burn leads, not convert them.
The investment in product mastery during phase one pays back in phases two and three with higher conversion rates and shorter sales cycles. The shadow calls in phase one are critical because they expose the new rep to real objections in a low-stakes environment before they are responsible for the outcome.
| Phase | Knowledge Goal | Activity Goal | Revenue Goal | Success Metric |
|---|---|---|---|---|
| Days 1-30 | Complete product certification and learn the ICP | Shadow 10 sales calls | No quota; revenue goals start in phase two | Pass product quiz; summarize 3 call recordings |
| Days 31-60 | Know the top 5 objections and the answers that work | Run 5 discovery calls and build a pipeline of 20 qualified leads | Close first deal (any size) | 5 solo discovery calls logged; 20 prospects in CRM |
| Days 61-90 | Know the product well enough to write a playbook section | Own full pipeline management | Hit 50% of full quota | Monthly revenue target met at 50% or better; playbook section written |
How to Create a 30-60-90 Day Plan (Step by Step)
Knowing how to write a 30-60-90 day plan comes down to seven steps: define success at day 90, write goals for each phase, attach a metric to every goal, list the resources, schedule the three reviews, co-create the plan with the new hire, and adjust it at every review. You do not need a special template or software. A well-structured Google Doc is enough.
SHRM's onboarding guidance describes onboarding as a comprehensive process that can last up to 12 months, not a one-time orientation for paperwork. The 30-60-90 framework applies the same logic to the first three months. Here is the process that works.
Step 1: Define what success looks like at day 90
Before writing a single goal, answer this question: if this person is fully successful, what are they doing independently by day 90? Work backward from that answer. The 30-day and 60-day goals exist to make day 90 possible.
If you are building a broader employee onboarding plan that includes paperwork, training schedules, and compliance steps alongside the 30-60-90 goals, start with the overall plan structure first, then plug the phase goals in.
Step 2: Write goals for each phase
For each phase, define 3-5 goals across the three categories: learning, performance, and relationships. Start with day 90, then day 60, then day 30. Writing backward makes each phase genuinely prepare for the next. Writing forward tends to front-load too much into phase one, while starting at day 90 and working back spreads the load naturally across all three phases.
Keep the language simple and direct. Goals that sound impressive in documents but are hard to evaluate in practice are useless. Every goal should pass this test: could a reasonable person look at this goal at its review and give you a clear yes or no on whether it was achieved? If the answer is maybe, rewrite the goal until the answer is yes or no.
Step 3: Attach a metric to every goal
For every goal, add a success metric: "Complete product certification quiz with 80%+," "Handle 3 accounts independently," "1:1 with all 8 direct reports completed." Vague goals are uncheckable. Specific metrics make reviews productive.
Step 4: List the resources they need
What tools, logins, training materials, or introductions does the person need to accomplish the goals? List them. This forces you to ensure everything is ready before the person starts, and gives them a reference when they forget what they are supposed to have access to.
At a small business, this step often reveals gaps: the training documentation that does not exist yet, the tool access that takes three days to provision, the introduction to a key customer that requires advance coordination. Finding these gaps during planning is far better than finding them on day one, with the new hire sitting there waiting.
Step 5: Schedule the three reviews in advance
Block 45-60 minutes on the calendar for the day-30, day-60, and day-90 reviews before the person starts. Unscheduled reviews get postponed, and a review that slips once rarely happens at all.
The milestones are not arbitrary. The SHRM Foundation onboarding guidelines written by Talya Bauer (2010) recommend check-ins at 30, 60, 90, and 120 days, and then out to a year after entry. That is why day 90 works better as a handoff into ordinary management than as an ending.
Step 6: Co-create it with the new hire
Share a draft before the person's first day. Ask them to review the goals and flag anything that seems unclear, unrealistic, or missing. Their input improves the plan, and their buy-in dramatically increases the chance they actually follow it. Nobody ignores a plan they helped write.
Co-creation also surfaces information you do not have. A new hire who has done similar roles before may tell you that your day-30 goals are too easy given their background, or that one of your day-60 goals depends on a relationship that will take longer than 60 days to build.
Feedback like that does two jobs. It makes the plan more accurate, and it signals to the new hire that you care about their actual success, not just the appearance of a structured onboarding process.
Step 7: Adjust at every review
At each 30-day review, assess what happened, document what worked and what did not, and update the goals for the next phase. The plan is a hypothesis. Reality will change it. That is expected and fine. A plan that adjusts to reality is more useful than a plan that ignores it.
The day-30 review is especially important because it sets the tone for how seriously both of you take the document. The quality of that day-30 conversation determines how much you both invest in the day-60 and day-90 reviews.
A genuine two-way conversation about progress, gaps, and what to adjust teaches the new hire that the plan is a real management tool. A five-minute formality where you say "looks good, keep going" teaches them the plan is theater. Treat the first review accordingly.
How Long Should a 30-60-90 Day Plan Be
One page is ideal for most roles, and two pages covers nearly everyone. The length depends on the role level, not on how much effort you put in.
| Role Level | Ideal Length | What to Include |
|---|---|---|
| Entry-level individual contributor | 1 page | 30-60-90 structure + 3 goals per phase + check-in dates |
| Mid-level professional | 1-2 pages | Goals by phase + success metrics + key relationships to build |
| Senior IC or specialist | 2 pages | Phase goals + metrics + strategic priorities + how they'll add value |
| Manager or team lead | 2 pages | People + operational + strategic goals by phase + first decisions to make |
| Director or VP | 2 pages | Full stakeholder map + org health assessment + 90-day strategic priorities |
The usual trap here is confusing length with thoroughness. A two-page plan with 5 specific, measurable goals per phase is more useful than a five-page plan with 20 vague bullet points. The person using the plan needs to be able to reference it in 30 seconds. If they have to read for five minutes to remember what their goals are, the plan is not doing its job.
How to Evaluate a 30-60-90 Day Plan in a Job Interview
When a candidate brings a 30-60-90 day plan to an interview, read it as a work sample rather than a promise. It shows how the person researches a company, sets priorities, and thinks about a transition. It cannot show what they will actually deliver, because they have not yet seen your numbers, your team, or your customers.
A candidate's plan is not an official document. It is a conversation starter, and the most useful thing you can do with it is test the thinking behind it. Look for evidence that the candidate researched the company, understood the role, and formed a sensible hypothesis about how to add value quickly. The official plan is still yours to write once they are hired.
What a Strong Interview 30-60-90 Plan Includes
A good interview plan mirrors the standard structure, but everything in it is framed as intention rather than agreement. The candidate is working from public information, the job description, and whatever they picked up in earlier interview rounds, so judge the quality of the reasoning rather than the precision of the guesses.
| Phase | Evidence of Research | What a Strong Plan Includes | Red Flags |
|---|---|---|---|
| Days 1-30 | Knows your culture, team structure, and current priorities | Learning goals, key people to meet, questions they plan to ask | Specific deliverables they cannot know yet |
| Days 31-60 | Understands department goals, recent challenges, and your product or service | Initial contributions they plan to make, skills they will apply | Promises about metrics they have no data for |
| Days 61-90 | Understands your strategic priorities and how success is measured in the role | Longer-term goals, how they expect to add value | Overpromising, or critiquing your current processes |
The best interview 30-60-90 plans are specific but humble. They show real research while acknowledging that the candidate does not have the full picture yet.
A plan that says "I will increase revenue by 40% in 90 days" reads as naive. A plan that says "By day 60, I want to have a clear hypothesis about which customer segment has the most untapped potential, based on conversations with the sales team" reads as thoughtful.
How to Discuss It in the Interview
Treat the plan as a conversation prompt, not a presentation to sit through. Ask the candidate to walk you through it, then test the assumptions: which ones they are least sure of, where each number came from, and what they would change if a day-30 goal turned out to be wrong.
That turns the interview into a working session for the hiring manager. You see how the candidate takes correction, and you learn as much from how they revise an assumption as from the plan itself. If you want every finalist to bring one, ask for it in advance and set the same length for all of them, so you compare like with like.
The 30-60-90 Day Business Plan in Sales Hiring
In sales hiring, the same document often goes by a different name: a 30-60-90 day business plan. Interview prep resources coach sales candidates to build one before the interview, so if you hire reps, expect experienced candidates to bring one and read it as a work sample rather than a promise.
A strong one names your actual territory, accounts, or customer segments and says what the candidate would do about them. A weak one is a generic template with a revenue number attached to nothing. Ask where each number came from. The answer tells you more about the person than the document does.
30-60-90 Day Plans for Remote Employees
The 30-60-90 framework works for remote employees, but it requires deliberate adjustments. The structure stays the same: three phases, phase-specific goals, scheduled reviews. What changes is how you compensate for the absence of physical proximity, which is where most remote onboarding falls apart.
When someone works in the same office, a lot of relationship-building and context-absorption happens passively: overhearing conversations, reading body language in meetings, grabbing lunch with a colleague. Remote employees get none of that. Every bit of context they need has to be intentionally provided. That means the 30-day learning phase requires more structure, not less, when the person is remote.
| Standard Plan Element | Remote Adjustment | Why It Matters |
|---|---|---|
| Daily check-ins (week 1) | Video required, not optional | Text check-ins miss tone and early warning signs of confusion |
| Meet key team members | Structured intro calls scheduled by manager | Remote hires will not organically meet people without prompts |
| Shadow work being done | Screen share sessions + recorded walkthroughs | Passive observation does not exist remotely |
| Buddy assignment | Buddy proactively reaches out daily for first 2 weeks | Remote buddies must be more intentional than in-person ones |
| 30-day goals | Add documentation goal: write down 3 things learned each week | Forces reflection and creates a knowledge base for the new hire |
| 60/90-day reviews | Video call with camera on, shared doc reviewed together | Written-only reviews miss the relationship-building value |
The most important remote-specific adjustment is communication frequency in phase one. At an in-person company, daily 15-minute check-ins in week one feel natural. At a remote company, managers often skip them because scheduling feels like overhead.
Skipping them is exactly the wrong call. Remote new hires who do not hear from their manager daily in week one feel invisible, and feeling invisible in week one leads to disengagement by week four.
How to Adapt the Plan for Different Industries
The 30-60-90 framework is industry-agnostic, but the specific goals inside each phase vary significantly depending on what the job actually requires. A customer service rep at a software company has a completely different set of day-30 priorities than a truck driver joining a small fleet or a nurse starting at a medical practice. The structure is universal; the content is not.
Here is how the focus shifts by industry:
| Industry | Days 1-30 Priority | Days 31-60 Priority | Days 61-90 Priority |
|---|---|---|---|
| Tech / SaaS | Product mastery, tool access, codebase or platform walkthrough | Own first feature, ticket, or customer interaction | Contribute to roadmap or process improvements independently |
| Healthcare / Medical | HIPAA training, EMR system, clinical protocols and compliance | Handle patient interactions with supervision | Operate independently within scope; participate in care team |
| Retail / Customer Service | Product knowledge, POS system, customer service standards | Handle transactions and complaints solo | Train new team members; hit customer satisfaction targets |
| Manufacturing | Safety protocols, equipment operation, OSHA basics | Operate equipment independently with floor mentor | Full shift ownership; achieve target output metrics |
| Professional Services | Client roster, project methodology, billing systems | Support client deliverables with minimal oversight | Own client relationship or project phase independently |
| Real Estate | MLS, contracts, brokerage compliance, E&O coverage | Lead first transaction with broker supervision | Close first independent deal; maintain pipeline |
Two settings deserve special attention. Healthcare plans have compliance requirements built in that non-regulated industries do not face, and sales-heavy teams need a ramp table alongside their 30-60-90 plans.
Healthcare
Healthcare onboarding plans must include training milestones that are not optional: HIPAA (Health Insurance Portability and Accountability Act) training, scope-of-practice review, EMR (electronic medical record) certification, and any facility-specific protocols. The HIPAA Privacy Rule requires training for each new member of the workforce within a reasonable period of time after the person joins (45 CFR 164.530(b)).
That wording puts the date in your hands, which is exactly why it belongs on the plan. A 30-60-90 plan for a healthcare employee should separate compliance milestones (non-negotiable, tied to a date you set and then have to defend) from performance goals (flexible, adjustable as progress dictates). Missing one is a different category of problem than missing the other.
Sales-Heavy Environments
Sales plans need a ramp table in addition to the 30-60-90 goals. A ramp table shows the expected quota attainment percentage at each milestone: 0% at day 30 (still learning), 25-30% at day 60 (first independent deals), 50-70% at day 90 (approaching full productivity).
The exact percentages depend on your sales cycle length and product complexity. What matters is that the new rep and their manager agree on the ramp table before the rep starts, so there is no ambiguity about what constitutes acceptable performance at each milestone.
Without a ramp table, sales managers often fall into one of two traps: holding new reps to full quota from day one (which is unrealistic and demoralizing) or never establishing clear expectations (which creates anxiety about what success looks like). The ramp table solves both problems by making the progression explicit.
Fill this in with the rep before their first day, and have both of you initial it. It sits alongside the 30-60-90 plan rather than inside it, because the plan describes what the rep will learn and do while the ramp table sets the number they will be measured against.
| A | B | C | D | E | F | G | H | |
|---|---|---|---|---|---|---|---|---|
| 1 | Milestone | Typical range in this guide | Agreed quota target | Activity target (calls, demos, meetings) | Pipeline target | Support in place (shadowing, coaching, leads) | Reviewed on | Initials, rep and manager |
| 2 | Day 30 | 0% of quota, still learning | ||||||
| 3 | Day 60 | 25 to 30% of quota | ||||||
| 4 | Day 90 | 50 to 70% of quota | ||||||
| 5 | Beyond day 90, only if your sales cycle runs longer than 90 days | Set it from your own average cycle length |
Common Mistakes That Make Plans Useless
After running dozens of these plans across different companies and roles, I keep seeing the same five mistakes. All of them are avoidable.
One root cause sits behind all five: treating the 30-60-90 plan as a formality rather than a working tool. Companies that use it as a checkbox create plans that sit in a folder and accomplish nothing. Companies that use it as an actual management tool schedule reviews, adjust goals, and track what happens. The document can be identical, and the outcome completely different.
One more mistake worth naming: writing the plan and never sharing it with the new hire before day one. The plan should land in the new hire's inbox during preboarding, alongside their offer letter and start date logistics.
When someone shows up on day one having already read their 30-60-90 plan, the first conversation is about goals instead of paperwork. That shift in tone matters more than any single goal on the document.
Frequently Asked Questions
What is a 30-60-90 day plan?
A 30-60-90 day plan is a written roadmap for someone's first three months in a new role, split into three phases: learning (days 1-30), contributing (days 31-60), and owning (days 61-90). Every phase gets its own goals, milestones, and success metrics, so progress can be checked at each review. It is used to onboard new employees, transition managers into leadership roles, and ramp up salespeople, and job candidates use it to show strategic thinking in interviews.
What should a 30-60-90 day plan include?
A 30-60-90 day plan should include: specific goals for each 30-day phase (learning, performance, and relationship goals), measurable success metrics per phase, a check-in schedule (day 30, 60, and 90 reviews), key relationships to build, and training or resources needed. Each phase should have 3-5 concrete goals, not vague targets. The entire plan should fit on one to two pages.
How long should a 30-60-90 day plan be?
One page is right for most roles, and two pages should be the ceiling. Entry-level and mid-level plans usually fit on a single sheet, while senior and leadership plans may need a second page for their wider stakeholder maps and strategic priorities. When a plan spills past two pages, it is overbuilt, and a document nobody rereads does nothing for the new hire. Keep each phase to 3-5 specific, measurable goals.
Who creates a 30-60-90 day plan?
It depends on the use case. For new employee onboarding, the manager typically creates the plan before the hire starts. For new manager transitions, the manager creates their own plan with input from their supervisor. In sales roles, the sales manager and new rep often co-create the plan. For job interviews, the candidate creates a speculative plan independently to demonstrate strategic thinking. The best plans are co-created, regardless of who initiates them.
What is a 30-60-90 day plan for a job interview?
An interview 30-60-90 day plan is a document a job candidate prepares to show what they would accomplish in their first three months if hired. For the employer, it works as a work sample: it shows how the candidate researches a company, sets priorities, and thinks about a transition. A strong one includes phase-specific goals, key relationships to build, questions the candidate plans to ask, and how they would measure their own success, all framed as hypotheses rather than promises. Use it as a conversation starter and probe the assumptions behind it. It does not replace your own plan: the hiring manager still writes the official version once the person is hired.
What is the difference between a 30-60-90 day plan for a new employee and a new manager?
The structure is the same but the focus differs significantly. A new employee plan prioritizes learning the role, building skills, and contributing to existing work. A new manager plan prioritizes understanding the team, establishing trust, making early decisions, and building relationships with peers and leadership. New managers need to listen before changing anything. The first 30 days should involve observation, not restructuring. Both plans use the same three-phase framework with phase-appropriate goals.
How do you write a 30-60-90 day plan?
Start with the three phases: learn, contribute, own. For each phase, define 3-5 specific goals across three categories: what they need to learn, what they need to do or deliver, and what relationships they need to build. Add success metrics for each goal so you can evaluate objectively at the day-30, day-60, and day-90 reviews. Schedule those reviews before the person starts. Keep the whole plan to one or two pages. Co-create it with the new hire if possible.
Can a 30-60-90 day plan be adjusted after it starts?
Yes, and it should be. A 30-60-90 plan is a hypothesis about what the new hire needs. Reality will not match it perfectly. If the person learns faster or slower than expected, adjust the goals at the day-30 or day-60 review. If business priorities shift, update the plan to reflect them. The goal is successful performance, not rigid adherence to a document. The best plans are living documents that evolve with the person.