• Replies 11 replies
  • Subscribers 2 subscribers
  • Views 2 views
  • Users 0 members are here
Options
Related

Tips for rolling out FieldPulse to a team that's resistant to new software?

Paula Hendrix

We're getting ready to roll FieldPulse out to our 12-person field team, and honestly, I'm bracing for some pushback. A few of our senior technicians have been vocal about not wanting to learn another system — they know their current workflow (paper dispatch sheets and Google Calendar) and see no reason to change.

I've read the migration guide and the general rollout tips, but I'm hoping to hear from folks who've actually navigated this. What actually worked to get resistant team members on board? Did you find certain training approaches more effective than others? Any mistakes you'd avoid if you did it again?

Our team is split between tech-savvy younger techs and a few veterans who are excellent at their jobs but skeptical of anything that feels like extra overhead. I want to set them up for success without creating resentment.

Parents

  • Thanks so much everyone for sharing! We're about to start our rollout too and this is all incredibly helpful.

    I have a quick follow-up — for those of you who did the "champion" approach with a respected skeptic, how did you identify who to pick? Was it just seniority or something else? And did you have backup plans if that person stayed resistant?

    Really appreciate all the insights!

  • in reply to Deja Washington

    Good question — for us it was less about formal seniority and more about who other techs actually listened to when the radio got quiet. There's usually one or two people whose opinion carries weight even if they don't have the title. Watch who gets asked for advice on tricky jobs.

    Backup plan: if he had stayed resistant, I was going to pivot to his closest work partner (they always got paired together). Same credibility transfer, just one degree removed. Didn't end up needing it though.

Reply
  • in reply to Deja Washington

    Good question — for us it was less about formal seniority and more about who other techs actually listened to when the radio got quiet. There's usually one or two people whose opinion carries weight even if they don't have the title. Watch who gets asked for advice on tricky jobs.

    Backup plan: if he had stayed resistant, I was going to pivot to his closest work partner (they always got paired together). Same credibility transfer, just one degree removed. Didn't end up needing it though.

Children
No Data