Practical guide
AI fluency for knowledge managers: reconcile duplicate guidance
Use a fictional knowledge-base pair to resolve conflicting instructions, assign ownership and preserve an update trail.
A knowledge manager can use AI to compare documents while retaining responsibility for which guidance becomes the active reference. This original exercise resolves a fictional pair of conflicting knowledge entries. It focuses on authority, applicability and maintenance decisions, rather than rewriting an announcement or treating the most recently edited document as automatically correct.
Inspect the two entries before merging them
Different wording may reflect a real scope difference rather than a duplicate.
Entry A says service requests go to the operations inbox and names the service owner. Entry B says requests go through a portal, but names no owner and carries a later edit date. A separate note says the portal was tested by one team. These fictional facts do not establish that the portal replaced the inbox for everyone.
Ask AI to compare instructions, audience, ownership and status. Keep a conflict table with exact passages. Do not immediately combine both routes into one instruction, because that could create an unsupported choice or send readers into an unfinished process.
Find the authority needed to resolve the conflict
A content-maintenance decision should be grounded in the responsible process owner.
The exercise supplies an owner confirmation: the inbox remains the general route; the portal is a pilot for the testing team only. Use that confirmation to distinguish the scopes. The later edit date of Entry B does not change the owner's statement. Record the confirmation with its date and the affected entries.
AI can help draft the revised wording, but it cannot create the missing authorization. If the confirmation were absent, the appropriate output would be a flagged conflict and a question for the owner, not a confident merged procedure.
Design the active reference
Give readers one clear route for their situation without erasing meaningful distinctions.
Revise the general entry to explain the inbox route and explicitly identify the separate pilot scope. Keep the pilot instructions available only where appropriate to the exercise's audience rules. Do not describe a test as a full launch or conceal it inside a footnote that changes the main instruction.
Use a concise applicability statement near the beginning. A reader should be able to decide whether the entry applies before following the steps. This is different from adding more keywords or merging all available text into a longer page.
Repair links and ownership together
A corrected page can still fail if other surfaces point readers to the superseded instruction.
List the fictional links from an onboarding checklist, a team bookmark and a service FAQ. Identify which need updating or an explanatory redirect within the knowledge system. Preserve a change note describing what was superseded and why. Do not leave an old entry active merely because its text is useful history.
Assign a current owner and an update trigger, such as the decision to end or expand the pilot. A fresh edit date alone is not evidence that the underlying process has been reconfirmed. Keep responsibility for that confirmation separate from the person who formats the page.
Test retrieval and maintenance
The final exercise should check whether a reader finds the right instruction.
Ask one fictional general user and one pilot user to identify their correct request route from the revised entries. Then introduce a pilot expansion to a second named team. Determine which applicability statements, links and ownership records need revision. Avoid assuming expansion to all teams.
Deliver the conflict table, active wording, link-change list and update trigger. Review scope discipline and maintenance reasoning within this case. The wider communications guide covers multiple artifact types; this role exercise specifically examines the lifecycle of an authoritative knowledge entry when near-duplicate guidance conflicts.
Sources and scope
The references below are background reading, not evidence that this fictional exercise has been validated or endorsed.
The case details, calculations and suggested review questions are original instructional material. Use them to discuss observable work, not to infer customer outcomes, professional credentials or performance in every setting. Before adapting the exercise, confirm the relevant facts, approved tools, data permissions and decision owners. If you change the case, revisit the expected answers and checks as well. These examples describe practice tasks, not a promise that a particular product includes the fictional features.
Sources: [1] [2]
Sources
- 1.AI RMF Core · NIST
- 2.AI foundation skills for work benchmark · Skills England