Walk a Glossary Change Without Derailing Launch
Decide how to propagate a late terminology change based on user impact, consistency debt, and release timing.
Terminology shock "Workspace" becomes "hub" one week before launch, with 312 localized occurrences. The team needs a propagation plan, not a blanket edit. MoSCoW for terminology Must now, Should next, Could polish, Won't this time A term change should follow user impact and release risk. Not every string carries the same consequence Visible product pathways deserve more urgency than stale archives. Controlled propagation A glossary change is only useful when the rollout path is controlled. 01 Scope 02 Propagation 03 Fresh case Find critical occurrences The term appears in navigation, onboarding, help headers, and archived release notes.
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in