How to Train New Employees: A Plan for the First 90 Days

Written by
Kevin Alster
February 26, 2026

Create engaging training videos in 160+ languages.

Training new employees starts by defining what the business needs them to do (and how quickly).

That’s why the most useful plans separate training into three layers:

  1. Foundations: Core knowledge, processes, and tools
  2. Skills: Role training, practice, and application
  3. Reinforcement: Feedback, coaching, and continuous learning

This guide gives you a structure you can reuse, a core plan for the first two weeks, and a 30–60–90 approach that works even when new hires are in meetings and delivery work in week one.

⚡ Quick start

Pick the path that matches your role.

For HR / People ops

  • Build the Foundations layer: shared orientation, tools, policies, and where answers live
  • Set clear owners across HR, IT, managers, and buddies
  • Add simple checkpoints so issues surface early

For hiring managers

  • Define the Skills layer: role outcomes, workflows, standards, and practice
  • Assign a structured buddy and schedule feedback loops
  • Build Reinforcement into week one (reviews, coaching, escalation paths)

Start with the business need

Before you design training, define any business constraints. If the business is hiring 50 engineers a week and expects them to join projects quickly, the training plan needs to support that. If the business can protect time for learning early on, you can sequence training differently.

Either way, the same question applies: what does someone need to do well in this role, and how quickly?

The ideal first weeks create space to learn the company, build relationships, and ask basic questions early. Research on onboarding and socialization supports the value of structured early support and clear pathways to information.

Onboarding vs. orientation
  • 🧾 Orientation covers the basics: introductions, policies, tools, and logistics.
  • 🌱 Onboarding is the ramp to role confidence: workflows, quality standards, relationships, and ongoing support.
  • Training sits inside onboarding. It’s how new hires learn to perform the role consistently.

In many teams, there is no dedicated time for onboarding. Delivery starts immediately. When that’s true, training needs to work in the flow of work: smaller modules, guided practice on real tasks, and fast feedback.

Foundations

Foundations are the shared basics that help new hires get oriented without guessing. This layer reduces repeat explanations and makes role training easier for managers to run.

For HR: Standardize the shared layer

HR’s job is to make Foundations reliable across roles and regions.

Focus on a few essentials:

  • A single onboarding hub that stays current
  • Clear ownership across HR, IT, managers, and buddies
  • Shared orientation modules that don’t change every week
  • Checkpoints that confirm readiness (access, required training, first-week plan)

Foundations should be easy to find later. People don’t remember where something was said. They remember where they can find it when they need it.

Skills

Skills are role-specific. They include the core workflows, the quality bar, and the practice needed to perform consistently.

For managers: Define what “good” looks like early

Start with role outcomes for the first 30–90 days:

  • What should they be able to do without guessing?
  • What does “done” look like for core workflows?
  • What’s the quality bar?
  • What usually goes wrong in week one?

Then design Skills training around experiences:

  • A short explanation of the workflow
  • One guided attempt on real work
  • A review loop (buddy or manager)
  • A place to find the answer later
Turn a job description into a 30–60–90 plan

Most managers already have a job description. Use it to define outcomes, tasks, and milestones—then refine with your team’s standards.

Prompt (copy/paste)

“You are helping me design a new hire training plan. Here is the job description: [PASTE JD].

Create a 30–60–90 day plan with:

  1. Outcomes by day 30, 60, and 90 (what ‘good’ looks like)
  2. The core tasks and workflows that demonstrate each outcome
  3. Required context to learn (tools, policies, stakeholders, domain knowledge)
  4. Practice assignments for each period (real work, with review)
  5. Checkpoints and questions for manager check-ins at 2 weeks, 30, 60, 90

Keep it realistic for a team where the new hire will be in meetings and delivery work in week one. Use clear, measurable language. Avoid jargon.

Treat this as a draft. Replace generic outputs with your standards, examples, and stakeholders.

Align training to your competency model (or build a lightweight version)

If your organization has a skills framework or career ladder, use it to define competence. If you don’t, start with a “top tasks” list and a few quality standards per task.

