How We Created A Global Engineering Handbook in 3 Days
summary
A global engineering handbook gets planned, written and published in 72 hours using a tight, staged process: ideation with Post‑its and voting, outlines, then focused writing sprints. A cross‑functional group of 20 people, 3 days produces dozens of pages, published via Getbook, using 30-minute writing sprints and editor review. Result: a live public handbook, sustained content program (100+ engineering blog posts in a year), and ~3,000 organic developer visits per month.
AI-written summary · about
chapters (7)
- 0:00Introduction and mission
- 3:34Assembling the team
- 8:09Day 1: Ideation and structure
- 13:34Day 2: Outlining content
- 18:08Day 3: Writing the handbook
- 23:22Results and future plans
- 26:11Key takeaways
related talks
41mCreating An Engineering Handbook In 3 Days (or Less)
31mGREAT BIG ENGINEERING ORG; itty bitty docs team
26mNo Community Members Were Harmed in the Making of This Doc Sprint: How we ran a 48-hour Event to Collect Community Wisdom into a Guidebook for Newsroom Developers
40mThe Knowledge: Towards a Culture of Engineering Documentation
30mBuilding technical documentation as a product at scale
40mAll together now: Turning technologists into documentarians
23mMain Takeaways After One Year in Documentation
25mCrowdsourcing platform engineering