Skip to content

Team goals, not leaderboards

Team goals vs. leaderboards in workplace wellbeing

Two workplace challenges can look identical at kickoff and behave nothing alike a month later. The difference is what the design bets on to keep people in.

4 min read

Listen to this post · 2 min

Narrated with an AI voice · Hepio NotesPodcast feed

TL;DR

  • A ranking needs someone below every climber, while a shared total only goes up and can include everyone who shows up.
  • If the highest-value action is one only some people can do, the shared total becomes a ranking in disguise.
  • Brief leadership with two numbers that identify nobody: total progress toward the goal and how many people took part at least once.
IllustrationOne number for the whole team, with milestones everyone unlocks together.

Two team wellbeing challenges can look identical in a kickoff message and behave nothing alike a few weeks later. The difference is usually not the activity, and it is not the reward. It is the bet the design makes about why people come back.

Two different bets about what keeps people in

The first bet is that people return because they can see themselves moving up. Give them a rank, refresh it daily, and the possibility of climbing keeps them coming back. This is the bet behind individual leaderboards, and it does work, for the people for whom climbing is plausible.

The second bet is that people return because the next step is small and because the group total is visibly theirs. Give them one shared number and a clear action, and the sense of being one of many keeps them coming back. This is the bet behind team goals.

The two bets are not equally robust. The first depends on a stable hierarchy: for everyone who climbs, somebody has to be below. The second depends on arithmetic: the total only goes up. One of those can include everyone who shows up. The other cannot.

When competition helps, and when it excludes

Competition is useful where the goal is genuinely comparative. A sales floor, a sports league, a recruitment drive with a fixed number of places: in each case the ranking describes the actual work, and everyone who enters knows what they entered.

A wellbeing challenge is a different kind of object. It asks people to change a small habit, in public, while their ordinary work continues. The comparison adds nothing to the habit and adds a great deal of risk around it. The field is not level either: a colleague with a long walk to the station covers more ground than one who drives ten minutes, and neither of those is effort.

So the honest question is not whether competition motivates. It does, for some people, some of the time. The question is whether you want a campaign whose reach is capped by who can win it, when the reason you ran it was to reach the people who usually do not take part.

What changes when everyone moves one shared goal

A shared goal changes three things at once. Progress is measured for the team rather than the individual, so the total can hold contributions that look nothing alike. The social cost of a quiet week drops, because a quiet week does not move anyone down a list. And the campaign shows progress from day one, since the total starts moving as soon as anyone does anything.

It is also easier to explain. A shared goal takes one sentence: the team is at this number, the goal is that number, here is what counts today. A leaderboard needs a paragraph on categories, eligibility, and why the same three people are always at the top.

There is one design constraint worth respecting. A shared goal only works if contributions are counted in a way people find reasonable. If the action worth the most is one only some people can do, the total starts to behave like a ranking in disguise, and the people locked out of it will notice before you do.

Rewards the whole team unlocks, not a personal podium

Rewards follow the shape of the goal. When the goal is individual, the reward has to pick a winner, and every announcement leaves most of the room watching. When the goal is shared, the reward can arrive for everyone at once, and the moment of reaching it belongs to the group.

Keep the reward small and collective. A team breakfast, an early finish on a Friday, a small budget the team spends together. Size is not the point, and an expensive reward creates a new problem: it makes the goal feel like a transaction and invites pressure on the people who did not opt in.

The modest version works better than it sounds when the milestone is visible. Reaching a goal and having the channel say so, with everyone included in the result, is already the recognition most workplace challenges try to manufacture with a ranking.

IllustrationMilestones belong to the team: when the goal is reached, everyone is invited.

How to explain the choice to leadership

The case to leadership is not that competition is bad. It is that a shared goal reaches more people for the same amount of effort, and it produces a cleaner report at the end.

State what the campaign is for, who it needs to reach, and what the design does to include them. Then give the two numbers that matter: total progress toward the goal, and how many people took part at least once. Neither one identifies anybody. (There is more on this in how to brief leadership without inventing ROI.)

If the concern is motivation, name the mechanism plainly. People return to a shared goal because the next action is small and because the total is visibly theirs. That engine does not stall when the top of a table stops changing.

If the concern is fairness, a shared goal has very little to be unfair about. There is no eligibility rule to argue over, the only weighting is a short, published points list, and nobody is structurally unable to do well. That is a short meeting, and it is usually a welcome one.

Keep reading

Hepio is a Slack-native way to run one shared team goal. Join the waitlist.

Get early accessMore writing

Hepio is in early access with a small number of pilot teams. It isn’t generally available or in the Slack Marketplace. Product details describe how it works today and may change. Questions: hello@usehepio.com.