Plan element What it means Example (Sales role)
Competency The capability you expect at this level. Run a discovery call that surfaces pain, priority, and buying process.
Tasks The work that demonstrates the competency. Prepare call plan, ask core questions, capture notes in CRM, summarize next steps.
Standards What “good” looks like in practice. Uses the discovery framework, confirms decision criteria, and logs fields correctly in CRM.
Practice A guided attempt on real work, followed by review. Shadow 2 calls → run 1 call with a buddy listening → review recording with manager.
Reinforcement Where the employee can find the answer later. Short “how to run discovery” video + call checklist + CRM notes example in the hub.

Example setup plans (Foundations + Skills + Reinforcement)

Use these as starting points. Customize for your operating model, role standards, and pace of delivery.

For HR / People ops (Foundations)

  • Publish one onboarding hub: links, FAQs, policies, and where answers live.
  • Standardize shared orientation: how the business works, tools, norms, required training.
  • Assign owners: HR (process), IT (access), manager (role Skills), buddy (navigation).
  • Confirm readiness checkpoints: access verified, training assigned, first-week schedule shared.
  • Set feedback points: end of week 1, day 30, day 90 (tell new hires upfront).

For hiring managers (Skills + Reinforcement)

  • Define week-one outcomes: what gets done and what “done” looks like.
  • Assign a first contribution: real work with a clear review path.
  • Map 3–5 core workflows: happy path, quality bar, common mistakes, escalation.
  • Set a buddy cadence: daily in week 1, then 2–3x/week in week 2.
  • Schedule feedback loops: midweek + end-of-week, then weekly in month 1.
  • Draft a 30–60–90 plan: outcomes, practice assignments, milestone check-ins.

Core new hire training plan

Core new hire training plan (first 2 weeks)

This baseline works for most roles. Add role-specific workflows and standards where the work differs.

Week 1: Foundations + first application

  • HR / People ops: Orientation essentials; hub link; required training assigned with due dates.
  • IT: Accounts and permissions verified; one support path shared.
  • Hiring manager: Week-one outcomes; first contribution assigned (clear “done”); check-in cadence set.
  • Buddy: Daily 10–15 minutes for navigation and questions; explains how reviews and handoffs work.
  • New hire: Completes first contribution; logs questions and flags one gap in docs/process.

Week 2: Skills practice + feedback

  • Hiring manager: Confirms priorities; reviews early work for quality and decision-making.
  • Buddy / SME: Guides the core workflow once end-to-end; reviews one output and gives specific feedback.
  • New hire: Repeats the core workflow with review; saves key links and examples in the hub.

Checkpoints

  • End of Week 1: Access works + first contribution shipped (or ready for review).
  • End of Week 2: One core workflow completed twice with feedback.

Reinforcement

Reinforcement is what turns early exposure into consistent performance. It’s where feedback loops, coaching, and repeat practice live.

Capture institutional knowledge with SMEs

Onboarding gets harder when institutional knowledge isn’t documented. Every team has a few people everyone relies on for how work really happens.

You don’t need every expert to teach. You need a few SMEs to help you capture the workflows that drive early performance.

Start with 3–5 workflows that matter in the first few weeks. Assign one SME per workflow and keep the ask specific:

  • Confirm the steps and the quality bar
  • Share one good example and one common mistake
  • Clarify escalation paths (when to ask, who to ask)

A 30-minute walkthrough plus a 15-minute review is often enough to produce training that stays useful.

Short video modules help here. A 3–5 minute walkthrough captures the repeatable parts once, so SMEs aren’t repeating the same explanation for every cohort. Link the video from the hub at the moment the workflow is used.

💡Tip: If you want a starting point for documenting workflows, use an SOP template like the one below so new hires can follow the steps and see what “done” looks like.

Run a structured buddy system

A buddy system works when it has clear expectations and a predictable cadence.

Choose buddies who are reliable and strong on norms. Set a simple cadence (daily 10–15 minutes in week one, then 2–3 check-ins in week two). Define what buddies cover: where questions go, how reviews work, how handoffs happen, and who to meet early.

Teach the business

New hires can follow steps and still struggle if they don’t understand how the business works.

Early training should cover:

  • how the company makes money
  • how decisions get made and what trade-offs matter
  • what the organization measures (OKRs, KPIs, customer outcomes)
  • how the role contributes to those goals

