Creating An Engineering Handbook In 3 Days (or Less)
summary
An 800‑engineer org organizes a 20-person workshop and turns concept into an almost‑published Engineering Handbook in 3 days, using ideation + outlines, peer review, strict character targets and an editor to force drafts, then publishes on GitBook. The MVP surfaces surprising differentiators (own data centers, test practices), converts skeptical teams (infrastructure ends up producing 30% of content), scales into monthly workshops, yields ~120 articles in a year and about 3,000 monthly readers.
AI-written summary · about
chapters (9)
- 0:00Engineering handbook project intro
- 3:19Why Infobip needed it
- 8:23Assembling the team
- 10:11Day one: Ideation & structure
- 17:24Day two: Outlining & review
- 21:19Day three: Writing & focus
- 26:15Results & long-term impact
- 30:11Six tips for engineering content
- 32:44Q&A
related talks
27mHow We Created A Global Engineering Handbook in 3 Days
31mGREAT BIG ENGINEERING ORG; itty bitty docs team
25mHypervelocity Engineering: The End of Slow Dev
06mRemoving engineering friction: Creating an evolutionary culture
32mApplying Engineering Principles to Technical Writing
32mBuild Teams as an Engineer
40mAll together now: Turning technologists into documentarians
40mThe Knowledge: Towards a Culture of Engineering Documentation