“The package room door won’t latch.”
The first resident reports it in March, and a second reports it in April. By the time a third resident reports it in May, the problem has existed for two months, and the office has fixed the latch twice.
Signal detection theory grew out of World War II radar work and was formalized in the 1950s by researchers including Wilson Tanner and John Swets. Its core idea is akin to your property’s complaint log. Anyone listening for a signal trades off two errors: missing a real one, or raising a false alarm over noise. Set your threshold too high, and you miss real failures. Set it too low and your team chases every bad day.
Most properties set it too high by default. Each complaint becomes a single ticket that gets closed and forgotten, so the pattern stays invisible until residents start writing it in reviews.
Lower the threshold with a few rules:
- Tag every complaint by category in your work-order system, so repeats show up across residents and units.
- Two of a kind in thirty days triggers a root-cause review. Act on the second report.
- Ask why five times before you fix anything, the way Toyota’s production system teaches. The latch fails. Why? The door closer is set wrong. Why? The vendor installs closers at the factory setting. Why?
Then sort single complaints with good intention. Preferences get a courteous follow-up. And repeat complaints spur action.
Fix the process that produced the complaint, and the complaint stops coming. — Mike Brewer
Discussion Prompt: What complaint showed up most in your log over the last ninety days, and what would asking “why” five times reveal about where it starts?