developeronboardingcost.com
← The Lab

30-60-90 Plan

Learn, build, lead. The plan that ramps faster.

A document, three check-ins, and a no-blame conversation at each milestone. Used well, the 30-60-90 day plan reduces ramp by 20-30%; Brandon Hall Group links a strong onboarding process to 82% higher new-hire retention.
Day 1-30

Learn

Become productive on the codebase. Understand the team, the architecture, and how work flows.

Success criteria

  • First commit by Day 2
  • First non-trivial PR merged by end of week two
  • Five+ key services or modules mapped
  • All ceremonies attended at least twice
  • 30-day check-in with manager completed

Slipping past Day 5 with no commit usually points to environment friction or unclear scope. Debug actively.

Day 31-60

Build

Ship features with steadily decreasing supervision. Move from pairing to independent work, with code review as the safety net.

Success criteria

  • Feature owned end-to-end (one minimum)
  • Sprint commitments met two sprints running
  • Production debugging without escalation
  • Code review quality consistently good (giving and receiving)
  • 60-day check-in with manager completed

Plateauing in week six is a yellow flag. Plateauing in week eight is a red flag - run a structured retro.

Day 61-90

Lead

Operate at full velocity. Contribute to technical direction. Begin mentoring and influencing.

Success criteria

  • 80-90% of team velocity sustained
  • On-call primary rotation completed
  • Contributed to a technical design document
  • Identified and shipped at least one process or code-quality improvement
  • 90-day review and onboarding marked complete

If the new hire is at 50-60% velocity at Day 90 with no obvious blocker, escalate. The cost of carrying mismatched fit is asymmetric.

Seniority overlay

Same plan, different bars.

Junior (0-2 yrs)

  • Day 30: first PR merged, sprint ceremonies routine
  • Day 60: shipping non-trivial bugs solo, contributing in design discussions
  • Day 90: at 50-70% of mid-level team velocity, owns small features

Mid (2-5 yrs)

  • Day 30: first feature owned, sprint commitments met
  • Day 60: sprint commitments met two-in-a-row, on-call shadow
  • Day 90: 80-90% of team velocity, primary on-call

Senior (5-10 yrs)

  • Day 30: first feature shipped, architecture context absorbed
  • Day 60: contributing to technical design docs, mentoring juniors
  • Day 90: full velocity, primary on-call, owns a critical service

Staff+ (10+ yrs)

  • Day 30: cross-team relationships built, current tech-debt mapped
  • Day 60: design doc authored, principal engineer collaboration routine
  • Day 90: leading a quarterly initiative, influencing roadmap

Manager check-ins

Three conversations. Twelve prompts.

Day 30

  • ›What is working?
  • ›What is friction?
  • ›Are 30-day milestones met?
  • ›Who has been most helpful so far?

Day 60

  • ›Are sprint commitments hitting?
  • ›Where do you need more context?
  • ›What are you uniquely positioned to improve?
  • ›Any concerns about pace or scope?

Day 90

  • ›Are you at 80-90% velocity?
  • ›What from the 30-60-90 plan didn't land?
  • ›What are your six-month growth goals?
  • ›Onboarding marked complete: yes/no?

FAQ

Common questions

Why does the 30-60-90 frame work?+

Because it forces both manager and new hire to articulate expectations at three concrete checkpoints. Companies with structured 30-60-90 plans report 20-30% faster time-to-productivity, and Brandon Hall Group found a strong onboarding process improves new-hire retention by 82%.

Should the plan be a document or a conversation?+

A document, reviewed in conversation. Written-only plans rot; conversation-only plans drift. The standard is a one-page Notion or Confluence doc owned by the new hire, reviewed at each check-in.

What if the new hire is ahead of plan?+

Lift the bar. The biggest mistake managers make with strong hires is leaving them under-stretched at Day 60. Add a stretch goal like 'design and propose a tech-debt initiative' or 'pair with a junior for two weeks'.

Should I share the plan with the team?+

Yes, the goals and milestones. Not the private 1:1 notes. The team needs to know what the new hire is working toward so they can spot mentorship opportunities and avoid duplicated work.

Related briefs

Phase-gated checklist

Ramp curve timeline

Seniority comparisons

Track the metrics

Twelve best practices

Quantify your case

Updated 2026-04-28