A badge is an Achievement Symbol awarded when a user reaches a meaningful milestone. It might recognize their first successful task, their fiftieth contribution, or their hundredth completed challenge. The same badge can develop with the user: one star for the first milestone, two for the next, and three for a more advanced achievement.
In the Octalysis Framework, badges primarily draw on Core Drive 2: Development & Accomplishment and Core Drive 4: Ownership & Possession. Reaching a milestone gives users a sense of progress and a visible sign of their status. Earning, collecting and upgrading badges gives them something to accumulate and improve. A user may want to reach the next achievement, complete a collection, or strengthen a badge they already own.
A badge can also unlock a Booster that helps the user in the experience. A higher-star badge might grant a different power, giving the user a new decision about how and when to use it. This connects the achievement to what they can do next. Giving someone an icon for logging in provides none of that by itself.
Yu-kai Chou makes the distinction in Actionable Gamification: “Achievement Symbols merely reflect achievement, but are not achievements by themselves.” The design work is deciding which Desired Actions deserve recognition, how the milestones develop, and what users gain from reaching them.
Design the milestone and the collection together
Core Drive 2 depends on the user experiencing accomplishment. Successfully resolving a difficult customer case can provide that experience; opening the case-management application usually cannot. A newcomer may feel accomplished after their first successful resolution. An experienced user may be pursuing a milestone of 50 or 100 resolutions, or a challenge involving more difficult cases.
The count needs to represent the Desired Action. If the badge rewards resolved cases, repeatedly opening a case should not advance it. If quality matters to the business objective, include that quality requirement in the milestone. Explain the condition and show progress toward it so users know what their next action can achieve.
Core Drive 4 adds the desire to build and improve a collection. Chou calls themed groups of items Collection Sets, Game Technique #16, and explicitly includes badges. A learner might collect badges for negotiation, diagnosis and collaboration, then improve the star rating of each. The collection shows both the areas they have developed and the ones they can pursue next. Letting users choose which badge to develop gives them a reason to return to their own collection.
Salesforce Trailhead provides a current example of cumulative badge progression. Its Road to Ranger guidance sets Ranger at at least 100 badges and 50,000 points. Individual badges accumulate toward a visible rank. Ranger is a rank, while learning badges, hands-on Superbadges and Salesforce certifications have different requirements. Keep those distinctions clear when deciding what your own badges communicate.
Discovery previews the experience; Onboarding delivers the first achievement
Discovery happens before the user enters the experience. There is no completed in-experience milestone to reward, so this is not the phase for awarding badges. Show the activity and its potential Win State: the customer problem a learner could resolve, for example, or the kind of challenge an experienced player can handle.
During Onboarding, guide the user toward their first major Win State. In a customer-service training simulation, that could be resolving a first realistic case with guidance. The learner has made decisions, seen the customer’s response and reached a successful outcome. A first Problem Solver badge can recognize that achievement. Logging in or clicking through an introduction does not establish the same accomplishment.
Keep the initial challenge achievable for the intended player type. Introduce the badge when the user reaches the milestone, then show its next level or its place in the collection. Explaining an entire badge economy before the first task would delay the success Onboarding is supposed to deliver.
Use badge levels to unlock useful powers
During Scaffolding, users know how the experience works and repeat its activity loops. Badges can recognize their first, fiftieth and hundredth successful actions. The activities between those milestones also need to develop: different cases, approaches, team roles and opportunities to apply what they have learned.
Consider this illustrative design for the training simulation. It is a proposed badge progression, not a description of a client implementation:
- One-star Problem Solver: resolve the first guided case. Earn a one-use Booster that reveals an extra customer clue in a later practice case.
- Two-star Problem Solver: resolve 50 cases that meet the quality criteria. Unlock a Booster that lets the learner test two responses and compare their consequences before committing in one practice round.
- Three-star Problem Solver: resolve 100 qualifying cases, including advanced scenarios. Unlock a team Booster that lets the learner give a teammate an additional clue during a shared challenge.
The thresholds are illustrative; choose them to suit the frequency and difficulty of the actual Desired Action. The badges record progress through Core Drive 2 and become an improving possession through Core Drive 4. Choosing when to use a clue, compare responses or assist a teammate adds Core Drive 3: Empowerment of Creativity & Feedback. The learner can try a strategy, observe its result and adjust.
This combines several Octalysis techniques. Milestone Unlock, Game Technique #19, introduces a new possibility when a milestone is reached. Boosters, Game Technique #31, help users achieve a Win State and are usually limited by time, use or conditions. A permanent badge can unlock access to such a power without being the Booster itself. State clearly what is earned permanently and what is consumed during use.
These powers belong to the simulation. Required learning materials and tools for the employee’s real work remain available. The Booster should create an interesting tactical option within the activity.
Higher badge levels can also recognize difficulty. Xbox’s official Forza Horizon 5 achievement list specifies “Unbeatable Triumph”: win six different Race Events against Unbeatable Drivatars, for 30 Gamerscore. This is an achievement example, not a badge-unlocked Booster. Its earning condition combines repeated success with a defined challenge level.
Give experienced users status and opportunities to contribute
In Endgame, experienced users may have completed the main collection and reached its highest levels. They need further uses for their abilities: mentoring newcomers, designing challenges or helping a team solve difficult problems. A badge can recognize those contributions and make the user’s role visible.
Stack Overflow’s Great Answer badge is awarded for an answer with a score of 100 or more and can be earned multiple times. Each award recognizes another contribution. It shows how a repeatable badge can continue to acknowledge achievement without inventing another tier for every veteran.
A Trophy Shelf lets users display their accomplishments to people who understand them. This adds Core Drive 5: Social Influence & Relatedness to the progress and ownership already present. In a learning community, visible mentor achievements can help newcomers find someone to learn from. The recognition supports an actual relationship when the experienced member helps them succeed.
Keep examples current and surprises relevant
Some badges can reward unexpected discoveries. In the book’s historical Foursquare example, Mario Herger received a “Jobs” badge after checking in at an Apple Store following Steve Jobs’s death in 2011. Chou uses it to explain an Easter Egg: a reward the user did not know to expect.
The date matters. Swarm’s current official App Store listing promotes mayorships and a weekly leaderboard; it does not verify the continued availability of that historical badge. Use the old example to explain the technique, with its original context.
Surprise badges can recognize exploration, while published milestones still need clear earning conditions. A user pursuing a three-star badge should be able to understand the remaining progress and the power it will unlock.
Connect the badge economy to Desired Actions
The PBL Fallacy is assuming that adding points, badges and leaderboards makes an experience engaging. A well-designed badge system needs meaningful achievements, an appealing collection and activities that develop as users progress. Our discussion of app gamification design examines that wider experience.
Start with the business objective and the Desired Actions that support it. Define the milestone, badge level, collection and any unlocked power together. Then check what the user can do after earning the reward. In Scaffolding, that may be a new strategy or team challenge; in Endgame, it may be a contribution that gives others a reason to seek their help. The badge continues to show progress while the experience gives users something worthwhile to do with it.
Apply this to your own badge economy
Start with the Desired Action. Define the first meaningful milestone, the repeatable milestones that follow, the collection users can build, and the Booster each higher level makes available. Then test whether every reward helps people make progress toward the Win State. A badge that only records a trivial action is decoration. A badge that marks a genuine achievement and opens a useful choice can become part of the experience.
If your product has points and badges but no clear reason for users to keep progressing, contact us. The Octalysis Group can map the Desired Actions, Core Drives and Experience Phases that give the badge economy a real job.
