Problem guide
The crew won't use the new system
Crews avoid a new system when it asks them for more work at the end of a job than the old way did, for a benefit that mostly lands in the office. They adopt a tool when using it is easier than not using it, which means starting from how they already work, one task at a time.
What it usually looks like
A contractor rolls out a new system that handles scheduling, time, materials and job notes. The office loves the demo. In the field, closing a job takes a dozen screens on a phone, with dirty hands, while the next customer is waiting. Within a month most technicians are back to texting photos of paper tickets to the office. The office manager enters them into the new system herself. Leadership sees the system filling up and believes it is working, while the crew has quietly opted out.
Signs you have this problem
- Crews still hand in paper, texts or photos after the system went live
- The office enters crew information into the new system on their behalf
- Records in the new system are incomplete or entered days late
- Supervisors spend time reminding people to log in
- The company now keeps two partial records instead of one complete one
What usually causes it
- The system was built for the office, so the crew does extra typing that helps someone elseThe field-to-office split
- Crew input still gets retyped or corrected by the office, so the crew sees no point in doing it carefullyThe re-entry trap
- Real jobs rarely fit the screens, so crews fall back to paper for anything unusualThe exception swamp
What to try this week
- Ride along and watchSpend a day with a crew and watch when and where they would use the system. Note the conditions: gloves, weather, no signal, a customer waiting.
- Count what you ask of themList every field and tap the system asks for at the end of a job. Mark which ones the office actually uses. Everything unused is friction with no return.
- Ask what they do insteadFind out what the crew uses in place of the system and why it works for them. The workaround shows you what they actually need.
- Cut the ask to one taskPick the single entry that matters most to the office and make that the only thing you ask for now. Let everything else wait.
- Measure use from your own recordsCompare jobs completed against jobs with a complete entry, week by week. Use your job records, not the system's login counts.
Where do-it-yourself stops
These steps show why the crew avoids the system and reduce what it asks of them. They do not change the fact that the system was built around the office's needs, not the crew's work. A lasting fix is a tool shaped around how the crew already works, for one task, whose output arrives in your office systems in the right shape without retyping. That is what a Workflow Spec designs.
Questions people ask
Why won't our crew use the new system?
Usually because it costs them time at the worst moment and the benefit goes to someone else. People adopt the thing that makes their own day easier.
Should we just require it?
A mandate raises logins, not good data. Crews comply with the minimum and the office cleans up after them.
Is more training the answer?
Training helps when people do not know how. It rarely helps when they know how and have decided it is not worth the effort.
How do we know if adoption is real?
Count completed jobs that have a complete, on-time entry, from your own job records. That number tells the truth about use.
Has this happened elsewhere?
Yes, often. Our proof page describes one full replacement system that a team did not move onto, and what shipped instead.
Next step
How we fix this
This guide is how to find it and work around it. If it keeps coming back, the fix is usually a tool built around how your crew already works.
Fox & Santiago, Genesee, Idaho. Home territory: the Inland Northwest, where we respond fastest. We fly anywhere in the United States for paid engagements.