Putting Gamification in its Place: The War on Words
Around 2011, the field I had been working in since 2003 finally got a name, and almost immediately a small civil war broke out over whether anyone should be allowed to use it. Academics called the word “gamification” intellectually dishonest. One serious-game theorist publicly labelled it “exploitationware.” Practitioners shrugged, kept charging clients for it, and watched the search volume curve climb anyway.
I had a decision to make. I had spent eight years quietly building what would become the Octalysis Framework while the discipline had no agreed name at all. Suddenly there was a name, and the smartest people in the room were telling me to drop it. I kept it. This post is about why, what the critics got right, what they got wrong, and what the term-war taught me about how a discipline actually establishes itself.
⚡ Speed Run Notes
- The 2011 fight over the word “gamification” was led by sharp people: Ian Bogost called it “exploitationware,” Sebastian Deterding dismantled Gabe Zichermann’s book chapter by chapter, and Jane McGonigal preferred her own framing entirely.
- The critics were right that most early gamification was bad. They were wrong that the fix was a better word. Bad design under a better label is still bad design.
- I kept the word because abandoning it meant restarting every elevator pitch from scratch. The term was a beachhead, not a thesis.
- The real distinction is human-focused design vs. function-focused design. The label is downstream of that distinction; the work is upstream.
- The controversy itself acted as a Core Drive 7 (Unpredictability & Curiosity) attractor. The fight drove the search volume the polite version of the field never could have.
Table of Contents
In This Article
About the Creator of the Octalysis Framework
Yu-kai Chou created the Octalysis Framework after studying gamification since 2003, years before the term entered mainstream vocabulary. As a Human-Systems Architect & Behavioral Designer, his framework has been applied by LEGO, Microsoft, Porsche, Coca-Cola, Salesforce, and MrBeast, impacting over 1.5 Billion Users.
Chou has taught the Octalysis methodology at Harvard, Stanford, Yale, Tesla, Google, BCG, and IDEO.
His work has been cited by Harvard, Stanford, MIT, Forbes, Wall Street Journal, Wired, US Department of Energy, NIST, NSF, NCBI, US Department of Education, ClinicalTrials.gov, and 3,700+ more academic publications. Explore his books here.
This particular post is one I have been threatening to write for over a decade. I was inside the field when the term-war broke out. I attended the GSummits where Gabe Zichermann was filling rooms. I read Sebastian Deterding’s chapter-by-chapter teardown of Gamification by Design the morning it went live. I had dinner conversations with people on both sides who could not stand each other. I built the Octalysis Framework while the rest of the field was arguing about whether the field should exist. So when I take a position on what the word means and why it survived, I am not summarizing a Wikipedia article. I am reporting from inside the room.
Why the Term Got Attacked
To understand the heat in 2011, you have to understand who was throwing it. These were not casual complainers. They were some of the sharpest minds in interactive design.
The most famous shot came from Ian Bogost, the Georgia Tech game scholar and designer of Cow Clicker. In a 2011 piece for The Atlantic, he labelled the entire practice “exploitationware” and argued the term “gamification” was a marketing-driven con designed to extract behavior from users without giving them anything that resembled actual play. Bogost was not a fringe voice. He was a respected academic with a long track record of taking games seriously, and he was telling the world that what we were doing was not games and was not legitimate.
The second front was Sebastian Deterding’s. Deterding is the Ph.D. researcher who has produced more careful, citation-worthy writing on the motivational structure of game design than almost anyone in the field. In 2011 he and Gabe Zichermann had what I described in Actionable Gamification as a debate of epic proportions. Zichermann is a brilliant marketer, the speaker who built the GSummit (the largest gamification conference in the industry at the time), and the author of Gamification by Design. Deterding wrote a public chapter-by-chapter response explaining why he considered Zichermann’s book flawed and inaccurate. The blog post was almost longer than the book itself.
One of Deterding’s specific complaints was that Gamification by Design treated serious games and advergames as examples of gamification. Wikipedia defines serious games as “a game designed for a primary purpose other than pure entertainment”: training, education, healthcare, and the like. BusinessDictionary defined advergames as “a video game which in some way contains an advertisement for a product, service, or company.” Both of those definitions have the word “game” in them, which is a problem. You cannot really gamify something that is already a game. It is like liquefying liquid. You can apply better game design to a game, but you cannot gamify it.
The third front was softer but more public. Jane McGonigal, the author of Reality Is Broken, did not attack gamification the way Bogost did, but she pointedly distanced her own work from the label. She talked about “gameful design” and “alternate reality games” and let the gamification crowd argue with itself. For someone trying to sell what we were selling, having the most famous voice in game-for-good consistently use a different word was its own kind of headwind.
So the case against the word, in 2011, was roughly this: it is intellectually sloppy because it covers too many things. It is ethically suspect because it implies you can extract behavior without earning it. It is being used by marketers to oversell what is mostly slapping points and badges onto a website. And the people loudest about defending it are not the people doing the most rigorous work.
That is a strong case. I want to be honest that it was a strong case at the time, and I want to be honest that parts of it have aged well.
What the Critics Got Right
Three things, mostly.
First, the critics were right that most early gamification was bad. The 2011 wave of “let us slap points, badges, and leaderboards on every dashboard” was, with very few exceptions, lazy. It treated the human inside the system as if they were a pigeon waiting for a pellet. It assumed that any extrinsic reward layered on top of any boring task would somehow make the task non-boring. That assumption is false, and the academic literature on the over-justification effect had already shown it was false. Bogost was within his rights to be angry about people charging Fortune 500 fees to do work that did not survive a freshman psychology textbook.
Second, the critics were right that “exploitationware” is a real failure mode. There is a version of gamification that uses Core Drive 8 (Loss & Avoidance) and Core Drive 6 (Scarcity & Impatience) to coerce users into behavior they will later regret. I now have a whole vocabulary for this (black-hat design, the post-fiesta drop, burnout) and an entire framework distinction between black-hat and white-hat motivation. But in 2011 that vocabulary did not exist publicly, and the loudest evangelists were not making the distinction. The critics were responding to a real abuse pattern.
Third, the critics were right that the word “gamification” was carrying water it could not really carry. The term smuggles in a metaphor, that what you are doing is “making things into games,” and that metaphor does not survive five minutes of inspection. You are not turning your call center into Halo. You are designing a system that takes human motivation seriously. Calling that “gamification” is a useful shorthand and a misleading one at the same time. Both can be true.
If I had only ever read the critics, I would probably have agreed with them. The reason I did not agree with them, and still do not, is that they were attacking the wrong target.
What the Critics Missed
The critics treated the word as if it were the disease. It was not. The disease was bad behavioral design. The word was a symptom and a vehicle, but the disease itself would not have gone away if the field had been renamed “engagement engineering” or “motivational architecture” or “gameful design.”
Three things the critics underweighted.
The first is that any new discipline goes through a period where the word for it is fuzzy and oversold. “User experience” was mocked when Don Norman coined it at Apple in the 1990s. “Growth hacking” was mocked when Sean Ellis coined it in 2010. “Behavioral economics” was mocked by classical economists for two decades. The fuzziness of a new word is not evidence that the underlying discipline is fake. It is evidence that the discipline is new enough that its scope has not been bounded by the standard academic gatekeeping process. Bounding it takes a generation, not a blog post.
The second is that a term that gets attacked also gets searched. The fight between Deterding and Zichermann did more for gamification’s mainstream visibility than any cooperative effort would have. Search volume for “gamification” climbed roughly in lockstep with the controversy in 2011 and 2012. Conferences filled. Books got contracts. Universities started offering courses. Some of that was hype, and some of it was real. The point is that the controversy was its own marketing budget. Inside the Octalysis lens, this is a Core Drive 7 (Unpredictability & Curiosity) attractor. Drama drives clicks. The polite, properly-scoped version of the term would have stayed in three academic journals and died there.
The third is that critics writing from inside academia underestimated how badly practitioners needed a category label to sell into. Imagine you are a designer in 2011 walking into a Fortune 500 office to pitch behavioral redesign of a learning platform. If you say “I do gamification,” the executive across the table has a folder of trend pieces about it and is willing to listen. If you say “I do gameful behavioral architecture rooted in self-determination theory,” you get walked back to the lobby. The label was the elevator pitch. The label was the budget line item. The label was what allowed thousands of practitioners to do real work inside organizations that would have otherwise rejected the work for not having a category.
This is the part I think Bogost and Deterding missed because they did not have to sell the work. They had tenure-track positions and academic standing. They could afford to wait for the perfect terminology. Working designers could not.
Why I Chose to Keep the Word
I had a quiet moment in 2012 where I had to decide whether to publish under the gamification label or under something else. I had been studying the field since 2003, eight years before the word existed. I had built the early Octalysis diagrams. I had taught at Stanford. I had spent years saying “behavioral design rooted in game psychology” because there was no shorter phrase available.
I picked gamification. Three reasons.
One: the word had achieved beachhead status. In military terms, a beachhead is a piece of ground you have taken at cost from which you can advance. The word “gamification” was that beachhead. It was understood, badly, by tens of millions of people. Abandoning it for a more precise term meant restarting public education from zero. I was not going to do that. I was going to take the word everyone misunderstood and slowly correct the misunderstanding.
Two: the word created identity. Practitioners who used “gamification” felt part of a movement. Inside the Octalysis lens this is Core Drive 4 (Ownership & Possession) and Core Drive 5 (Social Influence & Relatedness) doing their work. People wore the label. People referred clients to people who shared the label. People showed up to GSummit because they wanted to be in a room with their tribe. If you split the tribe across “gamification” and “gameful design” and “engagement engineering” and “behavioral architecture,” you do not get a stronger movement. You get four weaker ones. I would rather argue inside one tribe than try to organize four.
Three: the work was bigger than the word, but the word was load-bearing for now. I have always cared more about the underlying behavioral architecture than the label. The 8 Core Drives do not care what you call the field. Human motivation works the same whether you call it gamification or motivational architecture or applied behavioral design. But the label was load-bearing in the same way scaffolding is load-bearing. The building eventually stands on its own, but on day one the scaffolding is what holds it up. In 2012 the field needed scaffolding, so I wrote and taught and consulted under the gamification banner.
I will note that fourteen years later, the field is still standing under the same banner. That is not nothing.
Human-Focused Design vs. Function-Focused Design
Here is the framing I have used since the early 2010s, and the one I would offer anyone walking into the term-war today.
Most systems are designed function-focused. The designer assumes the user has motivation and engineers the shortest, most efficient path from intent to outcome. Function-focused design asks: how do I get this task done with minimum friction? It is the default mode of every engineer, every operations team, every product manager who has ever lived. It is also responsible for almost every confirmed-by-blank-screen, you-completed-a-task, please-rate-this-experience non-event you have ever sat through.
Human-focused design starts from the opposite assumption. The user does not necessarily have motivation. Building motivation is part of the design job. Human-focused design accepts some efficiency loss (extra screens, extra animations, extra narrative, extra ceremony) in exchange for the user actually wanting to do the thing. It treats the human inside the system as a being with feelings and preferences and a finite supply of attention rather than a deterministic input-to-output function.
That is what I mean by gamification. Not points. Not badges. Not leaderboards. Those are outcomes of human-focused design, sometimes the right outcome, sometimes the wrong one. The discipline is the shift from function-focused to human-focused. The label is “gamification” because the gaming industry was the first industry to figure out human-focused design and execute it at scale. Games have no other function except to please the human inside, so game designers had to get this right, and they did. Every other industry is now learning from them.
If you read Bogost’s exploitationware essay through that lens, his actual complaint was not with human-focused design. His complaint was with people doing function-focused design and slapping a points layer on top to make it look human-focused. He was right to be angry about that. The fix, though, was not to abandon the label. The fix was to do the work the label was supposed to point at.
I have written more about this distinction in What Is Gamification and the human-focused design literature on this site. The shorthand: gamification is a synonym for human-focused design with a more memorable name and a more controversial reputation. Both of which turn out to be features, not bugs.
What This Means for Practitioners Today
The term-war is mostly over. Bogost has moved on to other arguments. Deterding kept publishing. Zichermann kept speaking. McGonigal kept her own vocabulary. The label “gamification” lost some prestige in academia and gained an enormous amount of practitioner mass in industry. The Octalysis Framework has been applied to products reaching over 1.5 billion users. The word survived.
For people doing this work in 2026, here is what I would take from the history.
First: do not pick fights with respected critics by dismissing them. Bogost was not stupid and Deterding was not lazy. They were responding to real abuses, and the field is healthier because they pushed back hard. If you are a practitioner who has never read the exploitationware essay, go read it. Every working gamification designer should be able to articulate why the critics had a point.
Second: do not treat the word as the work. The word is a shipping container. What goes inside the container is the actual design. If your design is bad, calling it gamification will not save it; if your design is good, calling it something else will not improve it. The Octalysis Framework, the 8 Core Drives, the white-hat versus black-hat distinction, the four experience phases: those are the work. The word is the address you mail it to.
Third: notice the meta-pattern. Every emerging discipline goes through a phase where the loud people oversell, the rigorous people overcorrect, and the practitioners just keep building. UX did this. Growth hacking did this. Behavioral economics did this. AI prompt engineering is doing it right now. The honest move, when you are inside one of those phases, is to keep building under whatever label has achieved beachhead status while quietly raising the standards of the work itself. That is what we did with gamification. That is what someone is going to need to do with whatever word is contested next.
The concrete present-day implication: when a client tells you in 2026 that they want “AI personalization” or “intelligent engagement” or some new label that has not stabilized yet, treat the label the way I treated gamification in 2012. Take the beachhead, keep the tribe, ship better work than the loud people on either side, and let the underlying behavioral architecture do the long-run convincing. The word will sort itself out. The work has to be there now.
Related Reading
- What Is Gamification: A Deep Dive Into Gamification
- Octalysis: The Complete Gamification Framework
- Black Hat vs. White Hat Gamification
- Actionable Gamification: Beyond Points, Badges, and Leaderboards