Risk Radar

What it does

Risk Radar is an AI-powered risk analysis tool that proactively surfaces risks in your product plans before they become problems. It analyzes your PRDs, roadmap initiatives, and incoming signals to identify five categories of risk:

Technical risks — dependencies on unstable systems, known technical debt, or engineering complexity signals from GitHub and Jira

Scope risks — requirements that are vague, contradictory, or likely to expand based on historical patterns

Dependency risks — initiatives that depend on other teams, third-party services, or external timelines

Customer impact risks — changes that signals suggest will negatively affect active users

Capacity risks — initiatives that overlap with other high-effort work in the same time window

Each identified risk includes a severity rating (Critical / High / Medium / Low), a plain-language description of the risk, the evidence that triggered it, and a suggested mitigation.

When to use it

Before committing to a roadmap — run Risk Radar on your quarterly plan to catch conflicts and dependencies before they're locked in

During PRD review — identify scope and technical risks in a PRD before it goes to engineering

When a major incident occurs — assess which other areas of the product are at risk based on the same root cause

Before a launch — check for last-minute risks that emerged from recent signals

During sprint planning — flag capacity risks when too many high-effort items are scheduled in the same sprint

When onboarding a new initiative — understand the risk profile of a new feature area before investing heavily

How to use it

From a PRD:

Open any PRD in the PRD Editor

Click Risk Radar in the toolbar (or use Cmd+Shift+R)

Review the risk report in the right panel

For each risk: click Dismiss to ignore it, Add to Decision Log to record it, or View Evidence to see the signals that triggered it

From the Roadmap:

Open Roadmap from the sidebar

Click Run Risk Radar in the toolbar

Risk Radar analyzes all planned initiatives and surfaces cross-initiative risks (dependencies, capacity conflicts)

Risks are shown as warning badges on affected roadmap items

From the Risk Radar dashboard:

Open Risk Radar from the sidebar

View all active risks across your entire product plan

Filter by severity, category, or initiative

Use the Risk Matrix view to see risks plotted by likelihood and impact

Example

You're planning Q2 and have three major initiatives: a checkout redesign, an API v2, and a mobile app launch. You run Risk Radar on the roadmap and get:

Critical risk: API v2 depends on a third-party payment processor SDK that has had 3 outages in the last 60 days (evidence: 3 GitHub issues, 2 Slack threads from the engineering team).

High risk: Checkout redesign and mobile app launch both require the same design system components. Both are scheduled for the same 3-week window in May, creating a design team capacity conflict.

Medium risk: The checkout redesign PRD has 4 requirements marked as "TBD" — historically, TBD requirements expand scope by an average of 30% based on your team's past PRDs.

You address the critical risk by adding a fallback payment processor, resolve the capacity conflict by staggering the timelines, and schedule a PRD review to resolve the TBD requirements — all before a single line of code is written.