The art and practice of documentation triage
summary
Concrete workflow named documentation triage organizes work: do a content audit, hunt internal wikis and support threads, tag items by value vs effort, and give honest estimates in days or sprints. Prioritize ruthlessly toward minimum viable documentation, plan "good enough", write fast, publish, and instrument feedback paths so readers act as QA. Track notes about sources and owners, push big projects toward lower effort by recruiting sales or professional services, iterate and re-evaluate.
AI-written summary · about
chapters (6)
- 0:00Start
- 3:16WHAT IS DOCUMENTATION TRIAGE?
- 7:27CONTENT AUDIT EXAMPLE
- 9:00VALUE VS LEVEL OF EFFORT
- 14:37THINGS TO THINK ABOUT
- 23:08IDENTIFY
related talks
37mTaking a step back: Analysing your documentation
36mTo document, or not document that is the question
26mJust-In-Time Documentation: Employing Agile Methodology To Create Living Documentation
39mWe're Agile, we don't do documentation
26mWe're Agile, We Don't Do Documentation
10mCan we NOT do docs at the eleventh hour? Mmmmmaybe.
18mTechnical Documentation - How Can I Write Them Better and Why Should I Care?
38mThe Stuff You Don't Want to Write... Documentation