Behavioural & Game Mechanics · Reference Library

Motivational Mechanics

A working index of the behavioural and game mechanics that shape attention, memory, motivation, momentum and completion. Each one described plainly, with a real example and an honest read on where it turns coercive. Built for design critique, workshops and product argument, not for shipping as-is.

A mechanic is not a solution.

It is a behavioural ingredient. Whether it belongs in your product depends on context, intent, implementation, timing, and how vulnerable the person on the other side is.

The framework

Ten forces, twenty years of building them

The shorthand behind Motivational Mechanics. Drawn from two decades of game and campaign work for Coca-Cola, TV2 and SAS, and from Eyal, Csikszentmihalyi and Shafir. Nine come from the original toolbox; Flow is the tenth, added here as the state they aim at. Each force is a doorway into the library below: pick one to see every mechanic that pulls that lever.

Teardowns

What real products actually run

Seven observed stacks, from the densest game in the world to a B2B account plan. Open one to filter the library to exactly what it uses. Then switch the service context to see how the same stack reads somewhere else.

The library

Every mechanic, filtered how you need it

Pick the service context you are designing for and every risk mark is re-derived against it. What is merely delicate in a fitness app can be unacceptable in debt collection. Then search, narrow by family, behaviour or risk, and select two to four cards to compare them.

Provenance

Where this comes from

Much of this material rests on twenty years of working with gamification and game mechanics from four sides at once: as a marketeer building loyalty programmes, as a gamer, as a game designer, and as a product designer deploying loyalty programmes at scale in enterprise retail.

Scope

What the risk marks are not

The risk marks in this library describe a mechanic in a context, not a verdict on a design. A mechanic marked red flag is one whose effects are unacceptable in the setting currently selected, which is why the same mechanic reads one way in games and another in debt collection. Change the context and the mark changes with it.

That is a different thing from a dark pattern, or deceptive design as the field now tends to call it: an interface deliberately built to work against the person using it. Deceptive design is deceptive everywhere, so it does not move with context. Most of the red flags here involve no deception at all. Leaderboards and peer comparison are completely transparent about what they do, and they are marked red in some contexts because they cause shame, not because they trick anyone.

Deceptive design has its own catalogue and increasingly its own law, including Article 25 of the EU Digital Services Act. Patterns such as confirmshaming, hard-to-cancel flows, drip pricing, hidden costs, forced continuity, preselection and disguised advertising are deliberately absent from this library, because they are interface tricks rather than motivational mechanics. If that is the question in front of you, this is the wrong reference and you want a deceptive design catalogue instead.

Compare