At the 2024 ConVEx conference, Scriptorium CEO Sarah O’Keefe was part of a panel of content experts including Dawn Stevens, Val Swisher, and Rob Hanna. The panelists discussed the pros, cons, and cautions of using AI in content creation.
In episode 164 of The Content Strategy Experts Podcast, Alan Pringle and special guest Chris Hill of DCL talk about where you can find redundancy in your learning content, what causes it, and how a single source reuse strategy can eliminate duplication.
You really start to run into trouble when you need to make version two, and you discover a problem with version one. If I’m making some marketing materials, maybe I need to use some information from the engineering team or from the manuals for whatever product I’m marketing. I might just copy that information over and put it into my marketing materials. Then, when we go to produce our training for that particular product, we might say, “Okay, I need that stuff. I’m gonna copy that from wherever I can find it,” which might be from marketing or engineering depending on where I look and who I know better or which repository is easier for me to get to. The problem here is that if anybody has made any edits along the way, they have to ensure that those edits are propagated through all these departments. And that doesn’t always happen.
— Chris Hill
In episode 162 of The Content Strategy Experts Podcast, Bill Swallow and Christine Cuellar discuss the benefits of single sourcing as part of your content strategy through the example of two things they love: coffee and beer.
“We know companies that have moved away from a do-it-yourself approach because they had maybe two or three different people putting in half to almost full-time work on the publishing system and not on other facets of the company’s core business or the writing. They were simply there to keep everything working. It just blows my mind that on a scale where you have hundreds of writers contributing content, you are saying, Okay, you three people are going to be solely responsible for keeping this thing up and running so that they can produce their content, rather than having a system that’s designed to keep itself up and running.”
— Bill Swallow
The product content lifecycle should result in information that is traceable–each data point in a document should point back to a database or another information source from which the data point was derived.
But unfortunately, we are not there yet.
