Skip to main content

Strategy - Diamond ร— vimiRewards Day

The single most reliable way to turn a quiet team into one that talks about their rewards every week.

What this strategy deliversโ€‹

Run this strategy honestly for 60 days and you get three outcomes. First, staff stop asking "what does this diamond thing actually do?" because they've redeemed something real. Second, you have a fixed day each month your team looks forward to - the same way they look forward to payday, but cheaper and faster to run. Third, your retention conversation changes: when someone is thinking of leaving, they now have a small, concrete, social thing they'd miss. That thing is not your software. It's the ritual you built around it.

It's not magic. It's habit plus visibility plus a tiny budget used well. Most Malaysian SMEs can run this on RM200โ€“RM800 a month.

Why it worksโ€‹

This strategy leans on four of the ten psychology principles at once.

Recognition. Every diamond you hand out comes with a written reason ("for handling the angry customer on Tuesday"). Staff don't just get currency - they get a public record of being seen. Over three months, this is the thing that pushes retention curves up.

Anticipation. Because redemption only happens on fixed dates (the 10th and the 20th of each month), staff count their diamonds in advance. They plan. They swap strategies. They tell their spouse. This is the same mental pattern as payday - you've built a mini-payday on top of your real payday, powered by recognition instead of salary.

Social proof. Rewards Day is public. Photos. Team chat. The cheap item is redeemed by someone. So is the mid-tier item. And occasionally, the premium item. Staff who haven't redeemed see others redeeming, and they start calculating what they need to do to be next. The math does itself.

Variable rewards. Staff don't know exactly what's in the catalog this month, or what their exact earnings rate will be, or whether a surprise manual award is coming. The uncertainty keeps them checking the app - and the app is where performance data lives.

Four psychology hooks, one ritual, one monthly photo op. That's the whole thing.

When to use itโ€‹

This is the right first strategy for most vimigo customers. Specifically:

  • Team size: works from 5 staff up to around 100. Below 5 you don't have enough witnesses for social proof to kick in; above 100 you'll need to segment by department or branch to keep it intimate.
  • Stage: early rollout, month 1โ€“6 of vimigo. This is the ritual that bakes the whole system into culture before you add anything more complicated.
  • Industry: any. F&B, retail, services, B2B sales, manufacturing back-office - I've seen this work in all of them.

Don't use it when:

  • You're running a pure-commission sales floor where staff live on vimiBank payouts and don't see diamonds as meaningful. Pair diamonds with commission there, but don't lead with diamonds.
  • You, the boss, won't actually show up and run the Rewards Day publicly. If you're going to "delegate it to HR" on month one, stop. The first three Rewards Days need you personally - otherwise the ritual never locks in and you'll blame the software.
  • Your team distrusts you already. If there's an active conflict (unpaid wages, broken promises), diamonds will read as manipulation. Fix the trust first. Then come back to this page.

Setup - 5 stepsโ€‹

Step 1 - Set the diamond economyโ€‹

Open Diamond in the admin panel. You have two numbers to decide: the exchange rate and the monthly budget per department.

Exchange rate. The default is 500๐Ÿ’Ž = RM1. Keep this unless you have a strong reason to change it. Big numbers work better than small ones - "I earned 8,000 diamonds this week" feels more motivating than "I earned RM16." Staff don't need to know the exact conversion. You (the boss) do, for budgeting.

Monthly budget. Use this table as a starting point:

Team sizeMonthly diamond budgetApprox RM cost
Under 10 staff50,000๐Ÿ’Ž total~RM100
10โ€“30 staff10,000โ€“15,000๐Ÿ’Ž per department~RM200โ€“500
30โ€“50 staff15,000โ€“25,000๐Ÿ’Ž per department~RM500โ€“1,000
50+ staff25,000โ€“50,000๐Ÿ’Ž per department~RM1,000โ€“2,500

Top up the Principal Wallet at the start of each month. If you run out mid-month, staff will try to redeem and fail - a known way to kill momentum.

Tip: Budget for 3 months up front and get finance sign-off before launching. Running out in month 2 and cutting back is the fastest way to lose the team's trust.

Step 2 - Stock the vimiRewards catalogโ€‹

Open vimiRewards and add between 5 and 10 items at three price tiers. Cheap, medium, premium. Each tier serves a different psychology role.

Entry tier (5,000โ€“15,000๐Ÿ’Ž). Items every staff member can afford within the first month. These remove the "this is only for top performers" objection.

  • Coffee voucher (Starbucks / local cafe) - 5,000๐Ÿ’Ž
  • Phone top-up RM10 - 5,000๐Ÿ’Ž
  • Cinema ticket (weekday) - 15,000๐Ÿ’Ž

Mid tier (20,000โ€“50,000๐Ÿ’Ž). Items for consistent performers. Staff should need about 3โ€“6 weeks of normal earning to reach these.

  • Movie voucher for 2 - 30,000๐Ÿ’Ž
  • Shopee / Lazada voucher RM50 - 30,000๐Ÿ’Ž
  • Grab voucher RM80 - 40,000๐Ÿ’Ž
  • Hero tier: Team pizza (for the whole dept) - 50,000๐Ÿ’Ž

