10 minutes
Findable, current and owned A resource library is not a folder. Duplicates, orphaned files and titles in the division's private vocabulary quietly undo good material.
What you’ll be able to do Bring one shared resource page back to a trustworthy state by establishing a single current version, a named owner, a plain title and a review point for each item on it. Compare the responses to this question and explain your choice: What restores trust in that page fastest? Document a next step for Findable, current and owned: Open one shared page your team owns. For each item, write the owner and the last review date. Anything you cannot fill in is either someone's to claim in the next two weeks or ready to be retired. Why good material stops working Almost none of the material that fails inside a division failed because it was badly written. It failed because of what happened to it afterward. The person who wrote it moved to another role and nobody inherited it. A revision went up under a different name and both stayed. A training covered the same ground and described one step slightly differently. A reorganization moved the page and the links that pointed to it were never updated. Two years of that, and a shared page becomes something staff scroll past on their way to asking a colleague.
The failure mode is specific and worth naming: not an empty library, but a crowded one. A gap is honest — a person finds nothing and asks someone. Three unlabeled versions of the same instruction are not honest. Three people find three different answers, all of them believe they followed the guidance, and nobody discovers the difference until a decision has already gone out.
Findability has four parts, and titles are where most of the damage happens. Material inside a division tends to be named in the division's own vocabulary — the project name, the committee, the form number, the abbreviation everyone in that room understood at the time. The people who need it search in ordinary words for the task they are doing. A title written for the author is a file that will not be found by the reader.
What every internal resource needs attached to it A plain title in the words people would actually search for, naming the task rather than the project.
One sentence saying what it is for, readable before anything is opened.
The audience: which roles this is written for, and which roles it is not.
A named living owner — a person or a position, not a former staff member and not a committee that no longer meets.
When it was last looked at, and when it will be looked at next.
What it replaces, or what has replaced it, stated in one line.
Findability, in four parts The name
Does the title use the reader's words or the author's? Name the task and the audience. The project name, the committee and the form number belong in the summary, not in the title.
The words people search
Write down the five phrases someone would actually type, including the wrong ones and the old names. Put them in the summary so the search can find them.
Where it sits
Is it reachable from the place the work happens, or only from a page someone would have to already know about? A resource that requires prior knowledge to find is a resource for people who did not need it.
What points to it
Which workflow, message, template or page sends people here — and does any of those still point at a replaced version? Old links are how retired material stays in circulation.
Retire something on purpose What you can change You control whether superseded material stays in the main list, and whether anyone is told what changed.
What to watch for Do not leave a replaced document up because removing it feels risky. Ambiguity is the greater risk: the old version is still being followed by someone right now, and neither of you knows it.
Your next step This month, pick one duplicate pair on a page you own. Declare one current, mark the other replaced, write the single line about what changed, and tell the people who were trained on the old one.
A private reflection, not collected and not seen: think of a resource you own or inherited. If you left your role next month, would anyone know it was theirs? What would the people who rely on it discover only after it had quietly gone out of date, and how could the people most affected have shaped it earlier?
Carry this forward Good material stops working for reasons that have nothing to do with its quality: the author changed roles, a newer version appeared under a different name, or the title uses a program term nobody searches for.
Every internal resource needs five things attached to it — a plain title in the words people use, a one-sentence summary, the audience, a named owner, and when it was last looked at. Without the owner and the review date, everything else decays.
Duplicates are worse than gaps. A gap sends someone to ask a person; three unlabeled versions send three people to three different answers and nobody notices for a year.
Retiring material is a skill, not a failure. Mark what is replaced, say in one line what changed, and move it out of the main list rather than deleting the record of what people were told before.
A scenario about a page holding three versions of the same form instruction, a knowledge check on what restores trust in a shared page, and flashcard practice on the four parts of findability.
Open one shared page your team owns. For each item, write the owner and the last review date. Anything you cannot fill in is either someone's to claim in the next two weeks or ready to be retired.
Browse and download only. Course notes are not typed or saved on this page.
Reset this lesson
Previous lesson Next lesson Participation and course completion in this program do not count toward DHS-required training credits unless management, a director, or DHS leadership expressly approves an exception.
