# Vadim Kravcenko - The Surprising Power of Documentation (Highlights)  ## Metadata **Review**:: [readwise.io](https://readwise.io/bookreview/29979950) **Source**:: #from/readwise #from/reader **Zettel**:: #zettel/fleeting **Status**:: #x **Authors**:: [[Vadim Kravcenko]] **Full Title**:: The Surprising Power of Documentation **Category**:: #articles #readwise/articles **Category Icon**:: 📰 **URL**:: [vadimkravcenko.com](https://vadimkravcenko.com/shorts/proper-documentation/?ref=refind) **Host**:: [[vadimkravcenko.com]] **Highlighted**:: [[2023-07-11]] **Created**:: [[2023-07-12]] ## Highlights -  ([View Highlight](https://read.readwise.io/read/01h52a86j90ejjd2j35gky89we)) ^561919997 - Documentation first, meetings second ([View Highlight](https://read.readwise.io/read/01h52aew11xmjr57k1kgdw4vn5)) ^561921228 - The constant need to have meetings is a symptom of a deeper problem — **a lack of clear, accessible, and reliable documentation.** A well-documented workflow doesn't need an hour-long session for clarification. A well-documented decision doesn't need a room full of people to understand its rationale. A well-documented knowledge base doesn't need a group huddle whenever a new member joins the team. ([View Highlight](https://read.readwise.io/read/01h52ag2cq8ntq1kva455r5n7e)) ^561921528 - Also, meetings often favor the loudest voices, not necessarily those with the best ideas. It's a subtle form of bias that can stifle innovation and diversity of thought. Documentation, on the other hand, levels the playing field. It provides a platform for every team member to articulate their thoughts and insights, regardless of rank or communication style. It promotes a culture of thoughtfulness and reflection rather than snap judgments and impulsive decisions. ([View Highlight](https://read.readwise.io/read/01h52ajsymnzgr32mqj3kh6gpw)) ^561921693 - Now, as a CTO, how can you facilitate this? Encourage your team to document their decision-making process to clarify assumptions, reasoning, and expected outcomes. Make it a standard practice to discuss these documented decisions in your meetings, promoting a culture of open feedback and collaborative decision-making. ([View Highlight](https://read.readwise.io/read/01h52amd7db1hq5eaebf466asa)) ^561921784 - A documentation-first culture does not mean everyone is busy writing documents all day. *It means that everyone appreciates the value of documenting and sharing their experiences.* ([View Highlight](https://read.readwise.io/read/01h52an9aw8cc1xa33n80z85fs)) ^561921840 - What it also means, of course — when building a project, always account for documentation as part of ANY task. It should be a default that some percentage of employees’ time goes into writing down their stories. It's not just about efficiency — it's about creating an environment where shared knowledge is celebrated. It's about creating a culture that doesn't just create a product but crafts a story — a story of collective growth. ([View Highlight](https://read.readwise.io/read/01h52ap1kmk73t7gb37j1sdvfg)) ^561921859