How More Organizations Are Playing At Work

In 2013, Adam Penenberg published Play at Work: How Games Inspire Breakthrough Thinking, and the book became one of the loudest signals that gamification had crossed the line from buzzword to boardroom. Penenberg, a journalism professor at NYU and a contributor to Fast Company and the New York Times, walked through case after case of organizations stitching points, badges, simulations, and competitions into the fabric of daily work. Google. Microsoft. Cisco. Target. Canon. Lexus. The list was long, the numbers looked good, and the press loved it.

I read it that year as someone who had already been in the gamification trenches for a decade. My reaction was complicated. Penenberg gets the big picture right: yes, organizations are absolutely playing at work, and yes, well-designed games can produce results that traditional management cannot. But most of the workplace gamification deployments his book celebrates are still doing it badly. They are running Black Hat mechanics on people who should be motivated by White Hat ones, and the bill for that mistake comes due eventually. Usually it lands around the time the leaderboard becomes a surveillance dashboard and the highest-scoring employee turns out to be the one gaming the metric.

This post is my honest take on what Penenberg got right, what most workplace gamification still gets wrong in 2026, and the design rules I use when a CHRO calls me asking why their points-and-badges rollout is making everyone miserable.

⚡ Speed Run Notes

• Penenberg’s Play at Work (2013) was right that organizations are gamifying everything. The mistake most of them made (and still make) is gamifying the job itself instead of the citizenship behaviors around the job.
• Black Hat workplace gamification (point surveillance, leaderboard pressure, loss-aversion timers) gets short-term compliance and long-term burnout. White Hat (Epic Meaning, Empowerment of Creativity, Social Influence) gets the kind of engagement that actually compounds.
• The Microsoft Mountain Bike disaster is the canonical failure: a manager won the prize for finally doing his actual job. That is what happens every time you put points on top of a job description.
• Fold It, Galaxy Zoo, Eye Wire, Whale FM, and Ancient Lives work because they are voluntary, meaningful, and creative, not because they are clever. Cisco My Plan Net works for the same reason.
• Designer rule: gamify what people choose to do, not what they are told to do. Cross that line and you’ve built a monitoring tool wearing a fun-colored hat.

Table of Contents

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.

My view on Penenberg’s argument matters here because I have spent the last twenty-plus years inside workplace gamification engagements that look, on paper, exactly like the case studies he cites. I worked alongside Ross Smith at Microsoft on the Beta 2 Game and the Language Quality Game that helped Windows 7 ship in 99 languages. I have advised consumer brands and Fortune 500 employers on what to do after their first points-and-badges rollout collapses. The contrast Penenberg describes between great workplace games and exploitative ones isn’t theoretical for me. I have watched both ship from inside the room.

What Penenberg Got Right

Penenberg’s biggest contribution in Play at Work is just naming the trend honestly. By 2013, gamification at work had stopped being a Silicon Valley curiosity. According to the Entertainment Software Association, 70% of major employers were already using gamification to enhance performance and training. Penenberg projected that 70% of the world’s 2,000 largest firms would be running some form of workplace gamification by 2014. That number turned out to be conservative.

He also gets the diversity right. Play at Work doesn’t pretend gamification is one thing. The book moves from Google’s internal currency Goobles, used to regulate server resource allocation and as betting tokens for internal market predictions, to Microsoft’s training and consumer-facing Office tutorials, to the drag-and-drop simulation Canon uses to train repair tech specialists on virtual copy systems, to the sophisticated computer simulation software Japanese engineers at Lexus use to test vehicle safety. These aren’t all the same kind of system, and Penenberg never tries to pretend they are.

The Cisco numbers in Play at Work are the headline most readers remember. Cisco was able to boost their sales by 8-12% while reducing call time by 15% by deploying a sims-style game called My Plan Net, where sales executives take on the roles of CEOs of different service providers so they can understand how those CEOs make decisions and what problems they need to solve. With that insight, sales reps developed sharper pitches and the strategies needed to lift performance. The result is real, and the design is interesting because the win condition is empathy, not output.

