Legacy content strategy
Legacy content strategy
Embedded Files
The challenge: Building a single source of truth
The challenge: Building a single source of truth
An enterprise platform was entering a new phase of its product line. They needed a scalable documentation system to replace an outdated, fragmented setup. Critical information was spread across multiple disconnected, conflicting formats, including in-product Help, reference guides, and white papers, making it difficult for users to find what they needed.
I was brought in to design a content strategy, establish a unified source of truth, and lead the process improvements necessary to support a growing writing team and product.
My strategy
My strategy
Researched user needs
Researched user needs
To understand how users engaged with the existing documentation, I investigated what they used, what they avoided, and what they actually needed.
Audited legacy content and team workflows.
Interviewed users to identify content needs and pain points.
Built a foundation
Built a foundation
Before writing began, I established the structural foundation required to ensure the new content was consistent, scalable, and easy to manage.
Selected and implemented tools for authoring and version control.
Designed a new information architecture and content structure
Developed templates, content standards, and processes to keep the formatting unified.
Rewrite
Rewrite
Organized and led a team to rewrite all legacy materials into a single, unified source of truth.
Established subject-matter experts by assigning each writer a focused product area.
Provided editorial oversight to maintain consistent style and information architecture.
Built cross-functional relationships with product owners to ensure strong content advocates.
Impact & takeaways
Impact & takeaways
Built a centralized knowledge base by transforming 25 separate Word manuals and a legacy help site into a single, searchable center.
Tripled team productivity by implementing a docs-as-code workflow that integrated help authoring tools with source control to allow multi-writer editing.
Ensured users finally knew where to go by replacing conflicting legacy formats with clear, reliable, and easy-to-navigate paths.
Gave the team a unified, clear voice that users trusted as a single source of truth.
Page updated
Google Sites
Report abuse