The Problem
For a smaller set of Cisco phone models, generic help could tell users about features that did not exist on the device they were holding. The models shared content, but the experience had to reflect the capabilities of each phone.
Why It Was Hard
Copying the help for every model would create drift. Publishing one undifferentiated help system would be easier to maintain but less trustworthy for users. The system needed reuse and specificity at the same time.
What I Figured Out
Feature availability was metadata. If the publishing system knew which features a model supported, it could assemble the appropriate topics and navigation without requiring a separate source copy for every device.
What I Changed
The content system used feature metadata to drive model-appropriate topics, related links, lists, and navigation. Shared explanations remained shared, while the delivered help reflected the features available on each phone.
What Changed as a Result
Users received help that matched their phone and configuration. Writers retained reusable source without exposing users to irrelevant features or maintaining a complete independent help set for every model.
Evidence and Technical Detail
Structured FrameMaker, feature metadata, reusable source, variables, conditional content, and generated topics, links, lists, and navigation supported the model-specific experience.