Influencing through getting your carrots in a row
summary
Claims that aligning incentives beats persuasion alone and shows concrete effects: a max feature‑flag limit reduced flag count but causes hoarding and riskier pushes; switching release cadence from twice a week to every commit fails until a Slack deploy alert nudges teams and raises releases to once or twice a day; gamifying tests with a tests leaderboard increases coverage; splitting a monolith by extracting the hardest core (not the Strangler fig) succeeds where earlier attempts become zombie projects.
AI-written summary · about
chapters (5)
- 0:00Introduction
- 4:16Persuasion fails engineers
- 8:56Incentives shape behavior
- 10:59Aligning incentives
- 17:59Putting it together
related talks
54mManaging Misaligned Stakeholders
43mManaging Releases by the Numbers (Really?)
17mCreating Happy Engineers - Anecdotes from the Trenches
46mCracking the cadence of your software engineering 1:1s
31mHow to get everyone to get on board with software security: practical tips and suggestions.
20mHow to keep everyone happy (on a shoestring)?
01h 10mAgile Cross Team Collaboration How Tos
47mCodeCraft Leadership: Hacking the DNA of Agile Teams