> For the complete documentation index, see [llms.txt](https://www.designreference.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.designreference.xyz/cognitive-tools/universal/decision-making/pre-mortem.md).
# Pre-Mortem
The Pre-Mortem is a foresight strategy, typically employed in planning phases for projects in software design, product development, and other fields, designed to anticipate and neutralise potential failures before the work even begins.
Unlike a post-mortem, which is a retrospective analysis performed after a project has already failed, the pre-mortem proactively leverages "prospective hindsight" to enhance decision-making and reduce overconfidence.
The technique operates by assembling the project team, key stakeholders, and relevant subject matter experts and asking them to engage in a mental exercise, imagining that the project, product launch, or design initiative has failed spectacularly in the future, often six or twelve months out. This shared vision of failure is crucial, creating a safe space for dissent and encouraging individuals to identify potential causes of the disaster that they might otherwise be reluctant to mention.
Participants are then asked to individually and privately generate a list of all plausible reasons, technical, organisational, market-related, or otherwise, that could have led to this failure.
The collected reasons for the hypothetical failure are then discussed openly, grouped by themes, and prioritised based on their likelihood and potential impact. Following this brainstorming and prioritisation, the final step involves integrating these findings back into the current project plan.
This translates the identified risks into concrete mitigation strategies and contingency plans, with assigned ownership and deadlines, effectively strengthening the overall design and development approach before the first line of code is written or the first feature is finalised.
#### Further Viewing
{% embed url="" %}
#### Further Reading
{% embed url="" %}
{% embed url="" %}
{% embed url="" %}
{% embed url="" %}
{% embed url="" %}
{% embed url="" %}
{% embed url="" %}
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://www.designreference.xyz/cognitive-tools/universal/decision-making/pre-mortem.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
