Let’s Play a Game!
summary
Games scheduled as meetings force concrete tradeoffs and surface reasons: use bang for the buck to pair value vs cost with everyone taking turns, use buy a feature with play money like a $50 bill two $20s and a $10 so denominations force tough choices. Tools: post it, markers, Google Docs, play money, and innovation games rules. Teams end up allocating $90 here and $150 there and report that the conversation delivers ~75% of the value.
AI-written summary · about
chapters (15)
- 0:00Intro
- 0:43Why Games
- 0:58Meet Adam
- 1:14Games at Work
- 1:29Finding the Most Valuable Thing
- 1:44Games
- 1:59Bang for the Buck
- 2:28First Player
- 2:44Second Player
- 2:59Why does it work
- 3:29By a Teacher
- 3:44The Process
- 4:29Why
- 4:59Tools
- 5:15Outro
related talks
49mHard Choices, Tight Timelines: A Closer Look at Skip-level Tradeoff Decisions...
33mGames We Play to Improve Incident Response Effectiveness
20mHow to keep everyone happy (on a shoestring)?
43mPreparing your software engineering teams for times of financial uncertainty
20mChaos: breaking your systems to make them unbreakable
46mGames We Play to Improve on Incident Response
18mMaking Better Decisions in Incidents (Why Playbooks Aren’t the Answer)
39mWar Games – prepare for the unexpected