What It Is
Written-first culture means that the default response to any significant decision, discussion, proposal, or direction is to write it down — not to discuss it verbally and document the outcome later, but to start with writing.
The meeting is not the medium. The document is.
This is different from having a documentation culture (writing things after the fact) and different from note-taking (capturing what was said verbally). Written-first means the thinking happens in writing, not in conversation.
Why It Works
Writing produces better decisions. When you have to write something down, you have to think it through clearly enough to explain it to someone who was not there. Vague ideas that survive verbal discussion collapse under the obligation to write them precisely. 37signals’ principle: “Writing solidifies, chat dissolves.” (Source)
Writing is independent of schedule. “Communication shouldn’t require schedule synchronization.” (Source) A written proposal can be read at 2am in Tokyo or 3pm in São Paulo. A meeting cannot.
Writing helps everyone, including people who were not there. This includes people who couldn’t attend, people who join the company later, and people who need to understand the context of a decision made two years ago. Verbal communication disappears; writing compounds. (Source)
Writing is more equitable. In meetings, the loudest voices win. In writing, every comment exists as an artifact. People who process more slowly or who communicate better in writing get a fair hearing. [Inference — based on the absence of accent, fluency, and response-latency biases that real-time speaking tends to produce in mixed-language teams. The site does not cite an empirical study on this; the claim is a load-bearing inference rather than a measured finding.]
GitLab’s entire operating model is built on this premise. Their 2,000-page public handbook is not documentation overhead — it is the organizational infrastructure. When a decision is made, it goes into the handbook. The handbook is the company. (Source)
Where It Fails
Poor writers become organizational bottlenecks. In a written-first culture, people who cannot write clearly become coordination problems. Their proposals are misunderstood, their decisions are challenged, and their status updates generate follow-up questions. [Inference — practitioner observation across written-first companies; no published cross-company study quantifies the effect, but the corollary is visible in the explicit hire-for-writing requirements at Doist, Basecamp, and GitLab.]
Not all information belongs in writing. Sensitive personnel situations, crisis emotional support, and genuine real-time creative brainstorms have a legitimate claim on synchronous communication. Written-first companies that apply the norm too rigidly create unnecessary distance in the moments that require human warmth.
Documentation without maintenance is misinformation. A written-first culture that does not maintain its documents is worse than no documentation at all. Stale handbooks, outdated wikis, and overwritten Notion pages are actively misleading. GitLab treats handbook maintenance as real work — most companies do not. (Source)
Performative writing replaces real communication. When writing is rewarded, people write more — including writing that signals activity rather than producing clarity. Long update posts that nobody reads, detailed plans that nobody follows, documentation that exists to demonstrate effort rather than transfer knowledge. [Inference — practitioner observation; not a measured pattern, but a known failure mode in document-heavy organizations.]
Best Examples
37signals / Basecamp — Explicit rule: “Writing solidifies, chat dissolves. Substantial decisions start and end with an exchange of complete thoughts, not one-line-at-a-time jousts.” Internal email is banned. Meetings are last resort. All significant communication happens in long-form writing inside Basecamp. (Source)
GitLab — The handbook is the single source of truth. “If it’s not in the handbook, it doesn’t officially exist.” Decisions go into the handbook. Processes go into the handbook. Values go into the handbook. The public availability creates external accountability for writing quality. (Source)
Automattic — “Communicate as much as possible, because it’s the oxygen of a distributed company.” Their Expectations document specifies: “Strive for clarity in your communication with high-level summaries.” The P2 blog system creates permanent written artifacts of all project work. (Source)
Doist — Written communication is foundational to their no-meetings model. Twist’s threaded structure enforces writing by design — you cannot have a synchronous Twist conversation; the format requires written, asynchronous exchange. (Source)
Implementation Guide
1. Start with decisions, not all communication. Do not try to make everything written. Start with: every significant decision must be written down with the reasoning. This creates momentum without overwhelming people.
2. Write the memo before the meeting. If you are going to have a meeting about something important, require a written document first. Everyone reads it before the meeting. The meeting discusses it, does not present it. Jeff Bezos’s “six-page narratively-structured memo” practice at Amazon is the most famous version of this; he describes it directly in his 2017 letter to shareholders. (Source: Amazon 2017 Letter to Shareholders, p. 4)
3. Pick one canonical place. “Everything in writing” breaks down when the writing is scattered across Notion, Confluence, Google Docs, Slack pins, and GitHub READMEs. Pick one place for decisions. Pick one place for processes. Maintain the distinction.
4. Write for the person who was not there. Every document, decision, or proposal should be comprehensible to someone reading it a year later with no context. Assume no shared knowledge. This discipline produces documents that are genuinely useful.
5. Reward writing quality explicitly. If you want a written-first culture, writing quality has to be a visible factor in performance evaluations and promotions. Otherwise, the incentive structure pulls people toward meeting performance, which is more visible in the moment.
6. Maintain your documents. Assign owners to living documents. Establish a cadence for reviewing key handbooks and policies. Outdated documents create confusion that is worse than no documents.
Common Mistakes
Writing everything down without organizing it. An avalanche of documents is not a written-first culture. It is noise. Good written-first cultures have strong information architecture: predictable places for different kinds of content, consistent formats, clear ownership.
Confusing documentation with written-first culture. Documentation is writing after the fact. Written-first means the thinking happens in writing. Documentation is a product of written-first culture; it is not the culture itself.
Requiring long writing for short decisions. A small bug fix does not need a six-paragraph proposal. Written-first should be proportional to the significance of the decision. Over-applying the norm creates bureaucratic friction that makes people avoid writing at all.
Writing meeting notes instead of replacing meetings with writing. Taking good notes and circulating them after meetings is not written-first culture. It is better than nothing, but the meeting was still the primary mode. The shift is to write first and use meetings only when writing has been genuinely insufficient.
Sources
- The 37signals Guide to Internal Communication: https://basecamp.com/guides/how-we-communicate
- GitLab Communication Handbook: https://handbook.gitlab.com/handbook/communication
- Expectations — Automattic: https://automattic.com/expectations/
- How Doist Works Remote: https://doist.com/how-we-work/how-doist-works-remote
- Amazon 2017 Letter to Shareholders (primary source for Bezos’s six-page narratively-structured memo practice): https://www.aboutamazon.com/news/company-news/2017-letter-to-shareholders
Inferences
- Written-first culture is self-reinforcing once established, and very hard to establish after the fact. Teams that were built on verbal communication develop verbal communication habits, social norms, and hiring filters that favor verbal thinkers. Shifting to written-first after 50+ people requires either deliberate culture change at the top or a crisis that makes the cost of verbal-first visible.
- The correlation between written-first culture and remote work is strong but not necessary. The best written-first practitioners (37signals, GitLab) are remote. But the reasons written-first works — it creates permanence, forces clarity, scales across time — apply equally to colocated companies. The difference is that colocated companies can survive without it because verbal communication covers the gaps.
Work with Alex
If your leadership team is the source of institutional knowledge that has never been written down — and you want to change that before it becomes a crisis — Alex helps companies build the written communication infrastructure that makes distributed execution durable.