A 30-60-90 that means something
The structure earns its name with outcomes, not themes: by day thirty, the hire can operate the basics unaided, tools, processes, the vocabulary; by sixty, they own real work with review; by ninety, they own outcomes with normal supervision and their first-quarter goal is delivered. Each phase has named deliverables and a scheduled conversation, so drift is caught in weeks.
Write it before the start date and share it on day one: the plan itself is the first signal of what kind of company they joined, and hires read that signal accurately.
Teach context, not just tasks
Task knowledge gets documented; context knowledge, why things are the way they are, who really decides what, how customers think, what failed before and why, lives in heads and leaks out slowly through embarrassment. Make it explicit: the annotated org reality, the customer in their own words, the short history of big decisions, the glossary of internal language.
This is also where recorded walkthroughs earn their keep: the how-we-actually-do-it recordings that let a hire rewatch without asking twice, which is the difference between curiosity and interruption.
Buddies with a job, and honest measurement
The buddy is not a lunch companion; it is a role: available for the questions too small for the manager, checking in on a rhythm, explicitly safe for I do not understand. Pick people who teach well, recognize the work, and rotate it, because buddying is itself management development.
Measure ramp honestly: time to the first owned deliverable, time to normal-supervision productivity, and the ninety day retention and satisfaction check. Then treat every hire’s stumbles as curriculum, feeding the next version, because onboarding is the program you get to improve monthly.
Onboarding as an assignable path
On the Learning Desk, onboarding becomes an assigned path with due dates: the 30-60-90 as milestones, context modules and recorded walkthroughs linked, buddy check-ins on the cadence, and completion visible to the manager and the program owner. Meeting notes and files sit on the same desk.
Velora drafts the role-specific plan from your description of the job. Ramp measured, not guessed, from the Plus membership.
Frequently asked questions
What should a 30-60-90 onboarding plan include?
Outcome definitions per phase, operate the basics, own work with review, own outcomes, with named deliverables and scheduled conversations, written before day one.
What is the most commonly missed part of onboarding?
Context knowledge: who decides what, why things are as they are, what failed before. It lives in heads and leaks slowly unless made explicit in modules and walkthroughs.
How do you measure onboarding success?
Time to first owned deliverable, time to normal-supervision productivity, and ninety day retention and satisfaction. Every stumble becomes next month’s curriculum.