Evergreen
How to Turn an Annual Reflection Into a Decision Record
Preserve a year's evidence, surprises, decisions, stopped work, experiments, and open questions in a record you can test next year.
How to Turn an Annual Reflection Into a Decision Record
An annual reflection becomes useful when it preserves what happened, what evidence supports the story, which decisions changed, what stopped, and what the next year can test.
A motivational recap can feel true while quietly rewriting the past. A decision record gives the future reviewer something to challenge.
Freeze the time boundary
State the period, the date of the review, and the records available. Separate facts known during the year from facts learned later.
Venture Step E051 is a useful example. The episode records plans and beliefs from January 2025. It does not prove what later happened. A current article should not convert “I plan to move,” “I will launch,” or “I want twelve guests” into completed history.
flowchart LR
A["Dated evidence"] --> B["Expected and observed"]
B --> C["Surprise and explanation"]
C --> D["Decision"]
D --> E["Experiment or stopped work"]
E --> F["Review trigger"]
Build the evidence ledger
For each important area, link to the direct record where possible. That may be a published artifact, calendar, financial record, version history, training log, customer record, meeting decision, or private note.
Mark the source, date, owner, freshness, and access boundary. Do not copy sensitive personal or third-party information into a public reflection merely because it supports the story.
Stanford’s lateral-reading guidance is useful when the reflection relies on public claims. Leave the source and investigate how independent sources characterize it.
Compare expectation with observation
Write what you expected, what occurred, and the gap. Avoid converting the result into a character judgment.
If a project missed its target, the explanation may involve an incorrect demand assumption, weak distribution, constrained capacity, a delayed dependency, a changed priority, or a decision to stop. Preserve the uncertainty.
For a habit or goal, implementation-intention research can inform how cues and actions were designed. It cannot establish that the goal was valuable or that one missed cue caused the outcome.
Record the surprise
The most useful annual insight is often the belief that changed.
State the prior belief, new evidence, revised belief, confidence, and remaining question. If the belief did not change, state what evidence would have changed it.
A truth-seeking review group can challenge the explanation, but the decision owner should preserve dissent rather than editing the record into agreement.
Name the decision
A lesson without a decision is easy to admire and forget.
Record whether to continue, stop, reduce, increase, delegate, redesign, investigate, or defer. Name the owner, date, first action, expected evidence, cost boundary, and next review.
Gary Klein’s premortem can strengthen a new commitment. Imagine that it failed and convert plausible causes into safeguards, warnings, or stop conditions.
Preserve stopped work
Stopped work is part of the record, not an embarrassing omission.
Explain what ended, why, which commitments remain, what was learned, what can be reused, and whether reentry is possible. Research on goal disengagement and reengagement supports treating adaptation as part of self-regulation when goals become unattainable.
Do not use that research to justify any specific exit. Financial, legal, health, safety, relationship, and career decisions may require qualified support.
Create next year’s test
Finish with a small number of decisions that can be audited. For each, state the hypothesis, action, signal, review date, warning, and stop condition.
The next annual review should be able to locate the original expectation without relying on memory. It should also be able to say that the context changed and the decision was reasonably revised.
Separate private and public versions
The private record can contain sensitive detail needed for honest review. The public reflection should publish only what is necessary, authorized, and fair to other people.
Current location, relationships, health, finances, employment, and venture status should be confirmed independently. Historical plans should remain historical.
Preserve uncertainty
Do not force every event into a clean lesson. Some outcomes have several plausible causes, and some evidence will remain unavailable.
Record what is known, inferred, disputed, and unknown. Give the inference a confidence level and name the next source that could strengthen or weaken it. This keeps a polished narrative from becoming false certainty.
If a later source corrects the record, add a dated amendment. Preserve the earlier decision and the evidence available at that time. The purpose is not to prove that every choice was right. It is to make the reasoning inspectable.
An annual record should also note where measurement changed. A higher count may reflect a new definition, tool, or capture process rather than real improvement.
About this guide
This guide was developed from Venture Step E051 and cited research with AI assistance. It is an editorial framework, not medical, mental-health, legal, financial, relationship, employment, or career advice. Personal and third-party disclosures require separate approval.
Sources
Follow the evidence.
- hbr.org: performing a project premortemhbr.org
- youtu.be: QS6ZcBzr9j8youtu.be
- daltonanderson.net: level up in 2025 systems truth and venture buildingdaltonanderson.net
- NIST AI Risk Management Frameworknist.gov
- open.spotify.com: 6Vh2HutKSA0UOK1XQTwWllopen.spotify.com
- cor.stanford.edu: teaching lateral readingcor.stanford.edu
- doi.org: S15327965PLI1104 01doi.org
- journals.sagepub.com: 2666999journals.sagepub.com
- doi.org: S0065 2601(06)38002 1doi.org
- doi.org: 0146167203256921doi.org
- pubmed.ncbi.nlm.nih.gov: 15574664pubmed.ncbi.nlm.nih.gov
- daltonanderson.ghost.io: level up in 2025 systems truth and venture buildingdaltonanderson.ghost.io