Premium tier (80,000โ€“200,000๐Ÿ’Ž). Aspirational. Only top performers or staff who saved hard for 2โ€“3 months reach these. Their purpose is to be visible, not frequently redeemed.

  • Spa voucher - 80,000๐Ÿ’Ž
  • Gadget (headphones, smartwatch) - 150,000๐Ÿ’Ž
  • Weekend hotel stay - 200,000๐Ÿ’Ž

Important: The "Team pizza" (or any shared-experience reward) is the magic item. When one person redeems it, the whole department eats together. That one redemption does more cultural work than ten individual redemptions. Price it so it's reachable every 1โ€“2 months by a top performer.

Keep the catalog at 5โ€“10 items. More than 10 and staff get decision fatigue. Fewer than 5 and the variety doesn't feel real.

Step 3 - Pick your monthly Rewards Daysโ€‹

Pick two dates per month. I recommend the 10th and the 20th.

Why these? Three reasons.

First, they're evenly spaced - roughly every 10 days. Close enough to keep anticipation short. Far enough apart that each feels like its own event.

Second, neither collides with payroll. Most Malaysian SMEs pay salary on the 25th, 28th, or 1st. Keeping Rewards Days in the middle of the month means they're not drowned out by payday noise - they get their own emotional airspace.

Third, the 10th is late enough in the month that staff have earned this month's diamonds. And the 20th is a second chance for staff who missed the first one. Two shots at redemption per month is the sweet spot - one feels stingy, three blurs together.

If the 10th falls on a weekend or public holiday, move it to the next working day. Don't cancel. The consistency is what creates the anticipation.

Step 4 - Announce the systemโ€‹

Before Rewards Day works, staff need to know it exists. Don't just post a settings change and assume they'll find it. Announce it publicly.

Here's a script you can adapt for the team group chat or WhatsApp:

Hi team,

Starting [date], we're doing vimiRewards Day. Here's how it works:

1. You earn diamonds through your vimiGoal, through daily check-ins,
and whenever I manually award you for good work.
2. Twice a month - the 10th and the 20th - we open the rewards shop
in the vimigo app. That's when you can cash your diamonds for stuff
(coffee, movie tickets, team pizza, etc.).
3. Outside those two days, diamonds keep counting, but you can't
redeem. So save up.
4. First Rewards Day is [date] - I'll be running it personally.
Bring your phone, we'll do it together in the morning.

Any questions, DM me. Let's go.

Keep it this short. Long emails don't land. If you want to, pair it with a one-minute voice note in the chat - bosses who use voice notes get 3ร— the engagement on this kind of announcement in my experience.

Step 5 - Start awardingโ€‹

The system is only alive if diamonds actually flow. Aim for at least one diamond award per staff member per week during the first month. Even 500 diamonds with a two-line reason is better than no award.

Award on three triggers:

Automatic via vimiGoal. If a staff member hits their monthly goal, the diamond payout fires automatically on interval close. Good - this is your outcome reward.

Automatic via vimiCheckin / streaks. Every on-time week can earn a small diamond bonus. Good - this is your effort reward.

Manual, from the boss. At least once a week, use the diamond transfer in the admin panel or the mobile app to award a named staff member with a named reason. Post the reason publicly.

Example public award message:

"Awarded 3,000๐Ÿ’Ž to Aisha - for staying late on Friday to prepare the client presentation. That's the kind of effort that doesn't show up in numbers but keeps this place running. Thank you."

This single habit, repeated weekly, is what the whole strategy is built on. If you skip the manual awards, the system becomes mechanical and the team stops caring.

The first month - what to expectโ€‹

Don't expect the team to light up in week one. Real habit formation takes about 4 weeks. Here's the realistic timeline:

Week 1 - Confusionโ€‹

Most staff will ignore the first announcement. They've been promised "new exciting things" by bosses before, and they're waiting to see if this one sticks. Expect at least half the team to not know what's going on.

Action: send two or three quick reminders. Not angrily. Cheerfully. "Reminder - you have 2,000๐Ÿ’Ž in your account. Coffee voucher is 5,000๐Ÿ’Ž. Keep going."

Do two or three manual public awards this week. Big names, big visibility. People who watch quietly this week will start participating next.

Week 2 - Hoardingโ€‹

Early adopters start noticing their balance. A couple will start asking detailed questions - "can I save diamonds from this month to next month?" "What happens if I combine with a colleague?" This is a good sign. They're doing the math.

Action: answer every question publicly in the team chat. Questions from one person are questions from five. Transparency here builds fairness perception.

Week 3 - Skeptics joinโ€‹

The initial skeptics - the ones who ignored week 1 - see early adopters calculating redemptions and get curious. The Leaderboard helps here: people who see their name ranked in the middle of a visible board will subconsciously push to earn more.

Action: don't push. Let them come. Just keep awarding weekly and keep the public recognition going.

Week 4 - First Rewards Dayโ€‹

This is the moment the whole strategy hinges on. Make it a ritual.

