Think about the last time someone on your team was praised because of the system.
Not for the month's results. For the system. A well-written work order, a time entry logged on the spot, a photo of the part before the swap.
Now think about the last time someone got called out because of it.
The second memory came faster, didn't it?
Last week we talked about the "yes" that never turns into use. Today it's the question that comes right after: what keeps someone using it when nobody is watching?
🔧 Maintenance learned to talk only about the big stuff
In our line of work, good news is the absence of news. The pump that didn't fail doesn't get a meeting. The shift that ran smoothly never comes up.
👉 Praise, when it comes, goes to the big event: the downtime avoided, the availability record, the audit with zero nonconformities. The rest of the year is silence — or reprimands.
Software works the same way. The rollout is born with a big target: "one hundred percent of work orders in the system in ninety days," "backlog at zero by December." It's a leadership target, and it's right as a direction.
The problem is what the technician sees on Monday morning. They don't see the ninety days. They see three more fields to fill in, five more minutes per work order and no difference in their day.
In thirty years I've seen rollouts die not for lack of targets, but for lack of rewards along the way.
👉 A six-month target doesn't sustain Monday-morning behavior.
🧠 What happens right after the action decides whether it comes back
Every new behavior costs energy. And the brain decides whether it's worth repeating based on what happens right afterward — not on what was promised for the end of the quarter.
If nothing happens after closing the work order in the app, the conclusion is simple: it doesn't matter. If what happens is a chewing-out because a field was missing, the conclusion is worse: this is a place where I get things wrong.
👉 People who only hear about the system when they make a mistake learn that the system is a place for mistakes.
Three things make a small win work.
It has to be immediate: recognition on the same day is worth more than recognition at the end of the month. It has to be specific: "congratulations to everyone on the adoption" teaches nothing, because nobody knows what to repeat. And it has to be genuine: a team can spot manufactured praise a mile away.
There's a fourth ingredient, too, the most underrated one: the sense of progress. We can put up with a lot of effort when we can tell we're moving forward. And we give up fast on anything that seems stuck in place.
👉 A small win isn't a consolation prize. It's the only proof the mind accepts that the new effort is paying off.
⚠️ The signs of a rollout with no small wins
They show up slowly, and almost always after the novelty has worn off:
- Usage drops in the second month. The launch excitement is gone; the pressure stayed.
- Only the manager opens the reports. The team feeds a system that never gives anything back to them.
- The system only makes the agenda when a KPI gets worse. Nobody schedules a meeting to talk about what improved.
- The careful and the careless get the same treatment. The technician who describes the failure cause and the one who writes "done" spend the month hearing the same thing: nothing.
- "Adoption" becomes a slide metric. It shows up in the presentation to leadership and never in the conversation with the shift.
👉 When care and carelessness get the same silence, care is the first to give up.
And that's the cost nobody calculates. The first to drop good record-keeping are precisely the ones who were doing it right. What's left is the bare-minimum data — and, as we saw last week, fake data is worse than no data at all.
🛠 What the system can give back — and what only you can do
From my side of the table, no exaggeration.
Manusis4 keeps what usually gets lost. Every work request that becomes a work order, every time entry, every piece of evidence and every failure analysis stays in the asset history, with who did it and when. That gives you the raw material to make the small stuff visible: the technician who opens the pump's record and sees the history they built themselves; the repeat failure that only surfaced because three people described it properly; the work request response time that dropped this month.
The mobile app, which works with no signal and accepts photos and voice, helps in a different way: it lowers the cost of the action. And a cheap action is an action that gets repeated.
What the system doesn't do is notice for you. It stores the well-written work order; it doesn't thank the person who wrote it. A dashboard doesn't shake hands.
And there's a shortcut I have to advise against: gamification for show. Time-entry leaderboards, points, badges. A quantity ranking rewards whoever logs the most, not whoever logs best — and within a month you'll have work orders chopped into five to climb the table.
👉 Use data to see the small stuff, never to turn the small stuff into a competition.
💡 Five moves to make the small stuff work for you
- Define the smallest possible win — and say what it is. Not "use the system more." Something that fits in one sentence and can be seen this week: "every corrective work order on the shift closes with one line on the cause."
- Recognize it close to the action. Two lines in tomorrow's toolbox talk are worth more than a plaque in December.
- Praise the specific, by name. "The description Marcos wrote on the pump 3 work order saved the night shift two hours of troubleshooting." That teaches the whole team what to repeat.
- Give the data back to the people who produced it. Once a week, show the shift something that only exists because they recorded it: the failure that kept coming back, the part that's always missing, the preventive maintenance that prevented downtime.
- Raise the bar only when the small stuff has become a habit. One win at a time. Whoever piles five new requirements on in the second month goes straight back to the "yes" without use.
👉 Lasting adoption isn't born from a big launch. It's born from a hundred small confirmations that it was worth it.
🧠 This week's reprogramming
Count how many times this week you talked about the system with your team. Now count how many of those times were to demand something.
If the second count came close to the first, your team has already gotten the message — even if you never said it.
What gets noticed gets repeated. What only gets demanded gets faked.
This week, pick one real small win in how the system is being used and say it out loud, with a name and with detail. Then watch what happens the following week.
📣 Next week
👉 "The system is slow." "The screen is confusing." "This doesn't work for our reality." Almost always, the technical complaint is just the part that can be said out loud.
In #68 we'll talk about what users are really saying when they complain about the system — and how to listen to what's underneath.
Until then.