Get the free Core Drives in the Wild guide, behavioral design applied to real products, with one real-world example in your inbox each day: professorgame.com/WildCD
Episode Summary
Rob breaks down why disconnecting on vacation is so hard for driven people, and why it is a motivation problem rather than a willpower one. He maps the specific Octalysis Core Drives that keep high achievers tied to work during a break, including Core Drive 2 (progress addiction), Core Drive 8 (FOMO and Black Hat urgency), and Core Drive 1 (the mission needs me trap). Drawing on his own routine of leaving the phone at the apartment near the beach, he shows how to name each drive and switch off its trigger before the break starts. Listeners learn a pre-break diagnostic and how to design time off the same way they would design a user's exit from an engagement loop.
About the Host
Rob Alvarez is Head of Engagement Strategy, Europe at The Octalysis Group (TOG), a leading gamification and behavioral design consultancy. A globally recognized gamification strategist and TEDx speaker, he founded and hosts Professor Game, the #1 gamification podcast, and has interviewed hundreds of global experts. He designs evidence-based engagement systems that drive motivation, loyalty, and results, and teaches LEGO® SERIOUS PLAY® and gamification at top institutions including IE Business School, EFMD, and EBS University across Europe, the Americas, and Asia.
Key Takeaways
- Driven people stay tied to work on vacation because their Core Drives keep firing in the background. This is a motivation issue, which is why pure willpower so often fails to deliver real rest.
- Core Drive 2 (Development and Accomplishment) shows up as progress addiction. With no momentum at work, a break can feel like your progress is being trumped, which pulls you back to the phone to make something move.
- Core Drive 8 (Loss and Avoidance) is Black Hat motivation built on FOMO. The fear that something breaks, or that everyone else is still shipping, creates urgency and pushes you to check in even when nothing is wrong.
- Core Drive 1 (Epic Meaning and Calling), the sense that the mission needs you, is the noble sounding trap. It can justify sacrificing rest you have earned, so naming it is what lets you stop it from firing back.
- The fix is to design your break the way you would design a user's exit from an engagement loop: kill the notifications, remove the triggers (Rob leaves his phone at the apartment), and push yourself out instead of staying half in.
- A real emergency that truly needs you is rare, roughly 0.1 percent of the time. Plan ahead, brief your team on what actually counts as an emergency, and trust them to handle the other 99.9 percent without you.
Topics Covered
- [0:00] Why driven brains can't switch off
- [0:49] Disconnecting is a motivation problem
- [1:21] Core Drive 2: progress addiction
- [1:54] Core Drive 8: FOMO and urgency
- [2:30] Core Drive 1: the mission trap
- [3:08] Name the drive, deactivate the trigger
- [3:54] Leaving the phone at the beach
- [4:50] Why productive resting backfires
- [6:00] Design your break like an engagement loop
- [6:36] Diagnose your pull-back drive first
- [8:05] Rest is switching off the drives
Mentioned in This Episode
- Core Drives in the Wild, Rob's free guide (one Core Drive example per day)
- The Octalysis Group
- The Octalysis Framework and its Eight Core Drives (Yu-kai Chou), the basis for Core Drives 1, 2, 5, and 8 discussed here
Free Resources and Get in Touch
