The worst onboarding plan I ever got said "get oriented in month one." I oriented. I also shipped nothing, met no one, and by day 45 still couldn't tell what "success" meant. "Get oriented" is not a plan; it's a hope with a deadline.
So when I built a generator for onboarding, the only job was to turn that hope into milestones with owners.
Why 30/60/90 and not "week one to week twelve"
The three-bucket structure forces a shape onto the first quarter. Days 1–30 are about access, context, and first small win. Days 31–60 are about owning a piece of the work. Days 61–90 are about operating without hand-holding. That arc is obvious in retrospect and invisible when you're writing a plan from scratch at 5pm on a Friday, which is exactly when these get written.
The role-tuned part matters because a sales hire and an engineer hire have nothing in common in week two. The generator takes the role and shapes the milestones to it, so the engineer's 30-day goal isn't "close three deals."
Check-ins and owners are the anti-vaporware
A milestone with no owner and no check-in is a sentence, not a plan. The generator attaches a check-in date and an owner to each milestone, which sounds bureaucratic and is the only thing that stops the plan from living in a doc nobody opens. The first-week checklist is the smallest unit — the practical "can they log in, can they find the repo, did payroll get them" list that, if skipped, poisons everything after.
What it can't do is know your team's actual capacity. If you onboard three people the same week, the plan doesn't adjust. It assumes one hire into a team that has time; you have to scale the check-ins if you don't.
Building it: keep the structure, free the content
The 30/60/90 skeleton is the reusable part. OnboardPlan locks the skeleton and frees the goals, because the dates are universal and the work never is. If you build your own, don't let teams edit the bucket boundaries — that's where plans silently become "month one-ish."
The first-week checklist should be copy-pasteable into a ticket, not trapped in a pretty page. Onboarding lives where the work lives.
The limit
It's a planning template, not a management system and not a guarantee the hire succeeds. The milestones are a framework you fill with real goals; the tool doesn't know your product or your people. I keep the framing honest: it organizes the plan, you own the outcome.
When a new hire starts next week, OnboardPlan produces the skeleton in a minute and I fill the goals. The first-week checklist is the part I'd otherwise recreate by hand every single time, and recreating it is exactly where things get dropped.
The other thing I've learned is to review the plan with the manager before day one. A milestone nobody owns is a milestone nobody hits, and the tool can't tell you which owner is realistic on a short-staffed team. The skeleton is reusable; the ownership has to be real.
FAQ
What's in a generated plan?
30/60/90 milestones tuned to the role, each with a check-in date and owner, plus a first-week practical checklist.
Does it work for any role?
The structure is role-agnostic; the goals are tuned by role input. A sales plan and an engineering plan share the skeleton, not the content.
Can it track the hire after day 90?
No. It plans the first quarter. Ongoing performance management is a different system; this stops at onboarding.
Is the plan editable after generation?
Yes — the skeleton is fixed but the goals, owners, and check-ins are yours to adjust to your team's reality.
