Dr. Amanda Patterson, Comtech Services
August 15, 2025
Content reuse is a fundamental principle of efficient, scalable, and sustainable technical communication. In a recent CIDM Roundtable, members discussed a persistent challenge: how to measure reuse effectively. The conversation raised a variety of perspectives, from content management workarounds to automated knowledge graphs. What united members was a shared urgency to quantify reuse and prove return on investment in structured authoring environments.
The Metrics Maze: What to Measure and How
While reuse promises improved efficiency, quality, and cost savings, members noted, most teams still struggle to track it effectively. Several members discussed different measurement strategies—what metrics matter and how to derive them from disparate tools. One member shared that their team began tracking content reuse by analyzing legacy content, which revealed that more than 50% of it was being reused. They also implemented a system using issue tracking tools with custom data fields for documenting reuse requests.
Another member emphasized a broader view: reuse must be tracked not only in source documentation but also in translation workflows and across delivery channels. “It’s not just about what’s reused in English,” they noted. “It’s about how that reuse reduces localization effort, accelerates updates, and improves consistency across the board.”
One member described using manually labeled dependencies in a content management system to support planning and collaboration. While helpful, this approach still relies heavily on individual tagging, which can be inconsistent and difficult to scale.
From Manual to Automated: Knowledge Graphs as a Game-Changer
Perhaps the most forward-looking moment came when a member introduced an automated approach using knowledge graphs. Inspired by earlier enterprise work, their method uses SPARQL queries to extract structured reuse metrics from content repositories.
Rather than manually identifying reused content, the system builds a knowledge graph that maps reuse relationships across the documentation set. “You’re not just building a map,” they said. “You’re creating a living ecosystem that helps you see where your reuse is working—and where it’s not.”
They shared a public link to a SPARQL query guide, enabling members to explore this approach on their own. Several members expressed interest, especially those frustrated by the limitations of their current content systems.
The Tool Conundrum: What Works and What Doesn’t
While most members agreed that structured content systems like DITA and tools like Oxygen XML Author enable reuse, there was significant discussion about tool limitations—especially for distributed teams or web-based authoring environments.
One member raised concerns about the web version of their authoring tool, noting that it lacked robust support for reusable resource objects and metadata. Another confirmed similar frustrations, stating that “what works well in the desktop version doesn’t always translate to the portal.”
Others described their organization’s migration from a wiki-based platform to structured XML, using Git-based repositories. They’ve begun building a reuse strategy but are still defining metrics and identifying reusable modules. For many, the takeaway was clear: no single tool provides an end-to-end reuse measurement solution. Instead, success depends on combining CMS capabilities, manual strategies, and third-party tools.
Setting Thresholds: How Similar is “Reusable”?
The group also debated how similar content must be to qualify as reusable. One suggestion was to use a 50% similarity threshold as a starting point, while others recommended a more conservative 80% threshold. These differences highlight an important nuance in measuring reuse: not all similarity is created equal.
Members emphasized that while thresholds help, meaningful reuse often requires structural changes—such as implementing content references or using conditional content. One member, reflecting on a recent migration from unstructured tools to XML, noted that while initial conversions were straightforward, planning reuse across product lines required far more strategic oversight.
Another shared that their team uses a CMS that visually manages reuse, achieving 70–80% reuse across more than 1,200 product guides. Their system insulates writers from having to manage reuse IDs manually, making reuse seamless on the front end.
Governance, Visibility, and Writer Experience
Despite the focus on tools and metrics, members repeatedly returned to a human-centered theme: how reuse impacts writers’ daily work. One member noted that their team struggles because writers can’t see what a content reference contains in the current system—an issue others flagged as a serious usability barrier. “Most systems should let you see reused content during authoring,” one member said. “If not, it might be time to look for something else.”
Another member offered an alternative governance model where authors are empowered to manage their own reuse libraries within their maps. While some expressed concern about fragmentation, others acknowledged the model could work with the right safeguards. The conversation underscored that no reuse strategy—no matter how sophisticated—is complete without thoughtful governance and clear authoring guidelines.
Looking Ahead: AI, Reuse, and the Future
Members also discussed how AI might support reuse measurement and optimization in the future. Several members expressed cautious optimism about AI’s potential to identify patterns in large documentation sets and recommended reusable components.
Still, the consensus was clear: without clean content structures and consistent governance, AI alone won’t solve the reuse challenge. “Garbage in, garbage out,” as one member quipped.
Key Takeaways
Start Where You Are: Whether through Jira, dependency reports, or manual labels, begin tracking reuse with the tools you have.- Automate When Possible: Knowledge graphs and SPARQL queries offer powerful ways to extract reuse insights from structured content.
- Set Thoughtful Thresholds: Defining what counts as “reusable” depends on your business context and content maturity.
- Mind the Authoring Experience: Tools must support—not hinder—writers’ ability to see and manage reused content.
- Governance is Non-Negotiable: Successful reuse strategies depend on clear ownership, content lifecycle management, and cross-team coordination.
As content teams continue to scale their documentation efforts across products, languages, and platforms, measuring reuse will remain both a strategic imperative and a technical challenge. While tools and technologies matter, the foundation of effective reuse still lies in thoughtful planning, cross-functional collaboration, and a relentless focus on quality.