Blast radius

What this feature is for

Blast radius connects dependencies to journeys and customer-facing capabilities so an operator can prioritize response by impact. The important distinction is that PreFlight stores the observation alongside the app, release, provider, or customer path it belongs to. That context is what turns a signal into an operational decision.

Before you open it

A dependency map, defined journeys, and enough product context to name the affected capability.

Use a real app in the workspace and start with the smallest useful scope. A narrow, representative check gives you a stronger baseline than connecting every environment and every provider at once.

Run the workflow

Select the degraded provider or service, inspect the impacted nodes, prioritize the customer path, and attach the response to the incident.

1. Open the feature from the dashboard outcome hub.
2. Choose the app and environment that match the decision you are making.
3. Run or save the configuration, then wait for the evidence state to settle.
4. Assign the next action to an owner before leaving the page.

Read the evidence

The view should identify the dependency, impacted journey, severity, and assumptions behind the relationship. A green state means the configured assertion passed at the recorded time. It does not claim that every unconfigured path is healthy. A warning is a useful lead; a failure should have a concrete owner and a verification run.

When the result is not healthy

An incomplete map understates risk. Mark unknown relationships and improve the dependency model rather than assuming they are unaffected.

Do not erase the failed result after fixing the underlying system. Keep the history, rerun the check, and link the new passing evidence to the deployment or incident that caused the change. This gives the team a useful before-and-after record.

Use it with the rest of PreFlight

Use Blast radius with Vendor outages, User journeys, and Incidents & fixes. Outcome hubs are deliberately connected: Audit finds risk, Deploy decides whether to promote, Health watches the running system, Revenue verifies the money path, Growth manages discoverability, and Trust publishes safe proof. Use the related links below to move between those decisions without losing context.