Lesson 7 of 9 · 8 min
The first ninety days
Most founders treat onboarding as handing over logins and saying “ask if you have questions.” Six weeks later nothing is smoother. The ninety days below are what to do instead, and the milestones that tell you whether it is working.
Before day one
Your audit from lesson two becomes the reading list. Make the access list: every tool, and for each the lowest permission that allows the work, never an admin account by default. Decide the communication rhythm now, a daily async note plus a weekly thirty-minute call, say, because changing it three weeks in feels like instability. Have the brand voice document ready.
Days one to seven: shadow week
They own nothing this week. Day one: access checked, voice document read together, they watch you handle ten real tickets while you explain each decision aloud. Day two: they draft ten replies, you review every one. Day three: order monitoring with you watching their screen. Day four: their first draft procedure for one recurring task; you critique. Day five: half the tickets with light supervision, then a Friday review of what surprised them. It feels slow. It is the most leveraged week of the ninety.
Days eight to thirty: one workflow at a time
Week two, support: full ownership of the inbox; you read their first fifty sent replies and give written feedback. Week three, orders: daily monitoring and exceptions, with a three-line summary to you by mid-morning; you read the summary, not the orders. Week four, inventory and suppliers: they draft outbound supplier messages and you approve for two weeks, then they send. Day-thirty milestone: a written procedure for every recurring task, you no longer log into the helpdesk, and the weekly call is a fixture.
Days thirty-one to sixty: depth
No new responsibilities. Better judgement on the ones they have: they spot patterns (“twelve people asked about X this month, should it go in the FAQ?”), propose changes to macros and procedures, and write a weekly summary that analyses rather than counts. Day-sixty milestone: they can tell you which workflows run well and which need attention, and it feels like a colleague, not a contractor.
Days sixty-one to ninety: steady state
What day ninety looks like: under an hour a week of your time on operations; the summary lands Friday morning, you ask two or three questions, the week is done; issues reach you before they are problems; a backup could pick up from the procedures in under an hour; you could take a week off. If you are not there, it is one of three things: the wrong person, a founder who has not let go, or a role scoped too wide. Diagnose in month four; do not let it drift.
The Friday review, under thirty minutes
Numbers, five minutes: orders, revenue, ticket volume, response time, refunds, stock alerts. Wins, five. Issues, ten: what slipped, what pattern surfaced, what carries into next week. Next week, five: launches, promotions, supplier delays. Your asks, five. If the meeting runs long, the cadence is wrong; you should be operating between meetings, not in them.
Checked From the 30-60-90 guide, kept in full. The red flags by week are in lesson six rather than repeated here.
The day-by-day shadow week, the workflow order, the three milestones and the review template are the guide’s, and they are consistent with the complete hiring guide’s shorter version. The guide’s closing (“skip the build, our onboarding is built around exactly this plan”) is not here. Nothing in the plan depends on who runs it.