Training and Punishment Should Not Be Events
- Mac Davis

- Apr 4
- 2 min read
Updated: Jun 5
Most organizations don't have a training system or an accountability system.
They have training events and they have punishment events. And, statistically speaking, neither training nor punishment events are very effective.
Here's how punishment events work in practice:
Wait for disaster. Trace it back to where a standard wasn't followed. Punish to deter recurrence.
Nobody was checking that standard before the disaster which is why it happened in the first place. The system only activates after something breaks.
Here's how training events work in practice:
A compliance calendar ticks over (or someone goofs so bad everyone has to be retrained) and everyone gets trained. By powerpoint. Same content. Same room. And the event is mandatory - but learning the material is pretty optional.
Studies show 40% of trained knowledge is gone within 20 minutes (Ebbinghaus). Long-term effectiveness hovers around 10%. And nobody knows which 10% will be retained.
To have these two systems broken destroys an organization's ability to improve (and doesn't do any favors for daily operational capability).
The missing piece in both systems is the same thing: proactive detection of issues.
Organizations need a system sophisticated enough to check the hundreds or thousands of standards that actually matter because they prevent issues. Leaders can't remember to check all that stuff, it takes a system.
For an employee to perform a job correctly, three conditions have to be true. The employee needs to know what's expected, must understand why that expectation is there, and has to be trying to comply.
A detection system checks those three things persistently, proactively, and repetitively across the organization. Not after a disaster. Continuously.
When a gap is found, the path forward is obvious.
If an employee doesn't know the necessary information, just retrain that employee on the spot and record the gap found and filled. If the employee knows a standard but isn't following it, just record the lack of compliance and tell the employee what the expectation is.
Here's where it gets interesting. The act of checking and recording is itself corrective. You don't need a leader to fix the behavior. The system does it automatically because checking all those standards changes how people show up.
Pearson's Law says what gets measured improves. What gets measured and reported improves exponentially. The act of checking, consistently and at scale, resolves most issues outright.
And here's the mechanism behind why that works:
Employees only learn what they need to know. Repetitive checking creates a need to know because they know they'll be asked.
That need is what makes training effective. A detection system doesn't just find gaps; it creates the conditions for retention.
So what are leaders actually for?
Patterns. Repeated non-learning. Repeated willful disregard. That's where judgment and authority belong. Not in chasing individual training gaps or issuing first-instance corrections. A quality inspector or trainer can do those things.
Free leaders from the noise and they can do what they're actually needed for: improving processes, developing people, and moving the organization forward.
One detection system. Training and accountability solved. Leaders freed to actually lead. This is the basis of 180 OPEX.
Most organizations manage by event.
The strongest organizations manage by system.





Comments