Most failed rollouts had good training.
There was a kickoff, a deck, a champion on every crew, a laminated quick-reference in each truck. Six months later half the team is filling out forms in the parking lot at the end of the day, a quarter of them have quietly gone back to paper, and somebody is still sending reminder emails. The postmortem calls it an adoption problem and recommends more training.
It’s almost never a training problem.
Crews are economists about their own time
Not in a difficult way. In a rational one.
Somebody with eleven stops left and ninety minutes of daylight will use whichever method gets them home. If the digital version of a form takes longer at the moment of use than the paper version did, they will route around it, and they will be right to. Their job is the work, not the record of the work.
Training can teach a person how to use a tool. It cannot make a slow tool fast. When those two things are in conflict, the stopwatch wins every time, and it wins quietly, which is why the problem usually surfaces as a data quality complaint months before anyone names it correctly.
Where the friction actually is
It’s rarely where the rollout plan assumed. Almost none of it is about understanding the software.
The form doesn’t look like their form. A crew has used the same sheet for years and knows it by shape. Where the third box sits. Which side the signature goes on. What order the sections run in. Then a rollout hands them a redesigned version of the same information, and every job now includes a translation step. Nothing was gained. The fields are identical. The only thing that changed is that years of muscle memory became worthless. Keep the layout. When the form on the screen is the form they already know, most of the training conversation disappears on its own.
Recognizable is not the same as usable. Keeping the form’s identity doesn’t mean shrinking a letter-sized page onto a phone and calling it done. It has to be workable in gloves, in daylight, on a ladder. Traci Vargas, a Business Solutions Specialist at CHP Energy Solutions, described how they solved for both: “The list view makes our forms so much easier to use in the field, especially when the screen space is limited.” Same form, different view depending on where you’re standing. Nobody needed to be trained into that. It just stopped being annoying.
Typing what the system already knows. Job number, asset ID, customer name, the technician’s own name, the date. Every one of those is a field somebody fills in by hand that could have arrived pre-filled. CHP had technicians entering 27-digit HVAC serial numbers by hand. Scanning a barcode instead isn’t a nice feature. It’s the difference between a number that’s right and a number that’s close.
Questions that don’t apply to this job. A form built to cover every scenario asks every crew about scenarios they’ll never see. CHP runs more than 20 weatherization programs with different documentation requirements, and as Erik Garcia, their Director of Support Services, describes it, the fix was letting the form sort that out: “If a client only qualifies for programs A and B, not C, D, and E, then the form only prompts the subcontractor to collect specific pictures and complete relevant measures.” The form got shorter for everyone, which is the only length change anybody has ever thanked you for.
Losing work when the signal drops. This is the one that kills adoption fastest, because it doesn’t just cost time, it costs work already done. A crew that loses twenty minutes of entry once will never fully trust the tool again. NTL Pipelines works sites anywhere from thirty minutes to thirty hours from the nearest office, which makes offline capture less a feature than a precondition.
Hunting for the right form. If finding the correct template among forty takes ninety seconds, that’s ninety seconds of tax on every single submission, forever.
Not all friction is bad friction
This is where a lot of well-meaning simplification goes wrong.
There’s friction that adds work, and there’s friction that prevents rework, and they should be treated as opposites rather than as degrees of the same thing.
A required field is friction. It also stops a subcontractor from submitting a job without the photo that funding depends on, which is what turns into a return trip and a delayed reimbursement. Ten seconds spent at the point of capture beats a two-hour drive back, and everybody in the truck understands that math when it’s explained once.
So the test isn’t whether a step is fast. It’s whether the step costs less than what it prevents. Remove the friction that only exists because the form was built for the office. Keep the friction that’s doing a job.
What it looks like when you’ve actually done it
You stop needing to enforce it.
The clearest signal we’ve heard came from Jared Holmquist, CEO of NTL Pipelines, describing what would happen if they tried to reverse course: “Even the suggestion of going back to paper would be outright rebellion.” That isn’t compliance. Nobody sends reminder emails to sustain that.
Tony Tharp at Vestas described the same thing from the other end, at the beginning: “It was time savings, the day I started using it.” Not after the training landed. Not once the habit formed. Day one, because the tool was faster than what it replaced, and that was immediately obvious to the person holding it.
When the tool is faster, adoption isn’t a program you run. It’s a thing that happens while you’re not looking.
A better question than how do we drive adoption
Go watch somebody use it.
Not in a conference room. In the field, on their device, at four in the afternoon, on the eleventh stop. Time it. Count how many things they type that the system could have known. Count how many questions they answer that don’t apply to their job. Ask them whether the form on the screen looks like the one they used to carry. Ask them what they’d do if nobody were watching.
You’ll usually have your answer in one afternoon, and it usually won’t be training.
See how field teams cut the time it takes to capture a record at the source, so the tool gets used because it’s faster.
