The Pains of Composition: How to write your best documentation in a collaborative world
summary
Claims that collaboration speeds reviews but creates new frictions: moving docs into Confluence collaborative editor and using k-15t apps yields faster, transparent contributions but exposes process pain. Cites the $125 million Mars loss after 10 months as a prevention vs promotion example. Recommends concrete practices that work: pair writing, modelling constructive feedback, shared team values, internal blogs and timely reviews. Results: shorter feedback cycles and broader ownership, plus the new challenge of managing personalities and visibility.
AI-written summary · about
chapters (13)
- 0:00Intro
- 1:21Lone Tech Writer
- 5:30Agenda
- 6:05People have different personalities
- 13:27Different types of feedback
- 18:08Shared motivation and passion
- 22:26Sharing the process
- 27:34Collaboration
- 28:16Conclusion
- 28:46QA
- 29:36Remote work
- 32:38Doc reviews
- 37:00The value of documentation
related talks
05mCollaboration is scary and makes us better
42mCollaborating w/teams on content strategy planning: pitfalls & best practices
46mDocumentation as Marketing? From Conflict to Collaboration
51m”Co-Create: Creating Better Together”
29mClarity in Collaboration
39mInvisible influence: the documentation behind UX copy
40mDocumentation as User Experience
16mDesign Systems Showcase: Collaborative Structure