On the morning of the 10th (or 20th, whichever your first day is):

  1. Announce in the team chat that Rewards Day is live.
  2. Bring everyone together - physical if possible, on video call if not.
  3. Run the redemptions live, one at a time. Congratulate each person.
  4. Take photos. Post them in the team chat the same day.
  5. Hand over the actual rewards (or send the voucher codes) that day, not later.

The first Rewards Day locks in the habit. Phone it in and the habit never forms. Do it properly and you'll have a team that asks about the next Rewards Day without being reminded.

Warning: If you cancel or delay the first Rewards Day, you have done more damage than not launching it at all. Pick a date you can keep. Block it in your calendar in permanent ink.

Mistakes to avoidโ€‹

Five ways to wreck this strategy. Avoid them all.

1. Inflation. You start giving 50,000 diamonds for trivial tasks because you're excited. Within a month, the catalog is emptied, and now the next 50,000-diamond award feels normal. Rewards lose meaning. Stick to the reward-intensity table in strategies-intro.md and don't exceed it without a reason you can articulate.

2. Boss disappears on Rewards Day. You delegate the first or second Rewards Day to HR because "you have a meeting". The ritual becomes a transaction. Staff sense that you don't care, and the anticipation dies. Block those two mornings in your calendar for the next 6 months. Non-negotiable.

3. Catalog too rich-people-focused. All items cost 50,000+ diamonds. New staff see it, do the math, and realise they're 6 weeks away from their first redemption. They disengage immediately. Always include 2โ€“3 items under 15,000 diamonds that anyone can reach in week 2 or 3.

4. No public recognition. You award diamonds but only through the app's quiet interface. No announcements. No names in the chat. The Recognition principle is broken, and all you've built is a more complicated version of cash. Make public recognition a weekly habit.

5. Changing the system every month. You launch, don't see immediate results, panic, and reshuffle everything for month 2. The team, just starting to trust the system, now has to learn a new set of rules. Trust resets to zero. Commit to running the same system unchanged for 90 days. Then tune it.

Tuning after month 1โ€‹

Wait until after the second Rewards Day (about day 30) to run your first review. Look at these five numbers:

MetricTargetWhat it tells you
Redemption rate60%+ of staff redeemedBudget is calibrated right
DistributionNo staff with 0 redemptionsCatalog has entry-level items
Top 3 itemsShould emerge clearlyRestock these, they're popular
Dead itemsOver 60 days, no redemptionsDrop and replace
Budget burnUsed 70โ€“95% of monthly budgetYou're sustainable

If redemption is under 60%: either rewards are priced too high for the earning rate, or you're not awarding enough diamonds. Check both. The easier fix is usually to increase your weekly manual awards.

If some staff have zero redemptions: they don't have enough diamonds to reach even the cheapest item. Check who - it's usually someone whose vimiGoal isn't set up, or a new hire. Fix their goal or add a onboarding "welcome diamond" grant.

If one item dominates redemptions: good. Add more stock. Don't replace it with something "more interesting" - you'll frustrate the people who wanted it.

If the premium tier never gets redeemed in 3 months: either it's priced too high, or your top performers aren't earning enough. The premium tier's job isn't to be redeemed constantly - it's to be visible. But at least one person should reach it per quarter. If not, price-adjust.

If you burn 100%+ of budget: tighten the auto-awards (usually the vimiGoal reward tiers are too generous) or reduce manual award size. Don't reduce frequency of manual awards - that kills Recognition.

Variationsโ€‹

Once you've run the base strategy for 90 days, here are the common variations.

Sales-heavy teamsโ€‹

For teams where 60%+ of staff are in sales, pair this strategy with vimiSales and vimiBank commissions. Key rule: commission goes to vimiBank, diamonds go on top for effort. Don't turn your sales payouts into diamonds - staff will feel short-changed. Instead, use diamonds for the things commission misses: mentoring juniors, hitting activity targets (calls made, demos booked), helping a colleague close.

Service teamsโ€‹

For teams without natural KPIs (restaurant floor, retail, customer support), diamonds become the primary recognition tool. Increase manual-award frequency - aim for 2โ€“3 public awards per staff per week in service teams. Reduce vimiGoal pressure; weekly targets should feel like check-ins, not exams. The ritual and the recognition carry the strategy.

Multi-branchโ€‹

For chains with 3+ outlets, run a separate Rewards Day per branch but keep the catalog identical across all branches. Why separate days? Each branch manager needs to run their own ritual, and the logistics of handing out vouchers to 50 people in one session falls apart. Why same catalog? So staff who transfer between branches don't feel like the grass is greener elsewhere. Use Custom Leaderboards per branch for internal competition.

Remote teamsโ€‹

For fully-remote or hybrid teams, replace physical rewards with digital. The catalog becomes:

  • Food delivery voucher (GrabFood, FoodPanda)
  • Streaming subscription (Netflix, Spotify month)
  • Online course credit (Udemy, Coursera)
  • E-wallet top-up (TnG, Boost)

Run Rewards Day as a video call instead of in-person. The ritual still works - what matters is the fixed date, the public redemption, and the photo-or-screenshot evidence shared after. Remote teams that skip the video-call ritual always end up with a weaker version of this strategy.