Bottom line
Review a launched decision against the expectations recorded before execution, not against a story invented after the results arrived. Examine outcomes, delivery, and assumptions separately. Then make an explicit choice to continue, adjust, pause, or stop, with a named owner for the next step.
Bring the original record to the review.
Start with the decision, options considered, evidence available, success criteria, and known uncertainties. Ask whether the team executed the approved scope or something materially different. A result cannot fairly test a recommendation if the implementation changed its essential conditions. Record deviations without assuming that every deviation was a mistake.
Compare like with like.
Use the baseline, timeframe, and metric definitions agreed before launch. Check whether changes in customer mix, seasonality, or workload affect the comparison. In a hypothetical campaign review, more leads do not necessarily mean more qualified opportunities. Explain missing data and measurement limitations instead of replacing an uncertain result with a confident narrative.
Separate decision quality from luck.
A careful decision can produce a poor outcome, and a weakly supported decision can occasionally succeed. Ask whether the process used the evidence reasonably available at the time, considered credible alternatives, and respected constraints. Evaluate the observed result too, but avoid treating it as the only measure of how well the team decided.
More on Execution Intelligence — every week.
Join 2,400+ leaders getting the decision intelligence briefing.
Revisit the important assumptions.
Identify which claims held up, which failed, and which remain unresolved. Look for the assumption that most affected the outcome rather than cataloging every minor surprise. If customer demand was weaker than expected, ask whether the segment, problem, or offer was misunderstood. Do not use AI to generate a convenient explanation without checking it against actual evidence.
Choose a response proportionate to the evidence.
Continue when the conditions still hold; adjust when a specific problem has a credible remedy; pause when exposure exceeds the agreed boundaries; stop when the core rationale no longer applies. If more testing is necessary, define the question and deadline. An open-ended request for “more data” can delay an uncomfortable but necessary decision.
Write a short learning note.
Capture the original expectation, observed outcome, updated belief, chosen response, and next review trigger. Share it with the people making related decisions. Keep both the initial record and the new review so readers can see what changed. The purpose is accountable learning, not retrospective perfection or a document that makes every participant appear right.
Research context
PMI's 2024 research reports an average project success rate of 73.8%, leaving substantial room for better execution systems.
Project Management Institute: Pulse of the Profession 2024 (2024)This independently published statistic provides context for the topic; it does not substantiate every claim in this essay.
More on Execution Intelligence, weekly.
One essay. Every week. No noise.