Get the free Core Drives in the Wild guide, behavioral design applied to real corporate cases: professorgame.com/WildCD

Episode Summary

Rob breaks down why enterprise AI adoption stalls even with paid licenses and training, while a group of students beat a locked, proctored exam with ChatGPT and no support at all. Reading both cases through the Octalysis Framework, he shows how the exam accidentally stacked Core Drive 8 (Loss & Avoidance), Core Drive 6 (Scarcity & Impatience), and Core Drive 2 (Development & Accomplishment) into a ferocious, if mispointed, motivation engine. The enterprise bought the most capable tool and surrounded it with zero motivation, so nobody opened the app. Listeners learn why AI adoption is a motivation problem wearing a tooling costume, and leave with a two-part diagnostic question to ask of any AI initiative.

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

• Students beat a lockdown, proctored, face-to-face online exam by getting ChatGPT to answer questions live through a Chrome extension, with no license, no training, and no change management. Adoption was instant, total, and creative enough to defeat the security.
• The exam accidentally stacked three Black Hat Core Drives: Core Drive 8 (Loss & Avoidance, failing is high-stakes), Core Drive 6 (Scarcity & Impatience, one timed shot), and Core Drive 2 (Development & Accomplishment, clearing the hurdle to the grade).
• Enterprises buy the paid license, training, IT support, and a leadership mandate, then adoption stalls because none of those things are motivation. There is no personal loss for ignoring the tool and no personal win for using it.
• Motivation pointed at the wrong goal produces flawless adoption of exactly the behavior you did not want. The students aimed AI at passing, not learning, and got it.
• As AI removes capability constraints, the human motivation layer becomes the only constraint left, which is why behavioral design matters more in the AI era, not less.
• The diagnostic: ask what your team personally gains by using the tool and what they personally lose by ignoring it. If the honest answer is “nothing much either way,” no rollout plan will save it.

Topics Covered

• 0:00 – Students hacked a locked exam
• 0:52 – Same tech, opposite outcome
• 1:44 – Adoption was never the problem
• 2:39 – The exam’s accidental motivation engine
• 4:31 – Almost entirely Black Hat motivation
• 5:18 – Why the funded enterprise stalls
• 6:30 – Adoption and direction both matter
• 7:41 – Why behavioral design matters with AI
• 7:55 – Your diagnostic question for today

Mentioned in This Episode

• The Octalysis Framework, developed by Yu-kai Chou
• ChatGPT (OpenAI)
• Core Drives in the Wild, the Professor Game free guide

Free Resources and Get in Touch

• Core Drives in the Wild: Professor Game Free Guide
• Get Daily Value on Your Email
• Let’s chat about your gamification project
• YouTube
• LinkedIn
• Instagram
• Facebook
• Start Your Community on Skool for Free
• Ask a question

Looking forward to reading or hearing from you, Rob Full episode transcription (AI Generated)

Students hacked a locked exam

Rob Alvarez (00:00): What is the difference between a group of students hacking a high security exam and a multi-million dollar enterprise AI rollout? The answer might be the reason your team probably isn’t using the AI tools you just bought for them. Picture this: a lockdown, proctored, face-to-face, supervised online exam. The security was very real. Students still got ChatGPT to answer questions for them live inside that exam, in that locked environment, through a Chrome extension. Nobody gave them a license, nobody trained them, there was no change management program. And the adoption was instant, total, and creative enough to beat the security. Meanwhile, companies are spending millions and billions on AI rollouts where the licenses get bought and nobody opens the app. Same tech, opposite outcome.

Same tech, opposite outcome

Rob Alvarez (00:52): I’m Rob, I’m the host of Professor Game, and I head engagement in Europe at the Octalysis Group, where we help companies turn motivation into real outcomes. And today I’ll show you why the difference between those two scenarios isn’t the AI. It has everything to do with the motivation. I’ll break down the accidental motivation engine inside the exam and hold it up right next to the enterprise that actually fails with this implementation, and leave you with a diagnostic question you can ask your own team. And of course, if you like looking at the Core Drives being pulled apart in real situations like this one, that’s pretty much what our Core Drives in the Wild email series is all about. A few days of real corporate cases, the ones that got motivation right, the train wrecks, and the read through this whole framework. And of course, my own take through my experience. The link is below in the description if you want it. Now let’s get into this one.

Adoption was never the problem

Rob Alvarez (01:44): The dominant frame for AI in organizations nowadays is an adoption problem. How do we get people to use the tool? But the students prove that the adoption was never something difficult. Give a human enough reason and they’ll adopt a tool faster than any corporate rollout plan could ever dream of. They’ll out-engineer your security to get to their objective. So if adoption is actually effortless when motivation is high, then every failed enterprise rollout isn’t a tooling failure or a training failure at all. It is a motivation failure wearing a tooling costume. The more capable AI becomes, the more the bottleneck becomes the human layer. Capability stops being a real constraint, and motivation becomes the whole game.

The exam’s accidental motivation engine

