Can Your Team Find the Rule When They Need It?

An editor needs to know whether a disclaimer is still required. A course designer needs the approved term for a product feature. A reviewer needs the current escalation path. Each person searches the intranet, opens an old PDF, checks a team channel, and asks a colleague. They eventually get an answer—but not necessarily the same one.

That is not just a search problem. It is a content-design and governance problem. Guidance has accumulated around departments, tools, and past projects rather than the questions people have while doing the work. The safest rule may exist, yet a faster-to-find duplicate wins.

A useful 2026 case comes from the UK Government Digital Service. Around 3,000 people publish to GOV.UK. Its publishing instructions had grown across four manuals with long pages and separate search experiences. GDS consolidated and redesigned the guidance, sorting the old material into keep, merge, or remove, rewriting more than 130 pages, testing a two-level taxonomy, and running a private beta with working publishers. The lesson applies well beyond government: storing all the rules is not the same as helping people retrieve the right one.

Treat repeated questions as evidence, not interruption

“It is already in the manual” is not a useful diagnosis. Repeated questions tell you that the route from a work problem to an approved answer is failing. Capture the language people actually use in support tickets, chat, review comments, search logs, onboarding sessions, and handoffs. Record the task, the consequence of a wrong answer, the source people tried first, and what finally resolved the question.

Frame the need as an action. Current GOV.UK guidance on identifying user needs says content needs should be based on tasks, not vague goals such as “know” or “be aware of.” For an internal library, “I need to choose the correct review route for a revised safety statement” is more designable than “I need to understand compliance.” It tells you what the page must help someone decide or do.

Separate a knowledge gap from a retrieval gap. Training is appropriate when people need practice, judgment, or a mental model. Point-of-need guidance is better when a person must look up a changing threshold, exact phrase, file requirement, or sequence of steps. Often the pair works together: training explains why the rule matters; the maintained guide supplies the current rule at the moment of use.

Choose one current answer before improving navigation

Search cannot rescue contradictory guidance. Start with an inventory of every page, document, checklist, course, template, and saved message that answers the same question. For each item, identify an owner, intended audience, approval status, effective date, review date, and authoritative source. Mark it keep, merge, replace, archive, or investigate. Do not quietly preserve five “helpful” copies of a high-risk instruction.

The current GOV.UK guidance for communicating change warns that multiple pages with similar content can make it hard for users to identify a single version of the truth and can weaken trust. It recommends auditing related content and removing duplication first. That sequence matters. Decide which answer controls; then point old routes toward it, clearly mark superseded material, or remove it according to your records and retention requirements.

A canonical page does not have to contain every detail. It must state the answer, its scope, and the route to the controlled source. If a signed procedure, approved label, contract, or regulation governs the work, link to that record and distinguish it from the explanatory guidance. The summary helps someone act; it does not replace the authority behind the action.

Organize around real tasks, not the org chart

Department names make sense to the people who maintain a library. They may mean little to someone who needs an answer. Group guidance around recognizable work: prepare a draft, choose a template, review evidence, approve a change, publish a file, correct an error, or escalate a risk. Use the words people search for, with synonyms and old terms where they help retrieval.

Keep the first layer shallow. A person should be able to choose among a small set of meaningful routes without first understanding the whole content model. Use narrower collections only when the material truly needs another level. In its 2026 work on a service-delivery guide, the UK Department for Education used consistent content types, displayed content owners and last-reviewed dates, and began tree testing its top-level navigation to see whether content appeared where users expected it.

A tree test shows participants a text-only hierarchy and asks where they would look for a specific answer. It is useful before interface polish because it tests the labels and grouping themselves. If users repeatedly choose the wrong branch, change the structure or wording; do not solve the result with another orientation session.

Design each page for the moment of decision

Write a title that resembles the question, such as “When does a revised slide deck need medical review?” rather than “Review Policy 7.4.” Put prerequisites and decision criteria before background. Use tables for genuine comparisons, numbered steps for sequences, and callouts for consequences or exceptions. Link text should describe the destination rather than say “click here.”

Keep examples close to the rule they clarify, and test the wording as carefully as the navigation. Superscriptify’s guide to testing instructions with real users offers a practical way to observe hesitation, wrong turns, and recovery. The same approach works for an internal guidance page: give someone a realistic task and watch what they do without coaching.

Test finding and applying as two separate outcomes

First ask whether a participant can locate the page from a realistic starting point: the homepage, an intranet search, a course handoff, or a familiar old link. Measure the first route chosen, time to the correct page, failed queries, and whether the participant recognizes that the answer is current. A successful result is not merely a click; it is reaching the intended answer with reasonable confidence.

Then ask the participant to use the guidance. Can they choose the correct template, review path, wording, or next step? Can they identify an exception and know when to escalate? If they find the page but make the wrong decision, the answer design has failed. If they can apply the rule after you send a direct link but cannot find it alone, the information architecture or search language has failed.

Use a small set of high-value tasks before launch, then keep watching real queries and questions. Report measures that expose friction: successful first choice, time to answer, no-result searches, use of superseded links, unresolved questions, and repeat escalations. Handle search logs and support data according to your privacy and records policies; a useful feedback loop does not require collecting unnecessary personal information.

Make freshness visible and ownership real

Every important page needs a named owner or owning team, an approval route, and a review trigger. Calendar dates help, but event-based triggers are often more important: a regulation changes, a product is renamed, a template is replaced, a workflow moves systems, or support questions reveal a new ambiguity. Give readers a simple way to report a conflict or outdated instruction.

Digital.gov’s guidance on the content lifecycle connects maintenance with governance: assign ownership, define review and approval responsibilities, involve subject-matter experts, and decide when content should be consolidated or retired. The library is a maintained product, not the residue of completed projects.

When a rule changes, update the canonical answer and every route into it. Record the material change in language users can understand. Notify the audiences whose current work is affected; do not broadcast every minor edit. Check templates, learning modules, checklists, and localized versions that repeat the old rule. A controlled, translation-ready source also reduces drift when the same guidance travels across languages and formats.

Six questions for a guidance-library review

1. What work question does this page answer? Write it in the language the intended user would recognize.
2. Is this the canonical answer? Identify the controlled source and deal explicitly with duplicates.
3. Can someone find it without knowing the org chart? Test labels, navigation, search terms, and old entry points.
4. Can someone act from the page? State scope, decision, steps, examples, exceptions, and escalation.
5. Who keeps it current? Name the owner, approval route, review date, and event-based triggers.
6. What evidence will show improvement? Measure successful retrieval and correct application, not page views alone.

This article offers general content-design and governance information, not legal, regulatory, medical, or records management advice. Where guidance controls safety-critical or regulated work, follow the applicable approved source, retention rules, and qualified review process. The practical goal is simple: when the work creates a question, the current answer should be easier to find than the obsolete one.

Sources and further reading

• Government Digital Service. Launching GOV.UK’s New Content and Publishing Guidance. June 8, 2026.
• GOV.UK Content and Publishing Guidance. Identify User Needs.
• GOV.UK Content and Publishing Guidance. Help Users Prepare for Change.
• UK Department for Education. Publishing the First Release of Deliver Good DfE Services. July 2026.
• Digital.gov, U.S. General Services Administration. Crafting Quality Content Throughout Its Lifecycle. November 12, 2024.