Overview

A help system can contain accurate content and still fail users if information is difficult to locate. As documentation grows over time without a clear organizing strategy, users often encounter confusing navigation, overlapping topics, inconsistent titles, and search results that do not lead them quickly to answers.

This case study demonstrates how a structured reorganization of a help environment can improve findability, support self-service success, and create a cleaner foundation for long-term maintenance.

Client Situation

The organization maintained a large online help system supporting a complex software product. Over multiple releases, content had been added by different contributors and organized in ways that reflected internal product structure rather than user tasks or common support needs.

Although the library contained substantial information, users frequently struggled to locate the right topic efficiently.

The issue was not lack of content—it was discoverability.

Business Challenges

Several problems had emerged:

• Users could not predict where information would be located
• Similar content appeared in multiple sections
• Navigation labels were unclear or inconsistent
• Topic titles reflected internal terminology rather than user language
• Search results surfaced overlapping or weakly named topics
• Support teams continued answering questions already documented elsewhere

The organization needed a better user experience without starting over from scratch.

Documentation Risks

Without improvement, the help system faced ongoing costs:

• Increased support dependency
• Lower user confidence in self-service resources
• Slower task completion for end users
• Higher maintenance burden due to redundant content
• Greater complexity with each future release

As content volume grows, poor structure becomes more expensive over time.

Analysis

A review of the help environment showed that the primary issues were structural and navigational.

Common patterns included:

• Content grouped by internal departments rather than user goals
• Redundant topics covering similar questions
• Titles written from a product-team perspective
• Inconsistent relationships between task, concept, and reference topics
• Navigation paths that required too many clicks or assumptions

The strongest opportunity was to reorganize what already existed into a more intuitive model.

Strategy

I redesigned the information architecture around how users seek help rather than how the organization thinks about the product internally.

The strategy focused on four priorities:

1. Improve navigation clarity
2. Strengthen topic titles and labels
3. Reduce redundancy
4. Create cleaner relationships between content types

This approach improved findability while preserving valuable existing content where appropriate.

Solution Design

The proposed help system model included:

User-Centered Categories

Topics grouped by common goals, tasks, and decision points.

Clearer Navigation Labels

Section names written in plain, recognizable language.

Stronger Topic Titles

Titles aligned with likely user questions and search intent.

Reduced Overlap

Consolidation of duplicate or competing topics.

Better Content Relationships

Cleaner separation and linking between:

• Task topics
• Concept topics
• Reference topics

Scalable Structure

A model that could absorb future content growth without recreating the same problems.

Implementation Approach

A phased rollout would minimize disruption and allow measurable progress.

Phase 1: Audit

Review navigation, content overlap, titles, and high-friction areas.

Phase 2: Taxonomy Redesign

Define new categories, labels, and content groupings.

Phase 3: Priority Cleanup

Improve the highest-traffic or highest-frustration areas first.

Phase 4: Content Alignment

Update titles, links, and topic relationships.

Phase 5: Governance

Create standards to preserve findability over time.

Business Impact

A well-organized help system can create meaningful operational and user benefits:

• Faster access to answers
• Improved self-service success
• Reduced support burden
• Higher user confidence in documentation
• Easier maintenance for writers
• Cleaner onboarding for new contributors
• Stronger scalability for future releases

Key Takeaway

Many help systems do not need more content—they need better structure.

When users can predict where information lives and recognize it quickly, documentation becomes far more valuable without requiring a complete rewrite.

Let’s Connect

If users struggle to find answers in your current help system, I’d be glad to discuss how a reorganization strategy can improve usability and long-term maintainability.

View Services Contact Me