Target’s cashier game, also in the book, is the case I see consultants cite most often when they want to argue gamification is “proven.” The interface lives directly on the cash register screen and shows cashiers their average speed per transaction. According to Target, 88% of transactions regularly meet the company’s appropriate speed standards, and employees are motivated to enhance their efficiency because scores influence their salaries and promotions. I’ll come back to the Target example, because it is also the cleanest illustration of where Penenberg’s optimism gets dangerous.

Penenberg also covers the medical field’s use of simulations to help physicians learn to perform complicated surgical operations while gaining experience that improves their timing, decision-making, and precision. He nods toward Twitter as a game where interesting tweets grow your retweet and follower counts, lottery games like Powerball and Mega Millions, and Nissan’s in-car efficiency competitions. Even when the examples are weaker, the underlying observation holds: humans treat almost any feedback-rich, scored environment like a game whether the designer intended it or not.

What I respect most about Play at Work is the framing in the closing chapters. Penenberg explicitly hopes games will help humanity accomplish great things, not act merely as manipulative tools that serve as a means to an end. He is clear that game design has the potential to be gimmicky, and that for systems built to lift performance in the work force, there is a real risk of exploiting employees. He calls his shot. The book ends on a moral question, not a how-to.

Research on Gamification: Why Games Hijack the Brain

Penenberg also brings the brain science, which is the part of the book most managers skim and shouldn’t. In an interview with Forbes, he discusses the appeal of games from the perspective of brain researchers. Game environments are designed to provide relatively immediate experiences of gratification, particularly through feelings of achievement and accomplishment. That density of feedback is rare in real life situations, where the gap between effort and recognition is usually measured in months or quarters.

The feel-good sensations that make us want to keep playing originate from surges of a neurotransmitter called dopamine. Scientists believe these pathways were originally shaped by the survival instincts of the earliest phases of human evolution. Our ancestors had to constantly escape danger and acquire their means for sustenance, and that is how they derived their sense of accomplishment. The dopamine system was tuned to make survival behavior feel rewarding.

In the modern world, games provoke similar drives. Players have to escape from negative consequences and use strategic thinking to win rewards. The mechanics trigger dopamine pathways that were originally aligned with survival, but they are stimulated within controlled contexts where the stimuli are pertinent to the lives we now live. Penenberg cites Gary Marcus, a research psychologist at New York University and the author of The Haphazard Evolution of the Human Mind, who argues that our pleasure centers consist of multiple pathways that can be selectively activated by games and other forms of “pleasure technologies” like movies and music.

Here is the part most workplace deployments miss. Knowing that games hijack ancient survival circuits is not a green light to use those circuits on your employees. It is a warning. The same dopamine loop that makes a well-designed citizenship game feel meaningful will, in a poorly designed performance dashboard, feel like a slot machine running on top of someone’s livelihood. The neuroscience cuts both ways.

What Most Workplace Gamification Gets Wrong

Now the harder part. Play at Work reads, in places, like a victory lap. The reality on the ground in 2013, and on the ground in 2026, is messier. Most workplace gamification programs I have audited fail in a recognizable pattern, and the pattern isn’t about technology. It is about which Core Drives the program is engaging.

The Octalysis Framework breaks human motivation into eight Core Drives. Four sit on the right brain and tend to be intrinsic, expressive, and sustainable: Core Drive 1 (CD1): Epic Meaning & Calling, Core Drive 3 (CD3): Empowerment of Creativity & Feedback, Core Drive 5 (CD5): Social Influence & Relatedness, and Core Drive 7 (CD7): Unpredictability & Curiosity. Four sit on the left brain and tend to be extrinsic, transactional, and goal-driven: Core Drive 2 (CD2): Development & Accomplishment, Core Drive 4 (CD4): Ownership & Possession, Core Drive 6 (CD6): Scarcity & Impatience, and Core Drive 8 (CD8): Loss & Avoidance.

