Case Studies 6 min read November 16, 2026 project post mortem

The Delayed ERP Post-Mortem: Three Acts of a 40% Budget Blowout

A project post-mortem analysis of Chenab Mills' ERP implementation reveals how soft starts, expanding scope, and lack of closure led to disaster.

The Three Acts of Project Failure

The Chenab Mills ERP implementation tells a familiar story in project management: a project post-mortem revealing how good intentions led to a 40% budget blowout. This case study follows three acts that mirror common project failures. The first act began innocently enough, with project approval discussed casually during a dinner conversation. Without proper documentation, this soft start lacked the necessary foundation. The second act saw requests absorbed "one inch at a time" without proper scope boundaries, while the third act concluded with no formal acceptance or handover, leaving a shadow spreadsheet born from distrust. Each act represents a critical failure point in project execution.

Missing Project Charter

The first act's failure stemmed from the absence of a proper project charter. In our Project Management course, we emphasize that a charter defines the project's purpose, scope, and stakeholders from day one. Without this document, Chenab Mills lacked clear ownership and boundaries, allowing the project to drift from its original intent. The charter serves as your flight director's manual, establishing who owns the mission and what success looks like. Many projects fail not from technical issues, but from fuzzy definitions that lead to scope creep and misaligned expectations. The "Why Projects Fail — Field Guide" download in Week 1 helps you identify these definition failures before they derail your project.

Absent Scope Fence

The second act's expanding middle demonstrates what happens without a scope fence. Chenab Mills absorbed requests incrementally, each seemingly minor addition accumulating into significant scope creep. This is where the Project One-Pager becomes crucial—it forces you to name the outcome and draw the boundary explicitly. The five fields (outcome, owner and sponsor, boundary, success measure, top risk) create guardrails against uncontrolled expansion. Without these boundaries, projects like Chenab Mills' ERP implementation suffer from feature bloat and timeline delays. The "Project One-Pager Template" download provides a practical tool to establish these boundaries early in your project lifecycle.

Project StageDominant Failure Mode
InitiationUndefined purpose and ownership
PlanningInadequate scope definition
ExecutionUncontrolled scope creep
MonitoringLack of variance tracking
ClosureNo formal acceptance criteria

No Formal Closeout

The third act's unowned ending reveals the critical importance of project closeout procedures. Chenab Mills went live with no formal acceptance or handover process, leaving stakeholders with a shadow spreadsheet born from distrust. This is where the Project Life Cycle's closure stage becomes essential. Without proper closure, projects linger in limbo, consuming resources without clear resolution. The "Post-Mortem Dossier" download in Week 1 provides a framework for conducting thorough post-project reviews. These reviews aren't about assigning blame but extracting valuable lessons to improve future project outcomes. A proper closeout ensures that all deliverables are accepted, documentation is complete, and the team can formally disband.

Learning from Failure

Conducting a project post-mortem isn't about dwelling on what went wrong—it's about extracting actionable insights to prevent future failures. The Chenab Mills case teaches us that projects fail at specific points in their lifecycle, each requiring particular tools and processes to succeed. By understanding where and why projects typically fail, you can implement preventive measures before issues arise. Our Project Management program teaches you to recognize these failure patterns and apply the right tools at the right time. The Week-1 Workbook Lab helps you practice identifying these patterns in your own projects, turning potential failures into learning opportunities.

Your Next Step

Ready to apply these lessons to your own projects? The Project Management certification track provides 120 hours of comprehensive training with 60 cinematic video lessons, weekly labs on your real projects, and leads to the verifiable ZLCPM certificate. Week 1 opens free after sign-up, allowing you to experience the "Foundations of Project Management" module and complete "The Mission Brief" lab before committing. This practical approach ensures you can immediately apply what you learn to your current work challenges. The program's structure mirrors real project management challenges, with each week building on the previous one to create a comprehensive skill set.

Frequently asked questions

▸How long does the certification take?

The program spans 12 weeks with 120 training hours, designed for working professionals.

▸What does the certificate include?

You receive the verifiable ZLCPM certificate upon successful program completion.

▸Can I try before enrolling?

Yes, Week 1 opens free after sign-up to preview the content and complete initial labs.

▸Is this suitable for beginners?

The program assumes basic project knowledge but provides thorough foundational training.

Keep reading