Buddy System

What blocks someone during their first week is rarely the job itself. It's everything beside the job. There are thirty-odd channels and no obvious place to post a question. An invitation arrives for a meeting and it isn't clear whether attendance is expected or optional. Nobody has explained how lunch works. None of this appears in any document, because to everyone already there it isn't worth writing down.

Employee onboarding used to mean a handful of documents and one conversation with a manager. After the accounts and the links, fitting in was your own problem. People who settled quickly got described as sharp, and people who took longer got described as a disappointment. What actually separated the two groups was whether someone easy to talk to happened to sit nearby.

The scene this practice was built around happens on the afternoon of day three. A new engineer is stuck setting up a development environment. The instructions were followed exactly and the same error keeps coming back. They consider asking their manager and decide against it, because that manager writes the probation assessment and day three feels too early to admit the setup isn't working. Three hours disappear. The fix turns out to be one line of configuration that everyone on the team already knows.

A buddy system exists to delete those three hours. It doesn't reduce the number of questions a new hire has. It moves the person receiving them away from the evaluation. Once there is one named person who costs nothing to ask, the delay between being stuck and asking drops from three days to ten minutes.

As soon as a start date is set, the manager names one experienced colleague as the buddy and puts a month of recurring conversations on the calendar before the new hire arrives. Both moves belong to the company, not to the person joining. Told to get acquainted on their own, two people who each assume they're imposing on the other will do nothing at all.

Three criteria guide the choice of buddy.

1. Someone with no part in the evaluation. That rules out the manager and anyone who contributes an opinion to the probation review. The moment the listener is also an assessor, asking a question turns into disclosing a gap.
2. Someone between six months and two years in. That's the window where the experience of not knowing is still fresh. An eight-year veteran knows everything about the company but has forgotten what was invisible on the first day.
3. Someone whose working hours overlap, even from another team. With a time zone in between, an answer takes half a day to arrive, and half-day replies never build the sense that this person is safe to interrupt.

The month usually runs on this rhythm.

1. Fifteen minutes every day during week one. Short and frequent clears questions before they pile up.
2. Thirty minutes once a week from week two through week four. Work topics start appearing around here.
3. After a month it ends, and the regular conversation moves to the manager's one-on-one.

The buddy opens each conversation. Left to reach out first, most new hires don't, because interrupting someone who looks busy with something small feels like a cost they're imposing. Asking "anything you got stuck on today?" removes that calculation.

Buddies need instructions too. One page is enough: what the role covers, what it explicitly doesn't, and when it ends. Skip that and pairing someone by name produces one lunch in week one and nothing after. The buddy's own manager should also know that roughly an hour a week is leaving that person's workload.

The practice took hold first at companies hiring several people at once. When ten people join in a quarter, one manager cannot absorb ten streams of small questions, so the questions have to go somewhere else.

Remote teams lean on it harder. In an office you turn your chair and ask. Remotely, the same question becomes a written request with your name on it, addressed to a specific person. That takes a small act of resolve every time, and without an assigned recipient the resolve keeps getting postponed.

What the buddy actually does varies by role. In engineering it often means sitting alongside for environment setup and the first deploy, which visibly shortens ramp-up time. In sales it means bringing the new hire onto real calls to listen before they run one.

It's normally paired with a 30-60-90 plan. The plan says what counts as progress; the buddy is who you ask when progress stalls. With only one of the two, something is missing on the other side. A plan and no buddy leaves someone stuck on a document for days. A buddy and no plan produces a month of pleasant check-ins and nothing to show.

"Could you be the buddy for the person starting next week? Just the first month."

A request for about an hour a week of that person's time.

"You can ask your buddy instead of me, honestly."

A manager signaling both that the question is fine to ask and that it doesn't have to be asked of an assessor.

"The buddy was assigned, but they only met twice all month."

A report that the practice exists on paper and isn't running.

At Pagedeck, Grace introduced it once the company passed thirty people. Before that, every question from a new hire landed on a manager, and during afternoons full of meetings answers were running two hours behind.

Buddies are now named a week before the start date. When an engineer joins, Theo takes the pairing, blocks fifteen minutes each afternoon for the first week, and uses it to cover things like who to ask for a deploy and which channel lights up first during an outage.

The most common error is reading buddy as mentor or as the senior engineer who trains you. The shape looks identical — one experienced person attached to one new person — so the roles blur easily. But a buddy doesn't assign work, doesn't teach technique, and doesn't advise on career direction. The scope is finding your way around the company, and it ends after a month. Without that line drawn, buddies end up absorbing code reviews and hands-on training on top of their own work, and two months later nobody wants the role.

The second error is assuming that naming a person is the whole of it. Writing a name in a slot looks like a completed setup. In practice it takes the one-page briefing, the recurring slots already on the calendar, and the hour a week carved out of the buddy's workload. Drop any one of those and you get an assignment rate of 100 percent alongside an average of two actual meetings. The survey then records that buddies were in place, which makes slow ramp-up look like a mystery rather than the predictable result.