The short answer
Define the reader’s finding task, then propose clear groups, specific link labels and a route to the needed guide. Keep a collection, a sequential procedure and search as different aids. Editorial grouping is a hypothesis until suitable real evidence supports it; a successful link check does not establish that readers can find the answer.
What you’ll take away
- Start with what readers need to find, not the publisher’s department names.
- Group related references; use an actual procedure when the task requires a sequence.
- Keep ambiguous cards, cross-links and untested route assumptions visible.
Write a concrete finding task
A creator with a library of articles can ask a useful question: where would someone start to check a report’s period, prepare an accessible export or publish the intended file? These tasks do not require the same first guide. List what the person needs to reach and the information they already have. Do not define the need as “use our new navigation”; that presupposes your preferred solution.
Separate the proposed task from evidence that anyone has it. Relevant existing questions, permitted research and actual support patterns can inform the plan; an editor’s intuition can only supply a hypothesis. GOV.UK’s user-need guidance stresses the action and reason before the format. Its government task examples do not establish the needs of every LinkedIn creator.
Choose groups, cross-links and sequences deliberately
Use a group to help readers explore related references. Use a genuine step-by-step explanation when the job depends on a sequence, and keep any prerequisite visible. A “Publishing” folder is not a complete procedure just because its links happen to be numbered. Give each guide one stable destination and cross-link when the same resource genuinely helps more than one task.
GOV.UK distinguishes topic tagging, document collections, manuals and step-by-step navigation. Its collection rules explicitly reject using a collection as a substitute for guiding a task. These are that publishing system’s policies; the transferable decision is whether the reader needs a set of references or an explained route. No native LinkedIn folder, category permission or automatic related-link feature is asserted here.
Build and inspect one complete proposed map
The original exercise has six cards: A metric meaning, B reporting period, C export inspection, D document publication, E image alternatives and F disclosure/privacy review. A draft map puts A/B under understanding a report, C/E/F under preparing a public copy and D under publishing. D explicitly links to C and F as preparation; those links do not create duplicate guides or prove the sequence works for readers.
Check each proposed task against the map: a period question starts at B; a publishing task reaches D and can find C/F; a chart explanation can find A and E. Save unclear labels and missing routes rather than forcing every card into one folder. If a generic “Tools” label hides all six tasks, changing only its icon does not resolve the wording problem. This is an editor-constructed route inspection, with no participants or measured findability.
| Card | Task | Proposed entry |
|---|---|---|
| A | Interpret metric | Understand report |
| B | Check period | Understand report |
| C | Inspect export | Prepare public copy |
| D | Publish document | Publish; C/F preparation |
| E | Image alternatives | Prepare public copy |
| F | Disclosure and privacy | Prepare public copy |
Resolve three navigation choices
N1 — Constructed duplicate route: the same privacy guide is copied into two categories with different text and no stated owner. Decision: retain one intended source and use two descriptive links where both tasks need it; resolve existing factual differences before consolidation. Outcome: a proposed ownership and navigation repair, not a verified live merge or proof that one category always fits every reader.
N2 — Constructed prerequisite gap: a “Publish the PDF” link reaches a native-upload guide but gives no route to review the actual exported file or private details. Decision: name those prerequisite checks beside the publishing entry and retain the upload guide’s own complete steps. Outcome: a technically inspectable route proposal; actual reader task success remains unmeasured.
N3 — Constructed language gap: an English label says “Check the reporting period,” while its German counterpart says only “Analyse.” Decision: write a specific German task label and check that it reaches the same intended topic in German. Outcome: aligned editorial intent and a destination check, not independent localization validation or observed language preference.
Use real grouping and finding evidence appropriately
Card sorting can explore how willing relevant participants group and name existing cards; an open sort lets them propose groups, while a closed sort uses supplied categories. Victoria’s method notes the dependence on the prepared card set and warns that large sets can overwhelm. Results inform a structure rather than dictate the correct one. An automated persona sorting cards is not evidence of real readers’ mental models.
A June 2026 Department for Education design history reports an open sort with nine people, a draft structure and tree testing as a next step. That is the publisher’s reported process, not our study or a completed validation of this journal. For your own eligible future check, use neutral finding tasks and record actual routes, completion, confusion and uncertainty. A click alone does not establish comprehension or preference.
Sources & product references
Product details reflect the publication date. External features and interfaces may change.




