When employees complain, it is easy to get frustrated. Complaints slow you down, interrupt your day, and sometimes feel unfair. But during an ERP upgrade or any major organizational change, complaints are often early warning signs. They tell you where people are struggling, where processes are unclear, and where the change is not landing the way you hoped.
Instead of dismissing complaints, I encourage leaders to treat them as valuable data. When you listen carefully and respond thoughtfully, you can turn frustration into progress.
Here is a simple four step approach that works.
Step 1. Listen without getting defensive
When someone brings you a complaint, your first job is to listen. Let them finish. Ask clarifying questions. Show that you are taking them seriously. You do not have to agree with everything they say, but you do need to understand their perspective.
During an ERP transition, complaints often come from confusion, fear, or a lack of clarity. Listening helps you identify the real issue behind the frustration.
Step 2. Look for the underlying problem
Most complaints are symptoms, not root causes. Employees may complain about the system, the process, or the workload, but the real issue might be unclear expectations, missing training, or a workflow that no longer makes sense.
Your job is to look beneath the surface. Ask yourself what is really driving the frustration. When you identify the root cause, you can fix the problem instead of reacting to the noise.
Step 3. Decide what action you will take
Not every complaint requires a major change, but every complaint deserves a response. Once you understand the issue, decide what you will do about it. You might:
- fix a broken process
- clarify expectations
- provide additional training
- adjust a workflow
- explain the reasoning behind a decision
The key is to take some form of action, even if the action is simply explaining why things are the way they are.
Step 4. Close the loop
This is the step leaders skip most often. After you take action, go back to the person and tell them what you did. Closing the loop builds trust. It shows that you listened, took the issue seriously, and followed through.
During an ERP upgrade, closing the loop is especially important because people are already feeling uncertain. When they see you responding to concerns, their confidence grows.
Don’t let the situation get worse
Things really can be worse. It’s worse when employees stop complaining.
It’s not because things are better. They’re not. Employees no longer complain because they no longer believe it will make a difference. They give up.
Once apathy sets in, serious problems follow:
- Productivity tanks
- Errors and waste soar
- Problems are ignored
- Customers are mistreated
- Turnover rises
If your employees get to this point, it’s a long, hard road to turn things around. It’s much easier to address the problems when employees still want things to be better. That time is when they are complaining.
Moving forward
Employee complaints are not a distraction. They are a source of insight. When you listen carefully, look for the root cause, take action, and close the loop, you turn frustration into improvement. You also strengthen trust and help your team stay focused during a challenging transition.
If you want help building a stronger feedback loop during your ERP project or need support diagnosing recurring complaints, I would be glad to work with you.
