Measuring Project Success and Diagnosing Failure

The "Why": Success Is Not What You Think It Is

A project can be a physical failure and a political success. The Aswan Dam is the classic example — it delivered enormous strategic value to Egypt despite significant engineering compromises and environmental consequences. This single observation demolishes the naïve assumption that project success is a binary outcome.

Whether a project is judged successful depends entirely on the perspective from which it is viewed. The project manager who delivered on time and under budget may declare victory, while the end user struggling with an unusable product declares catastrophe. Both are correct — from where they stand.

This is why measuring success is not an exercise in checking boxes. It is an exercise in multi-perspective evaluation that demands structured tools, honest diagnosis, and the intellectual courage to distinguish between short-term metrics and long-term value.

Core Principle: The key ingredient of success or failure is not the short-term outcome, but what happens in the longer term. A project that meets its triple constraint but produces a product nobody uses is not a success.

---

The "What": Defining Success Across Perspectives

Most projects are a mixture of failure and success — some things worked and some did not. To perform a meaningful evaluation, the project must be examined from six distinct perspectives:

Traditional success indicators — schedule adherence, budget compliance, and deliverable completion — capture only the project manager's perspective. A comprehensive evaluation must go further.

Success Criteria: The Project Manager's View

From the PM's vantage point, success means:

• The project came in on schedule
• The project came in on budget
• The developed solution works as intended
• Given the problem it was designed to solve, the project does the best possible job
• The results represent a definite improvement over previous methods

Success Criteria: The Client's View

From the client's perspective, the criteria shift:

• The project came in on schedule and on budget
• The project is being used by its intended users
• The client is confident that start-up problems will be minimal
• The client is satisfied with the project process (not just the outcome)
• Use of the project has directly led to improved decision-making or performance
• The project will have a positive impact on stakeholders

Critical Distinction: Notice that the client cares about adoption and impact while the PM cares about delivery and functionality. These perspectives can diverge dramatically — a technically flawless deliverable that nobody adopts is a PM success and a client failure.

Project Manager's Success Lens

On Schedule

On Budget

Solution Works

Best Fit for Problem

Performance Improvement

Client's Success Lens

On Schedule

On Budget

Being Used by Users

Minimal Start-Up Issues

Improved Decision-Making

Positive Stakeholder Impact

Shared: Time & Cost

Relationship details

From	Relationship	To
Project Manager's Success Lens	leads to	Shared: Time & Cost
Client's Success Lens	leads to	Shared: Time & Cost

---

Tools for Success Measurement

Declaring success without measurement is opinion. The following four tools convert subjective judgement into defensible evidence:

1. Key Performance Indicators (KPIs)

Quantitative indicators developed in consultation with the client and project stakeholders, listed in order of priority. KPIs must be defined during project planning — not invented after the fact to justify outcomes.

2. Baseline Measurement

Pre- and post-implementation measurement of pre-defined criteria using a structured auditing process. This requires the discipline to measure the "before" state before the project changes it — a step frequently omitted.

3. Benchmarking

Measurement of project variables against established internal or external targets within defined ranges and tolerances. Benchmarking answers: "How does our performance compare to industry standards or our own historical data?"

4. Post-Implementation Review (PIR)

Periodic formal comparisons of actual results against metric targets after the completion of the project. PIRs are distinct from project closure reviews — they occur weeks or months later, once the deliverable has been in operation long enough to generate meaningful performance data.

---

Diagnosing Failure: The 16 Factors

Classic project management theory implies that any project can succeed if properly defined, planned, and implemented. This is dangerously wrong. Some projects will fail regardless of execution quality — because the conditions for success were never established.

The factors that lead to project failure cluster into two categories: execution failures (poor management of a viable project) and foundational failures (structural problems that doom the project before work begins).

Execution Failures

Foundational Failures

PROJECT FAILURE

Execution Failures

Foundational Failures

Lack of Planning

Unrealistic Plan

Uncontrolled Changes

Lack of Expertise

Lack of Leadership

Inadequate Monitoring

Poor Time/Budget Mgmt

No Evaluation/Audit

Inadequate Stakeholder Commitment

Risks Not Assessed

Concept-to-Application Gap

Not Recognised as a Project

Inaccurate Estimates

No Flow-On Understanding

Organisational Politics Ignored

Poor Preparation

Relationship details

From	Relationship	To
PROJECT FAILURE	leads to	Execution Failures
PROJECT FAILURE	leads to	Foundational Failures
Execution Failures	leads to	Lack of Planning
Execution Failures	leads to	Unrealistic Plan
Execution Failures	leads to	Uncontrolled Changes
Execution Failures	leads to	Lack of Expertise
Execution Failures	leads to	Lack of Leadership
Execution Failures	leads to	Inadequate Monitoring
Execution Failures	leads to	Poor Time/Budget Mgmt
Execution Failures	leads to	No Evaluation/Audit
Foundational Failures	leads to	Inadequate Stakeholder Commitment
Foundational Failures	leads to	Risks Not Assessed
Foundational Failures	leads to	Concept-to-Application Gap
Foundational Failures	leads to	Not Recognised as a Project
Foundational Failures	leads to	Inaccurate Estimates
Foundational Failures	leads to	No Flow-On Understanding
Foundational Failures	leads to	Organisational Politics Ignored
Foundational Failures	leads to	Poor Preparation

