{"id":1936,"date":"2026-05-25T16:51:53","date_gmt":"2026-05-25T20:51:53","guid":{"rendered":"https:\/\/www.precisioncontent.com\/blog\/?p=1936"},"modified":"2026-05-25T17:50:55","modified_gmt":"2026-05-25T21:50:55","slug":"its-the-content-why-ai-readiness-starts-with-better-documentation","status":"publish","type":"post","link":"https:\/\/www.precisioncontent.com\/blog\/its-the-content-why-ai-readiness-starts-with-better-documentation\/","title":{"rendered":"It\u2019s the Content: Why AI Readiness Starts with Better Documentation"},"content":{"rendered":"
\n

<\/h1>\n

\"\"<\/h1>\n

 <\/p>\n

AI does not fix content problems. It exposes them.<\/h2>\n

AI is changing the conversation about technical documentation, but not in the way many organizations expected. In the webinar \u201cIt\u2019s the Content,#%#$!<\/strong><\/a>\u201d, Rob Hanna<\/a> joined Scott Abel<\/a> and Patrick Bosek<\/a> for a practical discussion about what really determines whether AI can deliver accurate, trustworthy answers from enterprise content.<\/p>\n

The message was clear: AI readiness starts with content readiness.<\/strong><\/em><\/p>\n

Organizations are investing heavily in AI tools, copilots, chatbots, and retrieval-augmented generation systems. But if the underlying content is inconsistent, ambiguous, poorly structured, or weakly governed, the AI experience will reflect those weaknesses. It may still generate an answer. The risk is that the answer will be plausible, incomplete, or wrong.<\/p>\n

\"AI-generated
AI-generated image representing Scott Abel, Patrick Bosek, and Rob Hanna in conversation about AI readiness, structured content, and trustworthy documentation.<\/figcaption><\/figure>\n

For Rob Hanna, the first warning sign is consistency. When asked what makes technical documentation likely to produce unreliable AI answers, he answered plainly:<\/p>\n

\n

\u201cConsistency is number one.\u201d<\/strong><\/p>\n

Rob Hanna<\/p>\n<\/blockquote>\n

That consistency is not limited to terminology. It includes how teams write, structure, label, classify, and manage information across products, versions, teams, and time.<\/p>\n

Content needs clear intent<\/h2>\n

A major theme of the webinar was the importance of writing for intent. Rob connected this directly to information typing. Concepts, tasks, references, processes, and principles each serve a different purpose. They also require different structures, labels, and writing patterns.<\/p>\n

\"Visual
The five information types help content teams separate intent, reduce ambiguity, and create patterns that are easier for both people and AI systems to understand.<\/figcaption><\/figure>\n

When content teams mix those intents without discipline, they create confusion for readers and machines. A topic that blends conceptual explanation, procedural steps, reference data, and business rules may still be understandable to an experienced human. But AI systems do not reliably infer missing context the way people do.<\/p>\n

Rob explained that the purpose of information typing is to reduce cognitive load and improve precision. When organizations do not separate information by intent or purpose, content becomes harder to navigate and understand. With machine readers, he warned, some of that content may become \u201cimpenetrable.\u201d<\/p>\n

Structure is more than XML<\/h2>\n

One of the strongest moments in the discussion came when Rob clarified a common misconception. Structured content is not created simply by moving documentation into DITA, XML, or a CCMS. True structure comes from repeatable patterns that communicate meaning:<\/p>\n

\n

\u201cStructure is not XML. Structure is repeated patterns and language that convey meaning.\u201d<\/strong><\/p>\n

Rob Hanna<\/p>\n<\/blockquote>\n

His point was that structured content is not created simply by moving documentation into DITA, XML, or a CCMS. True structure comes from repeated patterns of language and organization that convey meaning. XML can make those patterns easier to enforce, but it cannot replace disciplined content design.<\/p>\n

Patrick Bosek reinforced the point by connecting structure to business outcomes. As he explained, the goal is to \u201cenforce the patterns that work for your business outcomes\u201d and create the consistency needed to do something valuable with the content later.<\/p>\n

That distinction matters. A document can be technically valid and still be functionally weak. If everything is tagged as a concept because that is easier during migration, the structure no longer tells the truth about the content. The system may validate the markup, but the content still fails to communicate intent.<\/p>\n

Patrick Bosek expanded the point by connecting structure to metadata. His definition was refreshingly clear:<\/p>\n

\n

\u201cIn my view, metadata is any information that isn\u2019t the actual text.\u201d<\/strong><\/p>\n

Patrick Bosek<\/p>\n<\/blockquote>\n

AI is another delivery channel<\/h2>\n

The webinar also reframed AI as another content delivery channel. Organizations would never assume that raw DITA should be delivered directly as a finished PDF, website, or in-app experience. Each channel requires transformation.<\/p>\n

AI is no different.<\/p>\n

Rob argued that teams need to think carefully about how they feed content to AI systems. The same structures that work in XML may need to be transformed into something more digestible for AI, with metadata and inferred semantic meaning made explicit. Patrick extended that idea by pointing out that AI should be treated like any other channel that needs optimized input to produce the best output.<\/p>\n

This is a critical shift. AI readiness is not about dumping a corpus into a model and hoping it finds the right answer. It is about engineering the content, metadata, classification, and context so the system can retrieve and use the right information.<\/p>\n

Classification improves the \u201cR\u201d in RAG<\/h2>\n

Patrick made one of the clearest business cases for content classification when he connected it directly to retrieval-augmented generation.<\/p>\n

\n

\u201cThe reason you categorize and type things is because of the R in RAG. It\u2019s the retrieval piece.\u201d<\/strong><\/p>\n

Patrick Bosek<\/p>\n<\/blockquote>\n

He explained that organizations cannot retrieve enterprise content effectively at scale if they rely only on pure vector search or keyword search. They need classification to improve both vector results and traditional search results.<\/p>\n

His summary was simple and powerful:<\/p>\n

\n

“We improve the ‘R.’ That\u2019s why we classify, so you can have better retrieval.\u201d<\/strong><\/p>\n

Patrick Bosek<\/p>\n<\/blockquote>\n

This reframes classification as a business-critical AI control, not a documentation preference. Better classification improves retrieval precision. Better retrieval reduces ambiguity. Reduced ambiguity improves the odds that AI systems generate accurate, trustworthy answers.<\/p>\n

Prompt engineering cannot compensate for weak content<\/h2>\n

The group also challenged the belief that better prompts can overcome poor source material.<\/p>\n

Prompting has value, especially for research, planning, and authoring support. But for content delivery, Rob emphasized that the content itself must contain the right information. It must also be disambiguated by product, version, locale, release, audience, and context.<\/p>\n

If the correct answer is missing, buried, ambiguous, or contradicted elsewhere in the corpus, a prompt cannot reliably solve the problem. The system needs trusted content and the right surrounding context.<\/p>\n

That is why the conversation is shifting from prompt engineering to context engineering. The future of AI-enabled documentation depends on how well organizations package the content and context that AI systems need.<\/p>\n

Content standards are a governance shield<\/h2>\n

Another practical takeaway was the role of content standards. Rob argued that organizations often have style guides, but not comprehensive content standards. A style guide may tell writers how to punctuate or title something. A content standard defines how content should be planned, structured, typed, labeled, reviewed, and governed.<\/p>\n

Rob described content standards as a \u201cshield\u201d when documentation teams face pushback from subject matter experts or product owners. Instead of treating classification and structure as personal preferences, teams can point to approved standards that define how content works across the organization.<\/p>\n

That governance layer becomes even more important in AI-enabled environments. Standards help control risk, improve consistency, and reduce the likelihood that AI systems will misinterpret ambiguous content.<\/p>\n

AI does not replace a CCMS<\/h2>\n

The webinar also addressed a question many organizations are asking: can AI help avoid the cost of a CCMS?<\/p>\n

Rob\u2019s answer focused on the content. Even without a CCMS, teams can start improving writing quality, chunking, titling, information typing, and standards now. As he put it:<\/p>\n

\n

\u201cContent first, technology second.\u201d<\/strong><\/p>\n

Rob Hanna<\/p>\n<\/blockquote>\n

Patrick took the economic angle. Using AI to compensate for unstructured content may look cheaper at first, but the costs show up quickly in token usage, validation, rework, support, and risk. A CCMS solves many deterministic content supply-chain problems. AI should be part of the toolchain, but it should not be used to replace systems that already handle governance, reuse, workflow, and publishing reliably.<\/p>\n

Patrick\u2019s warning was direct:<\/p>\n

\n

\u201cAI feels less expensive for a few months, but you find pretty quickly that it\u2019s not.\u201d<\/strong><\/p>\n

Patrick Bosek<\/p>\n<\/blockquote>\n

The larger point is that unstructured content shifts cost downstream. Teams pay later through manual validation, model tuning, rework, support escalations, and reduced trust. Structured content shifts cost upstream, where it can be governed and controlled.<\/p>\n

The Economics of AI: Bad Content Increases the Cost of Every Answer<\/h2>\n

Patrick Bosek offered one of the webinar\u2019s clearest executive arguments: using AI to compensate for unstructured content may look cheaper at first, but the economics change quickly.<\/p>\n

\n

\u201cAI token usage is a real thing. Every organization is starting to realize that it hits the bottom line in a very, very real way.\u201d<\/span><\/strong><\/p>\n

Patrick Bosek<\/p>\n<\/blockquote>\n

That matters because every unnecessary piece of content added to an AI context window increases cost. When organizations \u201cthrow everything into AI\u201d and hope the system can figure it out, they make the answer more expensive and often less accurate. Patrick\u2019s point was that better content structure allows organizations to give AI only the minimum context required to produce the right answer.<\/p>\n

\n

\u201cHaving a consistently smaller context window is a consistently less expensive AI solution.\u201d<\/strong><\/p>\n

Patrick Bosek<\/p>\n<\/blockquote>\n

This is the stronger takeaway for the blog. It is clear, practical, and directly tied to the value of structured content. Better content reduces the amount of material AI has to process. That improves accuracy, reduces ambiguity, and helps organizations get better return on every token they spend.<\/p>\n

The bottom line: content is AI infrastructure<\/h2>\n

Perhaps the most important message from the webinar is that content must be treated as infrastructure. Patrick noted that AI is often a content engineering problem, because what differentiates one specialized AI experience from another is frequently the context provided to it. Rob put it even more directly:<\/p>\n

\n

\u201cContent is your AI infrastructure.\u201d<\/strong><\/p>\n

Rob Hanna<\/p>\n<\/blockquote>\n

That idea should change how organizations think about documentation. Content is not just a publishing asset. It is not just support material. It is not a static repository of product facts.<\/p>\n

In an AI-enabled enterprise, content is the ground truth that systems rely on to answer questions, guide users, support employees, reduce risk, and deliver trusted experiences.<\/p>\n

The organizations that invest in consistent, structured, classified, governed, and trustworthy content will be better prepared for every AI channel that comes next. Those that ignore content quality will spend more time correcting AI output, managing risk, and explaining why the answers cannot be trusted.<\/p>\n

AI readiness starts with content readiness. And content readiness starts with the discipline to make content clear, consistent, structured, and trustworthy before the machine ever sees it.<\/p>\n

Thank You to Scott and Patrick<\/h2>\n
\n

A sincere thank you to Scott Abel and Patrick Bosek for a thoughtful and practical discussion about what AI readiness really requires.<\/p>\n

\"Webinar
Scott Abel, Rob Hanna, and Patrick Bosek during the \u201cIt\u2019s the Content,#%#$!\u201d webinar discussion.<\/figcaption><\/figure>\n

The conversation helped move the topic beyond tools and hype, and toward the deeper work of making content clear, consistent, structured, classified, governed, and trustworthy.<\/p>\n<\/div>\n

Watch the Full Webinar Recording<\/h2>\n
\"Title
Title slide from the \u201cIt\u2019s the Content,#%#$!\u201d webinar.<\/figcaption><\/figure>\n

The full conversation is worth watching for any content, documentation, or knowledge management leader thinking about AI readiness. Rob Hanna, Scott Abel, and Patrick Bosek go beyond the hype and get practical about what organizations need to do now to make their content more reliable, retrievable, and useful for AI-enabled experiences.<\/p>\n

The webinar explores why consistency, structure, metadata, classification, and governance are no longer just documentation concerns. They are the foundation for trusted AI outcomes.<\/p>\n

You can watch the full recording here:<\/p>\n

\n

Watch the webinar and hear the full discussion.<\/p>\n

Watch the Full Webinar
\n<\/a><\/p>\n<\/div>\n

Website: https:\/\/www.brighttalk.com\/webcast\/9273\/665954<\/a><\/p>\n

Note: A free BrightTALK account is required to access the recording.<\/p>\n<\/article>\n","protected":false},"excerpt":{"rendered":"

  AI does not fix content problems. It exposes them. AI is changing the conversation about technical documentation, but not in the way many organizations expected. In the webinar \u201cIt\u2019s the Content,#%#$!\u201d, Rob Hanna joined Scott Abel and Patrick Bosek for a practical discussion about what really determines whether AI can deliver accurate, trustworthy answers […]<\/p>\n","protected":false},"author":1,"featured_media":1945,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false},"categories":[35,12,2,5,7,3],"tags":[],"_links":{"self":[{"href":"https:\/\/www.precisioncontent.com\/blog\/wp-json\/wp\/v2\/posts\/1936"}],"collection":[{"href":"https:\/\/www.precisioncontent.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.precisioncontent.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.precisioncontent.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.precisioncontent.com\/blog\/wp-json\/wp\/v2\/comments?post=1936"}],"version-history":[{"count":29,"href":"https:\/\/www.precisioncontent.com\/blog\/wp-json\/wp\/v2\/posts\/1936\/revisions"}],"predecessor-version":[{"id":1975,"href":"https:\/\/www.precisioncontent.com\/blog\/wp-json\/wp\/v2\/posts\/1936\/revisions\/1975"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.precisioncontent.com\/blog\/wp-json\/wp\/v2\/media\/1945"}],"wp:attachment":[{"href":"https:\/\/www.precisioncontent.com\/blog\/wp-json\/wp\/v2\/media?parent=1936"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.precisioncontent.com\/blog\/wp-json\/wp\/v2\/categories?post=1936"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.precisioncontent.com\/blog\/wp-json\/wp\/v2\/tags?post=1936"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}