Big tech projects rarely derail overnight. They drift, one “green” status report at a time, until costs balloon, milestones slip, and confidence fades. The good news: you can recover. Here’s a pragmatic playbook distilled from dozens of remediation engagements and expert-witness investigations.
The 5-Step Rescue Framework
1) Admit there’s a problem (end the “all green” fiction)
Denial is expensive. If your gut says timelines are slipping, training hasn’t stuck, or benefits feel fuzzy, you’re probably right (and it’s usually worse than it looks). Name the risks out loud so you can manage them.
Red flags to trust:
- “Green” dashboards vs. messy front-line reality
- Vendor pressure to “keep moving” despite unresolved defects
- Heavy spend on build/config with thin investment in people/process
2) Run a rapid, independent health check (without stopping work)
In 2–4 weeks, perform a no-drama assessment in parallel to the project. Look beyond “does the software run” to program health across 13 core dimensions: scope, schedule, resourcing, PMO, testing, data, integrations, cutover, support, change management, training, benefits, and vendor management.
Important: Don’t let your system integrator grade their own homework. Independence = objectivity.
3) Prioritize the right problems (impact > noise)
You can’t fix 100 issues at once. Stack-rank by business impact and time-to-mitigate.
Typical top offenders:
- Change management & training: People can click through tasks, but can’t perform their jobs in the new model.
- Unrealistic plan: Compressed timeline and over-staffed SI burn rate.
- Testing gaps: Too little end-to-end/UAT; defects discovered at go-live.
- Data readiness: Cleansing, mapping, governance, and cutover rehearsal under-scoped.
- Vendor control: SI is steering scope, spend, and cadence.
4) Recast the plan (governance, scope, timeline, spend)
Reboot governance
- Activate the executive sponsor (decisions, priorities, blockers removed).
- Empower a business-led PMO to manage all workstreams (the SI is one vendor among many).
- Add independent QA to keep status honest and risks visible.
Right-size and re-sequence
- Re-baseline scope and timeline to reality; phase delivery around traceable value.
- Reduce SI staffing to what the plan truly needs; add capacity only when pre-reqs are met.
- Front-load data, UAT (multiple cycles), cutover rehearsal, and hypercare.
Put people and value at the center
- Define future roles, KPIs, and decision rights; train to jobs, not just screens.
- Tie every sprint/release to a measurable business outcome (cash, margin, cycle time, risk).
Use AI pragmatically
- Let AI accelerate testing, documentation, and analytics, and insist savings show up as reduced hours/cost, not more bodies.
5) Take back control (it’s your program)
If needed, slow the run-rate or pause briefly to reset; better a controlled stop than months of waste. Replace underperforming vendors, renegotiate change orders, and realign incentives to delivered outcomes.
30-60-90 Day Rescue Plan (example)
- Days 0–30: Stabilize
Independent health check; executive/PMO reboot; freeze scope creep; critical-defect triage; staffing right-sizing; risk register with owners/dates. - Days 31–60: Rebuild
Re-baselined plan approved; data strategy (cleansing, mapping, cutovers) live; UAT cycles scheduled; change plan with role/impact maps; value/KPI tree locked. - Days 61–90: Prove & Launch
UAT cycle 1 complete, defects burned down; cutover rehearsal #1; hypercare playbook staffed; first value release deployed with KPIs tracked.
Quick Self-Check (answer yes/no)
- Do you have a business-led PMO (not SI-led)?
- Are UAT and data cutovers planned as multi-cycle events?
- Can every feature tie to a benefit KPI owned by the business?
- Do status reports come from independent QA?
- Could you pause/slow next month without losing control?
If you answered “no” to 2+ items, you’re carrying more risk than you think.
Bottom line
Rescues succeed when leadership tells the truth, reclaims governance, and funds people, data, and testing with the same intensity as build. It’s your company and your program, act like it.
Want a second set of eyes on a wobbling project? Third Stage Consulting’s independent QA and remediation teams can run a rapid health check and help you recast the plan. Also see my book Welcome to the Jungle for failure case studies and patterns to avoid.
Eric is recognized globally as a leading voice in digital transformation and ERP strategy. Over the past two decades, he has helped hundreds of organizations – including Nucor Steel, Fisher & Paykel Healthcare, Kodak, Coors, Boeing, and Duke Energy – define their technology roadmaps, modernize complex operations, and deliver real business value from large-scale transformation initiatives.
As Founder and CEO of Third Stage Consulting, Eric leads an independent, technology-agnostic advisory firm focused on helping clients navigate the shift from traditional ERP to more flexible, AI-enabled Digital Enterprise Operations (DEO) models. His work spans ERP selection, implementation quality assurance, organizational change, and operating model design across a wide range of industries and geographies.
Eric is also a prolific thought leader, known for his pragmatic takes on AI, cloud, and enterprise software trends, as well as his firm’s benchmark research and frameworks for de-risking transformation. He is dedicated to helping executive teams cut through vendor hype, make confident investment decisions, and successfully reach the “third stage” of their digital evolution.
