Why Generic Onboarding Fails
Walk into almost any company and ask to see their onboarding materials. What you'll typically find is a collection of things that apply to everyone: a company overview, a handbook, compliance training, IT setup instructions, and a welcome message from the CEO.
These things aren't wrong. But they're not enough — and for most new hires, they're not what they actually need. A new Account Executive doesn't need the same day-one experience as a new Staff Engineer. When onboarding is designed generically, it communicates something unintentional: that you don't really understand what this specific person needs to succeed in this specific role.
The Job Description as Onboarding Foundation
The job description is one of the most underutilized documents in most organizations. Companies invest real effort in writing it, and then the moment the hire is made, it gets filed away and largely forgotten.
A role-based onboarding approach treats the job description as the starting point for a conversation: "You were hired to do X, Y, and Z. Here's everything you need to know to do those things well." For each major function of the role, you ask:
- What background context does someone need to do this effectively?
- What tools, processes, or systems will they be using?
- Who are the key people and relationships involved?
- What does good performance look like in this area, and how will it be measured?
The answers to these questions form the curriculum for the role's onboarding path.
The 30/60/90 Framework
Once you have the knowledge mapped to the role, the 30/60/90 framework provides the structure for sequencing it.
Days 1–30 are about foundation-building. This is not the time to ask the new hire to perform — it's the time to help them understand. What is the company, and how does it operate? What is this team's mission, and how does it contribute? The goal is context, not output.
Days 31–60 are about integration. The new hire now has enough context to start contributing in limited, supervised ways. They're learning by doing — taking on real work while still having a safety net. This phase is about building confidence and identifying gaps in the knowledge foundation.
Days 61–90 are about acceleration. By now, the new hire should be approaching independence in their core responsibilities. The onboarding plan in this phase focuses on the nuances — the things that separate good performance from great performance in the role.
What to Include in Each Phase
For each phase, the plan should include:
- Knowledge: What specific information does the new hire need to acquire? What documents, wikis, or resources should they engage with, and in what order?
- People: Who should they meet with, and why? What are the key relationships in this phase, and what should they learn from each?
- Deliverables: What should they produce or demonstrate? Clear milestones give the new hire feedback signals and give the manager checkpoints for assessment.
- Questions to answer: What are the most important things this person needs to understand by the end of this phase?
The Manager's Role in Role-Based Onboarding
One of the most important — and most neglected — parts of any onboarding plan is the manager. The most effective approach separates the manager's role from the information delivery role. Structured systems handle the knowledge delivery automatically. The manager's energy is then focused on the high-value, irreplaceable parts: setting context, providing feedback, building relationship, and accelerating the new hire's integration into the team.
Measuring Onboarding Effectiveness
A role-based onboarding plan should have measurable outcomes, not just activities. The question to ask at the end of each phase is not "did we cover all the material?" but "is this person where they need to be?"
Useful signals include: time-to-first-contribution for role-specific deliverables, new hire self-assessment of confidence and clarity, manager assessment of readiness for increasing autonomy, and retention at 90, 180, and 365 days.
The job description was the promise you made when you posted the role. Role-based onboarding is how you fulfill that promise — by building a path from "hired" to "thriving" that's specific enough to actually work.