The Tech Who Won't Use the Software: Decision Tree

Why this matters

You bought the field software, you trained the crew, and one tech is still writing tickets on paper or "forgetting" to close jobs in the app. It is tempting to read this as defiance and reach for a warning. Usually it is not defiance, it is friction, and the warning fixes nothing because it does not touch the cause. A tech who is not using the system is a hole in your data: jobs that look open when they are done, photos that never get attached, invoices that go out late. Find the real reason before you escalate, because the reason changes the fix entirely.

Start here: is it a can't or a won't

Every case sorts into one of two roots, and they get opposite responses. Find out which before you do anything else.

• A can't is friction: the app is slow on their phone, the steps are confusing, the login keeps dropping, the form does not fit how the job actually runs.
• A won't is resistance: they do not see the point, they think it is surveillance, they are protecting "how I have always done it," or they are quietly worried it makes them look slow.

The mistake is treating a can't like a won't. You cannot coach away a problem that is actually a broken tool, and you cannot tool-fix a problem that is actually about trust. Ask the tech directly and watch which way it leans.

If it is a can't (friction)

Most non-adoption is here. Work it in order, easiest cause first.

1. Watch them do it once. Stand next to the tech on a real job and watch them try to use the app. You will usually see the snag in the first ninety seconds: a step that takes too many taps, a field that does not make sense, a screen that loads slow on a weak signal.
2. Check the device and the signal. An old phone or a job site with no bars turns a ten-second task into a frustrating minute. If the tool fails where the work happens, the tech is right to abandon it. Fix the device, enable offline entry, or both.
3. Check whether the workflow matches the trade. If the form was set up for a different kind of job, the tech is fighting it every time. Trim required fields to what actually matters in the field and let the rest be optional.
4. Confirm they were actually trained, not just shown. A one-time demo in the shop is not training. Re-train on a live job, hands on the phone, you watching.

Clear the friction and most "won't use it" techs quietly start using it, because now it is easier than paper.

If it is a won't (resistance)

If the tool works fine and the tech still avoids it, the cause is a reason, not a snag. Sort the reason.

• "I do not see the point." They never got the why. Connect it to something they care about: photos that protect them in a dispute, faster pay because invoices go out same-day, no more callbacks from lost notes. Sell the benefit to them, not to you.
• "This is so you can watch me." The GPS and the timestamps read as surveillance. Be straight about what you do and do not use it for. See related: GPS Tracking Without Breaking Trust. The fix is honesty about purpose, not a lecture about compliance.
• "My way works fine." Often the best tech on the crew, and the proudest. Do not frame it as fixing them. Frame it as the shop needing one consistent record so the office, the customer, and the next tech are not guessing. Make it about the system, not their skill.
• "I do not want to look slow at it." A quieter one, common with a veteran who is not comfortable on a phone. They will never say this out loud. Pair them with a patient peer, not a manager, and let them get fluent without an audience.

When it is the rollout, not the tech

Before you decide it is a person problem, check whether it is everyone, not one person.

• If more than one or two are dragging, it is not a tech problem, it is a rollout problem. The training was too thin, the tool is genuinely clunky, or the why never landed with the crew. Fix the rollout. See related: Adopting a New Tool Without Disrupting the Week.
• If it is truly one holdout after the friction is cleared and the why is clear, then it becomes a normal accountability conversation, the same as any other expectation that is not being met.

Get this order right. Escalating one tech for what is actually a bad rollout breeds resentment and still does not fix the data.

The recap

1. Can't or won't? Ask and watch before you act.
2. If can't: watch them work, check device and signal, match the form to the trade, re-train live.
3. If won't: find the specific reason (no why, feels like surveillance, pride, fear of looking slow) and answer that reason.
4. If it is more than one tech, fix the rollout, not the person.
5. Only a true single holdout with no friction left becomes an accountability issue.

The judgment to bank: a tech who avoids the software is giving you information. Read it before you escalate, because nine times out of ten the tool or the rollout is the thing that needs fixing.

References

• U.S. Small Business Administration (SBA), managing change in small business
• Trade-standard practice for field technology adoption
• See related: Adopting a New Tool Without Disrupting the Week; GPS Tracking Without Breaking Trust