Sales enablement (or a similar team) often already has the simplest version of this story. You can reuse those materials to create a universal module for every new hire.

One clear explanation, a few real examples, and a shared language for priorities reduces misalignment later.

💡Tip: Ask every new hire to explain, in their own words, how their work connects to one business goal. Review it in a week-two check-in.

Turn a job description into a 30–60–90 plan

Most managers already have a job description. Use it to define outcomes, tasks, and milestones—then refine with your team’s standards.

Prompt (copy/paste)

“You are helping me design a new hire training plan. Here is the job description: [PASTE JD].”

Create a 30–60–90 day plan with:

  1. Top outcomes by day 30, 60, 90 (what ‘good’ looks like)
  2. The core tasks and workflows that demonstrate each outcome
  3. Required context to learn (tools, policies, stakeholders, domain knowledge)
  4. Practice assignments for each period (real work, with review)
  5. Checkpoints and questions for manager check-ins at 2 weeks, 30, 60, 90

Keep it realistic for a team where the new hire will be in meetings and delivery work in week one. Use clear, measurable language.

Training plans work when they reflect how the business operates. Use Foundations to make onboarding navigable, Skills to define performance, and Reinforcement to keep learning connected to real work.

Build feedback loops into the plan from the start. Consistent check-ins give you usable data across cohorts—and it’s easier for new hires to respond when they know exactly when they’ll be asked (for example: end of week one, day 30, and day 90).

📏 How to measure new hire training

Use lightweight pulses early, then review progress at the milestones your organization already uses.

Weekly pulses (month one)

  • New hire: “I know what to focus on this week” (1–5)
  • New hire: “I know where to get help” (1–5)
  • Manager: “They can complete core tasks with the right support” (1–5)

Milestone check-ins (30 / 60 / 90 days)

  • Review progress against the plan
  • Calibrate quality standards and independence
  • Identify one skill gap and the next practice opportunity

If you use probation periods

  • Match training reviews to the probation timeline so expectations and support stay explicit.

💡Tip: If you’re building the full experience end-to-end, pair this with our onboarding checklist and onboarding video script guide.

About the author

Strategic Advisor

Kevin Alster

Kevin Alster is a Strategic Advisor at Synthesia, where he helps global enterprises apply generative AI to improve learning, communication, and organizational performance. His work focuses on translating emerging technology into practical business solutions that scale.He brings over a decade of experience in education, learning design, and media innovation, having developed enterprise programs for organizations such as General Assembly, The School of The New York Times, and Sotheby’s Institute of Art. Kevin combines creative thinking with structured problem-solving to help companies build the capabilities they need to adapt and grow.

Go to author's profile
Get started

Create engaging training videos in 160+ languages.

faq

Frequently asked questions

What’s the best way to train new employees?

  • Start with the role outcomes and the core tasks the person must perform. Define what “good” looks like, then train through short modules, guided practice, and early feedback.
  • How long should new hire training take?

  • Most roles need a 30–90 day ramp. The first two weeks should cover essentials and the first real contribution, with deeper workflow and judgment-building through 30–60–90.
  • What should a new hire training plan include?

  • Role expectations, core workflows, quality standards, tool and process basics, escalation paths, and a cadence for feedback. Include a clear owner for each piece.
  • Who should own training for new employees — HR or the manager?

  • It’s shared. HR typically owns company-wide requirements and process; managers own role-specific training, standards, and coaching. SMEs and buddies support day-to-day learning.
  • How do you train new employees when the business needs them productive fast?

  • Design for the flow of work: smaller modules, just-in-time guidance, and practice on real tasks with review. Protect a few moments for learning, even if delivery starts in week one.
  • How do you align training with a skills framework or career ladder?

  • Map competencies to tasks and standards. Then build practice and checkpoints around those tasks so the training reflects how performance is evaluated.
  • What’s the difference between onboarding and training?

  • Onboarding covers readiness and integration (access, context, relationships). Training builds consistent role performance (workflows, standards, judgment).
  • How do you measure whether new hire training is working?

    Track time-to-access, first contribution quality, confidence (new hire + manager pulse), and avoidable errors. Review results at 30–60–90 and update the plan.

    VIDEO TEMPLATE