Write the Docs Berlin 2026
as the organisers put it
Write the Docs Berlin 2026 is a conference for documentarians and everyone who writes the docs. Join us Sep 6-8, 2026 in Berlin, Germany.
who it's for
technical writers, documentation managers, docs engineers, content designers, developer experience engineers, api writers, docops engineers
topics
judgment over generation; AI-assisted drafting workflows; docs health metrics; OpenAPI-driven API docs; docs-as-code repository patterns; content strategy for design systems; documentation infrastructure at scale; people-first accessibility for AI; versioned prompt repositories; feedback loops and ticket deflection; contribution and review workflows
| title | author | length |
|---|---|---|
| Beyond Automation: Human Judgment as the Strategic Core of Business Writing | Kel Raleigh | 35m |
Introduces the Judgment Over Generation model that treats writing as three lanes: AI-enabled generation, human-AI interpretation, and human-led judgment. Shows… | ||
| Proving and improving the value of your docs | Tal Gluck | 34m |
State of Docs surveys find one in four teams track no metrics and ~80% of decision makers read docs, so the talk lays out concrete measurement choices: use… | ||
| Moonshot mindset: A tech writer's guide to thinking big and breaking free from the GDZ | Kate Wilcox | 34m |
Argues that adopting a moonshot mindset — not just chasing requests — yields strategic wins using a practical CRAFT framework (inspiration, roadmap, alignment… | ||
| Write inclusive, people-first language about AI | Alexandra Klepper | 35m |
A proposal called "people first accessibility language for AI and agents" argues that people-first language must center humans because accessibility is for… | ||
| Documenting APIs: new era, same craft | Javier Rubio | 35m |
API docs need to be close to the code: generate an OpenAPI file from tests that go red auto-generate spec or from annotations so docs ship with every deploy… | ||
| Mapping Your Docs-as-Code Repo: Navigating Architectural Evolution of Repositories | Hridyesh Bisht | 23m |
Maps and compares four concrete repo patterns tested at scale and when each actually succeeds: Public-Private Mirror (keeps unreleased content private but adds… | ||
| Writing Less, Owning More: The Shift in Technical Writing | Whitney Burkes | 29m |
Describes a tested process at Deutsche Bank that turns ad hoc prompt use into a reproducible system: a shared prompt repository stored in Git, run via editor… | ||
| Monday Lightning Talks | Florian Stolzenhain, Deepak Valagam, Emily Axel, Jonathan Putnam, Moronfolu Olufunke, Fraser Keddie, Carolyn Stransky Vohr | 31m |
A sprint of six five-minute pieces: a talk that treats storytelling as a protocol and argues oral tales act like lossy compression for knowledge; a warehouse… | ||
| Structure after the fact: Bringing content strategy to existing docs for a design system | Jen Buley | 36m |
Joins a design system as the first content hire for a 700‑page Dev Portal built on Docsaurus and unifies work across ~60 developers and designers. Runs… | ||
| Good Enough at Scale: Documentation Infrastructure Under Capacity Constraints | Elena Baskakova | 28m |
Two writers support nine products and find writing itself is rarely the bottleneck; discovery, verification, reviews, and follow-up take most time. The team… | ||
| Doc Health Metrics: How Two Writers Built a Framework to Prioritize Docs | Anastasia Suboch | 31m |
Creates a measurable docs health system that scores product docs across five concrete metrics — coverage, readability, style compliance, freshness… | ||
| Silence Is Not Approval: When Better Docs Create More Feedback | Uladzislava Lahun | 26m |
Documentation for a proprietary game engine scales from 15 to 1,000 users, feedback stops being ignorable and a lightweight loop is built: annual surveys… | ||
| When words become attacks: prompt injection through a technical writing lens | Oishi Banerjee | 25m |
Documentation is an attack surface: a Chevrolet dealership bot agrees to a "$1 Tahoe that's a legally binding offer," Samsung engineers leak internal data to… | ||
| Trading in Trust: How Documentation Protects People, Not Just Projects | Stephan Rayner | 31m |
Documentation functions as trust infrastructure: a missing policy lets power and loudness decide, while a written contract changes interactions. Example… | ||
| Tuesday Lightning Talks | Brooke Stauner, Kenneth Whyte, Miranda Wilson, Gugulethu H., Erica Beyea, Anton Kolesnyk, Val Grimm, Carolyn Stransky Vohr | 40m |
Seven five‑minute pieces cover practical, weird and tactical moves: a push to write for users who are having a really bad day (EHR medics, immediate errors… | ||
| nothing matches | ||