The scene
Rosa has been dispatching nights for nine years. When the fleet rolled out its new AI-assisted dispatch board, she got the training, she got the login, and she used it exactly as designed, for about six weeks.
Then the board started recommending a load assignment that didn’t match how the shift actually runs. Not wrong on paper. Just different from the way things get done here: the night shift hands off to days with a quick phone call, not a note. The driver who covers the Fontana lane gets first call on anything going that direction because he’s covered for the others before. Nobody writes a late load into the system until the customer calls, because the last person who did got an earful at Monday’s meeting.
None of that is in the SOP binder. The binder is in English, hasn’t been updated in three years, and lives on a shelf in the office. The real rules live in people’s heads, and the new tool never learned them.
So Rosa did what any sensible person does. She went back to the rules that were actually running the place.
The pattern
Most owners treat a new AI tool like it’s the whole change. Pick the software, train the team, flip the switch. When it doesn’t stick, the diagnosis is usually about the tool or the people.
But a tool is an app. And apps run on an operating system.
Every fleet has one, even if nobody ever designed it. It’s made of three layers:
- The written rules. SOPs, checklists, handbooks, the binder on the shelf. In many small fleets, this layer is thin, outdated, or only available in one language.
- The unwritten rules. Who gets the good lanes. What you do and don’t say to the owner. When it’s okay to flag a problem and when it isn’t. These are the real decision logic of the operation.
- The daily rituals. Shift handoffs, morning huddles, how a late load gets reported, what happens on Monday. The habits that repeat so often nobody notices them anymore.
When the new tool conflicts with the operating system, the operating system wins. Every time. Not because people are resisting, but because the OS is what they’ve learned to survive on.
The reframe
This is the domain where the first five either get built into the fleet or get quietly overwritten.
Psychological safety (#1) isn’t a workshop. It’s whether the unwritten rule says «flag it early» or «don’t be the one who brings bad news.» The infinite mindset (#2) lives or dies on whether the daily rituals reward long-term thinking or only this week’s numbers. Leadership evolution (#3) shows up in who the unwritten rules say gets to make a call. Communication intelligence (#4) is the ritual layer: the handoffs and updates nobody designed. And resistance (#5) is often just the OS rejecting software it was never configured to run.
You can’t train your way to a new culture. You can only rewire the three layers, one at a time, and let the habits do the rest.
One thing you can check this week
Pick one daily ritual, just one, and map all three layers for it. The shift handoff is a good one.
- Written: Is there a documented handoff procedure? Is it current? Is it available in the language your team actually works in?
- Unwritten: What actually happens, as opposed to what the binder says? Who tells whom, what gets left out, what gets handled with a phone call instead of a note?
- Ritual: When does it happen, how long does it take, and what would break if the one person who always does it were out sick?
Where the three answers don’t match, that’s where a new tool will get overridden. It’s also where the biggest, cheapest improvement usually is.
One usable action: write that one ritual down on a single page, in both English and Spanish if your team works in both, using the unwritten version, not the idealized one. Have the people who actually do it check it for accuracy. A bilingual, honest, one-page procedure does more for adoption than another training session, because it puts the real rules where everyone can see and improve them.
Where this fits
This is domain six of twelve, and it’s the midpoint of the series for a reason. The first five domains are about readiness: whether people are safe, whether the thinking is right, whether leaders and communication are set up for change. This one is where it starts to become permanent, because culture changes when the daily habits change, not when the announcement goes out.
If you’d like a second set of eyes on where your written rules, unwritten rules, and daily habits are pulling in different directions, that’s a good thing to map before any tool goes in. Reply and tell me which ritual you’d start with.
YBOR Logistics AI
Helping logistics companies turn AI, automation and operational data into better decisions… Visit YborLogistics.ai
