Scaling a unicorn: how to mature your docs program and support a changing business
summary
Company grows from ~350 to ~1,600 people while docs expand across six products and team size moves from three to nine writers; 300 FAQs get converted into the community forum to avoid upkeep; a brittle scrappy redirect JavaScript gets handed to front-end engineers and replaced; measurement focuses on CSAT and ticket deflection plus internal analytics; ownership shifts into a pillar ownership with backups model so every area has primary and secondary coverage and clearer prioritization.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 0:30Claviyo's growth story
- 3:21The scrappy startup phase
- 6:11Narrowing the focus
- 8:34Maturing processes and tools
- 11:50Retaining key auxiliary tasks
- 12:52Cultivating team expertise
- 14:52Operating as a mature team
- 17:38Key takeaways and conclusion
- 19:44Q&A session
related talks
23mGad Salner- How to scale a unicorn-building engineering team (and stay sane)
30mThe Elements of Scaling
46mHow to scale a unicorn-building engineering team (and stay sane)
34mWhen scalability becomes more than a buzzword, or how to saddle an unicorn
33mScaling yourself during hypergrowth
36mHypergrowth - lessons learned from tripling the size of a tech team
24mHow to design your team for scale
15mManaging During Growth & Change