Rob Alvarez (02:39): But let’s take a look at why the students’ motivation was so well built. In fact, completely by accident. Through the Octalysis lens, the exam was an unintentional motivation engine pointed at the wrong outcome. In Octalysis terms, the business metrics were not being really targeted. Enter Core Drive 8, Loss & Avoidance. Failing the exam is real, immediate, and high stakes loss. You’re driven into action so that something that is really bad for you doesn’t happen. That’s a very dominant driver here. It’s enormous, in fact. And don’t get me wrong, this isn’t about justifying students who didn’t study for the exam, or who actually spend their time trying to go through the security rather than studying. I’m not talking about that. It is just about facing the reality that oftentimes it is something that you need to consider it in your design rather than just try to upfront fight against. Then there’s Core Drive 6, Scarcity & Impatience. You only get one shot, limited time window, no second chance at the moment. This scarcity is honest, it’s true, and it’s very real for every single student. That is a ferocious motivation stack. Core Drive 2, Development & Accomplishment: making progress, clearing this hurdle for them, the passing grade, just moving forward. This is something that is broken. It’s the extrinsic progression path that leads to an extrinsic diploma, not the genuine interest for learning and actually getting better. But again, face the facts and work with and through them. And then we have Core Drive 6: Scarcity & Impatience. One shot, timed window, no second chance in the moment. This scarcity is truthful. It’s honest. It is very real. That is a ferocious motivation stack.

Almost entirely Black Hat motivation

Rob Alvarez (04:31): Notice that it’s only, almost only Black Hat. The same family drives that the airline is also using on you on the loyalty program. Except here, they were strong enough to make people build technical workarounds in real time. Here’s the part that matters for you: the system got exactly the behavior it actually rewarded. It rewarded producing the right answer under pressure. So a tool that produces the right answer under pressure was almost a rational, almost inevitable response from the students. They weren’t subverting the system, they were responding to it. Now that points to a much bigger problem with how we structure exams in the first place. Yes, indeed. Whether they ever measured what we thought they did, but that is a completely separate episode on its own. So we’ll leave it apart for today.

Why the funded enterprise stalls

Rob Alvarez (05:18): Now look at the flip side of this coin. An enterprise with a paid license, training, IT support, leadership mandate, everything that the students never got. And adoption completely stalls. Why? Because none of those things are actual motivation. Let’s look at the absence of the very drives that the students were up against. There’s no real Loss & Avoidance. Nothing bad happens to me personally, or even professionally, if I don’t touch the AI tool. My old workflow definitely gets the job done. There’s no Development & Accomplishment. It doesn’t visibly make me better at something I care about. It’s framed as a company efficiency plan, not my win at all. There’s no real Scarcity or Impatience for this. It is available for everyone, and everybody, just like me, is supposed to have access to it. On top of that, if you don’t have these motivations, you don’t either have something like Epic Meaning or Ownership. It’s something that’s being done onto me, not something that is mine. The enterprise bought the most capable tool and surrounded it with zero motivation. The exam accidentally built this ferocious motivation engine we talked about around basically a free chatbot. Capability was never the variable.

Adoption and direction both matter

Rob Alvarez (06:30): What does this mean for you and future implementations? First thing, adoption. The more powerful the tool, the more its entire value depends on whether anyone is motivated to use it. The motivation layer is now the highest leveraged thing to design, not the tooling. Second, and this is the very uncomfortable one, direction. Even once the tool is being adopted, it only helps moving the needle if it is actually pointed and designed for hitting the right goal, and the motivation decides where it actually gets pointed. The students aimed AI at passing the exam, not at learning something new. They didn’t just prove that motivation drives adoption effortlessly, they also proved something sharper: motivation pointed at the wrong goal gives you flawless adoption of exactly the behavior you didn’t want. That’s the deeper version of the whole idea. Your motivation architecture decides both whether the AI gets used, and what it really gets used for.

Why behavioral design matters with AI

Rob Alvarez (07:41): So what does that mean? As AI removes the capability constraints, the human motivation layer becomes the only constraint that is left. That’s it. This is exactly why behavioral design matters more in the AI era, not less. The smarter these tools get, the more the bottleneck is us, the people, never the tech.

Your diagnostic question for today

Rob Alvarez (07:55): Here’s your prompt for today. If you’re running an AI initiative right now, stop asking, “Is the tool good enough?” or “Have we trained our people in the tool?” Although these are important, of course. Ask instead: what does my team actually gain personally, individually, professionally by using this? And what do they lose by ignoring it? If your honest answer is nothing much either way, no rollout plan is going to save it. You’re on a motivation vacuum, and that tool will sit unused no matter how capable it is. The students had a crystal clear answer to both questions. Does your team have an answer to them? Here is the whole reframe for you to take away: most AI initiatives are being run as only a technology project. They’re actually motivation-driven design projects wearing a technology costume. That’s one Core Drive situation read out in the wild: an exam that ferociously built this motivational engine, and an enterprise failing because they spent millions building no motivational engine at all. And if that’s the kind of thing that you want more of, that’s exactly what I do in our free guide, Core Drives in the Wild. A few days of real corporate cases, the wins, the train wrecks, all pulled apart through the view of the Core Drives and of course my own perspective and experience. You’ll get also regular emails after that, but the series is the part that I think right now you’ll actually be looking forward to. If you want it, the link is below in the description. And Engagers, as always, at least for now and for today, it is time to say that it’s game over. End of transcription