The framework also separates White Hat motivation (CD1, CD2, CD3) from Black Hat motivation (CD6, CD7, CD8). White Hat makes you feel good about the activity. Black Hat creates urgency and pressure that gets compliance fast but leaves you feeling used. CD4 and CD5 sit in the middle and can lean either way depending on design. The full breakdown lives in Black Hat vs White Hat Gamification if you want the long version.

Most workplace gamification deployments I audit are running almost entirely on Black Hat / Left Brain mechanics. Points decay if you don’t earn them this week (CD8). Leaderboards reset Friday at 5pm and only the top three get the prize (CD6). The dashboard turns red when you fall behind your team average (CD8 again). The system is brilliantly tuned to extract short-term compliance and absolutely lethal to long-term engagement. Six months in, employees stop trusting their managers, the word “gamification” becomes a slur in the breakroom, and the consultant who deployed the system has already moved on to the next client.

The diagnosis isn’t that points and leaderboards are evil. It is that points and leaderboards aimed at job duties activate the survival circuit Penenberg’s brain research describes. The survival circuit, applied to your livelihood, is just stress with a progress bar.

The Black Hat Workplace Trap

Let me make this concrete. Go back to the Target cashier example. The interface lives on the cash register and shows cashiers their average speed per transaction, with scores feeding into salary and promotion decisions. Penenberg presents this as a success because 88% of transactions hit the speed standard.

From an Octalysis lens, here is what that system actually is. The cashier’s job description already includes scanning items at a reasonable speed. The “game” doesn’t add a voluntary citizenship behavior on top. It instruments a job duty. The scoring isn’t separate from compensation, it directly feeds it. The cashier isn’t volunteering anything. They are being measured, in real time, against a standard that determines whether they keep their job. That is not Core Drive 3 (CD3): Empowerment of Creativity & Feedback. That is Core Drive 8 (CD8): Loss & Avoidance, dressed up as a leaderboard.

This is what Ross Smith and I started calling the “Do Your Job Game” trap. It is the most common (and most destructive) mistake in workplace gamification: gamifying activities that are already part of someone’s job description. It always backfires. When game rewards overlap with compensation, people get weird, emotional, and defensive. The internal dialogue becomes: “Am I doing this to earn points in the game, or am I doing this to get a paycheck? Am I in trouble if I don’t play?” That confusion does not motivate. It creates anxiety.

The cleanest Microsoft case study on this is what we now call the Mountain Bike Disaster. During Microsoft’s Beta 2 Game in the Windows Vista era, engineers earned points by enrolling machines into overnight testing. One person suddenly rocketed to 400 points when the typical score was 60. He won the mountain bike. The problem: he managed a testing lab that was already supposed to enroll all machines overnight. It was literally his job, and he hadn’t been doing it. The game rewarded him for finally performing his basic responsibility, while other participants who were actually volunteering their personal machines watched someone win for catching up on neglected duties.

Ross Smith likes to invoke Johan Huizinga’s concept from Homo Ludens: games operate inside a “magic circle” that is separate from ordinary life. Golf isn’t fun if you pick up the ball and drop it in the hole. The rules and constraints inside the circle create the experience. The magic circle does not like the day job. Overlay a game on mandatory duties and the circle breaks. The voluntariness that makes play feel like play disappears.

You can see the same dynamic in companies that gamify code commits, support tickets resolved, calls handled per hour, or sales calls dialed. Every one of these is a job duty. Every one of these systems eventually produces the same set of pathologies: people gaming the metric, people resenting the leaderboard, the highest scorers being the ones who care least about quality, and managers losing the credibility they had before they installed the dashboard.

The Black Hat workplace trap isn’t an aesthetic preference. It is a structural problem. CD6 and CD8, applied to compensated activity, do not behave like CD6 and CD8 in a video game. In a game, you can quit. At work, you can’t, which means the urgency stops being playful and starts being coercive.

What White Hat Workplace Gamification Looks Like

Now flip it. The workplace games that age well, the ones still running five years later, the ones employees ask to keep, share a different DNA. They engage CD1, CD3, and CD5 first, and they layer the Left Brain Core Drives on top only after the Right Brain foundation is in place.

