We are introducing an AI-driven automated workflow to replace several manual data entry processes. Naturally, the staff is worried about job security. As the Business Analyst on the project, I need advice on how to handle this cultural resistance while still gathering accurate requirements from the very people who are afraid of the new system.
3 answers
I faced this exact scenario when we implemented RPA in our HR department last year. The key is transparency. I held "Discovery Workshops" where I explicitly showed how the AI would take over the "boring" tasks, allowing the staff to focus on more strategic, high-value work. When they saw that I wasn't there to replace them but to augment their capabilities, their input became much more honest and detailed. You have to be a bit of a psychologist as well as an analyst during these digital shifts.
Have you considered setting up a "Change Champion" program where influential employees get early access to the tools? Sometimes peer-to-peer reassurance works much better than anything coming from the project team or upper management.
Focus on the "WIIFM" (What's In It For Me) for every stakeholder. If they don't see a personal benefit, they will unintentionally sabotage your requirement gathering process every time.
Spot on, Emily. Empathy is an underrated BA skill. If you can prove that the new digital workflow saves them two hours of overtime a week, you've won the battle.
David, that is a brilliant suggestion. I’ve started identifying a few key users who are tech-savvy. If I can get them on board during the UAT phase, they can help me sway the skeptics. It also helps me refine the user requirements by getting feedback from people who actually know the day-to-day pain points better than anyone else in the building.