Teaching a New Hire the Rules Nobody Wrote Down

A new hire gets a thorough onboarding: tool access, process documentation, a walkthrough of the org chart, maybe a buddy assigned for the first two weeks. None of that covers the fact that on this particular team, nobody replies to a message in the group channel unless it’s urgent, or that decisions announced in a meeting are actually finalized only after someone circulates a follow-up email, or that a certain senior colleague prefers a heads-up before their work gets referenced in front of others. These aren’t written anywhere, because nobody thought to write them down — they became obvious to everyone already on the team through months or years of simply being there.

Formal Onboarding and Actual Onboarding Are Different Processes

The documented onboarding process covers what’s easy to document: systems, permissions, official workflows. The unwritten rules — how disagreement actually gets expressed, which meetings are genuinely optional despite the calendar invite saying otherwise, who needs to be looped in before a decision feels settled — exist entirely in the accumulated experience of people who’ve been on the team long enough to have absorbed them without ever consciously listing them out. A new hire following the written onboarding perfectly can still stumble constantly, not because they did anything wrong by the documented rules, but because the documented rules were never the whole picture.

Why These Rules Rarely Get Written Down

Unwritten rules resist documentation for a specific reason: the people who could write them down don’t experience them as rules anymore. They’ve become invisible through familiarity, the same way a native speaker doesn’t consciously think about grammar while talking. Asking a longtime team member to list their team’s unwritten norms often produces a short, incomplete list, not because they’re withholding information, but because most of what actually governs daily interaction has become instinct rather than something they’d think to mention.

Where New Hires Actually Get Tripped Up

Common friction point	The unwritten rule behind it
Sends a detailed message in the main channel, gets no response	The team reserves that channel for urgent items only
Assumes a meeting decision is final	The team treats meetings as discussion, follow-up email as the real decision
Cc’s someone on a routine update	That person only wants to be looped in on exceptions, not routine status
Pushes back openly in a group setting	Disagreement here happens privately first, group settings are for consensus

None of these missteps reflect poor judgment. They reflect the absence of information that was never given, because nobody realized it needed to be.

Making the Unwritten Visible, on Purpose

The most effective fix isn’t a longer onboarding document — most unwritten rules resist being captured that thoroughly and a document that tried to list everything would become unwieldy fast. It’s a direct conversation, ideally within the first week, where someone explicitly walks a new hire through the team’s actual operating norms rather than its official ones: how disagreement gets raised, what the real decision-making moment is versus the performative one, who prefers what kind of communication. This requires the person running the conversation to actively notice their own team’s habits, which takes deliberate reflection rather than being obvious even to them.

Asking the New Hire What They’re Noticing

Counterintuitively, a new hire is often the best source of information about a team’s unwritten rules, precisely because they haven’t yet stopped noticing them. Something that felt strange or unclear in week one is exactly the kind of thing a team should want surfaced, both to help that specific person and to catch norms that might be worth explaining better to the next hire. Teams that build a habit of asking new hires directly — what’s felt confusing, what took you by surprise — end up with an evolving, real list of the norms actually worth documenting, generated from the people most equipped to notice them.

The Cost of Leaving This to Osmosis

Left unaddressed, new hires learn unwritten rules the slow way: through a series of small missteps, mild embarrassments, and gradually accumulated pattern recognition, usually over two or three months. This is slower and more stressful than it needs to be, and it disproportionately disadvantages people who are less inclined to ask questions directly or who come from different professional backgrounds where different norms were the default. A team that never addresses this gap isn’t just slowing down onboarding — it’s quietly making early tenure harder for exactly the people least equipped to absorb ambiguity through trial and error.

Revisiting the List as the Team Itself Changes

Unwritten rules aren’t static. A norm that held when the team was five people may not survive at twelve, and a habit that made sense under one manager may quietly disappear under another without anyone officially retiring it. Teams that periodically revisit what their current unwritten rules actually are — not just when onboarding a new person, but as a standing practice — catch the moments where an old norm has outlived its usefulness or a new one has formed without anyone consciously deciding it should.

Writing Down What Can Be Written, Naming What Can’t

Not every unwritten rule needs to become an official document, and trying to formalize all of them risks producing a rulebook that feels more bureaucratic than the informal culture it’s replacing. The useful middle ground is writing down what genuinely helps a new person get oriented faster — communication preferences, where real decisions happen — while accepting that some texture of a team’s culture will always be something a person absorbs by being there, not something any document can fully transmit in advance. The goal isn’t eliminating the unwritten. It’s making sure the unwritten stops being a source of unnecessary early friction for the people who haven’t had the time yet to learn it the slow way.

The Manager’s Blind Spot Is Usually the Biggest One

Managers often assume they have the clearest view of their own team’s norms, when in practice the opposite is frequently true — a manager’s presence changes how a team behaves in ways the manager themselves rarely notices. A norm around how disagreement gets raised, for instance, might look completely different when the manager is in the room versus when they’re not, and the manager is the one person least likely to ever see the second version directly. This means the unwritten rules a manager thinks they’re capturing for a new hire may be an incomplete or even inaccurate picture, and cross-checking with peers who work alongside the new hire day to day, rather than relying solely on the manager’s own account of team norms, tends to produce a more accurate and more useful orientation.

Building a Living Reference Instead of a One-Time Briefing

A single onboarding conversation, however thorough, captures only what the team happens to think of at that moment, which is rarely the complete set of norms a new hire will eventually need. Teams that treat this as an evolving reference — a lightweight, informally maintained document that gets a new entry whenever someone notices an unwritten rule worth naming, contributed to by whoever happens to notice it, not just by managers — build up a genuinely useful resource over time that serves not just the next new hire but existing team members who may have been quietly confused about a norm nobody had ever explained to them either.