
Knowledge/Answer
Senior-led answer · Methodology
Why your team does not follow the new ERP, even though you communicated everything
Change in an ERP implementation rarely fails on communication, but on a missing data foundation and unclear governance.
Contents
Your question in detail?
A senior-led conversation gets to the heart of your situation.
Related service
Change in an ERP implementation rarely fails on communication, but on a missing data foundation and unclear governance. When the system shows unreliable numbers and no one makes decisions bindingly, the team loses trust. No workshop and no email campaign brings that trust back.
Why does acceptance grow out of reliability?
Acceptance grows when the system works in daily use, not when it is talked about well. When Business Central delivers correct figures, when a document lands where it belongs, and when an open question is decided within days, the team follows by itself. Conversely, no communications campaign helps when the figures have to be debated first.
Two quiet causes destroy that reliability. The first is an unclean data foundation: the system then looks wrong although it calculates correctly, because it correctly processes wrong input. The second is missing governance: decisions fizzle out, workarounds appear, and every department builds its own path.
Both causes sit upstream of the communication and cannot be compensated by it. Whoever wants acceptance invests in data quality and decision cadence, and the communication then reports on something that holds.
Why is resistance a symptom?
Resistance is almost always a symptom and rarely the origin. When people work around the new system, they usually have a factual reason: the new path is longer than the old one, information is missing where it is needed, or an exception is not represented and still has to be handled. Adjusting only the communication treats the symptom.
The effective levers sit earlier. Business departments are involved in the data rules and in the business sign-off, so that they experience the system as theirs. Key users get real time in the calendar, not goodwill. And exceptions are documented and decided instead of drifting into workarounds.
Change is therefore less a communications task than one of control. Control stays on your side, with Business Central as home, and it is exactly this clarity about responsibility that dissolves resistance.
“
A team does not follow a system it does not trust. Trust grows from reliable numbers and clear control, not from an email campaign.
Frank Maier, founder of DGP
Frequently asked questions
Briefly asked
Does a dedicated change management programme achieve nothing?
It does, but only on top of a viable data foundation and clear governance. Without a foundation it only masks the actual problems.
How do we recognise genuine resistance?
When users return to old ways despite training. That almost always points to unreliable data or unclear responsibilities.
How much change management does a Business Central project really need?
Fewer slides, more reliability: clear process decisions, key users with real time, working data at go-live. Acceptance follows a system that holds up in daily work, not a communications campaign.
Related
Related questions
Knowledge · Governance
How long may decisions take in an ERP project?
How fast an ERP project runs is decided not by the code, but by the pace of decisions.
04.08.2026
Read →Knowledge · Governance
Who actually controls your Business Central project when it gets tough?
Governance in a Business Central transformation is its own discipline, not a by-product of the project plan.
03.08.2026
Read →Knowledge · Governance
Who really leads your Business Central implementation?
Administering tasks and owning a project are two different things. The difference decides your project.
03.08.2026
Read →Where does your project really stand?
Talk to a senior, not to a sales rep.