The ideal is nothing
When we initially designed the Axle preventive maintenance module, we took it to the shop floor and watched technicians perform a PM using the software versus paper. We came back humbled.
There is no software in the world that can overcome the desire not to use software, or even do anything at all.
Every company describes their product as "seamless" or "intuitive." But the most seamless experience is the one that does not exist. The bar for most software is not "easy." It is "as close to not happening as possible."
This is the tension at the heart of shop software, particularly when it comes to PM checklists. Managers and executives want visibility, compliance, and data. Technicians want to do their jobs and go home without being bogged down in endless minutiae. One group wants records and the other wants flow. Those are not the same goal, and no amount of good UX fully bridges them.
What we found
Technicians are fast with paper in a way that takes a minute to fully appreciate.
A seasoned tech doing a dry PM does not read the form. They feel it. They know where the checkboxes are by muscle memory. The pen moves while their eyes stay on the truck. The whole thing takes minutes.
One tech in Chicago ran a full wet PM with hands covered in oil, the form pinned under a flashlight, filling in values without breaking stride. The form was not slowing him down. It was keeping pace with him. Paper is not a workaround. It is a highly evolved tool.
Most fleet software vendors start from the assumption that paper is broken. But that depends on what you mean by broken. For the person actually doing the work, paper performs extremely well. If paper were truly broken, technicians would have abandoned it years ago.
Here is what it gets right that most software gets wrong:
- No login, no loading screen. You pick up the form and you are working. There is zero friction between deciding to start and actually starting.
- It follows your eyes, not the other way around. A paper checklist sits in your peripheral vision until you need it. It does not demand attention.
- It is forgiving. A tech can skip around, circle something, scribble a note in the margin, jump to suspension, and come back to brakes. Paper trusts the technician to know the job and set the pace.
- It works in every condition. Grease, rain, gloves, the roar of an air compressor. Paper does not crash, lose signal, or ask you to update before opening.
Where paper falls apart
The problems only show up later. Any issues with paper PMs are not on the shop floor. They are downstream, and they are quiet, which is part of why they persist.
- Legibility. Someone has to read that fast, confident handwriting hours or days later. Often they cannot.
- Data that goes nowhere. A paper form is a dead end. It gets filed, sometimes scanned, rarely analyzed. Patterns across trucks, across techs, and across time stay invisible.
- Compliance gaps. Forms get lost. A PM gets done but never recorded. The gap surfaces during an audit instead of when it happens.
- No accountability trail. Who did what, when, on which unit; paper makes this harder than it should be.
One thing that stood out during shop visits is how often technicians write notes that never travel anywhere. A margin scribble like "left brake line starting to rust" or "fan belt looks worn" does not fail the PM and does not stop the truck, so it stays in the margin. Two months later the truck comes back with a real issue and someone says, "We should have caught that earlier."
Paper captures the signal. It just cannot carry it.
Technicians told us all of this themselves. They are not blind to the problems. They have simply accepted them as the cost of a process that otherwise works well. So when PM software gets introduced, adoption stays low. Techs feel boxed in and slowed down, because they are. Eventually, they go back to paper.
The question that changed our direction
We went in asking: How quickly can we replace paper?
We left asking something harder: How can we keep what paper gets right and fix only what it gets wrong?
Those questions sound similar, but they are not. The first assumes paper is the problem. The second assumes paper is, in most ways, the solution, and that our job is far more constrained.
It also forces some honesty about why PM software has struggled with adoption. Every login screen, dropdown, and mandatory field, every moment of "wait, what step am I on?" is a withdrawal from an account paper has never touched. Technology keeps making a bad trade: fixing the downstream problems managers care about while creating new friction for the people actually doing the work.
The clear direction that emerges
The goal stopped being "build better software." It became: find the smallest possible delta between what paper already does well and what we need it to do differently.
That is a much harder design constraint than starting from scratch, but it is the only one that respects what is actually happening on the shop floor. And it turns out that constraint points clearly toward one answer.
More on that next.
In this three-part series, we explore how to capture the power of the margin without losing the simplicity of a paper PM.
Axle is building the system of execution for fleet repair and maintenance, so techs, fleet managers, and fleet executives can focus on trucks, not mindless admin.