![Why Points, Badges & Leaderboards Fail: Core Drive 2 — Development & Accomplishment [Octalysis]](https://yukaichou.com/wp-content/uploads/2026/04/core-drive-2-development-accomplishment-featured-v8-1024x538.png)
Why Points, Badges & Leaderboards Fail: Core Drive 2 — Development & Accomplishment [Octalysis]
Development & Accomplishment is the engine behind every progress bar, badge, and leaderboard you’ve ever encountered. It’s also the Core Drive that most companies get wrong. They slap on points and expect magic. Here’s why that fails — and how to design systems where people genuinely feel accomplished.
Core Drive 2 is the easiest of the eight to copy and the easiest to misuse. The mechanics look simple, the metrics look healthy, and the engagement looks real. Then a few months in, the badges feel patronizing, the leaderboard demoralizes everyone outside the top twenty, and the points have quietly devalued the whole experience. More game elements won’t fix it. What matters is what “accomplishment” actually means inside a user’s head.
⚡ Speed Run Notes
- Core Drive 2: Development & Accomplishment is the internal urge to make progress, build skills, and overcome challenges users find meaningful. It is why every progress bar in software exists.
- Points, badges, and leaderboards appeal to this drive, but having them does not mean users feel accomplished. The right design question is “do users feel they overcame something they’re proud of?”
- The LinkedIn Progress Bar took two hours to build and lifted profile completion 55%. The lesson is not “add a progress bar”; it is that completion-driven design beats interface polish when the friction is motivational.
- Badges only motivate when they symbolize something earned. A “Clicked My First Button” badge insults users. A Medal of Honor does not. Achievement Symbols reflect achievement; they cannot manufacture it.
- Leaderboards demotivate the moment a new user sees rank 20 with 25 million points. Show the rows directly above and below the user, refresh weekly, or scope to friends. Anything that protects Urgent Optimism.
- Core Drive 2 is a White Hat drive: it makes users feel powerful and satisfied. Without a Black Hat counterbalance, that engagement fades. Points, badges, and leaderboards work inside a system that earns the accomplishment, not as the system itself.
Table of Contents
- About the Creator of the Octalysis Framework
- Where Game Mechanics and Game Techniques Default
- Development & Accomplishment in Games
- LinkedIn Progress Bar
- Gamification with Twitter
- Football vs Soccer
- If you just slap on Badges, Badges will slap your Users
- A Point on Points
- Leaderboard Game Mechanics
- Designing Deep Accomplishment
- Status Seekers and Competence Protectors
- Competence and Mastery Are Two Different Targets
- The Scaffolding Phase
- Why Games Beat Work at Accomplishment
- The Progress Plateau Problem
- Real Money and Perceived Value
- The Endgame Problem
- The Boss Fight Framework
- A Deep CD2 Design Checklist
- Conclusion
- Frequently Asked Questions
- Explore All 8 Core Drives
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.
Below is a manuscript snippet of Gamification Book: Actionable Gamification – Beyond Points, Badges, and Leaderboards.

Where Game Mechanics and Game Techniques Default
Development & Accomplishment is Core Drive 2 of the Octalysis Framework — the internal drive to make progress, develop skills, and overcome meaningful challenges.
This is the Core Drive where people are driven by a sense of growth towards a goal and accomplishing it.
Many people have memories of their kindergarten teachers giving them golden star stickers to emphasize good behavior. Even though the golden star stickers don’t always become real prizes such as brownies, kids still become extremely intent on how many stars they are getting, and whether they deserve more or not. That’s a straightforward demonstration of the effects of Development & Accomplishment, and how easy it is to add into an experience.
This is also the most common implementation of gamification we see in the market, as most of the PBLs — points, badges, and leaderboards — appeal heavily to this drive.
Development & Accomplishment in Games
Almost all games show you some type of progress towards the Win-States. Games break down a user’s challenges into stages — check points, enemies, gems, levels, and bosses. This helps the user feel like there is always progress, and one achievement is coming after another.
Our brains have a natural desire to feel progress, to experience growth, and to see numbers go up. We need Win-States, and it is only a Win-State when it is concrete (being a “state”) and it demonstrates overcoming of a challenge (that’s the “win.”)
If a game is just a long and consistent 40-hour journey without clear stages and bosses to recognize accomplishment, the game is often not engaging.
To display that sense of Accomplishment, some games show you points, others show you levels, badges, stages, progress bars, better gear, victories … the list goes on.
However, just because you see progress towards something does not mean you feel accomplished.
The key to Core Drive 2: Development & Accomplishment is to make sure users are overcoming challenges they can be proud of.
Philosopher Bernard Suits famously defined playing a game as “the voluntary attempt to overcome unnecessary obstacles.” Game designer Jane McGonigal made the line famous in her book Reality Is Broken.
McGonigal points out that the challenge and limitation is what makes a game fun. For example, if golf were just a game with a goal without any limitations, then every player would just pick up the ball and put it into the hole. Everyone would score high, and everyone beyond the “putting a round peg through a round hole” game will probably not be engaged.
By adding unnecessary obstacles — such as requiring the use of a strange stick, certain distances, and landscape hazards — golf becomes fun because the player actually feels accomplished once such challenges are overcome.
Gamification aims to bring that feeling of Development & Accomplishment into everyday experiences within your product or service.
LinkedIn Progress Bar
One of the simplest and best-known examples of Development & Accomplishment in the industry is the LinkedIn Progress Bar.
As the largest professional social network in the world, LinkedIn realized that its value is only as good as the information people choose to put in it.
However, inputting one’s profile and job history on LinkedIn is tedious. Users quickly drop out early in the onboarding process.
LinkedIn realized that simply making the interface easier wasn’t enough; they needed to make it more motivating.
As a result, they introduced a simple Progress Bar (Game Technique #4) on the side of user profiles to show people how complete they were.
Our brains hate incomplete things dangling in front of our faces. When we see a progress bar that is taunting us as only being 35% of a professional, it gives us that extra push to finish the Desired Actions and become complete again as a human being.
The amazing thing is, word has it that this progress bar only took developers 2 hours to code, but improved LinkedIn’s profile completeness by 55% — an amazing change considering how they had spent millions of dollars trying to achieve this same goal. If every single two-hour employee effort produced a 55% increase in your core business metrics, wouldn’t that be something?
Gamification with Twitter
Twitter is yet another great example of Core Drive 2: Development & Accomplishment.
Most people remember Twitter’s innovation being the limitation of 140 characters (which is an interesting balance between Core Drive 6: Scarcity & Impatience combined with Core Drive 3: Empowerment of Creativity & Feedback), but few people remember that another one of Twitter’s key innovations was the one-way follow.
Back in the day, social connections were mutual — either both sides agree to be friends, or no relationship existed.
When Twitter was launched in 2006, it came with this new one-way follow system, allowing users to follow the message updates of people who are awesome, without these awesome people following the users back.
Because of the one-way nature of the relationship, many people saw getting many followers as a true achievement — meaning that everyone wanted to listen to your valuable opinions, even though you don’t give a rat’s pancreas about their opinions.
People tried as hard as they could to “earn” followers — tweeting out witty comments, sharing valuable links, and retweeting others to gain attention. Some even pressured their non-tech friends to follow them, just to look better on Twitter. This became a game for many, where the goal is to reach the highest amount of followers and retweets.
Then, at one point, influential people started to compete with each other to see who had more followers. At the beginning, the implicit comparing came between influencers in the tech world, such as Guy Kawasaki or Robert Scoble. This is the condition of most new tech companies — people in Silicon Valley as well as bloggers loved the platforms, but the mainstream population doesn’t even know it existed yet.
However, because of the “Accomplishment” nature that is baked into Twitter’s DNA, Twitter finally caught massive mainstream attention when celebrities like Ashton Kutcher joined the mix of “follower competitions” against other celebrities, and most notably, the official CNN Breaking News Twitter Channel.
In 2009, Ashton Kutcher publicly challenged CNN Breaking News to see who could first reach 1 Million Followers. Both sides, not wanting to lose the competition, started promoting Twitter and their own Twitter profiles on all their media outlets, hoping to be the first to hit that golden Million. Ashton Kutcher’s fans, who loved his movies but had no idea what Twitter was, also started to write blog posts and make YouTube videos telling everyone else to follow him.
Towards the end, Ashton Kutcher did achieve his victory of reaching 1 Million Followers on Twitter before CNN Breaking News. Again, because he considers this to be a true accomplishment, he brags with joy and pride.
CNN Breaking News, on the other hand, behaved in a sportsmanlike manner, as a big company should. By the time Ashton Kutcher won, CNN Breaking News had 999,652 followers, only mere hundreds away from winning.
Instead of bitterly saying, “So close! We were only off by a few hundred,” they gracefully announced to the world “Ashton Kutcher is first to reach 1 million followers in Twitter contest with CNN” with a “Congrats” on the tweet.
This contest turned out positive for the brand names of both CNN and Ashton Kutcher, but the biggest benefiter was Twitter, which received millions of dollars worth of free press into an audience that was unfamiliar with their platform.
Football vs Soccer
The understanding of Development & Accomplishment might also explain to us why American Football is by far the most popular sport to watch in North America, especially compared to Soccer.
The stereotype goes, compared to Europeans, the average American is more audacious, impatient, and expects more instant gratification. That may or may not be true, but for the sake of argument, let’s go with that statement. Of course, you as my reader are definitely not considered “the average American,” both in a humorous and logical sense, especially if you are not an American to begin with.
In Soccer, it’s a bit harder to keep track of progress and development for the average American. Sure — you can see where the ball is on the court, but it gets kicked back and forth so much, swapping between sides and players, it’s not completely obvious who is winning and who’s gotten ahead when the scores are equal.
Furthermore, after a long grueling battle, many games end up with 0 points on both sides, or at most one to two points, making it hard for the American audience to enjoy the feeling of Development & Accomplishment.
However, in “American” Football (the one where you use your hands), not only are points and scores more obtainable — 51 points vs 28 points, milestones and progress are also broken down to 10-yard runs that happen every few minutes, helping the American audience digest the progress of the game easily. “Oh, he made another 10 yards. YEAHHHHHHHH!!!!”
Not only that, each 10 yards is even broken down further to three to four attempts, so there is a level of suspense and a Countdown mechanism (Core Drive 6: Scarcity & Impatience) to add small challenges and wins within the game.
American Football also often pauses the game whenever something noteworthy happens, in order to remind viewers, “Something just happened! Now is the time to be happy and chest bump your friends!”
Breaking down all the places to cheer, celebrate, and watch more commercials, no wonder American Football is the most popular and biggest moneymaker sport in America.
If you just slap on Badges, Badges will slap your Users
I’ve often talked about how points and badges can ruin good gamification design as the so-called “gamification experts” slap them onto everything they see. However, they are useful tools and have their place in a gamified system.
Badges are what I call “Achievement Symbols” (Game Technique #2). As mentioned, Achievement Symbols can come in many forms — badges, stars, belts, hats, uniforms, trophies.
The dead horse has been complaining, but I’ll reiterate that the important thing about Achievement Symbols is that they must symbolize “achievement.”
If you go on a website and click a button, and then suddenly a popup springs out and says, “CONGRATULATIONS!!! You just earned your ‘Clicked On My First Button Badge’! Click here to see other cool badges you can earn!” Are you going to be excited?
Probably not.
You may even think, “Well this is pretty lame … what else is there? A ‘Scrolling Down Badge’? A ‘Click on the About Us Page Badge’?” You’re almost insulted.
But if you did something that you feel like you uniquely earned by using your creativity to solve a problem that not everyone could solve, and as a result received a badge to symbolize that achievement, you feel proud and accomplished. Now the motivation is valid.
Achievement Symbols merely reflect achievement, but are not achievements by themselves.
A similar example comes from where badges came from — the military. If you join the military, and immediately get a badge on your chest, “Joined the Military Badge!”
And on the next day, another badge gets pinned on your chest that says, “Survived My First Day Badge!” followed by “Made my First Friend Badge!” “Made Five Friends Badge!” You probably won’t feel accomplished and wear all these badges to your social gatherings. You are more likely to feel insulted.
But if you performed acts of valor — you risked your life to save a fellow soldier, and as a result received a Medal of Honor on your chest, you are likely to feel proud and accomplished.
Keep in mind some of those “insulting badges” do work great for children, because as small children, these are actual feats and accomplishments. More often than not, making your first friend is not something you have a parade about when you are a grown person.
Therefore, when I work with clients on gamification, I never ask them, “Do you have badges?” I ask, “Do you make your users feel accomplished?” Having badges (or any game element in itself) does not mean users are motivated towards the Win-State.
That’s why we focus on the 8 Core Drives.
A Point on Points
Similarly, Status Points (Game Technique #1) are for keeping score of progress. Internally, it allows the system to know how close players are towards the win-state. Externally, it gives players a feedback system to also keep track of their progress.
As a great candidate for “Feedback Mechanics” in the Octalysis Strategy Dashboard, showing people their score and changes on small improvements often motivates them towards the right direction.
However, how you craft the gaining and losing of points, as well as meaning behind the points can significantly change the users’ perception of your product. Done incorrectly, it can cause the user to devalue the entire experience and distrust your intentions as a systems designer.
Many companies think that giving users tradable points that can be redeemed for rewards would make a system motivating. After all, now there is an “economy!”
What companies don’t always realize is that running an economy is a complex thing. You have to carefully consider the correct labor to time to exchange to reward ratios and constantly adjust the balance to make sure people actually value your points and currency system.
Adam Smith, known as the “Father of Economics,” suggests in his book Wealth of Nations that the beginning of all Value is Labor. Because people have put in time and labor into the process and “mined out” points, it inherently has value for those who do not wish to spend the same amount of time to obtain those points.
The Federal Reserve Bank or Central Bank of any country knows that an economy is extremely sensitive and requires finesse. They understand that if they just change interest rates by a measly 3%, consumers, banks, insurance companies, real estate developers, and businesses will all behave drastically different.
For a company to just think that, “We have an economy and therefore we are engaging!” is a dangerous statement.
Leaderboard Game Mechanics
Leaderboards (Game Technique #3) is a game element where you rank users based on a set of criteria that is influenced by the users’ behaviors towards the Desired Actions.
Even though Leaderboards are meant to motivate people and bring in status, if designed incorrectly, they often do the exact opposite.
If you use a site for a few hours and received 25 points, and then you see on the Top 20 list, number 20 already has 25,000,000 points, that probably does not motivate you to try harder.
In fact, it could likely demotivate you and you won’t even want to try.
This was an issue that Foursquare, a geolocation mobile app that gamified the check-in process, had many years ago. Often times, a new user may check into a new coffee shop, and then realize the “Mayor” there has already achieved 250 check-ins and increasing everyday. “Fighting for the Mayorship” is probably not something the user would be interested in, because they know the odds of developing progress and feeling accomplished are low.
What users need is Urgent Optimism, another term coined by Jane McGonigal, where the user feels optimistic that she can accomplish the task, but also urgent as she needs to act now.
When you set up a leaderboard, there are a couple variations that have shown to perform better.
First, you always want to position the user in the middle of the leaderboard display, so all she sees is the player right above her, and the user just below her. It’s not motivating seeing how high the Top 10 players are, but it’s incredibly motivating when one sees someone who used to be below her suddenly surpasses her.
Another variation of the leaderboard is to set up Group Leaderboards, where the ranking is based on the combined efforts of a bigger team. In that case, even though not everyone is competitive and needs to be at the top, most people don’t want to be the laggard that drags the team down, so everyone works harder through the sense of Social Influence & Relatedness (Core Drive 5).
The next variation is to set up constantly refreshing leaderboards, where every week the data would refresh; hence no one falls too far behind and always has a renewed sense of hope, leading towards that Urgent Optimism.
Finally, it’s a good idea to implement micro-leaderboards, where only the users’ friends or similar people are compared. Instead of seeing you are ranked 95,253 out of 1 Million users, you see how you are the top 1 or 2 among 22 friends.
The point is that the user must quickly recognize the action item towards getting the win-state. If there’s no chance of achievement, there is no action.
Designing Deep Accomplishment
Everything above explains why the usual points-badges-leaderboards package underdelivers. So what do you build instead? Real Core Drive 2 shows up only when the user actually feels more capable walking away than they did walking in. You can ship a gold star and trigger nothing. Two players hit the same badge: one feels proud, the other rolls their eyes. Same mechanic, different result. The test was never “did we launch a points system.” The test is whether the player believes they earned something.
Three things have to be true for that feeling to fire. Success has to be genuinely at risk, so effort and skill decide the outcome instead of luck. Progress has to be visible, so the user can answer the only question that matters to them: am I actually getting better? And recognition has to be earned, so the symbol means something to the person wearing it. LinkedIn’s “your profile is 70% complete” works because it turns invisible progress into momentum. A martial-arts belt works because everyone in the room knows what it cost. Strip any of the three and accomplishment leaks out of the system.
Status Seekers and Competence Protectors
Core Drive 2 houses two very different players, and the same mechanic can motivate one while quietly punishing the other. Status seekers want to demonstrate they’re ahead. They chase leaderboards, hunt the badge only 5% of users unlock, and care about where they rank. For them, visible top-10 boards, scarce achievement symbols, ranked tiers like Champion and Master, and seasonal resets all land.
Competence protectors carry a different need. Feeling capable matters to them more than topping anyone. They want reassurance that they’re on the right track, and unclear progress freezes them. Drop this player onto a Hall of Champions leaderboard and you amplify their anxiety instead of relieving it. What works for them: progress indicators like “you’ve improved 40% this week,” skill checkpoints that confirm a concept is mastered, non-comparative milestones, and frequent positive feedback. Knowing which player sits in front of you changes every design choice that follows. This is also where CD2 starts leaning on Core Drive 5: Social Influence & Relatedness, because a badge only becomes status when other people can see it.
Competence and Mastery Are Two Different Targets
Daniel Pink’s Drive put “mastery” on every motivation slide in the world. The original word in Self-Determination Theory was “competence,” and swapping it cost us some precision. Competence is the feeling of being capable and effective right now. It’s intrinsic, and you’d want it even on the last day on Earth. Mastery is hitting skill milestones and expertise levels over time. It’s extrinsic, and it only means something if there’s a tomorrow to use it in.
The distinction has teeth for design. Competence work makes people feel capable immediately: a clean onboarding that hands out a real early win, feedback that quietly confirms they’re not failing. Mastery work builds the long climb: leveling systems, skill trees, certification paths, scaffolding toward harder problems. Competence gives people the confidence to start. Mastery gives them a reason to keep going. Strong CD2 systems design for both, and they sequence them in that order.
The Scaffolding Phase: Progress Underneath the Repetition
Octalysis Phase 3, Scaffolding, gets misread as the boring grind in the middle. The word comes from construction, where scaffolding holds up a structure that’s still going up. In a well-designed system the user keeps climbing even when the day-to-day activity looks identical. Watch content, solve problems, show up in the community. The content gets more sophisticated, the problems start demanding several skills at once, and the user’s role shifts from learner to helper. Netflix on a Tuesday feels like Netflix. Duolingo on a Tuesday feels like getting better, because the difficulty actually rises and the streak sits right there on screen.
The engine inside good scaffolding is the game loop: every reward feeds back into the experience. Currency buys boosters. Status unlocks harder content. A new level opens up new strategic choices. The reward always points the user deeper into the system. Most failed platforms break this loop by handing out rewards that point away from the activity, like gift cards, payouts, or time off, and engagement follows the reward out the door. Close the loop on itself and success compounds, so the user experiences strategy instead of chores.
Why Games Beat Work at Accomplishment
Work and a good game share the same skeleton: repeated actions, progress over time, growing skill. One energizes and the other drains. The gap comes down to three things games make obvious and most jobs hide. Games define what winning looks like. They give you constant, immediate feedback on how you’re doing. And they show you the path to improve. In most jobs, victory is vague (“do good work”), feedback arrives late and political, and nobody can quite tell you how promotions get decided. A player will repeat a task a hundred times in a game and call the same task at work soul-crushing. Same repetition, wildly different clarity, and clarity is what the emotion follows.
There’s a deeper lever here too. Feedback loops build more mastery than one-shot grading. When people know they probably won’t nail it on the first pass, they optimize for actually understanding the thing instead of performing it. The single submission was never where the learning lived. Revision based on feedback is. If you want depth, build in review and let people improve their work.
The Progress Plateau Problem
Core Drive 2 is a phenomenal engine for starting. It also has a ceiling, and a lot of products drive straight into it. Most progress runs like a hockey stick: rapid gains in weeks one through four, slower growth through week twelve, then a plateau near your personal peak. Nike Run Club and Strava both hit this wall. Users signed up for the feeling of improvement, and when the numbers flattened, the motivation flattened with them. Running still felt the same. The improvement signal was gone, so the drive went with it, because CD2 is extrinsic and results-oriented by nature.
A design built on Core Drive 3: Empowerment of Creativity & Feedback never hits that wall the same way, because the experience stays engaging even when the stats stall: new routes, running with friends, chasing a different kind of challenge. The fix for a CD2 system is to expand what counts as progress before the plateau arrives. Add route variety and terrain challenges, layer in social running groups (CD5), let routes respond to how someone runs (CD3). CD2 converts and engages people early. Plan the retention layer before growth naturally slows, not after users have already drifted.
Real Money and Perceived Value
Here’s the insight that catches most designers off guard: an easy path devalues the hard path even for the players who never take it. When Blizzard added a real-money auction house to Diablo 3, the damage wasn’t that some players bought gear. The damage was that everyone knew they could. Grinding suddenly felt foolish, even for the people who wanted to earn their gear. Your hard-won loot felt unearned, because someone had proved it could be bought.
What this reveals is that the psychological economy, meaning what people believe about earned versus purchased rewards, matters more than the actual economy. It’s why real-money loot boxes are so corrosive for accomplishment-driven games. Every box broadcasts the same message to the whole player base: this reward could have been a transaction instead of an achievement. The mechanics barely matter once that perception sets in. So if you sell anything, keep purchases to cosmetics and keep power progression earned. Perception is doing as much work here as reality.
The Endgame Problem
Most designers treat mastery as the finish line. Mastery is the point where the journey changes shape. In World of Warcraft, hitting max level is when the real game starts: raids that were locked the whole way up finally open. A game with four engagement phases runs Discovery, Onboarding, Scaffolding, and then Endgame, the part built for veterans who’ve already mastered the core. Plenty of products bleed their best users at exactly this transition because they never built an endgame at all. The user maxes out, collects every achievement, sees all the content, and finds nothing waiting. Your most engaged person walks.
So ask the uncomfortable question: what do your experts do after they’ve mastered everything? Good answers include veteran-only challenges, mentorship systems where veterans guide newcomers, creation tools that let them build things other users rely on (which quietly activates Core Drive 4: Ownership & Possession), elite competitions, and legacy systems whose contributions persist. If the honest answer is “they leave,” you have an endgame problem to solve before you have a growth problem.
The Boss Fight Framework
A boss fight takes smooth progression and concentrates it into a single high-stakes moment where mastery has to show up. Two mistakes wreck them. The first is surprising the player with new rules: they’ve done X for ten levels, and now the boss demands X and Y at once. That reads as random difficulty rather than earned challenge, because the system changed while the player didn’t. The second is gating the boss behind grinding, where the winning move is to out-level it over forty hours. That tests patience and hands the player a pile of chores dressed up as an achievement.
A meaningful boss fight tests skills the player already learned, forces them to combine several of those tools at once, leaves room for more than one creative solution, and punishes carelessness while rewarding genuine skill. It should feel climactic, like it validates the whole climb. Here’s the test that catches a fake one: after a defeat, can the player name exactly what they did wrong? If they can’t, the difficulty was theater.
A Deep CD2 Design Checklist
Before you ship any accomplishment system, run it through five questions. Is the accomplishment real, meaning did the user actually struggle, improve, and succeed, or did they just walk an easy path? Is the progress visible, so they can point to proof they’ve gotten better? Is the recognition meaningful, so the symbol signifies something the holder values instead of dropping for trivial actions? Would people still want it with no reward attached? And does finishing it create momentum or closure, meaning does the win leave them ready for the next challenge or does it feel like a place to stop? Five yeses and you’ve built deep Core Drive 2. Any no is a design leak worth closing before launch.
Conclusion
Since Development & Accomplishment is the easiest Core Drive to design for, many companies focus on this Core Drive. Consequently, many of the Gamification Platforms out there are specialized in appealing to this Core Drive too. However, if you do plan to implement these game elements into your product, make sure you do that carefully and elegantly. Always focus on how you want your users to feel, not what game elements you want to use.
Core Drive 2 is also the engine beneath Richard Bartle’s Achiever player type — which is why Achiever-heavy systems so often default to points and badges. For a full map of how each of Bartle’s 4 player types activates specific Core Drives, including the ones Accomplishment alone can’t reach, see the deep dive.
Frequently Asked Questions
What is Development & Accomplishment in gamification?
Development & Accomplishment is Core Drive 2 in Yu-kai Chou’s Octalysis Framework. It represents the internal drive to make progress, develop skills, and overcome challenges. It is the most common core drive used in gamification design, powering mechanics like points, badges, leaderboards, and progress bars.
Why do points, badges, and leaderboards often fail in gamification?
According to the Octalysis Framework, simply “slapping on” points, badges, and leaderboards without meaningful design leads to poor engagement. Badges must represent genuine accomplishments that users care about. Points need clear purpose (status vs. exchangeable). Leaderboards can demotivate users who feel they can never reach the top. Effective gamification requires these mechanics to connect to real progress and mastery.
What game techniques use Development & Accomplishment?
Key game techniques under Core Drive 2 include: Progress Bars (like LinkedIn’s profile completion), Achievement Symbols (badges that represent real accomplishment), Leaderboards (when designed to motivate rather than discourage), Status Points (non-exchangeable markers of achievement), and Win States (clear moments of victory that validate effort).
Is Development & Accomplishment a White Hat or Black Hat core drive?
Development & Accomplishment is a White Hat core drive, meaning it makes users feel powerful, accomplished, and satisfied. It sits at the top of the Octalysis octagon alongside Epic Meaning & Calling and Empowerment of Creativity & Feedback. White Hat drives create long-term positive engagement.
How does Urgent Optimism relate to Development & Accomplishment?
Urgent Optimism is a concept from game designer Jane McGonigal that describes the feeling of being optimistic you can succeed while also feeling urgency to act now. In the Octalysis Framework, Urgent Optimism is what makes Development & Accomplishment engaging rather than tedious. Leaderboards, progress bars, and challenges must be designed so users believe victory is possible but requires immediate effort.
Explore All 8 Core Drives of the Octalysis Framework
The Octalysis Framework identifies 8 Core Drives that power all human motivation. Understanding how they work together is key to effective gamification design:
- Core Drive 1: Epic Meaning & Calling — Being part of something greater than yourself
- Core Drive 2: Development & Accomplishment — Making progress and achieving mastery (You are here)
- Core Drive 3: Empowerment of Creativity & Feedback — Expressing creativity and seeing results
- Core Drive 4: Ownership & Possession — Owning things and wanting to improve them
- Core Drive 5: Social Influence & Relatedness — Social elements that drive behavior
- Core Drive 6: Scarcity & Impatience — Wanting something because you can’t have it
- Core Drive 7: Unpredictability & Curiosity — The drive of not knowing what happens next
- Core Drive 8: Loss & Avoidance — Avoiding negative outcomes and loss
Related frameworks: White Hat vs Black Hat Gamification | Left Brain vs Right Brain Core Drives | The Strategy Dashboard
Learn More in Actionable Gamification
This Core Drive is explored in depth in Actionable Gamification: Beyond Points, Badges, and Leaderboards — the definitive guide to designing engagement using the Octalysis Framework, referenced by over 4,000 academic papers. Get the book →
Related Frameworks by Yu-kai Chou
- Economy/Tokenomics Design Framework
- The Digital Convergence Model
- 10,000 Hours of Play: Unlock Legendary Success



