Every safety manager has seen the same chart. Observation reporting starts strong after a new initiative launches — a poster campaign, a toolbox talk, a new form — and then it declines, month over month, until it settles at a trickle. It\’s tempting to read that decline as people stopping caring. That\’s almost never what\’s actually happening. What\’s happening is that reporting got harder than it looked worth it, one small friction at a time.
Nobody consciously thinks \”the expected value of reporting this unsafe condition is negative.\” But that\’s functionally what happens every time someone notices something and decides not to log it. If logging it means walking back to an office, finding a computer, opening a form with fifteen fields, and writing a paragraph — the cost is real and immediate. The benefit — something might get fixed, eventually, maybe — is vague and delayed. Under that math, most observations never get reported, not because people don\’t care, but because the arithmetic doesn\’t favour reporting.
This is the single biggest lever available to a safety programme, and it has nothing to do with culture campaigns. It\’s about reducing the cost side of that equation until it\’s close enough to zero that reporting stops requiring a decision at all.
Reporting from where the observation happens, not from where a computer happens to be. If someone has to remember a hazard, walk away from it, and log it later, a meaningful share of observations simply evaporate between the moment they\’re noticed and the moment they\’d be recorded. A report logged from a phone, on the spot, with a photo, closes that gap. It should take under a minute — not because speed is a nice-to-have, but because every extra minute is a point where the observation can get quietly abandoned.
A form that asks only what\’s needed to act on it. What was seen, where — area, location, sub location — which branch, and a photo. That\’s enough to route it, act on it, and track it. Anything beyond that is friction the reporter pays and the organisation didn\’t actually need.
Visible follow through. The fastest way to kill reporting is for people to report something and watch nothing happen, with no visibility into whether it was even seen. A simple, honest status — new, open, under review, closed — gives the reporter something to check on, and gives the organisation a reason to actually move things through those stages rather than let them sit in \”new\” forever.
It\’s counterintuitive, but a safety programme with rising observation counts is usually in better shape than one with falling counts, even though more reports sounds like more problems. Observations and near misses are the leading indicator every serious safety manager is actually measured against, because they surface conditions before they become incidents. A programme where reporting has dried up doesn\’t have fewer hazards — it has fewer hazards being written down. The incident rate eventually tells the same story, just later and at a much higher cost.
This is why it\’s a mistake to treat a quiet observation log as good news. A near-zero reporting rate almost always means the reporting process has quietly become too expensive for people to bother with, not that the site has become uniquely safe.
Culture campaigns and safety messaging have their place, but they can\’t out-compete friction. If the actual mechanics of logging an observation are slow, the messaging is fighting the system it sits on top of, and the system usually wins. The fix isn\’t more encouragement — it\’s removing steps. Fewer fields. Reporting from a phone, on the spot. A photo instead of a paragraph. A status the reporter can actually check.
None of this is complicated engineering. It\’s mostly discipline about not adding anything to the reporting flow that isn\’t strictly needed to act on the report. Every field, every extra screen, every login step that isn\’t essential is a small tax on the exact behaviour a safety programme depends on.
