From travel content to technical content: my journey

on YouTube ↗43m

" summary

Argues that “technical writer” is misleading and that the job is a product-focused technical content designer role, lays out a six‑step content design workflow (discovery, user/job stories, design, writing comes fourth, review, maintain), shows converting Swagger endpoint dumps into task-based API menus, demonstrates fixing confusing API docs and using HelpDocs’ stale review feature to schedule updates, and shows gov.uk’s site redesign as proof the approach scales and improves usability.

AI-written summary · about

" chapters (10)

1. 0:00Start
2. 3:34Content Design by accident... and by choice
3. 7:16What is Content Design?
4. 8:53Content Design principles
5. 10:46The user! Think about the user
6. 11:17Someone trying to renew their driving license online
7. 12:02A dev trying to find out how to fix an API error
8. 13:59Content Design phases for tech writing
9. 21:59Technical content design in practise: after
10. 23:26Technical content design in practise: before

" related talks

• 34mFrom Graffiti Writer to Technical WriterKruno Golubić · Write the Docs Prague 2020
• 38mMyths, Mistakes, and Missed OpportunitiesLinda Ikechukwu · Write the Docs Portland 2023
• 36mTechnical writing in EnglishTomas Fernandez · Nerdearla 2020
• 36mThe Invisible Work: What It Takes to Be the First (and Only) Tech Writer on the TeamAlina Desiatnikova · Write the Docs Portland 2026
• 06mBe a SalmonFabrizio Ferri Benedetti · Write the Docs Prague 2020
• 39mKnitting Together a Technical Writing CareerHeather Zoppetti · Write the Docs Portland 2025
• 38mHow and Why Technical Writers should Lead OnboardingGideon Behrensmeyer · Write the Docs Atlantic 2024
• 38mSeven habits of increasingly technical technical writersJanine Chan · Write the Docs Portland 2025