Achievements are how you recognize progress beyond raw XP — a badge on a profile, a visible marker of what someone has actually done. As a GM, you're designing three distinct tools here, not one.
Three Tools, Three Jobs
- Achievement — a one-off milestone. "Finished onboarding," "Perfect score on the compliance quiz." Awarded once, doesn't imply anything came before or after it.
- Path — part of a themed series. Use paths when you want players collecting a set — "completed 3 of 5 modules in the Leadership track."
- Rank — a status tier, shown with extra framing on a player's profile. Use ranks when progress itself is the reward — Bronze/Silver/Gold, Associate/Senior/Lead — something that visibly upgrades as a player advances.
Automatic Triggers vs Manual Grants
Most achievements should fire automatically — on a level-up, a milestone chain completing, or a specific milestone finishing. Set the trigger once and forget it. You can also grant one manually, which is worth reserving for genuinely human moments: recognizing a standout contribution, a live event, something a rule can't detect.
Designing a Rank Ladder
If you're using ranks, decide the tier count up front — three to five works well for most programs, more than that and the distinctions stop feeling meaningful. Tie each tier to a real, visible threshold (a level, a set of completed milestones) so players can always see the next rung and what it takes to reach it.
Badge & Color Design Tips
Achievements render as hexagonal badges, so simple, high-contrast icon designs read best at small sizes. Reuse your Adventure's accent color for the badge border to keep the whole reward system feeling like one coherent visual language rather than a grab-bag of clip art.
Where to go next: Guilds — Designing Team Play, if part of your reward design is social or team-based.