Cultivating a Stakeholder Network for Our Docs
summary
Rewrites of Splunk’s custom search command docs produce task-based guidance and a standardized glossary across docset SDK and examples repo but initial release misaligns with how most customers build commands so direct outreach follows: one‑on‑ones, beta programs, blog posts and an active user group Slack. That outreach raises traffic and citation — measurable as a clear page views increase and more cross‑links — and a hostile critic converts into a collaborator who helps the docs actually fit real workflows.
AI-written summary · about
chapters (9)
- 0:00Start
- 3:20Project results
- 8:26Outcomes of community engagement
- 9:49Similar to doc feedback?
- 14:33Community channels
- 20:05Overcome internal obstacles
- 22:33Measure your impact
- 24:25Testimonial
- 25:53Takeaways
related talks
26mSilence Is Not Approval: When Better Docs Create More Feedback
37mWhat's past is prologue: Write the Docs, communities, and organizing techcomm
30mJudas Priest Ate my Scrum Master
13mWe’re Not in Kansas Anymore: How to Find Courage while Following the Technical Doc Road
49mHow-To: Build Thriving Cultures through Positive Communication
31mSRE Stakeholders: A Spotter’s Guide
33mEmbrace DevOps, Lead With Vulnerability
28mChange Management for Humans