Product workflow3 min readKeep one real product question in mind as you read.
A useful way through

Start with one real question and leave with a next step.

Start with the question in front of you, then use the guide to make the next decision easier.

Try saying

“I am trying to make this decision. What should I look at first?”

Start with context

Bring the smallest useful example.

Look for the signal

Separate what is known from what is assumed.

Take one step

Choose an action you can review.

Risk Radar

Score delivery risk · 25 s video guideRead the transcript

What it does

Risk Radar scores delivery risk from a ticket export. Upload a CSV from Jira, Linear or a spreadsheet, and you get a risk score from 0 to 100 for each initiative, an overall score for the whole set, and patterns that repeat across initiatives, such as late delivery or scope creep.

Scoring follows fixed rules, so the same file always gives the same scores. The AI only writes the optional executive summary.

In ⌘K and the top bar the view is called Risks. The sidebar lists it as Risk radar under Measure, and the page heading reads Roadmap Risk Radar. If your plan does not include it, a lock shows next to it.

What goes in the file

  • Required: Issue Key, Summary, Status
  • Recommended: Story Points, Assignee, Sprint, Parent, Due Date, Created, Resolved
  • Optional: Labels, Linked Issues

Jira CSV exports work as they are. Epics become initiatives and tickets join their parent. If the file has no epics, each sprint becomes an initiative. Click Download Template for a ready-made file.

How the score works

Each initiative is scored on six weighted factors: Scope Volatility, Estimation Drift, Dependency Density, Historical Slip Pattern, Workload Saturation and Long-Tail Issues. If work is running past its latest due date, a Schedule Delay factor sets a minimum score. Under 40 is low risk, 40 to 69 medium, 70 and above high. Each factor comes with a one-line reason, such as how many tickets are overdue.

How to use it

  1. Open Risk radar from the sidebar. If it is not there, turn it on in Settings → Sidebar Views or search for Risks with ⌘K.
  2. Drop your CSV on the upload area, or click Try with sample data to see how it works first. Sample data is made up and never saved.
  3. Read the top strip: Overall Risk, At Risk, On Track and Total, plus any Systemic Risks.
  4. Sort the table by Risk Score or Confidence, and click an initiative to see its Risk Breakdown and Ticket Status.
  5. Click Exec Summary for a one-page summary written by the AI, and copy it.
  6. Real uploads are saved to your workspace, so the result is still there next time. Click New Upload to clear it and start over.

Example

You upload a Jira export with three epics. "Checkout redesign" scores 74, high risk: most of its tickets with due dates are overdue or finished late, and one person has five tickets in progress at once. "API v2" scores 35, low risk. Systemic Risks is empty, so the problem is local, and you rebalance the checkout work before the next sprint.

Ready to apply this?

Start with your own product and keep the first read grounded. You'll create an account before the guided result so it can be saved to your workspace.

Try the guided start