Punishment Driven Development
summary
Shows that tying pay to UAT bugs backfires on juniors, stresses people, rewards nondoing and drives helpers away, with the concrete example of a bonus inversely proportional to number of bugs found in UAT. Describes simple fixes that work: send one‑line decision emails so a sidelined developer follows through, change color schemes so live and test differ, apologize to defuse rage. Cites a 2015 coil study on the dorsolateral prefrontal cortex that lowers the urge to punish but not blame.
AI-written summary · about
chapters (20)
- 0:00Blame-driven development
- 1:02Toxic management examples
- 2:00Interactive team competition
- 3:49Scenario experiment part 1
- 6:38Punishment in the workplace
- 8:28Bonus scheme analysis
- 10:38Reasons for punishment
- 11:59Scenario experiment part 2
- 13:38Neurodiversity and teamwork
- 16:02Scenario experiment part 3
- 17:53Self-punishment at work
- 19:49Managing difficult stakeholders
- 23:11Emotional regulation
- 24:27Scenario experiment part 4
- 25:28Handling conflict with empathy
- 29:54Continuous improvement
- 31:44The science of blame
- 34:15People-driven manifesto
- 35:39Q&A session
- 53:17Conclusion
related talks
01h 04mHow to Motivate Your Developers
54mIf Human Behavior is Badly Affecting Our Work, Can We Do Something About It?
26mDeveloper Joy – How Great Teams Get s%*t Done
44mDeveloper Joy – How great teams get s%*t done
33mMeasuring Developer Productivity: the good, the bad and the data
58mDeveloper Joy – How Great Teams Get S%*t Done
44mIncentives: why or why not?
34mBuilding a Culture For Developer Productivity