Onboarding a new teammate in team chat
A new teammate's first week is mostly one question asked many ways: why is it like this? The answers already exist. They are in old threads, in decisions somebody made out loud, in a doc that was linked once. Onboarding is the job of getting a new person to those answers without making everyone stop work to repeat them.
The intro-call week
The usual first week is built out of calendar invites. A welcome call with the manager. A thirty-minute intro with each person on the team. A walkthrough of the codebase, the roadmap, the process. Each call is pleasant. Each one repeats some of the last one.
Between calls, the new person gets a stack of forwarded links. A wiki page from last spring. A slide deck from the kickoff. A long email titled "context". Some of it still matches how the team works. Some of it does not, and the new person has no way to tell which is which.
The small questions are the hardest part. What does this acronym mean. Who owns the deploy script. Why did we drop the old pricing page. Each one feels too small for a meeting and too awkward for a DM to someone they met yesterday. So they wait, and save the questions for the next scheduled call, and lose a day.
When DMs hide the decision is the same problem from the other side: the answer was given, but in a place the new person cannot see.
Read the channel, walk into the room
In Bullpen, the project channel is where the work already happened. Decisions, owners, and blockers sit there as searchable lines. A new teammate starts by reading that history. Searchable team chat means they can type "pricing page" and land on the message where the team decided, with the thread around it.
The walk-in voice room beside the channel stays open. When a question needs a voice, the new person joins the room the way they would turn to the next desk. Whoever is in there answers. Nobody books a slot for a two-minute question, and the new person learns who to ask by hearing who answers. Walk-in voice rooms at work covers how that room works day to day.
Notes from the room post back to the channel it belongs to. The answer a new hire got on Tuesday becomes a line the next new hire can search on Friday. Onboarding stops being a set of conversations that each person has to have again.
AI helpers sit on the channel's roster too. Mention Scout and ask why the team moved off the old pricing page. Scout answers in the thread, under its own name with an AI badge, from what was actually said in the bullpen, and links the message it drew from. The new person reads the answer and the source side by side, and can follow the link into the original conversation. AI helpers that cite sources explains why that link matters.
The new teammate gets the history, the people, and a helper that points back to the record, all in one bullpen.
Before the next person starts
Before your next hire's first day, post one message in the project channel that says where to begin reading, and tell them the walk-in voice room is open for questions of any size. Then let the channel do the rest.