The Onboarding Problem Most Teams Don't Know They Have
The Onboarding Problem Most Teams Don't Know They Have
Most teams think their onboarding is fine. The new hire gets a laptop, a Slack invite, maybe a 30-minute call with their manager. Someone shares a folder of docs. There's a first-week checklist somewhere.
What they don't realize is that by the end of week two, the new person is already managing a second, invisible job alongside their actual work: reverse-engineering how the team thinks.
They're in meetings where people reference decisions made six months ago, using shorthand that nobody explains. They're reading docs that contradict each other. They're figuring out who actually owns what by watching who responds to which threads. They're asking questions they feel slightly embarrassed to ask, because everyone around them seems to already know the answers.
The onboarding doc isn't the problem. The problem is that the doc describes the org chart, not the operating system.
What New Hires Actually Need
There's a difference between information and context. Information tells you what. Context tells you why, how decisions get made, what's actually important vs. what's just listed as important, and where to find the things nobody thought to document because they felt obvious to everyone already there.
New hires can absorb information quickly. Context takes weeks — sometimes months — and most of it gets transferred through osmosis: sitting near experienced teammates, overhearing conversations, gradually building up a mental model by accumulating small signals.
In a co-located team, this is slow but it works. In a distributed team, or one that's growing fast, it breaks down. There aren't enough osmosis moments. The new person doesn't know what they're missing until it causes a problem.
What Good Onboarding Infrastructure Looks Like
The teams that onboard well tend to have one thing in common: they treat onboarding as a product, not a process. It has a spec. It gets maintained. When something changes — a new tool, a process shift, a team restructure — someone updates the onboarding materials, because those materials are attached to the actual work, not living in a separate doc that nobody remembers exists.
In Closot, onboarding lives as a structured space — not a one-time welcome doc, but an ongoing reference. Role overview, team norms, active projects with their context, key decisions and why they were made, who to go to for what. All of it organized and linked so a new hire can navigate it themselves rather than waiting to be walked through it.
The difference is that this space isn't built for the new hire's first week. It's maintained by the team all year, because it's the same space where they track ongoing work. The onboarding content stays accurate because it's adjacent to the live work — when the team changes a process, the page that describes it is right there.
The Questions That Reveal Whether Your Onboarding Works
A useful diagnostic: ask someone who joined in the last three months these questions.
How long did it take before you felt like you understood how decisions actually get made here? If the answer is more than four weeks, your onboarding isn't transferring context — it's just transferring org chart information.
When you had a question in your first week, what did you do? If the answer is "I asked someone," your documentation isn't doing its job. Not because asking is bad, but because the question being answered once, verbally, means it'll have to be answered again the next time someone joins.
Was there anything you wish you'd known earlier that you only found out weeks in? The answers to this question are almost always the same few things: how priorities actually get set, which processes are real vs. aspirational, where the important context lives.
Those answers are the gaps. They're the things your onboarding isn't covering. And they're almost always things that exist somewhere — in someone's head, in an old Slack thread, in a doc nobody links to — but haven't been surfaced.
The Compounding Return
Every time a new person joins and the team invests in helping them understand how things work, there's a choice being made: extract that context and put it somewhere findable, or deliver it verbally and let it evaporate.
The verbal delivery is faster in the moment. Over a year, with several new hires, the total cost of that choice adds up significantly — in onboarding time, in repeated questions, in mistakes made because context wasn't available.
Teams that build their onboarding into the same workspace where they do their daily work find that the marginal cost of each subsequent hire drops. The first person to join after the workspace is well-organized gets a dramatically better experience than the tenth person in the old system did.
That's the compounding return on investing in how your team documents itself — not as an end-of-sprint ritual, but as part of how work gets done.
Closot gives teams a shared workspace where onboarding content, active projects, and team context live in the same place — so new hires can find what they need without waiting to be told. Start free.