← All case studies
UpsideStar mark
Case study · Employee recognition

How UpsideStar uses Feedbank

Pay UpsideStar with Feedbank →

Peer recognition and small rewards inside the tools a team already uses.

The moment it loses people

A manager launches it, the first week is busy, the third week is silent.

The pattern

Insight: structured answers to act on

The hub files every answer by topic and screen, and the model names the core reasons behind them.

The trade

Gives: Team plan free for a quarter per accepted loop

Asks: Five questions from the team each month

The door, live at /pay/upsidestar
UpsideStar's door on a phone: Pay UpsideStar with Feedbank, what you get, what you give, and the button to start the first loop
The hub, as every brand's team sees it
The hub: accepted answers this month, answers that need a reply, credits issued, topic filters and the first answers

Planbrand's workspace, with answers in it. UpsideStar's hub has the same screens, filed under Giving recognition, Rewards, Noise and Leaving.

The weekly loop

Five questions on giving recognition, rewards, noise. Every answer is scored for how specific it is; a complaint earns what a compliment earns.

  1. 1Who did you want to recognise this week and did not, and why?
  2. 2Which reward did you choose, and what would you rather have had?
  3. 3Which notification felt like noise?
  4. 4What would make recognition feel genuine here?
  5. 5What happened in week three?

What UpsideStar learns

  • Why recognition stops
  • Which rewards matter
  • What is noise
At the moment of leaving

Anyone who stops gets three exit questions: what made you stop, what would have kept you, what did you expect. Scored like any answer, credited, and read first by the Insights model.

This page describes UpsideStar's setup on Feedbank. Figures appear only where the brand has published them.

← UnconstandPay UpsideStar with Feedbank →Wanteen →