GitLab Handbook First Decision Process

Document decisions by editing the company handbook directly. GitLab uses merge requests instead of meetings to make transparent operational choices.

5 time blocks, 65 minutes in total.

Time blocks

Search Existing Handbook Canon: 10 min
Check current documentation to establish existing baseline rules
Draft Merge Request in Markdown: 25 min
Write the proposed change directly into the handbook repository
Assign Async Reviewers: 10 min
Tag relevant team members and set an asynchronous review timeline
Process Review Feedback Threads: 15 min
Address inline comments and edit the pull request diff directly
Merge and Codify Canon: 5 min
Merge the change to establish the updated single source of truth

About this routine

GitLab operates as a fully remote organization guided by a public handbook containing thousands of pages. Rather than debating decisions in live meetings or buried chat threads, team members use the GitLab handbook first decision process. Every proposal starts as a direct edit to official company documentation.

When an employee identifies an operational change or strategic choice, they search existing handbook pages first. They open a merge request proposing specific text updates in Markdown format. Colleagues review the diff asynchronously, leaving inline feedback and making direct updates to the text.

Once feedback is addressed, the merge request is approved and merged into the main handbook repository. This workflow ensures that every decision creates an immediate searchable record without relying on verbal consensus or forgotten slide decks.

Why this routine works

Creates an immediate single source of truth for all operational choices
Eliminates repeated status meetings and live debate sessions
Allows distributed teams to contribute asynchronously across time zones
Builds a searchable historical audit trail of company decisions

FAQ

What is GitLab's handbook first policy?

It means every company policy, process change, or decision is documented directly in the public handbook before or as it is communicated, rather than being discussed purely in meetings or chat.

How does GitLab make decisions asynchronously?

Team members open a Merge Request on the handbook project, outline proposed updates, tag relevant reviewers, and gather inline comments before merging the change into canon.

Why use handbook first decision making?

It prevents loss of context, eliminates unnecessary alignment meetings, and keeps a single source of truth accessible to everyone in distributed remote teams.