Investing in your Single-Source Nightmare
I recently read a terrific blog post by HBS Professor Rosabeth Moss Kanter entitled “To Master Change, First Dread It.” In it, she argues:
“A counter-intuitive tip for mastering change is to start by wallowing in the feelings of dread it arouses. The sheer nail-biting horror of it all. Get in touch with every negative aspect, all the things that could go wrong. Then figure out a way to get that negative force on your side. In short, Dream your worst nightmare and invest in it.”
Nowhere in the learning industry today are stakeholders facing greater change than in the move towards single-source learning. The dream is grand one: content reusability, multi-modal delivery and real-time customization – all from a single source of enterprise content to meet the requirements of learners worldwide.
But what we often tend to overlook when launching these projects is that single-source is a paradigm shift for almost everyone involved, affecting directly and indirectly all aspects of learning production. Content authors, subject matter experts, instructional designers, management, and various stakeholders will all witness major changes one way or another. If we don’t invest in our stakeholder’s nightmare, we breed fear, the kind of fear that can bring any single-source initiative to its knees.
I recently had the opportunity to chat with some project leaders across industries that are in various stages of their single-source learning initiatives: I was interested in the change management issues they faced and what steps they took to effectively manage and overcome these potential obstacles. While you can read the entire conversation here, I’ve condensed this into sort of a job aid for single-source change management.
The Top Ten List for Investing in Your Single-Source Nightmare:
- Clearly set expectations that things are going to change: While the richness of the content will not change, its format, wording and structure will. Therefore, it’s crucial to communicate what changes to expect and the benefits of doing things in this new fashion.
- Educate your stakeholders: Each stakeholder needs to understand how these changes will affect them directly so they can effectively plan for addressing and controlling that change.
- Set aside pre-conceptions: Single-source is an evolutionary step for content development but will not be effective unless a shift in mindset takes place up-front. So be open-minded to the process.
- Invest more early on: Focus initial resources on planning content strategy, content design and content management practices within a single-source environment so that changes do not have an unexpected and negative impact.
- Give your content design breathing room: Designers need to go through transient stage when learning how to separate content from presentation, so provide the extra time they require up-front.
- Plan for content reuse: For content design, don’t think solely in terms of sentences and paragraphs but also in terms of “once it is written, how I am going to use for different outputs?”
- Identify shared content: Separate audience-specific content from content that can be shared throughout the enterprise, then make shared content context-neutral.
- Make content searchable: Speed to market will depend on the ability to quickly find topics for updates, course assembly and rendering to different outputs.
- Start with a high impact project: Make sure project provides many opportunities for content reuse and touches many deliverables so everyone can see the value.
- Market the advantages: For those people that will not experience the changes directly, make sure you market the benefits gained to them.
Are there any other best practices that can be added to the list?



Dawn Poulos is the primary author of this blog. She is Xyleme's VP of Marketing, writes a lot about XML, learns a tremendous amount from the training community and hopes she’s adding some insight.
Thanks for the useful information Eric. The folks that I spoke with I think hit nicely on your first two principals. What they didn’t touch too much on was the guide you reference in your third principal. Perhaps because these folks were the guides themselves, or maybe the role of guide was spread among multiple participants, or perhaps (but I doubt) there was no official guide in these projects. In any case, this is a very useful framework that I’m happy to pass along.
change management model…
Have you read my change management model blog post? Usually applying those steps towards change are useful in any situation….