Project Premortem for Solo Builders
Updated
Knowledge on this page was mainly distilled from Act Like It’s Impossible to Fail.
A premortem is a simple planning exercise: assume the project failed, then list the most plausible reasons before reality has to teach them to you. For solo builders, it is useful because it surfaces avoidable risks early without requiring weeks of planning.
The goal is not to predict every problem. The goal is to turn vague anxiety into specific checks, constraints, and kill criteria that make the next iteration safer and faster.
Basic premortem prompts
- Assume failure: If this project failed in 90 days, what most likely caused it?
- Name preventable risks: Which causes can be reduced now with a smaller scope, clearer metric, or earlier test?
- Set decision rules: What result would make you continue, pivot, pause, or stop?
Q&A
What is a premortem?
A premortem is a planning exercise where you assume a project has already failed and then work backward to identify the most likely causes. The point is to surface risks before the work becomes emotionally expensive to question. It is commonly used as a guardrail against overconfidence, especially when teams or founders are excited about an idea.
How is a premortem different from a postmortem?
A premortem happens before the work ships, while a postmortem happens after something goes wrong or ends. A postmortem explains what happened; a premortem tries to prevent predictable mistakes before they happen. Used together, they improve both planning and learning.
When should a solo builder run a premortem?
A solo builder should run a premortem before committing serious time, money, or reputation to a project. It is especially useful right before a build phase, launch, pricing change, or channel bet. If the cost of being wrong is rising, it is a good time to do one.
Can a premortem make you too pessimistic?
Yes, it can if you use it as a reason not to test anything at all. The healthy use is to reduce obvious failure modes while preserving motion, not to design a perfect plan. If your premortem creates more delay than clarity, the exercise is being overused.
What questions should a good premortem include?
A good premortem asks what failed, why it failed, which causes were knowable in advance, and what evidence would have warned you earlier. It should also ask what metric would prove traction is absent and what constraint keeps the test small. Those questions turn fear into decisions instead of rumination.
What should you do with the list after the premortem?
You should convert the list into concrete changes such as a smaller scope, a faster metric, a user interview, a pricing test, or a stop rule. The output should be a short action list, not a long document. If nothing changes after the exercise, the premortem was mostly theater.