You’re starting your content migration project. You’ve lined up the financing, the tools, and the logistics. But have you planned for human factors: the emotional and physical toll? Over the course of 18 months, we migrated our docs from lightweight markup to structured content. We’ll talk about managing the team’s emotional health at each stage, how we handled cross-organizational stress-points, the things we did right, and the lessons we learned about team-building and wellbeing along the way.
Your migration journey is going to involve fear, frustration, skepticism, exhaustion, and maybe even dysentery. We learned a lot about humanity while migrating our Markdown-in-Github docs to DITA. We’ll share our experience, describe our lessons learned, and help you prepare for the emotional aspects of your own content migration projects. You’ll learn about what to expect and how to plan for the human factors involved.
- What’s the state of your team culture and values? Are they up for this?
- What happens when people who are good at their job are temporarily bad at it?
- Why is Engineering mad at us?
- What things can you do to lift the team up when everyone is stressed out and generally peeved?
- What if a key person quits? What if anyone quits?
- We succeeded! Why don’t we feel elated?