The first login isn't the start of the project. It's the day each person silently decides whether the system is theirs or the boss's.
There's a minute in every rollout that doesn't appear on any schedule.
It's when the technician types his password for the first time, looks at the screen, and thinks: "is this here to help me or to watch me?"
He won't tell you the answer. But it will show up in every work note for the next twelve months.
Last week I closed Block 9 by saying nobody resists technology — they resist becoming someone else without having chosen to. Today we open Block 10 exactly where that choice happens: in the first days.
The script everyone knows
Maintenance system rollouts in Brazil usually follow the same script. Kickoff with leadership. A polished presentation. A ninety-day schedule. Classroom training: two days, projector, handbook, sign-in sheet. The following Monday, go-live.
In thirty years I've seen that script dozens of times, from both sides of the table — as the manager receiving the system and as the one delivering it.
👉 Classroom training teaches where to click. It doesn't teach why that matters to the person clicking.
And there's a cultural detail almost nobody considers: for the technician, the system almost always comes "from above." From leadership, from IT, from corporate. Nobody asked him anything.
👉 Anyone who was never consulted receives any tool as surveillance.
The sentence he doesn't say, but thinks: "now they'll know how long I take on every job."
Every beginning leaves a mark
The emotional state a person is in during their first contact with something sticks to them — and comes back, automatically, every time they encounter that thing again.
If the first contact with the system happened in a stuffy room, afraid of making a mistake in front of coworkers, with the supervisor noting who fell behind — that's the state that comes back every time he opens the screen. He's not rejecting the system. He's rejecting the memory.
👉 The first experience doesn't just teach the tool. It teaches what the person will feel every time they use the tool.
The opposite is also true. If the first contact ended with him solving something that had bothered him for years — finding the history of that pump that breaks every month, seeing his own work order closed with no paper lost on the clipboard — the mark is different.
Every culture marks a change of phase with a ritual: graduation, first day on the job, shift handover. A system rollout is a change of phase. It changes how work arrives, how it's recorded, and how it's seen.
👉 A rollout without a rite is an identity change without a ceremony. People cross over without knowing they crossed. Or worse: they feel they were pushed.
Signs of a badly done first login
They show up in the first weeks and are almost never read for what they are:
- Shared logins. "Use so-and-so's password." It's the first sign the system belongs to the department, not the person.
- The planner who "copies it over." The technician stays on paper and someone enters everything at the end of the shift, from memory.
- "Do I have to log this too?" The system is being seen as an extra task, not a tool.
- People who did the training and never logged in again. Paid license, empty seat.
- A supervisor who uses the system to push people and never to recognize them.
👉 And there's the cost that doesn't show up right away: data entered wrong in the first months contaminates the KPIs for years. MTBF, backlog, cost per asset — all calculated on a history nobody trusts. Then management concludes "the system doesn't work," when what didn't work was the beginning.
What the software does here — and what it doesn't
I'll talk about my side of the table with the same honesty as always.
Manusis4 provides the structure: assets, plans, work requests and work orders, history, KPIs. Our team configures, trains, and supports the go-live.
What the software doesn't do: it doesn't choose who goes in first. It doesn't decide what the person will feel. It doesn't replace the supervisor who sits next to the technician in the first week and says "let me look at it with you."
👉 No vendor rolls out culture. We roll out a system. Leadership rolls out the culture, in the first thirty days.
In the projects that worked, what I saw in common wasn't the most sophisticated configuration. It was someone in-house who treated the go-live as the beginning of something — not as a box checked.
Five moves to design the first login
- Start with his pain, not the menu. Before any training, ask each technician: "what bothers you most about the way work reaches you today?" The first thing he does in the system should solve exactly that.
- One login per person, from day one. Your own name on the screen is belonging. A shared password is anonymity — and nobody takes care of what's anonymous.
- First contact at the workplace, not in the classroom. The first real work order, with the equipment in front of him and someone he trusts beside him. The classroom teaches the tool; the field teaches the use.
- Mark the crossing. Each person's first work order closed in the system deserves a mention in the weekly meeting, by name. It seems small. It's the rite.
- In the first thirty days, no pushing people through the system. During that period it's there to show what got easier, not to point out anyone's mistakes. Whoever gets called out in the first month learns to log things to defend himself — and data logged in self-defense is useless for management.
👉 None of these moves costs licenses, consultants, or overtime. It costs intention.
This week's reprogramming
Think about the last rollout you led — of a system, a procedure, anything. What did people feel on the first day?
If you can't answer, that's the most important data point you don't have.
"The first login doesn't teach how to use the system. It teaches what to feel every time you open the screen."
Take this sentence to your next kickoff. It changes the question from "has everyone been trained?" to "how did everyone leave the first day?"
Next week
👉 Every project that takes hold has, somewhere, a person who started using it before being told to — and pulled the others along without realizing it.
In #65 we'll talk about that person: how to create internal champions without imposing anything — and why the champion chosen by the boss is almost never the one the team follows.
Until then.