Handbook-First Culture: The GitLab Model

GitLab pioneered what they call "All-Remote" — managing thousands of employees across 60+ countries with almost no mandatory meetings. Their foundational principle is Handbook-First: the company handbook is the single source of truth for every process, policy, and decision, and it is updated before any change takes effect.

If It's Not Written Down, It Doesn't Exist

In most companies, if you want to change a process, you call a meeting, agree on the change verbally, and then maybe update the wiki later — which nobody reads, and which is already out of date by the time someone finds it.

In a Handbook-First culture, the workflow is inverted:

1. The Change IS the Documentation: You don't "decide then document." You submit a Pull Request (PR) to the company handbook proposing the change — before any decision is made.
2. The Discussion Happens in the PR: Debate, objections, and refinements happen in the PR comments. This creates a permanent, searchable record of why a decision was made, not just what was decided.
3. The Merge is the Decision: Once the PR is merged, that is the new truth. There is no ambiguity, no "I thought we agreed to X on the call."

Here is what this looks like in practice. Suppose your team wants to change the on-call rotation policy. Instead of scheduling a meeting, the team lead opens a PR titled "Update on-call rotation: move from weekly to bi-weekly." The PR body explains the rationale, links to relevant incident data, and proposes the new policy text. Engineers comment with concerns or approval. After 48 hours, the PR is merged. The policy is live. The entire discussion is archived and searchable forever.

Benefits

• Onboarding is instant: New hires read the handbook. They don't need to shadow someone for three weeks to learn unwritten rules.
• Single Source of Truth: No more "Well, Alice said on the call that we should do X, but the doc says Y."
• Decisions are auditable: You can git log the handbook and see exactly when a policy changed and who approved it.
• Distributed contribution: An engineer in Seoul can propose a process improvement without waiting for a meeting slot that works across time zones.

The key rule: You are never allowed to say "Check the internal wiki" and point to a stale page. The handbook is the authoritative source. At GitLab, much of it is public — which creates an additional forcing function to keep it accurate and well-written.