Don't Fear Migration! How to Successfully Move Docs to a New Tool
summary
Company moves a messy support wiki into a neutral docs tool after finding agents spend 13% of their time hunting answers and only 3% of pages actually help. Migration follows seven steps: project plan, content audit, cataloging, information‑architecture design (tested with card‑sorting), block‑based work, staged launch with user testing and training, then a retro. The team builds tagging, templates and a feedback loop, completes the migration, and reports smoother searches, fewer interruptions and measurable adoption.
AI-written summary · about
chapters (12)
- 0:00Intro
- 0:18HELLO! I'M BROOKE
- 1:28LAND ACKNOWLEDGEMENT
- 4:04KEY STEPS FOR A SMOOTH MIGRATION
- 4:56CREATE A PROJECT PLAN
- 8:58AUDIT YOUR DOCS
- 11:30BUILD THE FOUNDATION
- 14:47PRIORITIZE IN BLOCKS
- 17:46MAKE CHANGE EASY
- 20:11EMBRACE FLEXIBILITY
- 22:28END WITH REFLECTION
- 25:40PLAN YOUR MIGRATION
related talks
40mFrom resistance to adoption: navigating the challenges of docs-like-code
37mTaking a step back: Analysing your documentation
30mWhy most technology migrations fail (and what we've learned along the way)
40mDocumentation Communities: Sound Strategy or Documentarian's Gambit?
35mThe right tool for the job
23mDocumentation in the Age of AI: Why Docs Are a Product
29mMove Fast and Document Things: Writing internal docs at fast-moving organizations
40mDocs Tools for OSS Maintainers