Mastering Project Turnarounds with Kerzner's Six Phase Recovery Methodology

Projects can fail for many reasons: unclear goals, poor communication, missed deadlines, or budget overruns. When a project starts to falter, it can feel overwhelming to get it back on track. Yet, recovery is possible with a structured approach. Kerzner’s Six Phase Recovery Methodology offers a clear roadmap to rescue failing waterfall projects and steer them toward success. In another upcoming post, I will outline a customized hybrid approach for Agile projects.

In this post, I will explain each phase of Kerzner’s methodology, as well as provide practical steps and examples to help project managers and teams regain control and deliver results.

Eye-level view of a project manager reviewing a detailed project recovery plan on a desk

Understanding Why Projects Fail

Before diving into recovery, it’s crucial to understand common reasons projects fail:

Project Management Support

Book Now

Unclear objectives leading to confusion and misaligned efforts.
Poor communications that cause misunderstandings and delays.
Inadequate risk management that leaves teams unprepared for obstacles.
Scope creep that expands project demands beyond capacity.
Lack of stakeholder engagement which generally reduces support and resources.

Recognizing these issues early helps target recovery efforts effectively.

Phase 1: Project Assessment

The first step is a thorough assessment of the project’s current state. This involves:

Reviewing project documentation, schedules, budgets, and deliverables.
Interviewing key stakeholders and team members to gather insights.
Identifying gaps between planned and actual progress.
Pinpointing root causes of failure, such as resource shortages or unrealistic timelines.

A clear, honest assessment sets the foundation for recovery by revealing what went wrong and what remains salvageable.

Phase 2: Project Replanning

Once the assessment is complete, the next phase focuses on replanning. This includes:

Revising project objectives to be realistic and measurable.
Adjusting scope to focus on critical deliverables.
Developing a new schedule with achievable milestones.
Allocating resources efficiently, including personnel and budget.
Establishing clear roles and responsibilities.

Replanning creates a fresh roadmap that reflects the project’s current reality and future goals.

Phase 3: Project Reorganization

Reorganization addresses team structure and communication channels:

Restructuring the team if necessary to improve skills alignment.
Clarifying reporting lines and decision-making authority.
Enhancing communication methods to ensure timely information flow.
Engaging stakeholders regularly to maintain support.

This phase strengthens the project’s human and organizational framework, which is vital for recovery.

Phase 4: Project Control

Control mechanisms keep the project on track:

Implementing rigorous monitoring of progress against the new plan.
Using performance metrics and dashboards for transparency.
Conducting regular status meetings to identify issues early.
Applying corrective actions promptly when deviations occur.

Strong control prevents small problems from escalating and keeps the team focused.

Phase 5: Project Recovery

This phase involves executing the recovery plan with discipline:

Prioritizing critical tasks that deliver the most value.
Managing risks actively to avoid surprises.
Maintaining stakeholder engagement through updates and involvement.
Motivating the team by recognizing progress and addressing concerns.

Recovery is about steady, consistent effort to rebuild momentum and confidence.

Phase 6: Project Closure and Lessons Learned

After the project reaches completion, closure is essential:

Verifying that deliverables meet quality standards and stakeholder expectations.
Documenting lessons learned to improve future projects.
Celebrating successes to boost morale.
Conducting a final review to ensure all contractual and administrative tasks are complete.

Closure provides a clear endpoint and valuable insights for continuous improvement.

Applying Kerzner’s Methodology: A Practical Example

Consider a software development project that missed its launch date due to scope creep and poor communication. Using Kerzner’s methodology:

The team assessed delays and identified unclear requirements as a root cause.
They replanned by narrowing the scope to essential features and setting a new timeline.
The project manager reorganized the team to include a dedicated requirements analyst.
Control processes were introduced with weekly progress reports and risk reviews.
The team focused on delivering core functionality first, keeping stakeholders informed.
Upon completion, they documented lessons learned about scope management and communication.

This structured approach helped the project recover and deliver a successful product.