We’re Not in Kansas Anymore: How to Find Courage while Following the Technical Doc Road
summary
Technical docs succeed through concrete habits: run a stakeholder whiteboard session (day two became a day-five goal), attend standups to capture feature changes, and pin write down goals where you can check them. Use design critique rules: collect raw feedback, map each item to project goals, then decide what stays. Practice sharing drafts aloud (even to a dog) and rehearse with the person whose feedback scares you most. Accept compromise, iterate quickly, and aim to help users rather than pursue perfection.
AI-written summary · about
chapters (7)
- 0:00Introduction and challenges
- 1:07Building your support team
- 3:04Vulnerability and collaboration
- 5:10Planning and research
- 7:28Handling feedback
- 10:11Accepting positive feedback
- 11:08Overcoming perfectionism
related talks
20mDo Docs Better: Practical Tips on Delivering...
52mKeynote: Steps to Wisdom
29mHumanizing Your Documentation
39mWe're Agile, we don't do documentation
29mChange Management for Humans
28mChange Management for Humans
33mWhat The Doc?!?! How to Write and Read Documentation That Allows You To Get Sh*t Done!
35mFrom Code to Clarity: Collaboration with Devels when Writing Product Documentation