Implementing a management system in a company is a bit like renovating a kitchen at home: everyone knows it "has to be done", but nobody feels like functioning differently for a while.
With every implementation you can hear a set of lines that are almost as standard as coffee at the morning meeting. Here is my TOP 10 from the battlefield, together with possible responses from the person leading the implementation and ideas for taming resistance without drama, but with a smile.
1. "We have done it this way for 20 years, so why change it?"
Possible response: "If it has worked for so many years, we have a great foundation to make it even better." Or: "The market is changing - maybe it is worth checking whether the current way is still the most effective."
What to do in the implementation: start by showing that implementation does not mean a revolution for the sake of revolution. First identify what genuinely works well and keep it. People accept change more easily when they hear: "we are not demolishing things, we are organizing them."
2. "But we already have quality."
Possible response: "And that is great - the system is supposed to help show it, maintain it, and develop it, not invent it from scratch."
What to do in the implementation: do not start with shortcomings, start with strengths. Show that a management system is not a punishment for success, but a way to make sure success is not accidental.
3. "This will only mean more paperwork."
Possible response: "It is not about producing documents wholesale, but about rules that genuinely help people work."
What to do in the implementation: minimize bureaucracy. Document only what is needed and useful. If something can be simplified into a checklist, a diagram, or a short instruction, all the better. Nobody dreams of a 47-page stapler procedure.
4. "We do not have time for this."
Possible response: "It will take a little time now, but it will save us a lot of time later."
What to do in the implementation: break the work into small stages. Short workshops, concrete tasks, clear priorities. People protest less when change does not sound like an extra full-time job.
5. "This is only for the auditor."
Possible response: "The auditor drops by for a moment. We live with this system every day, so first and foremost it has to work for us."
What to do in the implementation: show everyday benefits - fewer mistakes, less firefighting, easier onboarding, more predictability. When people see what it gives them, the auditor stops being the main character of the story.
6. "Someone from the top has come up with this again."
Possible response: "Maybe, but that is exactly why we want to build it with you, not beside you."
What to do in the implementation: involve employees in designing solutions. Consultations, workshops, questions about real problems. Resistance decreases when people feel they are co-authors, not extras.
7. "That will never work here."
Possible response: "Then let us check what exactly may not work and how to adapt it to your reality."
What to do in the implementation: do not implement by the book alone, implement practically. Every company has its own culture, pace, and language. The system should fit the organization, not the organization a binder.
8. "We had such an implementation once before and nothing came of it."
Possible response: "All the more reason to check what failed then so we do not repeat the same scenario."
What to do in the implementation: name previous experiences directly. Draw conclusions. Show the difference: better communication, greater leadership involvement, simpler tools, a real action plan. Sometimes the biggest enemy of implementation is not change, but a bad memory of the previous one.
9. "Everyone already knows what to do."
Possible response: "As long as everyone is in place - yes. The system helps when someone is new, absent, or when the work needs to stay consistent."
What to do in the implementation: show the risks of knowledge kept only in people's heads. A good example is a key person's vacation, employee turnover, or rapid onboarding. Suddenly an instruction turns out to be more useful than people thought.
10. "We have our own specifics here."
Possible response: "Every company has its own specifics - that is exactly why I do not propose a ready-made template, but a solution adapted to how work really functions in your organization."
What to do in the implementation: understand key processes, separate exceptions from standards, implement step by step, collect team feedback, and adapt the solution to practice.
These lines do not necessarily mean people are "against" the system.
Most often they simply mean:
- they are afraid of chaos,
- they do not know what will change,
- they have bad memories from previous "great projects",
- or they simply do not want another binder that dies a natural death after the audit.
That is why the person implementing the system should know how to do three things: talk, explain, and simplify. It also helps to have truckloads of patience and not roll your eyes. If you season all that with a bit of humor, success is much more likely.
Even when, for the eighth time, you hear: "But we have our own specifics..."
Anyone who has implemented a system knows this: the hardest thing is not describing the process. The hardest thing is calmly answering the line: "Why change it if it somehow works?"
So now a question for you: which sentence do you hear most often during implementations?