Lead
Build capability
We guide your people through the work, building capability that stays with your team.
Back to the business caseUpdate propagation ยท Implementation
Propagate the change beyond direct reuse
The workflow keeps one feature identity while changing its displayed name in the applicable release. Output checks establish whether the change reached users.
Follow the process- Business goal
- Increase efficiency
- Business metric
- Content cost
From approved rename to verified answers
Use an approved release record, version-aware term definitions, dependency records, and an expected output list. Preserve historical release scope.
The task in this example
Roll out the Demand planning name in release 26.4 everywhere customers will see it.
- Step 1
Confirm the rename
Product approves the name and effective release.
Product or customer dataThe release plan establishes Demand planning from 26.4; earlier versions remain separately scoped.
- Step 2
Update the term record
Change the preferred name and retain the alias.
TaxonomyA stable feature ID connects old and new wording without pretending the feature was removed.
- Step 3
Find dependent artifacts
Query beyond direct text references.
Ontology and knowledge graphInclude screenshots, translations, training, and assistant indexes with their owners.
- Step 4
Rebuild and review
Republish outputs and refresh indexes.
SystemPipelines expose build and index versions.
PeopleOwners update artifacts such as screenshots that cannot be repaired by a text rebuild.
- Step 5
Test the rollout
Ask questions using both names and inspect outputs.
Content teamMaintain expected answers and record which artifact or index version passed the checks.
This framework provides a practical baseline shaped by experience. Every organization operates under distinct technical and operational realities that require tailored design and governance. While you can adapt these measures independently, we frequently partner with teams to customize governance, integrations, and rollout. Performance outcomes will naturally vary.
Why these content layers matter
Intelligent content
Use shared term references and maintained question/answer checks rather than independent copies.
Taxonomy
Define the current preferred name, effective scope, and legacy synonyms against one stable feature identity.
Ontology and knowledge graph
Track artifacts and outputs that depend on the feature or term even when direct text reuse does not reach them.
Verify the result and handle exceptions
Inspect current topics, translated UI references, screenshots, training, and assistant answers. Test old-name questions and earlier-release guidance separately.
A failed rebuild or unreviewed asset keeps the rollout incomplete. Record intentional old-name occurrences so cleanup does not remove historical accuracy or search aliases.
How we work
with your team
We can guide your team, work alongside it, or deliver the work for you. Combine these approaches as your needs and capacity change.
Support
Add specialist backup
Your team owns the work. We provide experienced backup and specialist help where you need it.
Do
Delegate delivery
We handle work that is one-time, specialized, or outside your core business, without adding an ongoing burden to your team.
Build your team's skills with standard and custom courses.
Support for this implementation
Agree on approval and maintenance responsibilities for the content and outputs affected by product changes.
- Content strategySet priorities, ownership, and a rollout your team can sustain.
- Information architectureStructure content for reliable retrieval and reuse.
- Metadata and iiRDSDefine classification and delivery metadata, using iiRDS where it fits.
- DITA-OT plugin developmentExtend validation and publishing when your workflow uses DITA.
Where does your last product change still need to arrive?
Intuitive Stack can help model terminology and output dependencies, then define a propagation check with your publishing, localization, and search owners.