# Launch Premortem Risk Register

Canonical page: https://waitlist.crany.ai/marketing-templates/launch-premortem-risk-register

By Tangenix. Published 2026-10-24. Category: Launch planning.

Identify plausible launch failures before release, then assign prevention, observable warning signals and bounded response actions to named owners.

## Task

Prepare launch failure scenarios and response ownership before a go-or-hold review.

## When to use

Use this before a planned software launch when the team can still change a dependency, clarify an offer or prepare a response. Discuss plausible failure paths without pretending they are predictions.

## Choose another approach when

You need an active-incident procedure, want to score invented probabilities as measured risk, or plan to treat a completed workshop as proof the launch is safe.

## Inputs

- The actual release scope, acquisition routes and first user journey.
- Known dependencies, prior failures and relevant team observations.
- Owners with authority to review prevention and response actions within the approved scope.

## Template

    Launch scope / planning date: [version, audience and boundary]
    Failure scenario: [a plausible concrete outcome, not a vague fear]
    Why it could happen: [dependency or evidence; label speculation]
    Early signal: [observable event or check]
    Impact on the promised task: [what a user cannot do]
    Preventive action / owner / due date: [bounded work]
    Evidence that prevention worked: [specific check]
    If the signal appears: [authorized pause, fallback or escalation]
    Response owner / communication reviewer: [people and actual coverage]
    What must not be changed casually: [data, access or other protected state]
    Residual uncertainty: [what remains possible]
    Link to release decision: [separate go/hold record]
    Review trigger: [date or dependency change]
    Repeat for distinct failure paths. Do not average away an unresolved blocker with a low numerical score.

## Illustrative example

This is not a Crany customer result. Replace example details with verified facts.

    Fictional example: a founder imagines that launch visitors request access but the invitation journey fails. The concern is grounded in an earlier expired-link defect, not an invented probability.
    A fresh approved-account journey becomes the preventive check, with an owner and a deadline before announcements. If that check fails, the response is to hold further acquisition messages and investigate; it is not to delete waiting applicants or weaken sign-in protection.
    The register also records that an external service may still fail after the check. Passing a rehearsal reduces one uncertainty and informs the separate release decision. It does not guarantee uninterrupted launch access.

## How to use

1. Describe several concrete ways the promised launch experience could fail.
2. Connect each scenario to evidence, a warning signal and a bounded preventive action.
3. Assign response ownership and revisit unresolved risks before the separate release decision.

## Checks

- Scenarios are labeled possibilities rather than reported incidents or measured forecasts.
- Actions have owners, review points and evidence of completion.
- A fallback does not assume permission to remove data, alter access or bypass security.

## What to measure

Track actions actually completed, signals observed and scenarios that need revision. Compare the register with later launch experience to improve planning. A short premortem cannot quantify every risk or certify reliability.

## Research and sources

Atlassian’s premortem play connects potential risks to assigned actions and later review. This launch-specific register is original, with no claim that its scenarios or scoring have been statistically validated.

- [Atlassian Team Playbook: Pre-mortem](https://www.atlassian.com/team-playbook/plays/pre-mortem) — checked 2026-10-24. Potential project risks, assigned mitigation actions and later review. No numeric risk-reduction claim adopted.

Prepared with AI assistance. Sources support the stated principles; they do not endorse Crany or guarantee performance.

## About Crany

Crany is an AI marketing co-founder in development for software founders and vibe coders. It is designed to strategize, execute approved marketing and improve based on results. These free resources are usable independently of app access. The public waitlist is at https://waitlist.crany.ai/.