Build a team handbook in a weekend — the one document that prevents 80% of problems.

Every quarter, a founder asks me 'do we need a handbook yet?' The honest answer: you needed one at hire number five. The second-honest answer: most handbooks are useless, so I understand why you've avoided it. The version that works isn't a legal document, isn't a corporate values doc, and definitely isn't a 60-page Notion template you forked from a public startup. It's an 8-page operating manual for being a person on your team.

Done right, it answers the 30 questions every new hire silently asks in their first month, removes 80% of the 'is this okay?' Slack pings, and makes onboarding 3x faster. Here's the version that has worked across 40+ companies I've supported.

The 12 sections (and what to put in each)

• 1. How we make decisions — Who decides what, how disagreements escalate, what 'committed' means.
• 2. How we communicate — Slack vs. email vs. meetings, response time expectations, async-first rules.
• 3. How we run meetings — Default lengths, agenda discipline, who can call one, no-meeting blocks.
• 4. How we give feedback — The model you use (see SBI), cadence of 1:1s, how reviews work.
• 5. How we hire — Stages, who's on the loop, what 'no' means, how feedback is shared.
• 6. How we onboard — Day 1, Week 1, Month 1, Quarter 1 expectations. Buddy assignment. First-win target.
• 7. Comp & equity philosophy — Bands philosophy, raise cadence, equity refresh policy.
• 8. Time off — Vacation, sick days, parental leave, sabbaticals, public holidays. Be specific.
• 9. Remote / hybrid — Where people work, expected overlap hours, travel/visit policy, home-office stipend.
• 10. Performance — What 'meeting expectations' means, what triggers a PIP, how promotions work.
• 11. When things go wrong — How to raise a concern, how to report harassment, who handles what, confidentiality rules.
• 12. What we don't do — Anti-patterns. 'We don't counter-offer.' 'We don't do unpaid trial work.' 'We don't ghost candidates.'

The psychology: why explicit beats implicit

Edgar Schein's classic work on organisational culture distinguishes three layers: artifacts (what you see), espoused values (what you say), and underlying assumptions (what you actually do). Most early-stage cultures run entirely on layer three — unspoken rules that founders assume are obvious. They're not. New hires spend weeks reverse-engineering them, often incorrectly. A handbook drags the third layer up into the first — fast onboarding, fewer misunderstandings, less politics. And critically, it gives everyone a shared text to debate when something needs to change.

The 2-day writing sprint

Saturday morning (3 hours)

Open a blank doc. Write the 12 section headers. Under each, write 3–5 bullets — not paragraphs. Don't worry about prose. Just capture the actual current rules. Where you don't know the rule, write '???' and move on. This is the most important step: discovering where you've been operating on vibes.

Saturday afternoon (2 hours)

Go through the '???' sections with your co-founder or leadership team. Make a decision for each one. Write it down. The act of having to write it is what forces the decision.

Sunday (3 hours)

Turn the bullets into short paragraphs. Use plain language. Cut anything legal or aspirational — those belong in other documents. Add concrete examples. Keep it under 8 pages. Read it as if you're a new hire on day 1. Cut anything that wouldn't help them in the next 90 days.

How to make sure people actually read it

• Walk every new hire through it in their first week. 30 minutes. Live conversation, not a self-serve link.
• End the walkthrough with: 'What's unclear? What would you change?' Their notes are gold.
• Re-read it as a leadership team every 6 months. Update or delete 1–2 sections. Date the changes.
• When a Slack debate breaks out about 'how we do things,' the answer should usually be 'the handbook says X — should we change the handbook?'
• Make it the link you send candidates after the second interview. Your hiring conversion will go up.

Real case: the handbook that fixed five problems in a quarter

A 22-person company, as one HR leader recounted, was burning hours on five recurring problems: vacation-overlap disputes, ambiguous promotion criteria, inconsistent interview loops, comp negotiation chaos, and Slack-vs-email confusion. They wrote a 7-page handbook in a weekend. Within a quarter: vacation conflicts dropped to zero, promotion criteria stopped being argued about, interview loops got 40% shorter, comp negotiations got 60% faster, and 'where do I ask this?' Slack messages disappeared. The whole exercise took 8 hours and saved an estimated 12 leadership hours per week, every week, forever.

Take this home — your weekend handbook plan

• Block a Saturday. Tell your co-founder. Don't push it.
• Use the 12 sections as your skeleton. Bullets first, paragraphs later.
• Mark every '???' honestly. Decide each one before Sunday.
• Keep it under 8 pages. If it grows past 12, you're writing the wrong document.
• Walk every new hire through it personally for the first 5 hires. Then delegate to a senior IC.
• Re-read and revise it every 6 months. Date the changes. Tell the team what changed.