Motivation Theories a Working Manager Can Actually Use
I once inherited a team that had just received raises and was still visibly flat. Deadlines met, energy gone, best engineer quietly interviewing elsewhere. The raise had fixed nothing, which confused the management chain, because in their model money was the lever. The motivation theories on the PMP syllabus exist for exactly this confusion. They are not academic trivia; each one is a different diagnostic lens, and each has caught something real for me that the others missed.
Herzberg: why the raise didn't work
Herzberg splits the world into hygiene factors and motivators. Hygiene, salary, conditions, policies, job security, does not motivate when present; it demotivates when absent. Motivators are different substances entirely: achievement, recognition, meaningful work, growth. The flat team was a textbook case: hygiene newly fine, motivators absent. The engineers were maintaining a legacy module with no visible users, no growth path, and no one noticing their work. The raise removed a complaint; it could not add a reason. What worked was rotating module ownership and putting their names on the migration that everyone would use. Different substance.
Maslow: sequence matters
Maslow's hierarchy earns its keep as a sequencing rule: purpose-talk lands on deaf ears when the layer below is shaking. During any period of organizational uncertainty, restructures, contract renewals, layoff rumors, I have watched inspirational roadmap presentations bounce off teams whose actual question was "do I have a job in Q3". Security first, then belonging, then the vision speech. Leaders who skip layers sound, at best, out of touch.
McClelland: why the same job motivates one person and drains another
McClelland says people run on different dominant needs: achievement, affiliation, or power. This is my daily-use theory, because it explains within-team variance. The achievement-driven engineer wants a hard problem and a finish line; assign her endless maintenance and she wilts. The affiliation-driven one does his best work in pairing and coordination roles; isolate him on a solo module and he goes quiet. The influence-driven one wants their work to change how things are done. Same job description, three different fuels. Half of what gets called a performance problem is, in my experience, a fuel-matching problem.
Vroom: motivation as a chain that breaks at its weakest link
Vroom's expectancy theory says motivation needs three beliefs multiplied together: my effort will produce results, results will be noticed and rewarded, and the reward is something I actually want. Multiplication means any zero zeroes the whole thing. This gives a precise diagnostic: the cynical sentence "no matter what we ship, nothing changes" is a broken second link, and no team-building event repairs it. Only a visible instance of effort leading to consequence does. I once watched a team's energy return in weeks, purely because a long-ignored proposal from them finally got implemented and credited. One repaired link.
McGregor: the theory that describes the manager, not the team
Theory X assumes people avoid work and need supervision; Theory Y assumes people seek meaning and self-direction. The sharp edge is that both are self-fulfilling. Micromanage professionals and they stop volunteering thought, which then "proves" the supervision was needed. Trust competent people with real ownership, and most grow into it. Every micromanaged team I have taken over needed months to believe that autonomy was not a trap. The theory you hold about people quietly manufactures the people you get.
Using the lenses together
In practice I run them as a checklist when energy drops. Hygiene broken? Fix it first, expect no credit. Security shaking? Address it before any vision talk. Fuel mismatch per person? Reassign by need, not just by skill. A broken effort-to-consequence link? Repair it with one visible example. And check the mirror: is the management style itself producing the behavior it complains about? Motivation work is unglamorous diagnosis, not speeches. The speech is what you give after the diagnosis, if it is still needed, and by then it usually isn't.
Nguyễn Hải Nam
Project Management Lead. 16+ years from code to delivery. PMP®. Writing here about project management and engineering.