ERP Project Updates Look Good. The Program Isn’t.
Most ERP Steering Committees leave meetings feeling reassured.
Status is “Green”. Risks are “managed”. Milestones are “on track”.
That sense of control is often the first signal something is wrong.
Because by the time an ERP program visibly fails, the narrative has been stable—and positive—for months.
What Sponsors Expect
Project Sponsors and SteerCo members assume:
- Updates reflect reality
- Risks are surfaced early
- Issues are clearly owned
- Vendors are transparent
- Project Managers are objective
The implicit belief: “If something was going wrong, we would know.”
That belief is structurally flawed.
ERP programs rarely fail through visible collapse.
They drift—quietly—under a layer of professional-looking updates.
What Actually Happens in the Room
Instead of clarity, updates are often shaped to maintain momentum, avoid scrutiny, and protect positions.
The result is not lying.
It is managed perception.
Below are the most common patterns.
1. The Deflection Loop
What you hear:
- “That’s a good question—we’re still validating with the business.”
- “We’ll take that offline.”
- “It depends on how Finance wants to handle it.”
What is happening:
The question is not answered. Ownership is diffused.
Live example:
You ask:
“Is payroll configuration aligned to our award interpretation?”
Response:
“We’ve had strong engagement with HR and the vendor is confident.”
No answer. No ownership. No evidence.
Signal: If answers move sideways instead of forward, you are not getting truth—you are getting motion.
2. The Green Status Illusion
What you hear:
- “Overall status remains Green”
- “Minor risks, all under control”
- “No major blockers”
What is happening:
Status is being managed as a stakeholder comfort tool—not a delivery signal.
Live example:
- Data migration accuracy: 72%
- UAT defect backlog: growing
- SMEs unavailable
Status: Green
Signal: If “Green” coexists with unresolved fundamentals, the reporting model is broken.
3. The Complexity Shield
What you hear:
- “The integration architecture requires further refinement”
- “There are some dependencies in the middleware layer”
- “It’s a complex configuration scenario”
What is happening:
Complexity is used to discourage challenge.
Live example:
A simple issue:
Supplier invoices are not matching POs correctly
Becomes:
“There are multi-layer validation dependencies between procurement and finance modules.”
Signal: When simple business problems are explained in technical language, clarity is being avoided.
4. The Detail Flood
What you see:
- 40-slide decks
- Task-level updates
- Percent complete everywhere
What is missing:
- Decision clarity
- Risk exposure
- Outcome alignment
Live example:
You receive:
- “Configuration 85% complete”
- “Testing 60% complete”
But no answer to:
“Will we be ready to pay staff accurately on Day 1?”
Signal: High detail with low meaning is a deliberate masking pattern.
5. The “Happy Story”
What you hear:
- “Strong collaboration across teams”
- “Great engagement from stakeholders”
- “Positive momentum”
What is happening:
Narrative replaces evidence.
Live example:
Despite:
- Rework increasing
- SMEs disengaged
- Decisions delayed
Update focuses on:
“Workshops were well attended and feedback was positive.”
Signal: If sentiment is high but delivery signals are weak, you are being reassured—not informed.
6. The Slippery Answer
What you hear:
- “Yes, that’s being worked on”
- “We’re comfortable with where things are”
- “It’s progressing as expected”
What is happening:
Answers sound acceptable but contain no commitment.
Live example:
You ask:
“Is the asset register fully reconciled?”
Response:
“We’ve made significant progress and are working through remaining items.”
Translation: No, but we are not saying that directly.
Signal: If you cannot extract a clear “Yes / No / By When,” you do not have control.
7. The Blame Drift
What you hear:
- “The business hasn’t finalised requirements”
- “The vendor needs more input”
- “Dependencies are causing delays”
What is happening:
Accountability is diluted across parties.
Live example:
Procurement design is incomplete.
- Vendor says: “Waiting on business”
- Business says: “Waiting on vendor guidance”
No owner. No progress.
Signal: When everyone is involved, no one is accountable.
Why This Happens
This is not incompetence alone. It is structural.
- Vendors protect commercial position
- Project Managers protect delivery optics
- Internal teams avoid escalation
- Executives signal preference for “good news”
Over time, a system forms where:
Clarity becomes risky.
Ambiguity becomes safe.
The Real Cost
By the time reality surfaces:
- Data is not ready
- Processes are not aligned
- Users are not prepared
- Controls are weak
And then:
- Go-live is delayed, or worse—forced
- Confidence collapses
- Cost escalates
- Blame intensifies
Most critically:
The organisation loses trust in the system before it even stabilises.
Reframing the Role of SteerCo
SteerCo is not there to receive updates.
It exists to:
- Interrogate reality
- Force clarity
- Anchor accountability
- Make decisions under uncertainty
The shift required:
From:
“Are we on track?”
To:
“What is not working—and who owns fixing it?”
What to Do Next (Practical Control Moves)
Most governance frameworks focus on what the project team should do.
Start with what you, as Sponsor or SteerCo, must change.
Because one uncomfortable truth sits underneath all of this:
If you consistently receive polished updates instead of reality, it is often because the environment rewards polish.
1. Create Permission for Bad News
Make it explicit:
- “We expect to hear what is not working.”
- “Early risk is valued more than late surprises.”
Then reinforce it in behaviour:
- Do not react defensively
- Do not penalise escalation
- Do not rush to solutions before understanding
If people sense that bad news creates discomfort at the top, they will filter it before it reaches you.
2. Start with Facts, Not Narratives
Reset the structure of updates:
Ask for:
- What is proven (evidence-based)
- What is assumed
- What is failing or at risk
Before any commentary, sentiment, or storyline.
Example shift:
Instead of:
“Testing is progressing well”
Require:
“412 test cases executed, 96 failed, payroll scenarios not yet validated”
Facts anchor reality. Narratives can distort it.
3. Listen with Intent, Not Comfort
In most SteerCo rooms, listening is passive.
Updates are heard, not interrogated.
Change the posture:
- Listen for gaps, not just statements
- Listen for what is avoided, not just what is said
- Listen for ownership clarity, not activity
If something feels unclear, it usually is.
4. Challenge Your Own Preference for “Good News”
A critical self-check:
- Do you move faster when updates are positive?
- Do you slow down or disengage when issues are raised?
- Do you unconsciously reward confidence over accuracy?
If yes, the system adapts to you.
Teams optimise for executive preference.
If you prefer reassurance, you will receive it—at the cost of visibility.
5. Demand Direct Answers
Every critical question must result in:
- Clear answer (Yes / No / Not ready)
- Named owner
- Defined date
Reject:
- “In progress”
- “Being worked on”
- “We are comfortable”
Clarity is a discipline, not a by-product.
6. Translate Everything to Business Impact
Do not accept technical framing in isolation.
Force translation:
- What does this mean for payroll accuracy?
- What does this mean for revenue collection?
- What does this mean for service delivery on Day 1?
If impact is unclear, the issue is not understood.
7. Track Decision Latency
Monitor:
- Which decisions are pending
- How long they have been pending
- Why they are not being made
Delays signal hidden complexity, avoidance, or misalignment.
8. Enforce Single-Point Accountability
For every risk, issue, or deliverable:
- One accountable owner
- Not a group
- Not “the team”
Diffuse ownership is a primary source of slippage.
9. Replace Status Colours with Evidence
Remove reliance on:
- Green / Amber / Red
Ask instead:
- What has been validated end-to-end?
- What has not been tested in real conditions?
- What could fail at go-live?
Colour is perception. Evidence is control.
10. Introduce the “Clarity Test”
At the end of each update, ask:
- Can this be explained clearly in 2 minutes?
- Do we know what will break next?
- Are we hearing reality—or a managed version of it?
If clarity is missing, governance has not occurred.
Bottom Line
You do not eliminate “B.S.” by asking better questions alone.
You eliminate it by removing the incentive to provide it.
That starts with:
- Openness to uncomfortable truths
- Discipline in demanding facts
- Willingness to hear what you may not want to hear
Because in ERP programs:
The quality of information you receive is a direct reflection of the environment you create.
