Preparing report
Preparing report
Study setup · Product Discovery
“I want to discover why a field-service dispatch app has high office adoption but low field adoption among plumbers, HVAC technicians, and electricians.”
Across 10 qualified interviews, the main risk is not willingness; it is whether FieldFlow survives the service moment. The strongest signals were field-safe control gaps in 5 interviews and offline or stale schedule gaps in 4.
Executive summary
Dispatch resync board: FieldFlow Dispatch App adoption risk centers on the service moment. Across 10 qualified interviews, the strongest pattern was not technician resistance. It was workflow mismatch when the job update workflow met wet gloves, glare, mud, cramped spaces, dark areas, or unsafe conditions. The second core risk was trust. Dead zones and stale schedules left dispatch working from old job status, which moved work back to calls, texts, or radio. A related opportunity is the Offline evidence queue: photos, voice notes, and quick notes need local capture before structured cleanup. The anti-pattern is to lead with more training emails or reminders before fixing field-safe controls, offline queue visibility, and source-aware adoption measurement.
The clearest patterns in this study, supported across most interviews.
When controls assume clean office conditions, technicians abandon the app at the service moment and use safer or faster workarounds.
How to apply itRemove the broken step behind field adoption fails when job-site conditions break desktop-shaped controls, then test the smallest product change that simplifies the workflow.
Heard in 5 of 10 interviews
“I could update FieldFlow in a kitchen, but not with muddy gloves beside a sewer line. That is the moment I would want the team to study, because it shows what was happening before the surface metric or form answer simplified the story. The workaround was not rebellion. It was a practical way to protect the job record when the app could not handle the field condition. That workaround also moved cleanup to dispatch and made adoption metrics look healthier than reality.”
Beth Granger · Mainline PlumbingTranscript
Dead zones keep updates on the phone while dispatch sees an outdated job state, which shifts trust from the workflow to calls, texts, or radio.
How to apply itRemove the broken step behind offline state and stale schedule visibility decide whether dispatch trusts the workflow, then test the smallest product change that simplifies the workflow.
Heard in 4 of 10 interviews
“When a basement has no signal, the job update waits in the phone while dispatch thinks the plumber is still on the previous stop. By then the fallback behavior made sense to the person doing the work. It was faster, safer, or less embarrassing than staying with the official path, even though it created cleanup and confusion later. FieldFlow worked in the office, but the first break happened when the tech had wet gloves and could not hit the tiny status button without wiping the phone on his shirt. That is the moment I would want the team to study, because it shows what was happening before the surface metric or form answer simplified the story.”
Linda Vance · ProPlumbTranscript
Patterns with good support — apply these with a bit more judgment.
Evidence happens while the technician is still in the field condition; if the app makes capture feel risky or slow, users preserve the record outside FieldFlow.
How to apply itRemove the broken step behind photo, voice, and note evidence must be captured before paperwork closeout, then test the smallest product change that simplifies the workflow.
Heard in 3 of 10 interviews
“A photo-first mode with later cleanup would fit the job because evidence happens before paperwork in the field. I would prioritize field-safe job updates, an offline evidence queue, dispatch resync, and clear source attribution for office backfill. That would make the product feel like part of the service job instead of another task after the service job. That recommendation is easy for a new customer to understand because it connects directly to the participant story instead of sounding like generic best practice.”
Jordan Patel · ClearPipe ServicesTranscript
Approaches that consistently backfired for participants.
The evidence points to workflow mismatch under field conditions, with office backfill and alternate channels masking the real adoption gap.
What to do insteadDo not lead with more training emails or reminders; first fix field-safe capture, offline queue visibility, and source-aware adoption measurement.
Heard in 3 of 10 interviews
“Office adoption looked high because dispatchers were cleaning up the record after technicians finished the day. That is the moment I would want the team to study, because it shows what was happening before the surface metric or form answer simplified the story. The workaround was not rebellion. It was a practical way to protect the job record when the app could not handle the field condition. That workaround also moved cleanup to dispatch and made adoption metrics look healthier than reality.”
Omar Shah · MetroFix ServicesTranscript
Open questions for a follow-up study