Explain a failed pilot without hiding the original assumptions

A pilot can succeed as an experiment while failing its delivery gate, but that distinction must not be used to rewrite the original objective. Leaders need to see what was assumed, what was observed and why the decision changed.

Build the decision artifact

Reproduce the original charter and thresholds. Compare each material assumption with observed evidence. Separate execution errors, environmental constraints and invalid hypotheses. State costs, residual value, reusable artifacts and the recommended stop, redesign or continuation. Keep causal language at the system level.

The commercial leadership lab makes the artifact inspectable with authored inputs:

from leadership_cases import failed_pilot_case

result = failed_pilot_case()
assert result["failed"] == ["representative scans", "source permission"]
assert result["decision"].startswith("stop")
assert result["blame"] is None
assert result["success_relabelled"] is False

Only 61% of scans are readable against a 90% assumption, and source permission does not arrive. Reviewer capacity holds. The fixture stops, preserves extraction tests and assigns no blame. It does not relabel the outcome after seeing it.

Protect the decision from weak evidence

Avoid a celebratory lessons-learned story that omits the failed business gate. Also avoid treating one pilot as proof that the whole problem category is impossible. Bound conclusions to the tested workflow, data and access conditions.

Keep these artifacts for review:

• original charter and immutable thresholds
• assumption-versus-observation table
• causal analysis and limitations
• stop/change/continue record plus reusable assets

This practice aligns with the discovery, productisation, client enablement, technical leadership and capstone sequence in the FDE for Professionals course. The course link describes the pathway; the local scenario is fictional and does not claim a client engagement, investment result, hiring decision or certificate.

Practice task

Write a two-page failure memo using an unchanged original gate. Give the sponsor enough evidence to disagree with your recommendation constructively.

Continue learning

This article is part of the Commercial judgement and delivery leadership sequence. Use the neighbouring tasks when you need the prerequisite or the next application.

• Review the prerequisite or neighbouring task in Present an AI investment recommendation with uncertainty.
• Continue with Build a delivery risk register with accountable owners.

Reference: Google SRE Workbook: Postmortem Culture.