If Human Behavior is Badly Affecting Our Work, Can We Do Something About It?
summary
Claims concrete results from coaching 25 years with ~400 teams: apply just-in-time training for three weeks and teams change intuition and cut delivery time by 30% less time. Use specific experiments and fixes: rework a parking system from a clean sheet and force stakeholder demos with instruction zip your mouth handcuff your hands to observe real misuse (demo crashes on invalid credit card input), change pill-box colors to stop dispensing errors, and treat 80/20 of software as misuse protection rather than vague process talk.
AI-written summary · about
chapters (31)
- 0:00Introduction
- 1:52Human behavior in product dev
- 3:56Discipline vs shortcuts
- 6:48Intuition in decisions
- 9:43Research on intuition
- 12:12User intuition vs design flaws
- 14:23Observing user behavior
- 16:54Testing unexpected actions
- 17:16Effective sprint demos
- 18:44Overcoming assumptions
- 21:16Dangers of miscommunication
- 23:26Clarifying ideas with docs
- 25:11Written communication power
- 27:17Perception vs behavior
- 28:42Emotions driving behavior
- 30:08Excuses for delays
- 31:13Failure as improvement
- 34:14Real aim of testing
- 36:47Learning from mistakes
- 39:14Mistake reporting culture
- 40:59Handling feedback
- 42:27Questions over instructions
- 43:50Cultural differences
- 45:13Culture cannot change directly
- 46:40Cultural awareness
- 48:30Encouraging initiative
- 50:18Change vs uncertainty
- 51:47Just-in-time training
- 52:07Good vs bad project politics
- 53:14Focus on solutions
- 53:57Conclusion and key takeaways
