A division produces a large amount of material for its own staff. Guidance documents, work instructions, templates, short trainings, shared resource pages, onboarding packets, the note that explains the exception to the rule. Nearly all of it is written once, by someone who knows the subject extremely well, and then met many times over by people who do not, while they are in the middle of something else.
When that material is not working, the symptom is almost always the same. People ask anyway. They ask a colleague, they ask the inbox, they ask the person who wrote it, or they stop asking and build their own version. From a distance all of that looks like one problem, usually described as staff not reading what was sent. Up close it is three different problems, and they need three different repairs.
Not found. The person never reached the material. The title uses the program's vocabulary rather than the words people search for, the page sits three levels down, nothing in the workflow points to it, or there are four similar files and no way to tell which is current. Not understood. The person reached it and could not follow it. The structure is legal or chronological rather than task-based, the answer is on page eleven of a document with no headings that name questions, or the language assumes a shared background the reader does not have. Not usable at the moment of need. The person found it, understood it, and still could not use it, because it is twenty-four pages and they had ninety seconds between a call and a deadline.
Sending the announcement again repairs none of these. It is worth saying plainly that this is not a staff attention problem. When several capable people fail at the same material in the same place, the material is the thing that has the defect.