---

The Duck Alignment Theory: Maximising Success Before Execution

Derek Lidlow of Lidlow Technologies proposed a deceptively simple model for maximising project success. His insight: just as ducklings must align behind their mother before learning to swim, project teams must establish five preconditions in sequence before beginning work.

The Duck Alignment Theory does not guarantee success. What it does is maximise the probability of success by ensuring the right conditions exist before resources are committed.

Key Insight: The theory requires no additional spending, no resource diversion, and no ego management. It requires only commitment to the sequence — spending time ensuring each duck is aligned before taking action. The investment is small relative to the consistently excellent returns.

🦆 Duck 1 — Comprehension

🦆 Duck 2 — Motivation

🦆 Duck 3 — Skills

🦆 Duck 4 — Resources

🦆 Duck 5 — Communication

✅ Maximised — Success Conditions

Relationship details

From	Relationship	To
🦆 Duck 1 — Comprehension	leads to	🦆 Duck 2 — Motivation
🦆 Duck 2 — Motivation	leads to	🦆 Duck 3 — Skills
🦆 Duck 3 — Skills	leads to	🦆 Duck 4 — Resources
🦆 Duck 4 — Resources	leads to	🦆 Duck 5 — Communication
🦆 Duck 5 — Communication	leads to	✅ Maximised — Success Conditions

---

The NASA Mars Climate Orbiter: When Foundational Failure Meets Execution

On 23 September 1999, NASA lost contact with the Mars Climate Orbiter as it passed behind Mars. It never reappeared. Investigation revealed that the probe's trajectory had dropped to roughly 57 km altitude — far below the intended 150 km orbit — causing it to break apart in the Martian atmosphere.

The root cause was a unit-of-measurement mismatch between NASA (using Newtons) and subcontractor Lockheed Martin (using Imperial units). This is not merely a technical error. Mapped against the failure taxonomy above, it represents multiple simultaneous foundational failures: assumptions not assessed, inadequate monitoring, and a missing concept-to-application bridge between two engineering cultures.

The disaster illustrates a critical lesson: catastrophic failure is rarely caused by a single mistake. It emerges from a chain of failures — each individually survivable, but collectively lethal.

Lockheed Martin — Imperial Units

Navigation Data — Transmitted

NASA Assumes — Metric Units

Trajectory — Miscalculation

57 km Altitude — (Expected 150 km)

Mars Climate Orbiter — Destroyed

Assumptions — Not Assessed

Inadequate — Monitoring

No Evaluation / — Audit

Relationship details

From	Relationship	To
Lockheed Martin — Imperial Units	leads to	Navigation Data — Transmitted
Navigation Data — Transmitted	leads to	NASA Assumes — Metric Units
NASA Assumes — Metric Units	leads to	Trajectory — Miscalculation
Trajectory — Miscalculation	leads to	57 km Altitude — (Expected 150 km)
57 km Altitude — (Expected 150 km)	leads to	Mars Climate Orbiter — Destroyed
NASA Assumes — Metric Units	leads to	Assumptions — Not Assessed
Trajectory — Miscalculation	leads to	Inadequate — Monitoring
Navigation Data — Transmitted	leads to	No Evaluation / — Audit

---

The Pitfalls: Common Mistakes in Success Evaluation

Measuring only the triple constraint — Schedule, budget, and scope compliance tell you whether the project was managed well. They tell you nothing about whether it delivered value. A project can hit all three constraints and still produce something nobody uses.

Confusing PM success with project success — The project manager's criteria and the client's criteria overlap only on time and cost. Ignoring adoption, stakeholder impact, and operational viability produces a dangerously incomplete picture.

Evaluating too early — Meaningful success measurement requires operational data. Conducting the only evaluation at project closure — before the deliverable has been used in production — captures delivery performance but misses outcome performance entirely.

Ignoring failed projects — Some of the best lessons for future improvement come from evaluating projects that failed. Organisations that only review successes develop a systematically biased understanding of what works.

---

Key Takeaways

• Project success depends on the perspective from which it is viewed — PM, client, end user, and organisation may reach different conclusions about the same project
• Success criteria for the project manager emphasise delivery performance; success criteria for the client emphasise adoption and impact
• Four measurement tools — KPIs, baseline measurement, benchmarking, and post-implementation reviews — convert subjective judgement into evidence
• Project failure stems from both execution failures (poor management) and foundational failures (structural problems that exist before work begins)
• The Duck Alignment Theory provides a sequenced checklist of five preconditions that maximise success probability before resources are committed
• Catastrophic failures like the Mars Climate Orbiter emerge from chains of individually survivable errors, not single points of failure