# Incident templates written before the outage

> Prewrite incident templates for common failure modes so the first update is clear, fast, and consistent when the team is under pressure.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/incident-templates-written-before-the-outage/
- Source: [support.atlassian.com](https://support.atlassian.com/statuspage/docs/create-an-incident-template/)
- GrowthDex source hub: [Atlassian Statuspage Docs: Create an incident template](/sources/atlassian-statuspage-docs-create-an-incident-template-support-atlassian-/)
- Last checked: 2026-05-29
- Rarity: uncommon
- Budget: free
- Channels: Support, Lifecycle, Operations
- Stages: incident response, ops hygiene, trust, support load


## Why this can grow

Bad incident copy wastes the most valuable minutes of an outage. Teams scramble for wording, skip the practical next step, or publish an update that sounds evasive because nobody had the language ready. Statuspage supports incident templates for the recurring problems a product expects to face. That turns the first message into an operational asset instead of improvised copy. The gain is speed, but the bigger gain is clarity. Customers get a recognisable structure, teams stop rewriting the same explanations from scratch, and support can mirror the same language everywhere else.

## Ian's take

From scaling consumer platforms across MENA and Southeast Asia, my default is to distrust growth work that only looks good in a slide. My bias is to treat this as a small market test first. Make the audience narrow, make the promise concrete, and let the first real response decide whether it deserves more work. I would run it small enough to learn quickly, then only scale the parts that real users repeat, save, reply to, or buy from. For this tactic, I would watch one clear growth signal before putting more time or budget behind it.

## Action plan

1. Define one narrow startup segment where incident templates written before the outage can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Support and Lifecycle channel.
3. Use the evidence from support.atlassian.com to set the first version of the message, format, and audience.
4. Launch a small test for 7 to 14 days with one success metric: one measurable growth signal.
5. Review the result, keep the winning message, remove weak variants, and turn the learning into a repeatable growth playbook.

## Source-backed example

Statuspage supports incident templates so teams can prepare updates for common issues in advance and use them when an incident starts.

## Adjacent tactics in the same lane

- [Priority required before triage exit](/growth-ideas/priority-required-before-triage-exit/) - 2 shared channels, 1 shared stage
- [Drain-and-fill cutover before final support history batch](/growth-ideas/drain-and-fill-cutover-before-final-support-history-batch/) - 3 shared channels
- [Triage responsibility rotation linked to on-call schedules](/growth-ideas/triage-responsibility-rotation-linked-to-on-call-schedules/) - 2 shared channels, 1 shared stage
- [Template default properties for cleaner cross-channel intake](/growth-ideas/template-default-properties-for-cleaner-cross-channel-intake/) - 2 shared channels, 1 shared stage

## Read GrowthDex essays

Browse the plain-English essay index at [GrowthDex Blog](/blog/).

## Related GrowthDex essays

- [The status page should answer before the ticket does](/blog/the-status-page-should-answer-before-the-ticket-does/) - brand trust, incident communication, support deflection

## Advisory

If you want help turning this into a working growth system, Ian Goh offers advisory at https://iangoh.com/advisory.