What happened?
Describe the completed and missed actions without turning the count into a judgment about identity or character.
Use case: week-end review
A review is not a score for the person. It is a structured comparison between the method you selected and the week that actually happened.
State what happened, name the situation that helped or blocked the action, compare the result with the signal chosen at the start, and decide whether the next cycle should continue, reduce, switch, or replace the method.
Four review questions
Describe the completed and missed actions without turning the count into a judgment about identity or character.
Name the cue, time, setting, effort, or competing demand that changed whether the action happened.
Compare the observable result with what you decided to watch before the cycle started.
Continue, reduce, switch, or replace the method. Choose one direction rather than writing a new catalogue of advice.
Product rules
| Rule | What it prevents |
|---|---|
| Review is available even when not all seven days are complete | Turning imperfect execution into a reason to discard the evidence |
| Status is recorded before the written review | Replacing the day's observable record with a retrospective story |
| One paragraph, not audio or video | Creating unnecessary proof burdens or media collection |
| The dossier updates after review | Losing the useful context when the next weekly plan is generated |
Important boundary
Customer-reported completion and reflection can guide the next experiment. They are not independently verified outcomes, clinical measurements, or guarantees that a habit has formed.
Close the loop
The introductory cycle includes the day-seven review and next-cycle decision framework for an eligible account.
Start the free cycle