The Beta 2 Game at Microsoft, done right, is the canonical example. After the Mountain Bike Disaster, Ross’s team rebuilt the game around a Hangman mechanic on top of existing telemetry. Spell B-E-T-A by enrolling your personal machine into overnight testing at increasing commitment levels. B was enroll once, just to learn the process. E was three out of five days in a week. T was five consecutive days. A was 20+ days out of 30. The result, in Ross’s words, was mind-boggling: VPs running into his office asking “where’s my E?”

What changed? The activity being gamified was no longer anyone’s job. Enrolling personal hardware into overnight testing was a voluntary citizenship behavior. The game recognized something people were doing out of goodwill and made it visible. The magic circle held.

The Language Quality Game, Windows 7’s secret weapon, is the prettier sibling of the Beta 2 Game. Localizing Windows requires native speakers to review every dialogue string, but marketing, HR, and legal staff in international offices don’t want to install unstable beta builds on their work machines. The team built a lunch-break game where employees viewed screenshots of localized UI, circled errors, and dragged them to a “has a problem” bucket. No beta installation required. Windows 7 became the first version of Windows to ship in 99 languages simultaneously. A senior executive initially said “There’s no way we’re doing this. We don’t play here. We work.” The team built grassroots support by testing with willing international subsidiaries, then returned with data: three regional GMs were sending org-wide emails saying “On Tuesday, we’re all going to take time and play this game.”

The Penenberg-era examples that hold up to this lens are the ones I still recommend in keynotes. Fold It is the obvious one: participants come up with different ways to fold proteins, the results are scored by scientists to see which ones could create the strongest impact in real-life situations, and the game has produced peer-reviewed protein structures. Galaxy Zoo: players collaborate to classify astronomical objects like planets, stars, and solar systems. When the game was first designed, the team estimated a year to classify a million objects. It took a day to classify 50 million. Eye Wire, developed at MIT, lets participants map retinal connections so scientists can learn more about visual perception. Ancient Lives: players help to decode ancient texts from Egypt. Whale FM: oceanologists listen to sounds made by orcas and match them to similar-sounding calls.

Notice the pattern. Every one of those games gamifies something that is not anyone’s day job. Every one engages CD1 (Epic Meaning & Calling) before any other Core Drive. Every one offers Empowerment of Creativity through real choices and real feedback rather than instrumented compliance. Every one creates a community of contributors who feel they are part of something bigger than the points.

Cisco’s My Plan Net actually fits here too, when you look closely. The sales rep isn’t being scored on call volume in real time. They are stepping into the role of a CEO making strategic decisions, then carrying that empathy back to their actual work. The game is teaching perspective. CD3 (Empowerment of Creativity & Feedback) and CD7 (Unpredictability & Curiosity) doing most of the work, with CD2 (Development & Accomplishment) layered on quietly. The 8-12% sales lift is the byproduct, not the design target.

Designer Rules for Workplace Gamification

If you are designing or buying workplace gamification in 2026, here are the rules I give every client before they sign anything.

Rule 1. Gamify what people choose to do, not what they are told to do. The line between gamification that engages and gamification that surveils is exactly the line between citizenship behaviors and job duties. Cross that line and you’ve built a monitoring tool with point decorations. Stay on the right side and you’ve made the invisible visible: the help, the volunteering, the going-above-and-beyond that makes organizations actually work but that no performance review captures.

Rule 2. Lead with Right Brain Core Drives. If your design starts with leaderboard rank, countdown timers, and decay penalties, you are leading with CD6 and CD8. Reverse the order. Start with CD1: what is the meaning of this activity? Why does it matter beyond the points? Then CD3: what creative agency does the participant have? Then CD5: who do they get to do this with? Only then layer in CD2 progress markers and the occasional CD6 scarcity moment. The order matters because the foundation determines whether the rest reads as engagement or coercion.

Rule 3. Keep game rewards separate from compensation. The moment a leaderboard rank affects someone’s salary or promotion, the magic circle breaks and you’ve built a performance management system, not a game. Game rewards should be intrinsically valuable (recognition, status, voluntary perks) but never the substitute for the paycheck. Once the two collide, every quirk in the metric becomes a fight between you and the employee, and the employee will always win because they’re the one running the metric.

