"Chat, Are We Cooked?" Help in the Moment: Designing Policy Documentation for High-Stakes, Real-Tim…
summary
A study with Partner streamers in December 2025 labels supporting docs “mushy” and prompts a redesign: build a friction spectrum (levels 1–4) to decide when to publish concrete guidance, run creator roundtables to map policy knots, and train the AI chatbot on help center fixes so daily escalations surface gaps. Two tiers of deliverables appear: a crisis response quick‑reference (findable in ~30 seconds) and planning guidance; automation of help center workflows frees staff to do this strategic work.
AI-written summary · about
chapters (23)
- 0:00Introduction
- 1:43Talk title explained
- 2:26Policy doc challenges
- 3:08Live streaming needs clarity
- 4:33Twitch docs gaps
- 6:19Triforce framework
- 7:44Creators' policy fears
- 9:10Creator policy knots
- 14:03Education friction spectrum
- 18:39AI chatbot stress test
- 20:23Two-tier content strategy
- 21:47Stakeholder buy-in
- 22:51Measuring impact
- 24:35Evergreen frameworks
- 25:59Call to action
- 26:39Q&A: Community safety
- 27:21Q&A: Avoiding L3 content
- 28:46Q&A: Flexibility vs protection
- 29:31Q&A: Social norms advice
- 30:35Q&A: Live stream reactions
- 31:40Q&A: Policy contradictions
- 33:05Q&A: Team of one journey
- 34:29Closing remarks
related talks
40mRelease-ready Docs: How a 2-person team keeps a help center consistently accurate
39mBake a Little Documentation Love into Your Product
29mPanel: The Toxic Content Dilemma – Is In-game Game Chat a Lost Case or Can it be Saved?
31mFireside Chat on Documentation
21mOnly Interesting Conversations: The Symbiotic Relationship Between Docs and Support
31mEnhance Developer Experience by community
13mEmbed The Docs!
22mLess tech, more value tacking digital waste with sustainble produ