Why Work with a Tech Writer?
summary
Tech writing engagement turns a messy set of playbooks, runbooks, postmortems and QuickStart guides into maintainable, findable docs by choosing repositories, adding templates, running a doc fix-it and producing a 12-week engagement model that includes kickoff, research, outlines, drafts, reviews and a handoff with a maintenance plan. Claims: documentation frees engineer time, reduces repeated user questions, and makes work reusable. Options range from full-time hire, contractor for a defined assignment, one-writer-to-many-teams support, or short consultations to set strategy.
AI-written summary · about
chapters (10)
- 0:00Intro
- 0:20About me
- 2:37Team internal docs
- 3:27Common problems
- 3:53It can get better!
- 4:51(2) User doce
- 5:23User does: Types
- 6:10Bonus: Docs to increase your visibility/disseminate knowledge
- 7:53Tech Writer engagement models
- 9:10Sample engagement
related talks
21m7 Values of Effective Tech Writing Teams
17mHacking Your Documentation: Who Should WTFM?
25mTechnical Writing for Developers and Engineers
36mTechnical writing in English
30mTechnical Documentation
04mRight our Docs
34mDocumentation Thinking Beyond the Docs: Lessons from Decision-Facing Technical Writing
35mFrom Code to Clarity: Collaboration with Devels when Writing Product Documentation