FSM Change Management & Technician Adoption Engagement

The reason most FSM implementations fail isn’t the software — it’s that the field technicians don’t use it. The mobile app sits unused on the truck while techs keep writing on paper and calling dispatch on the phone. The data quality collapses. The platform’s reporting becomes useless. Six months in, leadership concludes “the software doesn’t work” and starts the next selection cycle. The software was usually fine. The adoption wasn’t.

This engagement focuses on the technician side of the rollout — the part the vendor’s training plan typically under-serves and the part where most of the operational ROI actually lives.

What’s involved

The work breaks into three phases:

Phase 1: Discovery. Interviews with six to twelve technicians across tenure, age, and tech-comfort levels. Half are conducted in-person on-the-truck or at the shop, half remotely if travel isn’t practical. The goal is to understand how techs actually work today, what they think of the current tools, and what they expect (or fear) about the new system. The interviews are confidential — no individual responses get reported back to leadership.

Phase 2: Strategy. A written adoption plan that takes the operation’s reality into account. Includes training cohort design (the older long-tenure techs and the recent hires often need different approaches), mobile app rollout sequencing (which features land first, which get delayed), the support model in the first six weeks (who answers a tech’s questions at 9 PM on a Saturday), and the incentive structure (or lack thereof — usually the wrong answer is a per-job adoption bonus).

Phase 3: Execution support (optional). In-field coaching during the first four to eight weeks of rollout. I ride along with techs, observe how they’re using the system, identify where they’re working around it, and feed that back into the implementation team for fast iteration. This phase is optional and typically billed weekly.

Who this is for

Operators with 15+ technicians who are about to roll out (or are mid-rollout of) an FSM mobile app. Particularly useful for operations where the technician base is older, long-tenured, or has lived through a failed software rollout in the past — those are the populations where the vendor’s standard training falls flat.

Less useful for operations under 15 technicians where the owner can essentially hand-coach every tech personally.

Deliverables

• Interview synthesis (anonymized) covering what the field actually thinks
• Written adoption strategy (15–25 pages) with cohort design, sequencing, support model, and incentive recommendations
• Manager talking points for the conversations leadership needs to have with field crews before, during, and after rollout
• A 90-minute readout call with your team
• One revision round after the readout
• Optional Phase 3: weekly in-field coaching with weekly written status during the active rollout window

Time and structure

Phase 1 + Phase 2: four to six weeks elapsed time. Phase 3 (optional): four to eight weeks running in parallel with rollout. Fixed-scope pricing for Phases 1 and 2; weekly billing for Phase 3.

What’s outside scope

• Replacing your operations manager. The strategy informs how the operation runs the rollout; someone on your team owns the day-to-day execution.
• Building training videos or e-learning modules. The strategy defines what training should cover; producing the training materials is a separate scope (or the vendor’s responsibility).
• HR decisions about specific technicians. Sometimes the adoption work surfaces that a particular tech won’t make the transition; that’s an HR conversation, not mine.

Next step

Book a free scoping call to discuss the operation’s size, the platform you’re rolling out, and where you are in the implementation timeline. Best results come from starting before go-live; remediation engagements (where the rollout has already stalled) are possible but harder.