For operations
Operations is only noticed when it fails.
A warehouse, a fulfilment desk or an internal ops team does its best work invisibly: the order that shipped on time, the shortage that never reached a customer. That is the work worth making visible.
Get this wrong and it backfires
The trap: rewarding volume
The number every operations system gives you is throughput: orders picked, tickets processed, items moved. Rank on it and the team learns to take the easy ones first, to skip the check that slows the line, and to leave the awkward order aside: the one with the missing part, the wrong address, the customer who has already called twice, for whoever comes on next.
Volume also hides the best work entirely. The person who noticed that the same picking error happened forty times and fixed the shelf label did not move the throughput number at all. They removed a problem that would have cost forty apologies. No count-based board can see that, which is why operations teams so often feel that nobody knows what they do until the day something breaks.
What a reward looks like
What an operations board looks like here
Rank on promises kept rather than units moved: orders shipped on time, backorders cleared, issues caught before a customer reported them. Show throughput beside the score without counting it, so the team can see it without being ranked on it. Judge time-to-ship by the slowest orders rather than the average. The average hides the late ones, and the late ones are where the complaints come from.
Team level by default, and for an operation that runs in shifts, rank the shift. A shift that leaves the floor clean for the next one is doing work no individual number will ever show.
Rewarding the fix, not just the catch
Catching a problem is worth a card. Making it stop happening is worth a better one. Send both: an issue caught, a process fixed, and give the fix the better odds. The cards that fit are in the Ecommerce deck already: clearing the backorder with an email to each customer, the honest delivery date, restocking the bestseller before it ran out.
None of these needs a new system. A stock alert, an order status change and a resolved exception are events your existing tools already emit; the difference is that they now land somewhere that credits a person.
Peer recognition covers what no system logs: the colleague who stayed to finish the last pallet, the one who trained the new hire properly. Capped daily, so it means something.
Getting it in
Order management, warehouse and ticketing systems can send us a message when a status changes. Send the order or case id and the status it reached, the operator’s email so the credit lands on a person, and the promised date if there is one. A re-sync counts each change once, so nothing is inflated.
An afternoon for whoever administers the system, and the free tier covers a ten-person team indefinitely if you want to see it first.
Questions
The ones that come up
What should you measure an operations team on?
Promises kept: on-time shipping, backorders cleared, issues caught before the customer noticed, with throughput visible but not ranked. Volume alone rewards the easy order and hides the best work.
Our work is done in shifts, not by individuals. Does that fit?
Yes. Rank the shift or the team rather than the person; a board is configurable to either. Shift-level is usually the honest unit for a floor, and it avoids ranking someone on the shift they were dealt.
Can we reward fixing a recurring problem more than handling it?
Send the fix as its own event and give it better odds than the catch. That is the point: the board should make removing a problem worth more than processing it forty times.
Rank what this team actually does.
Free for your first 50 people. No card, no sales call.