Does Gamification Increase Feedback Volume?

Reward contribution quality, not activity

Points for submitting anything produces noise: duplicates, one-line requests, vote farming. Points awarded when a submission reaches a status — triaged, planned, shipped — reward usefulness instead.

The same logic applies to voting: reward voting with a comment, not the click.

The team controls statuses and customers do not, which is what makes outcome-based points hard to game. A customer can post ten times in a minute; they cannot move their own post to Planned.

Activity is not the same as signal

The question in the title has an easy answer and a more useful one. Rewards usually raise the number of posts, votes and comments. What you want to know is whether they raise the number of requests that tell you something new, from people whose needs you are trying to meet.

More posts can mean more duplicates for someone to merge. More votes can mean the same few people voting on everything. More comments can mean '+1' replies that add nothing a vote did not. Before switching rewards on, decide which of those you would count as success, and write it down, so you are not tempted to call any increase a win.

Where it works best

Communities with an existing identity — developer tools, games, prosumer software — respond strongly. Enterprise buyers mostly do not care about badges but do respond to recognition, such as being credited in the changelog entry they inspired.

Rewards amplify participation that already exists; they do not create it. A board nobody visits will not fill up because points are on offer. Fix the basics first: link the board from inside the product, reply to posts, and tell people when their request ships. Rewards are worth adding once there is a steady trickle of contributors to recognise.

Internal boards, where employees post ideas, are a middle case. Points can help, but public recognition from a manager usually counts for more, and a leaderboard of colleagues can feel like a performance review.

The backfire cases

Leaderboards on a small user base turn into one power user dominating the roadmap conversation. Rewards with monetary value attract gaming almost immediately.

Mitigations: cap earnable points per period, require moderation before points settle, and keep leaderboards scoped by segment.

Setting point values: Looph's defaults as an example

Rewarding outcomes over activity is easier to agree on than to set up, so here are the default values in Looph, the tool we make, as one worked starting point. Every value can be changed, and other tools use different scales.

Read the ratios rather than the numbers. A shipped idea is worth a hundred votes, and an idea reaching Planned is worth five posts, so most of the points depend on decisions the team makes rather than on how often a customer clicks. Votes still pay something, because a board where nobody votes cannot rank anything, and the voter bonus gives backers a share of the outcome without making it a strategy to vote for everything popular.

If you change the scale, change one value at a time and wait a few weeks before judging it. Raise the comment value if comments are thin and you want more context; lower the post value if duplicates start rising; keep the voter bonus small relative to the author's shipped award. Daily caps on each action, which Looph switches on by default, matter as much as the values themselves.

Use leaderboards with care

A leaderboard is the most visible part of a rewards system and the easiest to get wrong. A few choices keep it encouraging rather than discouraging.

Recognition that costs no points

Some of the most effective rewards are not points at all. Name the customer who first raised a request in the changelog entry that ships it, with their permission. Reply on their post by name when it moves to Planned. Invite your most useful contributors to try a feature before it launches, or to a short call about what they posted. These cost the team a few minutes and tell the contributor something a points total cannot: that a person read what they wrote.

For B2B products in particular, this kind of recognition is often what the buyer values, because it reaches their own colleagues and shows their request carried weight.

What to instrument

Track submissions per active user, duplicate rate, and the share of shipped items that originated from a rewarded contributor. If duplicates rise faster than shipped-from-feedback, your incentives are pointed at the wrong action.

Take a baseline for a month before switching rewards on, and change nothing else about the board while you compare, so you are measuring the rewards rather than a new launch or a busy season. Then compare the same measures a month or two later.

Rewards in Looph

Looph's rewards engine is part of the Growth and Business plans, and every new workspace can try it during the Business trial. It is switched on by default and can be turned off. Customers earn points for the actions in the table above; your own team members do not. Streaks count the weeks in a row someone has contributed, lifetime points move people through five levels you can rename, and a store lets points buy rewards you set up, with larger redemptions waiting for a teammate's approval.

The guards against gaming are on by default. Daily earning caps apply, and points from brand-new accounts are held for 24 hours. Points are taken back when a post is merged as a duplicate or removed as spam, and a daily check flags patterns such as pairs of people voting for each other. A higher level does not give anyone more vote weight; every vote counts once. Rewards and points covers each setting, and moderation and spam covers the moderation tools that sit alongside it.

Frequently asked questions