Write once, reuse everywhere
· 1 min read
Keep shared procedures in one place so a change updates every article that needs it.
In brief
How many knowledge articles explain how to reset a password? In most organisations the honest answer is several, and they do not all agree. It happens innocently: IT writes the steps, HR copies them into onboarding, Facilities pastes them into the visitor guide. Then the process changes. One copy gets updated. The other two quietly start giving wrong answers. Duplicated content does not fail loudly. It fails one confused colleague at a time, usually the newest one.
This article argues for a better habit: keep shared content such as a standard procedure, a contact list or a policy statement in one place, and reference it from every article that needs it. Change it once and every article is right again. This matters more as AI assistants answer from your knowledge base. Give a machine three versions of the truth and it will pick one, fluently, and you may not like which. Enterprise service management is about departments sharing one way of serving people, and shared knowledge is the simplest place to start. Join the conversation on ESM's Exchange.
Several answers that do not agree
How many knowledge articles explain how to reset a password? In most organisations the honest answer is several, and they do not all agree.
It happens innocently. IT writes the steps. HR copies them into onboarding. Facilities pastes them into the visitor guide. Then the process changes. One copy gets updated. The other two quietly start giving wrong answers.
Duplicated content does not fail loudly. It fails one confused colleague at a time, usually the newest one.
Write once, reference everywhere
The better habit: keep shared content, like a standard procedure, a contact list or a policy statement, in one place, and reference it from every article that needs it. Change it once. Every article is right again.
Why this matters more now
This matters more as AI assistants answer from your knowledge base. Give a machine three versions of the truth and it will pick one, fluently. You may not like which.
Enterprise service management is about departments sharing one way of serving people. Shared knowledge is the simplest place to start.
Next step
Where does the same answer live three times in your organisation? Tell us on ESM's Exchange: https://exchange.esm.institute
Tags: knowledge management, service management, self-service, ESM
Join the Exchange free
Join free to unlock the complete knowledge library.
Founder membership is free for life
More from Esm
How should the service desk handle a Microsoft 365 outage it cannot fix?
4 min read
Deploying AI is the easy part: who runs it once it goes live?
5 min read
How do I compare help desk tool pricing before rolling it out across several departments?
4 min read
Turning 'not helpful' into a fix
1 min read
When the author leaves, who owns the article?
2 min read
Test after every change, or find out from users
1 min read
Related articles
How should the service desk handle a Microsoft 365 outage it cannot fix?
Treat a supplier cloud outage as your own major incident: log it once, tell people early on a channel that still works, update on a rhythm and review your dependency afterwards.
Deploying AI is the easy part: who runs it once it goes live?
Only a third of large enterprises have met the business case for their main AI programme. New research points to a gap in who runs AI after launch, and what leaders can do.
How do I compare help desk tool pricing before rolling it out across several departments?
Compare help desk tools on a full year's cost for your real agents, approvers and requesters in every department, not on the headline monthly price.
Turning 'not helpful' into a fix
'Not helpful' is free, honest feedback, and most of it goes nowhere. Turn that click into a fix.
When the author leaves, who owns the article?
Articles keep being read after their authors move on. Make sure the care for them does not leave too.
Test after every change, or find out from users
Knowledge changes fail quietly. A short, repeatable test after every change finds the problem before your users do.