The technician who argues with you still believes it's worth it. The one who says "sure, no problem" and goes back to paper has already given up on the conversation.
Monday meeting, seven in the morning. The manager wraps up the presentation: "so, everyone, starting today every work order gets closed in the system. Deal?"
Everyone nods. Nobody asks anything. He leaves the room thinking: "that was easy."
Three weeks later, the report shows four work notes on the night shift. And on the shop wall, the clipboard is still there, with the pen tied on by a string.
Last week we talked about champions — the people the team follows. Today is the other side of the same coin: the people who agree with everything and follow nothing.
A strategy that worked for years
Before calling it sabotage, it's worth looking at where it comes from.
In Brazilian maintenance, disagreeing with the boss in front of everyone has always come at a price. Technicians learn an unwritten rule early: in the meeting, agree; in the shop, do it the way that works.
And they have memory. They saw 5S arrive, TPM, the previous manager's spreadsheet, the system headquarters sent down in 2015. They saw all of them become a poster on the wall and then disappear.
👉 The silent "yes" isn't laziness or bad faith. It's a strategy that has protected this professional for years — and that, to this day, has never failed him.
In thirty years I've seen managers spend months fighting with the technician who complained out loud, while the one who said "no problem" went untouched. The loud one was still negotiating. The quiet one had already decided.
👉 Calling it sabotage is the shortest path to turning resistance into a cold war.
🧠 The words agree. The behavior answers.
Three things happen underneath that "yes."
First: every behavior protects something. The clipboard doesn't stay on the wall out of stubbornness. It holds something the system hasn't yet held for that person — the memory of what he's done for fifteen years, the autonomy to take notes his own way, the right not to be measured minute by minute, or simply not being embarrassed by getting the screen wrong in front of his coworkers.
👉 Until you find out what the paper protects, you'll keep trying to rip the clipboard off the wall — and he'll keep hanging it back up.
Second: the mouth and the body tell different stories. The "yes" comes too fast, without a single question, arms crossed and eyes on the clock. People who want to use it ask questions. People who have already decided not to use it agree so the meeting will end.
Third, and the most uncomfortable: the more you push, the more agreement you get — and the less use. Pressure produces obedience in front of the boss. Buy-in is something else, and it happens when the boss isn't looking.
👉 You're not facing a lying "yes." You're facing a "no" that hasn't found a safe place to be said.
Signs of buy-in that's just for show
It almost always shows up in the numbers before it shows up in conversation:
- Training with no questions at all. A whole class, zero questions. That's not mastery — it's distance.
- Batch logging. Every work order on the shift closed at 5:48 p.m., one right after the other.
- One-word descriptions. "Done." "Ok." "Completed." The field is filled in; the information isn't.
- The notebook is still alive. The information that matters still circulates in personal notebooks and the shift's WhatsApp group.
- Numbers that are too perfect. One hundred percent of preventive work completed, no notes, no anomalies in three months.
👉 Data that's just for show is worse than no data. With no data, at least you know you don't have it.
The cost comes in layers. First, you calculate MTBF and MTTR on made-up times. Then you set investment priorities based on a history nobody really wrote. And in the end the paradox happens: the manager thinks the rollout was a success, and leadership concludes "the system doesn't deliver."
What the software shows — and what it can't do for you
From my side of the table, with the usual candor.
Manusis4 makes this pattern visible. Every work request, every work order, and every work note has a name and a time, so you can see the work order closed long after the job, the batch entered at the end of the shift, the text field that always comes back empty. And the mobile app, which works without a signal, removes the most common excuse — "there was no computer near the machine." With that, paper loses its practical advantage and keeps only the emotional one.
What the system can't see is the reason. It shows the delay, not the fear. It shows the empty field, not the embarrassment of writing something wrong.
And there's a risk I need to name: that same data can become a hunting tool. A ranking of who isn't using it, public call-outs, screenshots in the group chat. The day that happens, you confirm exactly the fear that created the silence — and the next "yes" comes even faster.
👉 Use the system's data to ask questions, never to make accusations.
Five moves to turn the "yes" into use
- Swap "any questions?" for "what's going to get in the way?" The first question has a ready-made answer: no. The second assumes there's an obstacle — and gives permission to talk about it.
- Change where the conversation happens. The real "no" doesn't show up in the meeting room. It shows up one-on-one, next to the machine, ideally with you listening more than talking: "if it were your call, what would you change about the way we log this?"
- Find out what the paper protects — and offer the same protection inside the system. If it's memory, show him the asset history he himself will build. If it's fear of making mistakes in front of others, train him one-on-one. If it's time, cut fields nobody uses.
- Agree on what you'll watch, and watch it together. No "you all need to use it more." Something concrete: "the shift's work orders get closed during the shift." And follow along beside them, not over them.
- Thank the first "no" out loud. When someone finally disagrees in the meeting, your reaction will teach the whole team whether it's worth disagreeing again.
👉 Resistance that speaks, you can negotiate with. Resistance that agrees, you only find out about too late.
This week's reprogramming
Think about the last meeting where you presented a change. How many people said "no"?
If the answer is zero, don't celebrate yet.
"Behind every "yes" without use there's a "no" that had nowhere to be said."
This week, your task isn't to get more agreement. It's to create the place where the "no" can show up — because only after it does the real "yes" arrive.
Next week
👉 Nobody falls in love with a system on training day. They fall in love on some random Tuesday when it saved them twenty minutes and a chewing-out.
In #67 we'll talk about micro-engagement: the small wins in using the software — and why celebrating the small stuff sustains buy-in far more than demanding the big stuff.
Until then.