Leading Change and New Technology

Change is constant in this business — new technology in the machines, new systems in the office, new processes, new expectations — and the manager’s job isn’t just to adopt it but to bring the team through it. Most change efforts fail not on the technology but on the people, and leading that well is a core management skill.

People resist change for reasons

When a manager rolls out a new DMS, a precision platform, or a new process and hits resistance, the instinct is to blame stubbornness — but resistance usually has real roots: fear of looking incompetent at something new, past changes that were botched, extra work during the transition, or simply not understanding why. Treating resistance as a problem to steamroll makes it worse; understanding and addressing the real concern — the tech worried the new diagnostic system makes their experience obsolete, the office staffer overwhelmed by a new procedure mid-season — is what moves people. People don’t resist change so much as being changed on; they’ll go along with change they understand and were brought into.

Explain the why and involve them

The single biggest lever is the why — people accept change they understand the reason for and resist change that just lands on them. Explaining honestly why the change matters (what problem it solves, what it means for them and the dealership), involving the team in how it’s implemented where possible, and being straight about the hard parts builds the buy-in that makes it stick. Involving people also surfaces the practical problems a top-down rollout misses. Change done with the team goes far better than change done to them.

Support the transition, then sustain it

The transition period is the hardest part — people are slower and more frustrated while learning the new way, and that’s exactly when many changes get abandoned and the team slides back. Leading through it means providing real support (training, time, patience, help), expecting the temporary dip in performance rather than panicking at it, and holding steady until the new way becomes normal. Then sustain it so it doesn’t drift back. A manager who explains the why, involves the team, supports the transition, and holds the course gets change to stick; one who mandates it, provides no support, and blames resistance gets the failed rollout and a more cynical team.

Where it goes wrong

• Treating resistance as stubbornness instead of understanding its real cause.
• Mandating change without explaining why or involving the team.
• Panicking at the temporary performance dip and abandoning the change.
• Not sustaining the new way, letting it drift back to the old.

Related

Process improvement · Industry trends · Software updates and reprogramming · Culture, vision, and employer brand.