Functional Documentation Testing
summary
Argues for measuring documentation by concrete outcomes not surface metrics, using user studies to record a time to competency (binary success plus minutes) and an Independent Learning Factor (how many times help is requested). Gives thresholds — anything over 60 minutes is bad, over 20 minutes is also suspect — and recommends before/after deltas to prove that doc changes cut minutes and help requests, a number managers can act on.
AI-written summary · about
chapters (4)
related talks
37mHumanising Your Documentation
43mWhat If Documenting Were Enough to Test?
34mDocumentation Thinking Beyond the Docs: Lessons from Decision-Facing Technical Writing
44mTesting Documentation: Why So Technical?
01h 24mWriting Documentation - Practices and Theory
18mTechnical Documentation - How Can I Write Them Better and Why Should I Care?
20mDo Docs Better: Practical Tips on Delivering...
40mDocumentation as User Experience