Our operations team is resisting our shift toward AI-powered automation because they are comfortable with our manual legacy workflows. How do we use the IDS process to dismantle this operational inertia and permanently solve the system bottlenecks that are capping our capacity?

Question

Tyler Smith · Accepted Answer

When your team resists moving from manual workflows to automated systems, it is rarely a technical issue. It is almost always an emotional issue rooted in a fear of incompetence or job loss. You must use the IDS® process to surface and solve this underlying resistance.

Begin the Identify phase by putting the bottleneck on the table. Do not define it as the software transition is behind schedule. Define it around human behavior and accountability. Ask who owns the transition on the Accountability Chart™ and whether they truly GWC™ that seat.

During the Discuss phase, allow your team to express their frustrations without judgment. They need to air their fears about how the new automated processes will affect their daily work. Ask them specifically what manual steps they are desperate to keep and why. Often, you will find they are holding onto tasks because they do not trust the new system to handle edge cases.

To Solve the issue, create a clear, stepped transition plan as a series of weekly To-Dos. Do not force a massive, overnight change. Have the team run the legacy process and the new automated system in parallel for two weeks to build trust in the data. By solving the trust issue first, the technical rollout will naturally succeed.