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, hereafter called “content 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, content 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. Content debt allows you to create something quickly instead of doing it exactly right and taking much longer.
Too much content 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 episode 169 of The Content Strategy Experts podcast, Sarah O’Keefe and special guest Sebastian Göttel of Quanos engage in a captivating conversation on generative AI and its impact on technical documentation. To bring these concepts to life, this English version of the podcast was created with the support of AI transcription and translation tools!
Sarah O’Keefe: So what does AI have to do with poems?
Sebastian Göttel: You often have the impression that AI creates knowledge; that is, creates information out of nothing. And the question is, is that really the case? I think it is quite normal for German scholars to not only look at the text at hand, but also to read between the lines and allow the cultural subtext to flow. From the perspective of scholars of German literature, generative AI actually only interprets or reconstructs information that already exists. Maybe it’s hidden, only implicitly hinted at. But this then becomes visible through the AI.
Folge 169 ist auf Englisch und Deutsch verfügbar. Da unser Gast Sebastian Göttel sich im deutschsprachigen Raum mit KI beschäftigt, kam die Idee, diesen Podcast auf Deutsch zu erstellen. Die englische Version wurde dann mit KI-Unterstützung zusammengebastelt.
Sarah O’Keefe: Was hat die generative KI mit Gedichtinterpretationen zu tun?
Sebastian Göttel: Ja, nun, also oft hat man da ja den Eindruck, dass KI das Wissen schöpft, also Informationen aus dem Nichts erschafft. Und da ist die Frage, ist das denn wirklich so? Denn für die Germanisten ist es, glaube ich, schon eher normal, nicht nur den vorliegenden Text anzuschauen, sondern auch zwischen den Zeilen zu lesen, den kulturellen Subtext einfließen zu lassen. Und aus dem Blickwinkel der Germanisten, interpretiert oder rekonstruiert generative KI eigentlich nur Informationen, die schon vorhanden ist. Möglicherweise ist die verborgen, nur implizit angedeutet. Aber die wird durch die KI dann sichtbar.
In episode 168 of The Content Strategy Experts podcast, Sarah O’Keefe and special guest Leslie Farinella, Chief Strategy Officer at Xyleme, discuss the challenges facing content operations for learning content, insights for navigating information silos, and recommendations for successful enterprise-wide collaboration.
Why do we still have these silos of content? Back to what you said, Sarah, if we’re thinking about the learner experience, the learner doesn’t distinguish between classroom, e-learning, looking something up, or going to technical documentation. They just know, “I gotta get my job done. I need to perform. I need to know what I’m doing.”
— Leslie Farinella
In episode 167 of The Content Strategy Experts Podcast, Sarah O’Keefe, Alan Pringle, and Bill Swallow discuss the difficulties organizations encounter when they try to create a unified content experience for their end users.
AP: Technical content, your tech content or product content, wants to convey knowledge so the user or reader can do whatever thing that they need to do. Learning content is about improving performance. And with your knowledge base content, it’s when, “I need to solve this very specific problem.” So those are the distinctions that I see among those three types.
SO: Okay, and from a customer point of view, what does this mean?
AP: Well, in reality, I don’t think the customers care. They want the information available, and they want it in the formats they want it in. And also, they want the right information so they can either get that thing done, improve their performance, or solve a specific problem.
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.
For your customers to effectively use your products and services, it’s critical that your enabling content is fully integrated across content types.
