Achievements That Work Like Duolingo, Not Like Corporate Hardware

I open an employee profile at a client demo. In the "achievements" section the person has five identical shields labeled "5/10/25/50/100 thank-yous received." Asked "are you at Gold, or what level?", they look at the stack, count, and say "I don't know, Silver maybe?" That's the first sign gamification isn't working: the employee themselves doesn't understand what they've achieved.

Most corporate achievement systems look like a stack of shields in the profile. Each tier is a separate image, takes up space, visually overlaps its neighbors. The employee sees noise instead of progress. The manager sees "Masha has lots of badges." Nobody sees what exactly this person mastered, and how far it is to the next milestone.

We rewrote the achievements system from scratch a year ago. And the main thing I learned in that time: achievements only work when they're built like Duolingo — one object, visible progress, a clear next goal — not like a room of certificates in a school principal's office.

Let me share what changes with the right architecture.

What Was Broken

The standard approach to achievements in HR tech is this: for each tier of a chain, you draw a separate badge. Got 5 thank-yous — Bronze. 10 — Silver. 25 — Gold. 50 — Platinum. And so on for every track.

In the profile this turns into a stack of 4–5 identical images on the same theme. Visually — mush. Semantically — repetition. The employee looks and doesn't get it: "Am I Gold or Silver on 'thank-yous received'? And why are there four identical ones?" The answer is — because they've actually earned all four tiers, and each one displays separately.

This is a basic design error: the levels of one achievement shouldn't look like separate achievements. It's one achievement in which the employee passes through several levels. One object — one visual element.

On top of that came a second problem: the admin side was monstrously complex. Eight technical tabs ("Catalog," "Chains," "Templates," "Chain templates"...), overlapping entities with different behavior, and the same thank-you displayed in three places with different logic. HR couldn't set up their first chain without an onboarding call with support.

And a third: in the company's public achievements catalog, an employee saw a list of "available trophies" — with no understanding of how to get to them. Just a grid of images: "here's what exists." No progress, no next action.

The solution turned out to be conceptual, not cosmetic. We rewrote the data model, the visual language, the admin panel, and the user-facing catalog.

One Medallion Instead of a Stack

The main visual decision — one object per achievement chain, with tiers reflected inside the object.

How the new medallion works. It's a composition of two layers:

• The frame — reflects the current tier: bronze, silver, gold, platinum, diamond. It's a visual level signal — without words, it's clear how far the employee has progressed.
• The icon inside — reflects "what" the achievement is about: thank-yous, ideas, comments, company anniversaries. This part doesn't change as the level rises — the icon is the same across all tiers. The employee always recognizes "their" achievement at any level.

Below the medallion is a short label with an explicit level marker ("GOLD LEVEL," for example), so there's no doubt. No 5 identical images. One object per growth track.

The effect for the employee at launch: "Ah, now I understand what I have." The effect on the design side: the profile gets cleaner, and each person's individual trajectory is visible. The effect on the admin side: setting up a chain reduces to one task — "pick an icon and define the level thresholds" — rather than drawing five separate badges with a similar icon.

Progress Is the Main Motivator — Not the Reward Itself

The biggest UX discovery in the redesign: progress matters more than the reward itself. I didn't invent this — it's visible in any product with proper gamification. Duolingo, Strava, any fitness tracker. People don't come back for "the green checkmark at the end." They come back because they see they're moving.

This means: if an employee in the achievements catalog only sees "here's what exists" but not "where I am now and how far to the next milestone," motivation doesn't kick in.

What we added in the new version:

• The full chain of tiers is visible in the public catalog. Bronze → Silver → Gold → Platinum → Diamond. The employee sees the whole path at once.
• The current position is highlighted. Where the employee is now — which level.
• "X of Y to the next." A number expressed in a real unit (thank-yous, ideas, comments). Not "70% progress," but "12 of 30 to Platinum." Specificity motivates more than abstraction.
• Hidden achievements. Some achievements in the catalog are not revealed until the employee takes a first step toward them. This isn't hiding for hiding's sake — it's the discovery effect, which adds genuine interest. When, after a first published idea, a new "Idea Person" branch appears in the catalog, the employee thinks "oh, interesting, what's this?"

