Would you make the same decision?
Six weeks ago, three paying customers was the goal. Now there are two.
Fictional example · not George's experience
- Original target
- 3 customers
- Six-week result
- 2 paid
One onboarding incomplete. $5,500 of $6,000 spent. Integration late.
Was the integration delay the reason?
The delay happened, but these records do not prove it caused the missing customer. The original goal, three paying customers who complete onboarding, was not met.
A two-week extension capped at $1,000 is one possible next experiment. The team keeps the original result and stops the extension if no additional customer completes onboarding. Continuing is a new decision, not a rewrite of the old one.
The full example and its assumptions
On January 1, a team records a six-week pilot with a $6,000 budget. Its acceptance criterion is three paying customers who complete onboarding. At review, records show two paid customers, one incomplete onboarding, $5,500 spent and a late integration.
The team marks the acceptance criterion unmet. It observes the integration delay but cannot prove that delay caused the missing customer. It chooses a two-week extension capped at $1,000 to test onboarding, with a stop condition if no additional customer completes it. The original criterion remains in the record instead of being rewritten to call the pilot a success.
Illustration only, not a business forecast or a recommendation for your finances.
Try this next
Find the original note before writing the review. Put the expected result beside what happened, then decide what another week or dollar would help you learn.
Find the original note
Find the note, forecast or message from when you chose. What alternatives did you have? What did you expect? Which assumptions mattered? If the record cannot answer a question, leave it unknown rather than completing the story from memory.
Separate the outcome you wanted from the result you expected. A choice can be reasonable on the available evidence and still end badly. Conversely, a good outcome can conceal a process that depended on luck.
What actually happened?
Put the result beside the original expectation. Say where the result came from. Then write your explanation separately. If several things changed at once, the records may not tell you which one caused the outcome.
Ask which assumptions held, which failed and which were never tested. Include costs transferred to another person or delayed into the future. If the team is reviewing the decision together, let people record their observations before agreeing on a single story.
Decide what happens next
List what continuing, changing direction and stopping would each require. Use the evidence you have now and the obligations that remain. Time already spent explains the history; it does not by itself establish that more time is useful.
Choose a next step and a date or event that will reopen it. For a public essay, preserve legitimate earlier beliefs and add a dated follow-up explaining what changed. Correct factual errors visibly; a fabricated experience is not a past belief worth defending.
- The original note and expected result
- What happened, with causes kept separate
- The next choice and when to revisit it
Choose a next step
Decision worksheet
Pick one thing to do next. Keep a short plan without filling in a form.
Add detailed notes
Add notes only if they help. Answers stay in this page's memory and are never uploaded or saved automatically.
What did we know, expect and choose? What remains unknown?
What happened, and which records support that account?
Which assumption should we revise, and how confident are we?
Will we continue, pivot or stop? What would change that choice?
From George's writing
The Day I killed our product strategyOriginally published
George wrote about ending an earlier product strategy and choosing another direction. Read it for the reasons he recorded at the time. It does not isolate what caused later company results.
What this account does and does not show
What George reported
- The earlier strategy and the choice to change direction
- The author's explanation of that choice
Questions it leaves open
- A controlled before-and-after comparison
- An isolated causal explanation for later company results
This is a decision account, not measured proof that the strategy change caused a later outcome. Keep the original reasons, actual observations and retrospective interpretation separate in your own record.
Example-led guide · Updated
Work through the question
From the field
Personal accounts behind the questions. Each essay reflects when it was written.
I have stopped knowing what a productive day feels like
A personal account of producing more while finding it harder to know when the day’s work is enough.
Why this reading: Read this when more output stops being a useful measure of your working day. Record a task and its review burden in Work Changed.
The company is moving faster than I am
Vinci didn't exist 30 days ago. The company has already changed shape several times. I'm not sure I've processed any of it.
Why this reading: Use this account to ask which responsibilities have changed and which older expectations need to be reopened.
I am not afraid of failure. I am afraid of becoming irrelevant.
Failure feels survivable. The harder fear is spending an important period in history building something that doesn't matter - and not knowing whether that…
Why this reading: Read this as a personal account of uncertainty, then name the concrete decision behind your own concern.
Six Months After My Post-AI Manifesto - A Reflection
Six months ago I posted the Post-AI Manifesto - five layers to stay ahead of AI. Here's what happened to each one, and the single line that captures the…
Why this reading: Compare an earlier framework with the author's later account of it. Preserve what was known then instead of rewriting the original belief.