Silence is the Biggest Risk in ERP
Judith O’Callaghan & Jakob Bent Smed
When ERP programs fail, the post-mortem rarely blames the technology. More often, the real culprit is silence.
Not the silence of systems, but the silence of people.
ERP programs don’t usually collapse because the system isn’t capable. They collapse because people didn’t feel safe raising their hand early — and because leadership didn’t create the space for them to do it.
That’s what resilience in transformation really looks like. In our combined experience, silence kills more ERP programs than complexity ever will.
The Early Warning Signs
The cracks always show up early:
- Data quality issues that keep reappearing despite repeated migration cycles.
- End-to-end processes that fall apart when tested in real-world scenarios.
- Timelines that everyone knows are impossible, but nobody dares to challenge.
We’ve both seen it:
- The junior analyst who spots critical data integrity gap but stays quiet.
- The plant manager who knows a process won’t meet GMP requirements but hesitates to escalate.
- The finance lead who worries about cutover risks but doesn’t want to be branded “negative” or “not a team player.”
By the time leadership notices, the issue isn’t a risk anymore. It’s reality — and far more costly to fix.
Why Silence Thrives in ERP Programs
Silence thrives when:
- The program is treated as purely “technical” instead of cultural and strategic.
- Leadership rewards optimism but punishes realism.
- Risks are logged but never acted on.
- People fear their careers will suffer if they’re seen as blockers.
One of the most dangerous assumptions in ERP is that “no news is good news.”
In truth, no news almost always means bad news waiting to surface.
Phase 0: Where Culture is Set
Silence takes root early — in Phase 0, the decisive moment where governance, direction, and culture are set.
Phase 0 isn’t just about system selection or high-level design. It’s about shaping the environment the program will live in. It’s where leadership decides whether honesty will thrive — or whether silence will grow and fracture the program later.
We’ve seen both outcomes play out:
- In one global rollout, a CFO said: “If we can’t talk about risks openly, we’ll fail. I want bad news on the table fast.” That single statement gave cover for honesty and the course-corrected program early.
- In another, leadership demanded “positive messaging only.” Concerns were suppressed until UAT, when broken processes and missing data came to light. The result: a delayed go-live, spiraling costs, and a burned-out team.
Same technology. Different cultures. Very different outcomes.
How We Break the Silence
When guiding organisations through Phase 0, our focus is simple:
🔹 Create psychological safety so risks and gaps can be raised without fear of blame.
🔹 Help leadership truly listen — not just nod politely, but act when people speak up.
🔹 Bring the human side of transformation into the same room as process design and system decisions.
This isn’t soft leadership. It’s the hardest form of control: building a culture where truth surfaces early enough to act on it.
The Truth About ERP Failure
Here’s the reality:
- Projects don’t fail because someone made a mistake.
- They fail because no one felt safe admitting it.
Safety isn’t soft. It’s not a “nice-to-have.”
It’s the single most important control mechanism in transformation.
That’s why Phase 0 has become our shared focus — the moment when ERP programs are set up for success or failure. It’s when leadership has the chance — and the responsibility — to build a culture resilient enough to handle the complexity ahead.
#ERP #DigitalTransformation #D365 #SAP #Leadership #BusinessTransformation #ERPStrategy #Phase0 #ChangeManagement #LifeSciences #Manufacturing