Draft a 30-60-90 Onboarding Plan Template

Workflow area: HR & Recruiting · Tier: Core · Hands-on time: ~30 minutes

The 30-60-90 is a simple contract: by day 30 you understand, by day 60 you contribute, by day 90 you own. Most versions fail because they list activities ("meet the team") instead of outcomes ("can route any customer issue to the right owner without help"). AI drafts outcome-based plans quickly — but only if you feed it what ramped success actually looks like in your team, which is a five-minute conversation with the manager, not a model's guess.

When to use — and when not to

• Use it for any role you hire more than oncethe template pays for itself on the second hire.
• Use it before the offer stagesharing a concrete plan with a finalist is a closing tool; it shows the role has a shape.
• Use it for internal transfers and promotionsa 30-60-90 for a first-time manager is the cheapest management-development intervention there is.
• Skip generic plans for genuinely novel rolesa first-of-its-kind hire (your first data person, your first counsel) needs the manager to think through the role first; the model can structure that thinking but can't substitute for it.
• Skip performance-management usea 30-60-90 is a support scaffold, not a probation trap. If you need a performance-improvement plan, that's a different document with HR in the room.

The recipe

1. 1.

   Collect three inputs from the hiring manager. What does "fully ramped" look like in this role (2–3 observable behaviors)? What are the 5 relationships this person must build? What usually goes wrong in the first month for new joiners here? Two minutes each — these answers are the plan's spine.

2. 2.

   Generate the plan, outcomes first.

   Copy

   Draft a 30-60-90 onboarding plan for this role.
   
   Role: [TITLE, TEAM, MANAGER]
   What "fully ramped" looks like: [MANAGER'S ANSWER]
   Key relationships to build: [LIST OF 5 — roles, not names]
   What usually goes wrong for new joiners here: [ANSWER]
   Company context: [ONE LINE — size, industry, remote/office]
   
   For EACH phase (days 1-30, 31-60, 61-90) produce:
   1. THEME: one line ("Learn", "Contribute", "Own" adapted to
      this role)
   2. OUTCOMES: 3-4 success criteria, each observable and checkable
      ("can X without help", "has shipped Y", "owns Z") — no vague
      verbs like "understand" or "familiarize"
   3. MILESTONES: concrete deliverables with target days
   4. MEETINGS: recurring and one-off (manager 1:1 cadence,
      stakeholder intros, shadowing sessions)
   5. CHECK-IN QUESTIONS: 3 questions the manager asks at the
      phase-end review
   
   Also produce a WEEK 1 checklist separately: access, tools,
   accounts, first-day schedule, and a "first small win" achievable
   by day 5.
   
   Rules: front-load relationship-building into phase 1. Every
   outcome must be verifiable by the manager without asking the new
   hire "do you feel ramped?". Keep the total plan under 2 pages.
   

3. 3.

   Pressure-test the outcomes. Good output reads like this:

   Copy

   DAYS 31-60 — CONTRIBUTE
   Outcomes:
   - Handles the weekly vendor reconciliation end-to-end; manager
     reviews output only (was: shadowing)
   - Has drafted and shipped 2 process notes for steps that had no
     documentation
   - Runs the Tuesday ops stand-up once without the manager present
   Check-in questions: What took longer than it should have this
   month? Which handoff is still unclear? What would you change
   about how we onboarded you so far?
   

   Cut anything unverifiable, and ask the model: "Which of these outcomes depend on other people delivering something? List those dependencies so the manager can line them up in advance." Missed dependencies — access not granted, stakeholder on leave — are the number-one reason plans slip.

4. 4.

   Convert to a reusable Notion template. Ask: "Turn this into a Notion-ready template with placeholder fields — {{NAME}}, {{START_DATE}}, {{MANAGER}}, {{BUDDY}} — and a status property per milestone (Not started / In progress / Done)." Paste into a Notion page, turn it into a template in your team's HR space, and add a linked database of milestones if your team tracks that way.

5. 5.

   Personalize per hire in ten minutes. Duplicate the template, fill placeholders, and adjust for the specific person — their background changes phase 1 (an industry veteran skips domain basics; a career-switcher gets more shadowing). Share it with the new hire on day 1, or before: the plan works best as a mutual document, reviewed together at each phase gate.

Make it yours

• Role-family variants: generate sibling versions in one chat — "same structure for the senior version of this role: compress phase 1, add a mentoring outcome" — and keep a small library per team.
• Buddy-system add-on: ask for a parallel one-pager for the onboarding buddy: what to cover in weeks 1–4, and the questions new hires won't ask their manager but will ask a peer.
• Google Docs alternative: no Notion? The same template lives fine as a Doc with a milestone table; use checkboxes and a phase-gate comment thread per section.

Quality check

• Every outcome is observablea manager could mark it done without an opinion survey.
• Phase 1 is heavier on relationships than deliverablesearly output pressure with no context produces rework, not ramp.
• Dependencies are listed and ownedaccess, intros, and equipment have names and dates before day 1.
• The plan fits two pageslonger plans get skimmed once and abandoned.
• The new hire sees ita 30-60-90 kept secret from its subject is a surveillance doc, not an onboarding plan.