Skip to main content

Strategies - How to design what actually works

How to mix vimigo modules into a system that actually changes how your people behave.

You've bought the software. Good. That was the easy part. The hard part is the next 30 days, when you have to decide what to switch on, who gets what, and why anyone on your team should care. This guide is where the coach steps in - not to sell you anything, but to keep you from making the same mistakes the last 200 bosses did.

Why your business doesn't scale yet​

Short answer: because your team doesn't run itself yet.

Long answer, and the reason I wrote this whole guide: it doesn't matter if you have 5 staff or 50, every SME boss in Malaysia I've sat down with eventually tells me the same thing. "I want to grow, but the moment I take my hand off the wheel for a week, things drift." That's not bad luck. That's a system problem, and the system you need is the same shape whether you're at 5 staff or 50.

If you're a small team (under 15 staff), the wall hasn't fully hit you yet, but the patterns that produce it are already forming. If you're past 20 staff, you're in it, and you know exactly which people I'm talking about. Same wall, same shape, just a different level of pain.

Let me coach you through what's actually breaking. Whether you've never had a formal performance reward system (most Malaysian SMEs don't), or you have a KPI sheet that nobody opens anymore, here's what I see going wrong under the surface.

Effort goes unwitnessed. At 5 staff in one room you mostly know who's hustling, but the quiet grind of your second-best person still goes unsaid because you're focused on the loud cases. At 25 staff across outlets you don't see anyone clearly - you manage by report, by feeling, and by who shouts loudest in the WhatsApp group. Either way, your real top performers stay invisible. The real coasters get praised because they're loud.

Annual bonuses don't move daily behaviour. Telling Aisha in January that "if you hit your sales target by December you'll get a 1-month bonus" gives her zero reason to push hard on a Tuesday in March. The reward is too far away. By the time it arrives, half the team has forgotten the goalposts existed and the other half has been job-hunting since August.

Salary increments stop motivating after the third one. A RM 200 raise once a year feels meaningful the first time, fine the second time, and like an entitlement by year three. It's not a reward anymore. It's the new baseline. Staff don't work harder for it because it's already priced into their expectations.

The strong subsidise the weak in silence. In every SME team, whether yours is a team of 5 or 50, two or three people quietly do most of the real work. They see the others coasting on the same salary. They burn out, they quit, and the team you carefully built collapses overnight. Without a public, fair scoreboard, your best people leave first.

You become the bottleneck on motivation. Every promotion, every raise, every "thank you" still runs through your mouth and your time. The day you take a one-week holiday, the team coasts because nobody else owns the job of recognising effort. This is the moment most SME bosses quietly give up on growing the business - not because they couldn't find more customers, but because adding more people just adds more management work to themselves.

You see the pattern. Whether your team is 5 or 50, the wall is the same shape: a business that runs on you - your memory, your praise, your push - can't run without you. And a business that can't run without you can't scale, because adding people just adds more work for you. Recognition, accountability, and rewards have to live somewhere outside your own head, in something everyone can see, every day, on their phone. Otherwise the same boss who built the team slowly burns out trying to keep it together.

vimigo is built to be that system - the performance reward system that runs the daily layer for you. If you've never run a formal performance reward system before, vimigo is the lightest possible way to start - you don't need a KPI document or an HR background. If you have a KPI sheet that nobody opens, vimigo is the daily, public layer that makes it actually live. Either way, the rest of this guide is how I'd coach you to design it properly. Because turning vimigo on without a strategy is its own kind of failure - and there are exactly four ways bosses make that mistake.

Four design mistakes that kill your setup in 2 weeks​

Here's the pattern I see almost every week. A boss in KL or JB or Penang sets up vimigo on a Monday. By Friday, every module is switched on. Diamonds are flying, badges are awarded, leaderboards are live. Two weeks later, nothing has actually changed. Sales are flat. Staff are still late. Nobody talks about diamonds in the office.

What went wrong? Almost always one of four things:

Too generous. You set "100 diamonds for showing up" and "10,000 diamonds for closing a sale". Within a week, the bottom of the catalog is empty, the budget is gone, and Ahmad in Operations is comparing payouts with Wei in Sales and feeling cheated. Diamonds become Monopoly money. People stop caring.

Too stingy. The opposite. You set up a beautiful catalog where the cheapest item is 30,000 diamonds, but the average staff earns 1,500 diamonds a month. After three months, nobody has redeemed anything. Staff conclude this is "another HR thing the boss won't follow through on" and quietly disengage.

Too rigid. You launch one giant quarterly goal. Aisha misses it in week 2 because she had food poisoning. From week 3 onward, she's mentally checked out - she can't catch up, so she stops trying. By week 8, three other people are in the same boat, and you've accidentally taught your best people to give up.

Too random. Diamonds get awarded when you remember to award them. Some weeks you give 10,000 to your top performer. Some weeks you forget. Staff can't predict what behaviour earns what reward, so they don't change behaviour. The system feels like a lottery, not a coaching tool.

The good news: every one of these failures is fixable, and they're all variations of the same root cause - designing the rewards before designing the strategy. This guide flips that order.

Start with your staff's pain points (not your problems)​

Before you pick a single module to turn on, stop and ask a different question. Not "what do I want my staff to do?" - that's the boss's question. Ask "what does my staff actually need?" - that's the coach's question. Most performance reward systems fail because they're designed around what the boss wants to get, not what the staff wants to receive.

Maslow's hierarchy, applied to your Malaysian SME​

Psychologist Abraham Maslow stacked human motivations into five levels. The lower ones have to be met before the higher ones matter. Apply this to your team:

LevelWhat it isHow vimigo-relevant SME staff feel it
1. PhysiologicalFood, shelter"Will this job pay enough to live?" Basic salary covers this.
2. SafetyJob security, stable income"Will I still have this job next month? Will my commission actually pay out?"
3. BelongingBeing part of something"Does my team actually include me? Am I seen?"
4. EsteemRecognition, status"Does anyone notice when I do good work?"
5. Self-actualizationGrowth, mastery"Am I becoming better at something? Is there a future for me here?"

Most SME staff in Malaysia are somewhere between level 2 and 4. Your reward strategy has to speak to where they actually are, not where you wish they were. If Ahmad is worried whether this month's commission will actually be paid (level 2), giving him a trophy (level 4) won't move the needle. Pay him transparently, on time, first - then the trophy matters.

The three pain points every SME staff faces​

Across every conversation with Malaysian SME staff, the same three pains come up:

"Am I earning enough?" This is pure level 1–2. Base salary, commission, overtime. If the answer is no, nothing else you build matters. Solve this first.

"Is my effort being seen?" Level 3–4. Invisible work is the biggest silent motivation killer. Staff who believe the boss doesn't know what they're doing disengage - even when the boss secretly does know, because nobody said so out loud.

"Is this going anywhere?" Level 5. Does this job build a skill I can use? Will I be promoted? Is there a future that's better than the present? Staff without a "yes" to this question quietly start job-hunting on LinkedIn.

A strategy that addresses all three wins. A strategy that only addresses one is a patch - useful, but not transformative. Good strategies move staff up the pyramid over time; bad strategies ignore the level they're actually stuck on.

The win-win principle​

Every good strategy in vimigo creates value for BOTH the company and the staff member. If the strategy only helps the company, staff will comply but not commit. If it only helps the staff, the budget runs out. The sweet spot is the one where both problems shrink at the same time.

Here's the best example I've seen.

The GrabFood moment​

Picture this. Your staff Faizal is a skilled graphic designer on your team. His base salary is RM3,800, which is tight. After work, three nights a week, he rides out to do GrabFood deliveries for another RM800 a month. It helps him pay bills. Nothing wrong with that - on the surface.

But look at what's happening. Your company just trained Faizal on Illustrator, Photoshop, branding, and client communication - tens of thousands of ringgit of skill investment. At night, that skill is idle. He's moving paper bags of nasi lemak across KL because that's the only "extra work" accessible to him.

The win-win strategy is obvious once you see it. Don't let him drive for Grab. Offer him extra work at your company, at premium rates, using the skills you already trained. "Faizal, we have a rush poster design job for client X this weekend. Take it, and we'll pay you RM400 extra." Suddenly:

  • Faizal earns RM400 for a few hours of skilled work he enjoys, no bike commute, no cold nasi lemak.
  • Your company earns more on client X's rush job than if you hired a freelancer, because Faizal is 10× faster than an outsider (he already knows your brand guidelines).
  • No hiring cost. No vetting a new freelancer. No training. No NDA.
  • No wasted skill. Your Illustrator investment is working instead of sitting.
  • Bonus: Faizal trusts you more. You just proved you value him as a craftsman, not just a seat.

Both pain points removed. Both sides win. And you didn't need a new module or a new strategy - you just reframed the problem so both sides gain.

Design every strategy this way​

When you're about to launch a strategy, write two sentences:

  1. The company wins because: __________________
  2. The staff wins because: __________________

If you can't finish both sentences with something real, the strategy is not ready. Don't launch it.

A commission structure where the company wins (more sales) but the staff loses (worked 80 hours for RM200 commission) is a patch, not a win-win. Staff will quietly leave. A bonus for "coming to work every day" that pays well (staff wins) but doesn't improve productivity (company loses) is a patch too - the budget will get cut within six months.

Win-win is the test. Apply it before you launch anything.

The 10 psychology principles every strategy uses​

Performance reward systems aren't really about money. They're about psychology. Every successful strategy in vimigo leans on at least three of the principles below. The trick is knowing which ones to use for which problem.

1. Small Win​

This is the single most undervalued principle in Malaysian SME reward design, so it goes first.

People need to score early or they quit. A "small win" is a task so easy that even your least confident new hire can hit it on day one - clocking in on time, attending a morning briefing, posting a check-in photo, saying "good morning" in the team chat. The win itself is trivial. The fact that the win earned them something they can see (even 500 diamonds) breaks down their resistance to the whole system.

Small wins work because they establish agency. Staff who earn even one diamond on day one of a new performance reward system feel "I can win this game." Staff who go a week without earning anything start thinking "this doesn't apply to me." Once that thought sets in, it's very hard to reverse.

The rule: everyone on your team should earn at least one small win per week. Not a big one. Not a hero. Just one tiny acknowledgment that they're in the game. If your rewards design has anyone going three weeks with zero earnings, you've accidentally told them they don't matter. Fix it immediately by carving out an effort-based daily diamond (attendance, check-in, team chat participation) so even the slowest performer accumulates something.

Stack small wins into a ladder and you have the next principle (Progress Ladder). Combine small wins with daily visibility and you have a habit (see Momentum). Small wins are the atom of every successful strategy.

In vimigo, you give Small Wins by setting a basic vimiGoal target almost everyone can hit (like "log 1 site visit per day"), by handing out diamonds the first week with a one-line reason ("for asking a good question in the team meeting"), or by turning on a daily vimiCheckIn streak with diamond micro-rewards.

2. Progress Ladder​

People are wired to climb the next rung if they can see it. A Progress Ladder is a tiered reward - hit 5 sales, get 2,500 diamonds; hit 10, get 7,500; hit 15, get 20,000. The numbers escalate fast enough to feel exciting but slow enough to feel earned. The key is making the next tier visible while you're still on the current one.

In vimigo, you build ladders inside vimiGoal using its tiered targets, or inside vimiChallenge for short-term ladders.

3. Hero Win​

Every team needs at least one moment a month where someone earns a reward so big it shocks the room. A Hero Win is a single, oversized payout - 50,000 diamonds for closing the biggest deal of the year, 100,000 for hitting an annual stretch target. The dollar amount matters less than the witness count: everyone has to see it land.

In vimigo, you trigger Hero Wins by manual diamond transfer with a public reason, by hero tiers in vimiGoal, or by a single jackpot prize on the Lucky Wheel.

4. Nobody Wants to Be Last​

This is the most underused principle in Malaysian SMEs. Most bosses focus on rewarding the top - but the loss-aversion side of the brain is much more powerful. Knowing your name is going to appear publicly in the bottom three of a leaderboard is a stronger motivator than the prospect of being #1. Almost nobody talks about this honestly with their team, but everyone feels it.

In vimigo, you turn this on by enabling Leaderboard and making rankings visible to everyone - not just the top 5.

5. Comeback (Weekly Reset)​

If a system never resets, anyone who falls behind quits the game. A Comeback is a forced reset point - every Monday, every 1st of the month, every quarter - where the scoreboard zeroes out and the trailing person can compete fresh. Without resets, the same five people win every cycle forever, and the bottom 80% disengages.

In vimigo, you build resets through weekly vimiChallenge cycles, monthly leaderboard windows, and monthly vimiClass grading.

6. Momentum / Streak​

Habits form when an action becomes easier to repeat than to skip. A streak is a daily count - 5 days of on-time check-in, 7 days of vimiGoal updates - where breaking it feels worse than maintaining it. After 14 days the brain starts treating the action as "what I do", not "what I'm trying to do".

In vimigo, you build streaks through vimiCheckIn on-time tracking and the daily update reminders inside vimiGoal.

7. Recognition (Boss-Awarded)​

Numbers miss most of what makes a workplace work. Mentoring a junior, staying late to fix a customer issue, keeping calm during a stressful week - these never show up on a sales leaderboard, but they're the things that make staff actually want to keep working for you. Recognition is the name for the small, manual, public award you give for invisible effort.

In vimigo, you do this with a manual diamond transfer (see the Diamond guide) with a specific, visible reason - "for handling the difficult customer on Tuesday with patience."

8. Fairness​

A performance reward system that feels rigged is worse than not having one at all. Fairness means everyone can see how scores are calculated, who got what, and why. The targets are visible. The grades are visible. The diamond transactions have remarks. There are no secret bonuses going to the boss's nephew.

In vimigo, you enforce fairness by using vimiGoal (visible targets), vimiClass (transparent monthly grading), and the Diamond transaction history (every award has a remark).

9. Variable Rewards​

Predictable rewards become wallpaper after a month. A variable reward is one where you don't know exactly what you'll get - it could be a 1,000 diamond consolation or a 20,000 diamond jackpot. The unpredictability is what keeps people checking back. This is the same principle that makes slot machines work - used for good, it keeps a reward catalog fresh instead of stale.

In vimigo, you use the Lucky Wheel for variable rewards, or surprise vimiChallenge bounties announced mid-month.

10. Effort + Outcome Balance​

If you only reward outcomes (sales closed, targets hit), the people who sit furthest from those outcomes - admin staff, support staff, new hires - give up immediately. They have no path to win. Mixing effort rewards (attendance, knowledge sharing, helping a colleague) with outcome rewards keeps the whole team in the game.

In vimigo, you balance this by giving small daily diamonds for effort (check-in, vimiCheckin streak, vimiKnowledge contributions) alongside larger periodic diamonds for outcomes (goals hit, sales closed).

The 7-day test - the best strategies show results in a week​

This is the single most important rule for designing strategies: short cycles beat long cycles, almost every time. And the gold standard of a strategy is when you can see measurable change in 7 days.

Bosses love designing quarterly strategies. "Q1 goal: hit RM500k in sales. Q2: retain 95% of customers." It feels strategic. It feels executive. It's also usually a disaster, because by the time you realise something is off, three months have burned. You can't re-steer a ship that's already docking.

The 5 indicators of a winning 7-day strategy​

The best strategies show visible change across all five of these within a single week:

IndicatorWhat "changed" looks like in 7 days
Staff behaviourPeople start doing new things without being told - checking the leaderboard, posting in team chat, staying engaged after the boss leaves the room
MotivationThe energy in the office is different. People talk about their diamond balance, ask when the next challenge is, compare progress with teammates
CultureSmall rituals start to form - the "Monday morning leaderboard review", the daily chat shout-out, the "who bought coffee with their diamonds" joke
PerformanceMeasurable KPIs move. Sales go up. Late check-ins go down. Goal completion rate climbs
Company profitThe bottom line is actually better than the previous week. This is the real test - everything else is leading indicator

If your strategy moves all five in seven days, keep it and scale it. If it moves three out of five, tune the remaining two and keep going. If it moves zero after seven days, kill it and start over with a different design. Do not wait a month to make this call.

Why 7 days, not 30 or 90​

  • Short attention spans. Most SME staff can hold a 1-week goal in their head clearly. A 3-month goal fades by week 2.
  • Faster feedback = faster improvement. A weekly cycle gives you 4 chances to adjust in a month. A monthly cycle gives you 1. If your first target was wrong, you save 3 weeks instead of 3 weeks of wasted pain.
  • Profit visibility. With the right setup (vimiSales daily updates, live leaderboards, weekly vimiBank payout summaries), you can actually see the revenue line move within days, not weeks.
  • Morale compounds. A team that experiences visible wins in week 1 rolls into week 2 with momentum. A team still waiting for "Q1 results" is already demoralised.

How to design a 7-day strategy​

The pattern to use: design so that a measurable outcome lands within 7 days of launch, and the first adjustment point is at 14 days. If a strategy can't show you anything meaningful in week one, scale it down until it can.

Bad (slow feedback): "Everyone gets a bonus if we hit Q1 sales of RM500k."

Good (7-day feedback): "This week: every sale over RM1,000 earns 2,000💎 the day it's closed. Top 3 sellers at end of week get a 10,000💎 bonus and public shoutout Monday morning."

Same idea, compressed. You see in 7 days whether sales volume actually moved, whether staff are engaging, and whether the reward intensity was right. Adjust Monday. Re-launch Tuesday.

In vimigo, that means: start with a weekly vimiChallenge instead of a quarterly vimiGoal. Run a single daily-diamond rule for a week, see what happens, then extend. Let your first vimiClass grading be a dry run for 30 days before you tie real stakes to it.

You're not being slow. You're being iterative. Three small weekly wins teach you more than one big quarterly failure.

The framework: SET → CHECK → REWARD​

These ten principles are the ingredients. The framework below is the recipe. Almost every strategy you'll design in vimigo follows the same three-stage cycle, and you'll know your system is broken when one of the three stages is missing.

SET - Decide what you're measuring before anyone earns anything. This is where vimiGoal lives. You define a target ("close 8 deals this month", "log 20 site visits this week") and make it visible to the staff member it applies to. The target follows SMART rules - specific, measurable, agreed, realistic, time-bound. If you skip this step, your rewards become arbitrary, and we're back to "lottery, not coaching".

CHECK - Make progress visible every day, not just at month-end. This is where Leaderboard, vimiClass, and the live progress bars in vimiGoal earn their keep. Staff should be able to glance at their phone and know exactly where they stand. The dangerous opposite is the boss who says "let's wait until month-end to see who did well" - by then, behaviour is already locked in for the month, and there's nothing to coach.

REWARD - Celebrate at fixed, repeated moments. This is where Diamond + vimiRewards Day come in, plus vimiBank for commission payouts and vimiBadge for instant recognition. Rewards are not the engine of the system - visibility and clear targets are. Rewards are the punctuation that makes the cycle feel intentional and worth repeating.

The framework matters because most failed performance reward systems have all three pieces but in the wrong order. Bosses tend to design rewards first, then bolt on goals, then forget to check progress until month-end. Flip it: SET the target, CHECK constantly, REWARD on a ritual.

The goal - a self-driven system (setup and forget)​

The ultimate destination of a good reward strategy is not to make YOU a better manager. It's to make you unnecessary for day-to-day motivation. The system should run without you.

Call this a self-driven system. The goal is simple: you set it up, it runs, your role shifts from enforcer to coach. Bosses who reach this stage say the same thing: "I used to spend half my day chasing people. Now I look at the leaderboard for 10 minutes in the morning and then work on the things only I can work on."

Signs your system has become self-driven​

What you used to doWhat happens instead when the system self-drives
Remind people to check in on timeThey check their own leaderboard position; peers remind each other
Track who hit the sales targetThe vimiGoal dashboard auto-calculates; winners self-announce
Decide monthly bonuses manuallyvimiBank payouts compute from the commission formula
Chase staff about goal progressStaff refresh their own goal page 3× a day
Manually publicise top performersLeaderboard auto-publishes weekly; public Rewards Day celebrates
Pick who deserves a badgeTeam members nominate each other via vimiBadge requests

How to get there - the 90-day path​

You can't switch this on overnight. It takes about 90 days for most teams. The path:

  1. Month 1 - Boss-driven. You award diamonds manually. You remind people about targets. You're hands-on. Don't skip this - staff need to see the boss believes in the system before they will.
  2. Month 2 - Shared drive. You start delegating. Managers give diamonds within their teams. Staff start checking leaderboards on their own. You pull back from daily reminders.
  3. Month 3 - Self-driven. You step back further. Your role is now weekly review + occasional big-moment public recognition. The week-to-week loop runs without you. The system is now a habit.

The biggest trap​

Bosses who want control cannot reach month 3. If you keep overriding the leaderboard ("actually Wei should be first even though he's #3 in sales"), or if you secretly adjust payouts every month, the system never self-drives. Staff learn that the rules are the boss's feelings, not the system. Trust dies, and you're back to chasing people.

The harder it is for you to let go, the more you need to let go. Design the system so the rules are fair, make them transparent, and let the rules win. You're not abandoning your team - you're graduating them to self-management. That's what frees you to grow the business instead of babysit it.

How to design your first strategy​

If you've read this far and you're thinking "OK, but where do I actually start?" - here's the five-step decision walkthrough. Do it on paper or in a notes app. Don't open vimigo yet.

Step 1 - Pick the ONE behaviour you want to change first​

Don't boil the ocean. List every annoying behaviour in your team - late check-ins, missed sales targets, weak customer service, slow leave applications, low attendance at morning briefings. Now pick one. Just one.

The right one to start with is the one that is (a) easy to measure, (b) affects most of the team, and (c) you can affect within 30 days. For most Malaysian SMEs, that's either on-time check-in, daily sales updates, or hitting a basic monthly goal. Resist the urge to fix five things at once.

Step 2 - Pick the right reward intensity​

Match the reward to the difficulty. Cheap behaviour, cheap reward. Hard behaviour, big reward.

Showing up on time daily       → 500–1,000💎 per day (Small Win)
Hitting a weekly target        → 2,500–10,000💎 (Progress Ladder)
Closing a major deal           → 30,000–50,000💎 (Hero Win)
Annual stretch achievement     → 100,000💎+ (Hero Win)

If your reward feels too small, add a public moment to it - even 1,000 diamonds feels bigger when announced in the team chat with a name and a reason. If your reward feels too big, you're probably about to inflate the diamond economy. Pull it back.

Step 3 - Decide how visible to make it​

Some rewards work as private moments between you and the staff member ("Thanks for staying late. I added 3,000 diamonds to your account."). Others work only when public ("Wei just closed the biggest deal of the quarter. 50,000 diamonds. Everyone clap.").

Private rewards are good for capturing invisible effort and personal recognition. Public rewards are good for setting cultural norms and triggering the "Nobody Wants to Be Last" effect. A healthy strategy mixes both, but new bosses tend to default to private - push yourself to make at least 30% of awards public.

Step 4 - Set a review window​

Pick how often you'll look at the data. For most teams, weekly is right - short enough to see patterns and adjust, long enough that one bad day doesn't trigger an over-reaction.

In vimigo, set a weekly leaderboard window, schedule a 30-minute review meeting on Friday afternoon, and put a recurring reminder in your phone. If you don't review, you don't adjust, and the strategy drifts.

Step 5 - Be ready to adjust after 30 days​

No strategy survives first contact with the team. After the first month, expect to find: one tier you set too easy, one you set too hard, one staff member gaming the system in a way you didn't predict, one quiet performer you'd been overlooking, and at least one reward in the catalog that nobody redeems.

Don't take this as failure. It's data. Adjust the numbers, communicate the change clearly, and keep going. The strategies that win in vimigo are the ones tuned over 90 days, not the ones designed perfectly on day one.

Common mistakes​

I've seen the same five mistakes wreck strategies in dozens of companies. Watch out for these.

1. Rewards too small to feel real. Giving 50 diamonds for closing a deal when 500 diamonds = RM1 means the staff member just got 10 sen. Even psychologically, big-number gamification only works if the number actually buys something. Calibrate to your catalog - the smallest reward you give should be enough to redeem the cheapest item within two weeks of consistent earning.

2. Rewards too big and unsustainable. The opposite trap. You start month one giving 10,000 diamonds for trivial things to get people excited. By month three you've blown your budget, you can't sustain the rate, and you're forced to cut. Cuts feel like betrayal. Better to start slightly stingy and ratchet up than start generous and pull back.

3. Ignoring effort, only rewarding outcomes. Sales-led bosses do this constantly. They reward only deal closures and ignore the back-office team that made the deal possible. Result: admin and support quietly resent sales, then quietly resign. Always carve out 20–30% of your diamond budget for effort-based rewards (attendance, helpfulness, knowledge contributions).

4. Forgetting the Comeback reset. You set a quarterly goal and never reset. By week six, the bottom half of the team knows they can't win, so they stop trying. By week ten, you're carrying dead weight. Always have a reset cycle - weekly leaderboards, monthly grading, monthly Rewards Days. Reset = hope.

5. Never publicly recognising. You award diamonds correctly but never mention names in the team chat. The Recognition principle dies. Staff feel the awards are transactional, not relational. Once a week, take 30 seconds to publicly name three people and what they did. This costs nothing and changes everything.

Strategies in this guide​

Three strategies are fully written so far. More will follow as we document them.

  • Diamond × vimiRewards Day - the flagship strategy for any 5–100 staff team. Pairs daily diamond awards with a fixed monthly redemption ritual. Best place to start.
  • vimiBonus - transparent performance-linked bonus distribution - the methodology for replacing "boss decides bonus by feeling" with a fair formula using vimiClass + vimiGoal data. Run quarterly or yearly.
  • How to budget your rewards - the explicit framework for sizing every reward bucket as % of revenue, splitting into self-funding vs committed costs, and tracking weekly so you don't bleed your P&L.
  • (Coming soon) Sales floor commission strategy - pairs vimiSales + vimiBank + diamonds for high-pressure sales teams.
  • (Coming soon) Service team recognition strategy - for teams without natural KPIs (kitchen, retail floor, support).
  • (Coming soon) Multi-branch competition strategy - for chains with 3+ outlets running parallel teams.
  • (Coming soon) Onboarding gamification strategy - for fast-growing teams hiring 2+ people a month.