My Information Experience Adventure
summary
Atlassian moves technical writing out of QA into Design and redefines it as an Information Experience craft with an expanded team working on Bitbucket, Confluence and SourceTree. The group measures every doc page with Google Analytics and Optimizely, uses Scroll Viewport and k15 plugins, ports Markdown via a Harp pipeline, runs card sorting and sparring, and even ships a Python script to enforce English variants. An IX toolkit and training win influence company ADG and create one third of design talks delivered by IX.
AI-written summary · about
chapters (12)
- 0:00Start
- 0:10Dan Stevens
- 3:12Transition from the Qa Organization To Design
- 3:54Big Wins
- 4:18Expanded Team
- 8:26Resistance To Change
- 11:08Design Influence
- 12:46Developer Docs
- 14:22English Standardization
- 15:34Content Strategy
- 23:46Managing Content like Code
- 25:23Surveys and Metrics
related talks
38mAI for Software Development: A Reality Check
43mKeynote: Coding Culture
27mDX for 10x IaC: The Force Awakens
40mAll together now: Turning technologists into documentarians
14mDeveloper Experience: Your documentation deserves more love!
22mDecomposition and beyond: frontend engineering at scale
23mMaster JIRA APIs: Essential Documentation Tips
44mTesting Documentation: Why So Technical?
