Incident follow-through · Early research

Make the incident review lead to a verified improvement.

A planned post-incident review workspace that connects contributing factors, follow-up owners, and completion evidence. Join the waitlist to shape a focused pilot.

Get early access ↗

In research · Join the waitlist · No payment required

Designed around small engineering teams that resolve incidents but struggle to close the improvement work.

PRODUCT CONCEPT / 14
Concept preview · fictional example
ImprovementOwnerEvidence needed
Test backup restorePlatform teamRestore exercise result
Clarify runbookService ownerPeer walkthrough
Tune alert thresholdOn-call leadBefore and after review
Illustrative sample data. This is a product concept; these features are not available yet.
MADE FOR THE WORK IN BETWEEN↗
THE FRICTION

The incident is resolved and the review document is written. Weeks later, the preventive task has no clear owner or no evidence that the intended safeguard actually works.

THE PRODUCT WE’RE EXPLORING

AfterAction, in three parts.

AfterAction would keep reviewed observations next to a small set of improvement tasks. Closure would include what changed and how the team checked it.

Three planned capabilities we want to validate with early users.

01 / PLANNED

Separate facts from interpretations

Planned review sections would distinguish observed events, contributing factors, and questions that remain open.

02 / PLANNED

Define a testable follow-up

Proposed action records would name an owner, a target date, and what evidence would show the work is complete.

03 / PLANNED

Preserve closure evidence

Planned completion notes would link to the change, exercise, or review that verifies the intended improvement.

AN INTENDED WORKFLOW

A clearer next step.
Less work around it.

A focused approach for small engineering teams that resolve incidents but struggle to close the improvement work.

  1. 01

    Review the incident record

    A pilot would use an approved summary and selected evidence links after the immediate response is over.

  2. 02

    Choose specific improvements

    Turn observations into a small number of owned actions with clear verification criteria.

  3. 03

    Close and revisit

    Attach evidence when an action is complete, and flag work that needs another check later.

GOOD TO KNOW

A few useful answers.

Is incident analysis available today?

No. AfterAction is a research waitlist. There is no incident import, generated analysis, task sync, or review workspace yet.

Will it identify a definitive root cause?

That is not promised. The proposed workflow would support human review of evidence, multiple contributing factors, and remaining uncertainty.

Will it replace our incident platform?

The intended scope is post-incident follow-through. Paging, live response, and status-page communication would remain in your current tools.