At eight people, onboarding was easy: sit the new person next to someone senior, answer questions as they bubble up, and let the small room do the teaching by osmosis. At twenty-five it fell apart silently. New hires were still visibly lost in week six. Two quit inside ninety days, both citing "unclear expectations" in their exit conversations. We were spending fifteen to twenty thousand dollars per hire to recruit them and then setting fire to a meaningful chunk of that value in the first month because nobody actually owned the ramp. The cruel part is that none of it felt like a crisis day to day — it was just a slow, expensive leak we'd stopped noticing.
Onboarding doesn't scale by vibes
The informal approach works right up until it doesn't, and the failure is invisible because nobody is technically dropping the ball — there just isn't a ball. No single person knew the full picture of what a new engineer or a new CSM should be doing in week two versus week three. The senior person they sat next to was busy with their own deadlines. The manager assumed onboarding was happening because they'd seen the new hire in a few meetings. It wasn't happening; it was just occurring, which is not the same thing.
What finally forced the issue was a new hire who, three weeks in, asked me in a 1:1 what she was actually supposed to be working on. She wasn't lazy or lost — she was perfectly competent and completely un-pointed. We'd hired a sharp person and given her three weeks of ambient confusion.
Building a real plan for every role
I ran the 30-Day New-Hire Onboarding Plan, Week by Week prompt through Gemini 3 Pro Preview for our next four hires. For each I entered the role, the team description, the stakeholders to meet, and the specific 30-day goals. Gemini is the right pick for this one because the output is dense and tabular — a day/theme/activities/people/deliverable grid per week, plus a check-in schedule table and a pre-start prep list — and it handles that long, structured synthesis cleanly without losing the thread or the formatting halfway down the page. What came back was a plan a manager could literally follow row by row, not a generic listicle of "set up your email" energy.
What we measured
We tracked time-to-first-contribution — when did they own and ship their first independent thing? — and a manager-rated confidence score at day 30 on a 1-to-5 scale, and we compared the four structured hires against the four immediately before them who got the old osmosis treatment. I wanted a number, not a feeling, because the whole point was that feelings had been hiding the problem.
- Time-to-first-contribution: 5.5 weeks structured vs 9.2 weeks unstructured
- Manager-rated day-30 confidence: 4.1 vs 2.8 out of 5
- Early attrition in first 90 days: 0 vs 2
- New-hire-reported clarity on expectations at day 30: 85% vs 45%
The single highest-leverage row in the whole output was the Day 1 agenda. Gemini returned a warm, specific first day that started with a real welcome and a coffee with the team before a single password got reset or a single benefits form got signed. We followed it to the letter for all four hires, and every one of them, completely unprompted, mentioned their first day when I later asked what made them feel they'd joined a good place. It's the cheapest, most forgettable-seeming part of onboarding and it's the part people remember a year later, which tells you everything about how the human stuff and the operational stuff are weighted.
The honest caveat
The prompt is refreshingly willing to push back. For one role I'd written a 30-day goal that was really a 90-day goal, and Gemini called it out and proposed a sensible 30-day milestone toward it instead of pretending the original was achievable. That single piece of pushback saved the new hire from feeling behind on day one for missing a target that was never fair — and it saved me from setting it. I now read the pre-start prep flags carefully too, because the first time I ignored them and a new engineer spent his actual first morning waiting on repo access that should've been arranged the week before.
Grab the 30-Day New-Hire Onboarding Plan, Week by Week prompt on Prompt Dock and build a plan before your next start date — not on day one, when it's already too late to feel intentional. I pair it with my Offboarding Checklist & Warm Farewell Email Generator prompt so the door swings both ways with the same level of care; the way someone joins and the way someone leaves are the two moments every other employee is quietly watching.