Rule 32 of 33 · Chapter VII — People and Sustainability
Onboard people like you want them to stay
Why this rule exists
The first few weeks set a new person's entire trajectory, because that's when they form their sense of whether this place is competent and welcoming or chaotic and cold, and that first impression is stubbornly hard to reverse. A good onboarding, a clear path to a first real contribution, a buddy to ask the dumb questions, docs that actually match reality, is one of the highest-leverage investments we make, because it turns a nervous newcomer into a productive, confident teammate weeks or months faster. Onboarding is also the ultimate test of our documentation and our clarity: if a new person can't get productive from what we've written, that's a signal our knowledge is trapped in people's heads, which is a risk for everyone, not just them. We invest heavily here because the alternative, throwing someone in and hoping they swim, wastes their potential and often their tenure, and rehiring is far more expensive than onboarding well. How we treat people in week one tells them, accurately, how much we'll invest in them for the rest of their time here.
In practice
Before someone starts, prepare a real onboarding: access sorted, a first task picked that's meaningful but achievable, and a buddy assigned to be their go-to for questions. Aim for a genuine contribution shipped in the first week or two, because nothing builds belonging like actually doing the work and seeing it land. Have them fix the onboarding docs as they go, since they're the only ones who can see what's missing or wrong, and that both improves the docs and gives them early ownership. Make it explicitly safe to ask anything, and answer generously, because every question they're afraid to ask is time they'll waste and confidence they'll lose. Check in deliberately for the first month rather than assuming no news is good news. And remember they're evaluating us too, so show them the team at its considerate best.
When it doesn't apply
Onboarding depth should scale to the role and the person's experience; a seasoned hire in a familiar stack needs less hand-holding than a junior in new territory. And a good onboarding still expects the new person to bring initiative, it's a partnership, not a spoon-feeding.