From Unclear Outcomes to a 12-Month Partnership
How pausing to define outcomes turned a failing project into a phased, multi-workstream engagement.
- Engagement
- ERP implementation
- Stage
- Mid-project
The situation
A four-month ERP implementation was at real risk of failure, with confidence eroding on both sides.
What was really going wrong
- The client's core team didn't fully understand its own business processes, so requirements were wrong.
- Those wrong requirements led to flawed early design decisions.
- Nobody had defined what a successful outcome looked like, which left the delivery team building without a clear target.
How we fixed it
Step 1: Stop building the wrong thing.
We paused solution design and refocused the engagement on business objectives, outcomes, and who owned each decision.
Step 2: Have the honest conversation.
The turning point was a direct, transparent conversation with the company's founder about the gap between how well the business understood its own processes and what it expected from the implementation, and what needed to change internally:
Right now, the challenge isn't the system or the team, it's that the outcome isn't clearly defined. Until we align on that, we risk building the wrong solution.
Step 3: Help them get aligned.
We worked with leadership to find the gaps in their own process understanding and structured their internal alignment before resuming delivery.
Step 4: Restructure the work.
We reframed the implementation as phases: outcome and requirements alignment first, then implementation phases once there was clarity. We were clear that delivery would move at the pace of the client's alignment.
The results
Bar comparison. Original engagement 4 months. After reset about 12 months of phased work.
Original engagement: 4 months
After reset: ~12 months of phased work
~12 months
of phased work across multiple workstreams, grown from a 4-month implementation
Sponsorship
Executive sponsorship from the founder
Steady progress
Project moved from likely failure to steady progress
The lesson
When the outcome isn't clear, building faster only builds the wrong thing. Pausing to align is often what saves the project.