After these changes we see at clients a significant rise in visits to the achievements page and, more importantly, repeat visits: the employee comes back to see how they've progressed. We measured a sample of clients before/after the release; exact figures vary depending on the program's starting state — so in a public article I give a qualitative description rather than a single "hospital average."

The Admin Side — a First Chain in 10 Minutes

If it's hard for the employee to understand achievements, that's half the trouble. If HR can't set them up without support's help, it kills the self-service funnel of a SaaS product.

The old admin panel was a form of engineering thinking: 8 tabs, each with its own data model, templates, chain templates, overrides, versioning. It was convenient for a developer. Impossible for an HR director.

What we did:

• One page — a list of chains, each expanding into tiers, milestone by milestone.
• Nested rows. A chain is shown as one row with all its tiers in a nested list, not as separate entities.
• Live preview. As HR configures the medallion, the right side instantly shows how it'll look in the employee's profile. Exactly the same visual the end user will see.
• Ready-made templates. "Thank-yous received," "Ideas published," "Posts commented on," "Days with the company." These templates fill out in 2 minutes — pick an icon, set the level thresholds, done.
• Dragging thresholds. Not "enter the numbers in a form," but "drag the slider to 30, to 100, to 250." It's nicer and faster.

We ran a small usability session with HR directors unfamiliar with the product: "here's an account, build your first achievement chain in 10 minutes without help." On the new version most managed within the time — on the old one only a few did, with an average time of 35–50 minutes. The sample is small (around 10 people), this isn't representative research, but the difference between versions was visible in every participant.

That's the very difference that separates a self-service SaaS from a product requiring an implementation specialist.

How Achievements Differ From Thank-Yous and Badges

The most common conceptual mistake in HR-tech products is lumping achievements, thank-yous, and badges into one pile. They look similar visually, and an untrained eye confuses them. In reality these are three different layers with different logic and different purposes.

Thank-yous — peer-to-peer recognition in the moment. Someone said "thanks for a specific action." It's an act of attention. It lives in the feed, not in the profile as a "trophy." The goal is to support a recognition culture among colleagues.

Badges — formal awards from the company for outstanding events. "Best Newcomer 2025," "Speaker of the Year," "Hackathon Winner." Awarded rarely, usually on behalf of HR or the CEO. They're separate, one-off, ceremonial. The goal is to mark the outstanding.

Achievements — a personal path through milestones of activity. Tiers passed automatically by behavior (received X thank-yous, published Y ideas, reached Z days with the company). It's the employee's own skill tree, visible to them and their colleagues. The goal is to show a trajectory, to give visible progress.

If you confuse or merge them, both layers become useless:

• If you mix badges with achievements, the employee stops feeling the "ceremony" of a badge: "What's special? I already have 15 icons from achievements."
• If you turn thank-yous into achievements ("1 thank-you = 1 badge in the profile"), they get devalued and become a quantitative metric, not a qualitative moment.
• If you turn achievements into pure recognition, you lose the main thing — progression, the individual trajectory.

In our product, each of the three systems has its own architecture, its own UI, and its own logic. They interact (thank-yous can trigger achievements automatically), but they don't merge into one entity. That's the right separation, without which a corporate portal turns into a mush of icons.

The Bottom Line

Achievements work when they're built as a real progression system: one object per chain, visible "X of Y to the next milestone" progress, the full chain of tiers in view, plus hidden achievements to motivate the first steps.

A stack of five identical shields is an antipattern that kills the employee's understanding and, as a result, the desire to come back to the catalog.

The admin side must be simple too: a first chain in 10 minutes without a support call. Otherwise it's not a SaaS product but a service with mandatory implementation.

And most importantly — don't mix achievements with thank-yous and badges. These are different layers, and each handles its own job. Merging them spoils all three.

Next, we'll dig into the idea bank with an AI assistant: how we help employees not stay silent, and why 80% of good ideas at companies never reach the idea bank.

If you want to see our achievements catalog live, in the demo environment, follow the link in the card. A 5-minute demo, no presentations.