The Truth About Employee Engagement
Lencioni traces job misery to three root causes: anonymity (nobody knows me), irrelevance (my work doesn’t matter to anyone), and immeasurement (I can’t tell if I’m doing well). The fable follows an executive who takes over a pizza restaurant and tests the model on jobs nobody would call glamorous, which is the point. Engagement is not a property of interesting work; it is a property of how the work is managed.
What I appreciate most is that the fixes sit with the manager, not with a program. Knowing your people as people, connecting their work to a specific someone it helps, and giving them a way to gauge their own progress cost nothing and require no approval from HR. That also means there is nowhere to hide. If a team is miserable, the model points at the manager’s behavior before it points at compensation, workload, or the company.
Immeasurement is the cause I have thought about most in technology work. Support and infrastructure roles are notorious for it: when everything works, nobody notices, and the only feedback arrives when something breaks. People in that position slowly conclude their work is invisible, because functionally it is. The correction is giving each person a measure they can read themselves, response times, resolution quality, systems kept healthy, so a good week is visible to them without waiting for anyone’s praise. The measure has to be theirs, though; a metric imposed for reporting purposes becomes surveillance, which makes things worse.
Irrelevance has a technology-specific version too. It is easy for someone three layers from the customer to forget anyone benefits from their work. Passing along a client’s thanks by name, or letting an engineer sit in when a client describes what a project did for them, does more than any recognition program I have funded.
A short read for any manager who suspects an engagement survey is not going to fix the problem, and an uncomfortable one in the right way.