Review a failed week without inventing a story

The short answer

First preserve what happened without explanation. Compare the intended result, actual result and completed inputs; mark missing evidence explicitly. Then generate several plausible causes, choose the cheapest test that separates them and rebuild the next week around one protected action rather than cramming every missed task back in.

Key takeaways

• A disappointing result does not identify its own cause.
• Missing data should lower confidence, not become a zero.
• Do not punish a failed week with an impossible recovery plan.
• Change the next test before changing the entire direction.

Why failure produces confident explanations

When a week misses its goals, the mind quickly creates coherence: there was not enough time, the market was weak, motivation failed or other people blocked progress. The explanation may be true, but the emotional need for a reason arrives before the evidence.

A useful review delays causality. It treats the result, the execution record and the explanation as separate objects. This protects the next plan from overreaction and from repeating a comfortable story.

Build a neutral record

1. Intended result Write the original target and definition of done without revising it.
2. Actual result Record the observable outcome, including partial movement.
3. Planned inputs List the controllable actions and timing the strategy required.
4. Actual inputs Record completion, quality and timing. Separate unrecorded from not completed.
5. Changed context Name only events that materially altered capacity, information or dependencies.

Generate competing explanations

Use at least three classes. Execution: the intended inputs were not completed or were late. Capacity: the plan required more time, energy or skill than available. Strategy: the completed inputs did not create the expected conversion. Information: measurement cannot distinguish what happened. Dependency: an external actor or event prevented the next state.

Ask what evidence would be expected if each explanation were true. If execution is the cause, completion and timing should be weak. If strategy is the cause, inputs should be present while the next conversion remains weak. If information is the cause, the first useful action is better observation rather than more volume.

Choose the smallest recovery decision

1. Continue Use when execution was incomplete but the strategy remains plausible and the opportunity still matters.
2. Change Use when completed inputs provide enough evidence that the mechanism or sequence is weak.
3. Stop Use when expected value has fallen, downside increased or the goal no longer serves current direction.
4. Test Use when competing explanations remain and a short action can distinguish them.

Do not create a punishment plan

Rolling every missed action into the next week increases load without increasing capacity. It also gives old commitments automatic priority over new information. Re-rank each item against the current goal and constraint.

Protect one recovery action early in the week. Reduce maintenance, renegotiate a commitment or remove a lower-ranked outcome to make the plan physically possible. A credible week is more valuable than an ambitious plan that fails for the same reason.

Separate accountability from self-punishment

Accountability means preserving the original commitment, naming the actual result and changing the system in response. Self-punishment adds shame, unrealistic volume or longer hours without improving the mechanism. It can feel serious while making the next failure more likely.

Use language that is specific enough to act on. Replace “I lacked discipline” with the observed sequence: the decisive block was scheduled after four meetings, started ninety minutes late and was replaced by reactive client work. The first statement is an identity judgment; the second reveals choices and constraints.

Compassion and rigor are compatible. Context can explain why a plan failed without declaring the outcome acceptable or inevitable. The purpose of the review is to make the next commitment more truthful and more likely to matter.

Record what would change your mind

Before the next attempt, write the expected signal and decision threshold. If the action is completed and the expected conversion still does not appear, change the strategy. If the action is again displaced, solve the capacity or attention system instead of re-litigating the market.

Over several weeks, compare explanations with outcomes. If “not enough time” repeatedly appears while lower-ranked work fills the calendar, the blind spot is not capacity alone; it is allocation or an avoidance pattern. Repetition turns a story into a testable system claim.

Questions

Should missed goals lower the next target?

Only after diagnosing whether the target, strategy or execution was unrealistic. Lowering it automatically can hide a solvable constraint.

How do I avoid being too harsh or too lenient?

Use the same evidence categories every week and judge the process separately from the outcome. Context matters, but it should be named explicitly.

What if the week failed because of an emergency?

Record the changed capacity, protect recovery and re-rank commitments. Do not pretend the original plan remained feasible.

When is one week enough to stop?

When downside is high, the evidence is decisive or a predefined kill criterion is met. Otherwise prefer a small reversible test.