Rule 4. Design leaderboards so most people can win something. Leaderboards primarily motivate the top percentile. The middle and bottom feel demoralized, and the bottom-tier players work mostly to avoid looking like losers. That is CD8 (Loss & Avoidance), which burns out fast. Build multiple leaderboards by activity type, time period, and team. Use custom leaderboards filtered by email parameter so people can compare against their actual peer group. Show top 10 plus the participant’s personal rank so they always know where they stand without scrolling past hundreds of names. Cap each leaderboard’s duration at a month so the rankings don’t calcify into permanent hierarchies.

Rule 5. Make sure everyone can be in the top 10 of something. A programmer who joined late should still be able to lead the “this week” board. A new hire should be able to top the “rookie” leaderboard. A non-competitive contributor should be able to anchor a cause-based team where they earn donations for a non-profit they care about. Multiple visible leaderboards mean multiple paths to glory, which means more people stay engaged past week three.

Rule 6. Treat the executive sponsor as a player, not a spectator. When a VP actively participates and their progress is visible, the entire organization takes the game seriously. The worst case is a VP with a profile that exists but stays inactive, because that signals the game does not matter. Make the executive sponsor’s participation a design constraint, not a marketing afterthought.

Rule 7. End the game. Permanent leaderboards calcify. If the #1 player has 1,100 points and #3 has 50, it is game over for everyone except #1. Run finite seasons. Reset visibly. Let new contributors enter with a clean slate.

If your vendor’s pitch deck doesn’t address Rules 1, 3, and 7, you don’t have a workplace gamification system. You have a surveillance dashboard with seasonal banners.

Exploitation Versus Accomplishing Great Things

Penenberg ends Play at Work on the right note. He wrote the book hoping games will help humanity accomplish great things, as opposed to acting merely as manipulative tools that serve as a means to an end. He cites Fold It, Galaxy Zoo, Eye Wire, Ancient Lives, and Whale FM as proof of what is possible when game design points outward at meaningful problems.

He also predicts, plainly, that along with great developments in gamification, there will be poor ones. Game design has the potential to be gimmicky. For systems built to enhance performance in the workforce, there is the real risk of exploiting employees. The difference between good games and bad games, in his framing, is the quality of the design to provide rewarding experiences for the players.

I would push his framing one click harder. The difference between good workplace games and bad ones isn’t only design quality. It is the choice of what to gamify in the first place. A beautifully designed surveillance dashboard is still a surveillance dashboard. A scrappy citizenship game with rough graphics and a manual leaderboard is still better than a $2M enterprise platform that turns sales calls into a slot machine.

If your organization is about to deploy workplace gamification, the first question is not “what game mechanics will we use?” It is “what behavior are we trying to make visible, and is that behavior something employees would choose to do if no one were watching?” Get the answer right and you can use almost any mechanic. Get the answer wrong and the most sophisticated platform on earth will turn into a problem.

If improving someone’s work means adding a better sense of meaning, progression, feedback, autonomy, strategy, and social connection, sign me up. I would love to be in that work environment. If “improving someone’s work” means a leaderboard tied to their next paycheck, I’ll pass. So will most of your employees, eventually. They are just polite enough to wait until the year-end engagement survey to tell you.

Related Reading

• The Octalysis Complete Gamification Framework: the full eight Core Drives and how they map to workplace design decisions.
• Black Hat vs White Hat Gamification: the long version of the contrast that runs through this post.
• Workplace Gamification: the category landing page with deeper case studies on Microsoft, Cisco, and others.
• Core Drive 1: Epic Meaning & Calling, the Complete Guide. Why the foundation Core Drive matters more than any leaderboard.
• Core Drive 3: Empowerment of Creativity & Feedback, the Complete Guide. The right way to build the feedback loops Penenberg’s brain research describes.
• Actionable Gamification: the book that walks through the design rules above in full.

WOULD YOU LIKE YU-KAI CHOU TO WORK WITH YOUR ORGANIZATION?