AI and accountability
Generative AI + lip service to guard rails = instant free content.
The brutal reality is that content is a commodity.
Generative AI + lip service to guard rails = instant free content.
The brutal reality is that content is a commodity.
We’re ready to bring you more industry-leading content ops insights in 2026! Check out these upcoming events.
Thanks for joining us this year! Through webinars, podcasts, LearningDITA training, and more, we’re grateful to be part of your content ops journey.
Like every conference in the past few years, AI was a major emphasis at tcworld in mid-November. With around 4,000 attendees and a huge trade show, tcworld is bigger than any of the North American technical documentation events. The program includes sessions in both English and German, and attendees come from all over the world.
Ready to see the business advantages of structured content in action? These case studies show how moving to structured content can reduce time-to-market, enable accelerated global content delivery, and deliver personalized outputs that improve user experiences.
Working in the AEM Guides CCMS? Unlock its full potential with self-paced, online AEM Guides training.
Will cheap content cost your organization more in the long run? In this webinar, host Sarah O’Keefe and guest Dawn Stevens share how poor workflows, inaccurate source data, and the commoditization race can undermine both product quality and brand trust. Sarah and Dawn also discuss why strategic staffing and mature content ops create the foundation your AI initiatives need to deliver reliable content at scale.
Sarah O’Keefe: I write content that’s great for today. Tomorrow, a new development occurs, and my content is now wrong. We’re down the road of “entropy always wins.” We’re heading towards chaos, and if we don’t care for the content, it’ll fall apart. So what does it look like to have a well-functioning organization with an appropriate balance of automation, AI, and staffing?
Dawn Stevens: I think that goes back to the age-old question of, “What are the skills that we really think are valuable?” We have to see technical documentation as part of the product, not just supporting the product. That means that we, as writers, are involved in all of the design. As we design the documentation, we’re helping design the UX.
What happens when AI accelerates faster than your content can keep up? In this podcast, host Sarah O’Keefe and guest Michael Iantosca break down the current state of AI in content operations and what it means for documentation teams and executives. Together, they offer a forward-thinking look at how professionals can respond, adapt, and lead in a rapidly shifting landscape.
Sarah O’Keefe: How do you talk to executives about this? How do you find that balance between the promise of what these new tool sets can do for us, what automation looks like, and the risk that is introduced by the limitations of the technology? What’s the roadmap for somebody that’s trying to navigate this with people that are all-in on just getting the AI to do it?
Michael Iantosca: We need to remind them that the current state of AI still carries with it a probabilistic nature. And no matter what we do, unless we add more deterministic structural methods to guardrail it, things are going to be wrong even when all the input is right.
For nine years, the Scriptorium site LearningDITA.com served more than 16,000 students seeking knowledge about the Darwin Information Typing Architecture (DITA) XML standard. A critical system failure forced Scriptorium to rebuild the site, so we focused our consulting expertise on ourselves to address a replatforming challenge for structured learning content.
Your organization’s content debt costs more than you think. In this podcast, host Sarah O’Keefe and guest Dipo Ajose-Coker unpack the five stages of content debt from denial to action. Sarah and Dipo share how to navigate each stage to position your content—and your AI—for accuracy, scalability, and global growth.
The blame stage: “It’s the tools. It’s the process. It’s the people.” Technical writers hear, “We’re going to put you into this department, and we’ll get this person to manage you with this new agile process,” or, “We’ll make you do things this way.” The finger-pointing begins. Tech teams blame the authors. Authors blame the CMS. Leadership questions the ROI of the entire content operations team. This is often where organizations say, “We’ve got to start making a change.” They’re either going to double down and continue building content debt, or they start looking for a scalable solution.
— Dipo Ajose-Coker