Onboarding learning flow: first 90 days

A practical, adaptable 90-day learning flow that combines product, process, and culture onboarding so new hires become productive, connected, and confident faster.

Purpose and outcomes

This 90-day learning flow gives hiring managers, learning designers, and mentors a clear, adaptable path to help new hires ramp faster and stay engaged. It balances essentials (orientation and tools), role-specific immersion, and an increasing expectation of ownership and improvement. Use it to reduce time-to-proficiency, capture tacit knowledge, and increase retention.

How to use this template

Copy and tailor the sections below for the role and team. Assign a mentor, set measurable milestones, and make the learning checklist and competency milestones visible to the new hire. Review progress weekly and adjust scope based on performance and feedback.

Phases (high level)

  • Week 0 — Orientation & essentials: access, safety, policies, tools, team introductions, and a clear 30/60/90 expectation overview.
  • Weeks 1–4 — Role immersion & paired work: close pairing with a mentor or peer; observe, shadow, execute small tasks with guidance; begin product/process walkthroughs; initial competency checks.
  • Weeks 5–12 — Ownership, experiments & feedback: increasing independent work, owning small projects, running experiments or improvements, regular feedback loops, and a formal 90-day review.

Detailed weekly focus and suggested activities

Week 0 (Orientation & essentials)

  • Complete access provisioning and basic tool training (email, ticketing, code repo, calendar).
  • Receive role overview, immediate priorities, and 30/60/90 goals.
  • Meet core team members and assigned mentor; schedule recurring 1:1s.
  • Complete required compliance and safety training.

Weeks 1–2 (Foundations & observation)

  • Shadow key processes and attend customer/product demos.
  • Run small, low-risk tasks with mentor pairing and checklists.
  • Start building a personal learning checklist and knowledge notes.

Weeks 3–4 (Guided execution)

  • Take responsibility for routine tasks end-to-end with mentor review.
  • Demonstrate core competency milestones for the role (examples below).
  • Participate in a feedback session and adjust learning goals.

Weeks 5–8 (Growing ownership)

  • Lead a small project or feature with a defined scope and timeline.
  • Run a lightweight experiment or propose one process improvement.
  • Start contributing to team knowledge artifacts (how-tos, checklists).

Weeks 9–12 (Independent delivery & scale)

  • Deliver independent work against agreed success criteria.
  • Complete a formal 90-day review (self-assessment, manager assessment, mentor input).
  • Agree next-quarter development plan and ongoing KPIs.

Core artifacts (what to create and share)

  • Learning checklist: role-specific items that the new hire can check off as they complete them (access, trainings, walkthroughs, shadow sessions, tasks). Keep items small and verifiable.
  • Role competency milestones: 6–8 observable milestones tied to outcomes (e.g., "Can independently deploy a change to production with checklist X" or "Can resolve Tier 1 customer issues within SLA"). Rate as Observed, Needs Practice, or Not Observed.
  • Mentorship schedule and agreements: weekly 1:1s for the first 8 weeks, paired sessions, review rubrics, and a short mentoring charter (time commitment, communication norms, feedback cadence).

Example learning checklist (starter items)

  • Complete IT onboarding and confirm access to required systems.
  • Attend product overview and architecture walkthrough.
  • Observe two customer support cases and document learnings.
  • Complete first production-like task with mentor (list task).
  • Publish a one-page "How I onboarded" note to the team knowledge base.

Sample role competency milestones (examples)

  1. Operational knowledge: Understands primary team processes and tools; can run the daily/weekly routine.
  2. Technical skill: Can complete core technical tasks without assistance or with minimal review.
  3. Customer impact: Can handle common customer scenarios or product-support tasks within SLA.
  4. Communication & culture: Demonstrates team norms, participates in standups, and documents work clearly.
  5. Continuous improvement: Proposes at least one small, testable improvement to a process or doc.

Success metrics and checkpoints

  • Weekly mentor check-ins with short notes (progress, blockers, next actions).
  • 30-day informal check: manager + mentor quick alignment on progress.
  • 60-day evidence review: completed checklist items and observed competency ratings.
  • 90-day formal review: self-assessment, manager scorecard, mentor input, and next steps agreed.

Manager and mentor tips

  • Make expectations explicit—share the checklist and milestones on day one.
  • Keep early tasks meaningful but low risk so the new hire builds confidence quickly.
  • Use paired work to transfer tacit knowledge; encourage note-taking into shared docs.
  • Give frequent, specific feedback; focus on behavior and observable outcomes.

Common pitfalls to avoid

  • Overloading with documentation and no guided practice.
  • Assuming visibility equals understanding—ask for demonstrations or walk-throughs.
  • Letting mentoring drift—schedule and protect mentor time explicitly.
  • Failing to capture tacit knowledge—encourage mentors to co-author short how-tos.

How to tailor this flow

Adjust the tempo, artifacts, and milestones to fit role complexity, regulated environments, or physical/field roles. For senior hires, focus early on context, cross-team relationships, and strategic priorities rather than routine tasks. For frontline roles, increase hands-on supervised practice and safety checks.

Next steps — implementation checklist for the hiring manager

  1. Assign mentor and schedule recurring 1:1s before the hire’s first day.
  2. Customize the role competency milestones and learning checklist for the role.
  3. Prepare at least three paired-work tasks for weeks 1–4.
  4. Schedule 30/60/90 checkpoint meetings and reserve time in calendars now.
  5. Decide how progress will be recorded and shared (team doc, LMS, or interactive form).

Use this template as a starting point. The goal is a living, adaptable flow that captures hands-on practice, toggles between guidance and autonomy, and helps new hires contribute—and feel like they belong—sooner.


Discussion

Comments and conversation will live here.