LavaCon 2024 delivered actionable insights, emphasizing that your business case for content operations requires strong alignment with business goals. Successful content modernization hinges on executive support, effective change management, and a wary eye on AI.
Whether you’re surviving a content operations project or a journey through treacherous caverns, it’s crucial to plan your way out before you begin. In episode 176 of the Content Strategy Experts podcast, Alan Pringle and Christine Cuellar unpack the parallels between navigating horror-filled caves and building a content ops exit strategy.
Alan Pringle: When you’re choosing tools, if you end up something that is super proprietary, has its own file formats, and so on, that means it’s probably gonna be harder to extract your content from that system. A good example of this is those of you with Samsung Android phones. You have got this proprietary layer where it may even insert things into your source code that is very particular to that product line. So look at how proprietary your tool or toolchain is and how hard it’s going to be to export. That should be an early question you ask during even the RFP process. How do people get out of your system? I realize that sounds absolutely bat-you-know-what to be telling people to be thinking about something like that when you’re just getting rolling–
Christine Cuellar: Appropriate for a cave analogy, right?
Alan Pringle: Yes, true. But you should be, you absolutely should be.
Are you looking for real-world examples of enterprise content operations in action? Join Sarah O’Keefe and special guest Adam Newton, Senior Director of Globalization, Product Documentation, & Business Process Automation at NetApp for episode 175 of The Content Strategy Experts podcast. Hear insights from NetApp’s journey to enterprise-level publishing, lessons learned from leading-edge GenAI tool development, and more.
We have writers in our authoring environment who are not writers by nature or bias. They’re subject matter experts. And they’re in our system and generating content. That was about joining us in our environment, reap the benefits of multi-language output, reap the benefits of fast updates, reap the benefits of being able to deliver a web-like experience as opposed to a PDF. But what I think we’ve found now is that this is a data project. This generative AI assistant has changed my thinking about what my team does. Yes, on one level, we have a team of writers devoted to producing the docs. But in another way, you can look at it and say, well, we’re a data engine.
— Adam Newton
Translation troubles? This podcast is for you! In episode 173 of The Content Strategy Experts podcast, Bill Swallow and special guest Mike McDermott, Director of Language Services at MadTranslations, share strategies for overcoming common content localization challenges and unlocking new market opportunities.
Mike McDermott: It gets very cumbersome to continually do these manual steps to get to a translation update. Once the authoring is done, ideally you just send it right through translation and the process starts.
Bill Swallow: So from an agile point of view, I am assuming that you’re talking about not necessarily translating an entire publication from page one to page 300, but you’re saying as soon as a particular chunk of content is done and “blessed,” let’s say, by reviewers in the native language, then it can immediately go off to translation even if other portions are still in progress.
Mike McDermott: Exactly. That’s what working in this semantic content and these types of environments will do for a content creator. You don’t need to wait for the final piece of content to be finalized to get things into translation.
It’s hard to believe that the DITA standard needs additional tags. I tried counting them, but gave up at 150, when I had only reached the letter G. (Be my guest: https://www.oxygenxml.com/dita/1.3/specs/langRef/quick-reference/all-elements-a-to-z.html)
When organizations replatform from one content management system to another, unchecked technical debt can weigh down the new system. In contrast, strategic replatforming can be a tool for reducing technical debt. In episode 172 of The Content Strategy Experts podcast, Sarah O’Keefe and Bill Swallow share how to set your replatforming project up for success.
Here’s the real question I think you have to ask before replatforming—is the platform actually the problem? Is it legitimately broken? As Bill said, has it evolved away from the business requirements to a point where it no longer meet your needs? Or there are some other questions to ask, such as, what are your processes around that platform? Do you have weird, annoying, and inefficient processes?
— Sarah O’Keefe
Technical debt is “the implied cost of future reworking required when choosing an easy but limited solution instead of a better approach that could take more time,” Wikipedia, “Technical debt.”. Like financial debt, technical debt isn’t always a bad thing. You can use a loan to buy a house right away (at least in the U.S.) and then pay off the debt over time while living in the house. Technical debt allows you to create something quickly instead of doing it exactly right and taking much longer.
Too much technical debt, though, will hamstring your work. The trick is to find the Goldilocks solution.
In this episode of our Let’s Talk ContentOps! webinar series, Scriptorium principals Sarah O’Keefe (CEO), Alan Pringle (COO), and Bill Swallow (Director of Operations) provide practical insights on the future of content operations. They’ll deliver sunny predictions, warn of upcoming storms, and equip you to weather unprecedented fronts in the content industry.
In the wide world of content, we’ve got a lot of terms. Some may be new to you, and others have contested definitions, which makes clear communication—typically our bread and butter—a challenge. If you’re exploring efficiency in your organization’s content processes, this post clarifies the foundational concepts of an enterprise content strategy.
In this episode of our Let’s talk ContentOps! webinar series, Pam Noreault, Principal Information Architect at Ellucian, and Sarah O’Keefe, CEO of Scriptorium, discuss the dynamics of authoring teams whose tools are controlled by IT or third-party SaaS ecosystems.
