The Power of Two: How Support and Docs Teams Transform Technical Content Quality
summary
A practical, repeatable framework pairs support case data with docs expertise to prioritize and ship content changes on a quarterly cadence, delivering two projects per quarter on average. Built artifacts include a structured ticket template, a central program wiki and a single source‑of‑truth project doc. Concrete results: S3 permission cases are 17% of annual cases, docs reference rises from ~2% to +27%, customer doc tickets fall 4% on average, some pages see 90% ticket drops and projects hit 100% escalation reductions.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 0:36Yanjies background
- 1:52Our teams
- 8:11Streamlined framework
- 15:21Launch and monitoring
- 18:27The impact
- 21:58Key lesson 1
- 24:14Key lesson 2
- 26:27Key lesson 3
- 32:05Questions
related talks
27mThe hidden power of information assets The role of documentation in product success
40mRelease-ready Docs: How a 2-person team keeps a help center consistently accurate
21mOnly Interesting Conversations: The Symbiotic Relationship Between Docs and Support
34mProving and improving the value of your docs
44mTesting Documentation: Why So Technical?
40mAll together now: Turning technologists into documentarians
39mQuantifying the Impact of Documentation: Findings from DORA Research
23mMain Takeaways After One Year in Documentation