Leadership during ERP implementation | Learning cycles, retrospectives, psychological safety
There is a particular kind of discipline the gym teaches that many leaders overlook. It is not the discipline of lifting heavier, pushing harder, or adding one more set. It is the discipline of knowing when not to push. The discipline of recovery. The discipline of pausing. The discipline of rest.
Progress in training does not happen only when the weight is moving. It happens after the workout — when the body repairs, adapts, and returns stronger. Without recovery, training becomes strain. Strain becomes fatigue. Fatigue becomes injury.
ERP implementations are no different. However, many leaders manage these projects as if constant pressure is the only way to succeed. They push for more reviews, escalate issues, emphasize urgency, work late, and demand rapid progress. But intensity does not equal progress. Moving quickly does not mean successful adoption. And exhaustion doesn’t prove true commitment.
The best implementations understand something more fundamental. Rest days are part of training.
The Hidden Fatigue Inside ERP Projects
An ERP implementation asks people to do two jobs at once.
They must run today’s business while helping to build tomorrow’s operating model. They must meet customer deadlines while attending workshops, validating masters, testing transactions, learning new screens, and adapting to new controls.
On the project plan, these are tasks. Within the organisation, there are loads.
A finance executive is reconciling old habits with new approval workflows.
A production planner is concerned that data accuracy will disrupt scheduling.
A sales user is anxious about capturing every lead and follow-up in the CRM.
A warehouse supervisor fears dispatch delays after go-live.
This is why some projects look healthy in meetings but feel heavy on the ground. The dashboard may be green even as people run out of energy.
In the gym, that is the athlete smiling through overtraining. The numbers may still look fine — right up until the breakdown begins.
Go-Live Is Not the Finish Line
One of the most common leadership mistakes is treating go-live as the final rep.
The system launches. Emails are sent. Photos are taken. Leadership congratulates the team. Attention then shifts to the next priority.
But anyone who has lived through an ERP implementation knows the real work often begins after go-live.
That is when users face live pressure.
That is when process gaps become visible.
That is when confidence is tested.
That is when small frustrations can turn into resistance.
In gym terms, go-live is not racking the weight and walking away. It is the moment you ask: was the lift strong, or did we compromise form to finish it?
Retrospectives: Checking Form After the Lift
Strong leaders create pauses during implementation, not because the project is failing, but because learning requires space.
A retrospective is the organisational equivalent of checking the form after a lift. You do it not because something went wrong, but because improvement requires feedback.
After blueprint sign-off.
After UAT.
After training waves.
After the mock migration.
After the first month’s close on the new system.
The questions are simple and powerful:
- What worked well?
- Where did users struggle?
- What surprised us?
- Which assumptions were wrong?
- What must we improve before the next phase?
Without these pauses, teams repeat friction until it becomes the norm.
Psychological Safety Is Recovery for the Mind
Physical recovery repairs muscles. Psychological safety repairs trust.
Every ERP project depends on people speaking honestly and early. Yet many stay silent.
They do not admit to confusion.
They hide adoption problems.
They understate risks.
They say “all good” when they mean “we are stuck.”
Why? Because honesty can feel unsafe. Psychological safety is not softness. It is a form of implementation intelligence. When people feel safe, they say:
- “Training was not enough.”
- “This workflow is slowing us down.”
- “Master data needs cleanup.”
- “Users need support on the shop floor.”
- “We made the wrong design choice.”
That honesty saves projects. Silence delays failure until it becomes costly. In the gym, ignored pain becomes injury. In ERP, ignored truth becomes rework.
Great Implementations Use Cycles
The best training programmes do not require maximum effort every day. They work in cycles: push, recover, adapt, repeat.
ERP leadership should do the same.
There are phases for design intensity.
Phases for testing discipline.
Phases for hypercare support.
Phases for stabilisation.
Phases for optimisation.
If every phase is treated like an emergency, people burn out and judgment declines.
Sometimes the best leadership move is not another escalation meeting. It is a day of focused user support.
Sometimes the fastest decision is not more pressure. It is less confusion.
Sometimes the smartest way to move forward is to pause and restore confidence.
What Leaders Should Do Now
§ Build recovery into the plan- Stabilisation is not optional. Schedule it.
§ Run retrospectives at every milestone - Capture lessons while they are fresh.
§ Measure energy, not just status - A green tracker can hide a tired workforce.
§ Reward early truth - Thank the person who raises a problem early.
§ Stay visible after go-live - Leadership presence matters most when confidence dips.
Final Lift
Any leader can ask for one more sprint. Mature leaders know how to sustain performance.
ERP implementation is not won by endlessly pushing people. It is won by helping people learn, adapt, recover, and grow stronger through change.
Because in the gym, and in transformation, recovery is not the opposite of progress.
It is where progress becomes tangible.
