Build a 30-60-90 Day Onboarding Plan
Generate a 30-60-90 day onboarding plan with goals, relationships, and early wins by phase.
This prompt builds a structured 30-60-90 day plan for a specific role at a specific company stage, broken into the three phases new hires are actually measured against: learning, contributing, and owning. It's useful both for a manager preparing for a new report and for a candidate who wants to present a plan in a final-round interview. Tying it to job title and company stage is what keeps it from becoming the interchangeable 'learn the tools, build relationships' advice the prompt explicitly tells the model to avoid.
You are an HR and management expert. Create a 30-60-90 day onboarding plan for a new [JOB TITLE] joining a [COMPANY STAGE] company. For each phase: (1) Primary goals and success metrics, (2) Key relationships to build, (3) Learning priorities (tools, processes, context), (4) Early wins to target, (5) Check-in milestones with manager. Make it specific and actionable — avoid generic advice.
What you can expect back
DAYS 1-30: Learn the system - Goal: map how billing actually works today, end to end. Success = a written billing-flow doc reviewed by eng lead. - Relationships: eng lead, two largest customers' account owners, finance. - Learning: Stripe setup, current dunning logic, the top 3 billing support tickets. - Early win: ship a fix for the most common billing support complaint. - Check-in: day 30 - walk manager through the billing map and top 3 problems. DAYS 31-60: Find leverage - Goal: define and prioritize the billing roadmap. Success = ranked backlog agreed with eng. - Relationships: deepen with sales (pricing pain) and CS (churn drivers). - Learning: unit economics, why past pricing changes succeeded or failed. - Early win: run one pricing or dunning experiment. - Check-in: day 60 - present roadmap and the experiment's early read. DAYS 61-90: Own and ship - Goal: deliver the first roadmap item to production. - Success = feature live + a measurable billing metric moved. - Check-in: day 90 - retro on the launch and a 6-month plan.
Illustrative example — your results will vary by tool and inputs.
Get sharper results
- 01Add the company stage detail honestly — a Series A 'no process' plan looks nothing like a plan for a 5,000-person enterprise, where the first 30 days are mostly navigating stakeholders.
- 02Give the model 1-2 known priorities the hire is being brought in to fix, so 'early wins' are real targets rather than invented placeholders.
- 03Ask it to mark which goals depend on others ('can't do the 60-day roadmap until the 30-day audit is done') so the plan reads as a sequence, not three disconnected lists.
- 04For interview use, add 'frame this as something I'd present to a hiring manager' so it's written in the first person with appropriate humility about unknowns.
- 05Request that every success metric be observable by someone else ('a doc the eng lead signs off on') so progress isn't self-graded.
Adapt it for your case
Reframe as 'a plan for me, the manager, to onboard this hire' so it lists what the manager must prepare, introduce, and check at each phase.
Specify whether the role manages people; a first-time manager's 30-60-90 emphasizes team trust and 1:1s over shipping personal work.
Add 'fully remote team across time zones' so relationship-building shifts toward async intros, recorded context, and deliberate virtual coffees.
Common questions
Is this for the new hire or the manager?
By default it's written for the person being onboarded. Add 'write this as the manager's onboarding plan for the hire' to flip it into a prep checklist for the people leader.
How do I stop it from being generic?
Generic output comes from generic input. Feed it the specific role focus, the company's actual stage, and one or two real problems the hire must solve — the prompt already instructs the model to avoid boilerplate.
Can I use this in a job interview?
Yes, and it's a strong move. Add that it's for a final-round presentation and supply what you learned about the company so the early wins reference real challenges, not guesses.
You may also need
Generate Interview Questions for a Role
Build a structured interview question set with technical, behavioral, and culture-fit categories.
Build a Structured Hiring Scorecard
Generate a structured interview scorecard with competencies, anchors, and disqualifiers.
Write a Compelling Job Description
Write an inclusive, outcome-focused job description that attracts top candidates.
Generate Role-Specific Interview Questions With Scoring Cues
Builds a structured, role-specific interview set with strong-answer cues and red flags for consistent scoring.