Flow Performance & Variant Explorer

Flow Performance takes the workflow your team actually runs and lays timing over it, so you can answer three questions at a glance: where does work wait the longest, how long does delivery really take, and which routes does work follow from start to finish?

It shares its map with Workflow Discovery — but the two answer different questions:

• Workflow Discovery is the structure view: what your workflow looks like and where you set up how statuses and people are grouped.
• Flow Performance is the performance view: where that workflow is slow and which routes work takes.

If the map looks sparse or mislabeled, set things up in Workflow Discovery first — Flow Performance reads the same workflow.

Drawing the map

Pick a site and project, optionally narrow to an issue type and a time range, then press Mine. The map is built from your real ticket history for that window.

How to read it

The map. Each step is a state your work passes through; each arrow is a hand-off between two states. Arrows are shaded green → red by how long work typically waits before that hand-off — so the slowest parts of your process stand out immediately, and the busiest routes are the boldest.

The header. Two delivery-time figures for the project:

• Median (typical) cycle time — half your completed work finishes faster than this.
• Slow-tail cycle time (85th percentile) — most work finishes within this; it captures the slow cases the median hides.

Watching both together tells you whether your process is consistently quick or usually quick with a painful tail.

Where work waits. A side panel lists your statuses ordered by how long work sits in each — a fast read on the single biggest queues, with both a typical and a worst-case figure per status.

The Variant Explorer

Real work rarely follows one tidy path. The Flow variants panel lists the distinct end-to-end routes work actually takes — same states, same order counts as the same route — ranked by how many issues followed each, with the share of all completed work. Routes that loop back (rework) or skip steps show up as their own variants.

Click a variant to light up that exact route on the map and dim everything else, so you can trace it step by step and see where that particular path loses time.

Replaying an earlier point in time

The As of date slider replays the map as it looked on an earlier date. Drag it back and release to redraw the workflow for the window ending then — useful for "did this bottleneck exist last quarter?" The header and panels stay all-time for a stable baseline to compare against.

Ask the AI

Three one-click insight cards summarize the map — Where work waits, Slowest routes, and a plain-language Flow summary — and the Ask Flow box answers free-form questions like "which route is slowest?" or "where do issues pile up?" in plain business language.

Tips

• Start wide, then narrow. Mine all issue types first for the overall picture, then scope to one type (e.g. just Bug) for a leaner map.
• Use the filter threshold to hide one-off paths and keep the map readable; lower it to surface edge cases.
• Pair it with Workflow Discovery. If statuses are showing up as "unknown" or the lanes look wrong, fix the groupings there — Flow Performance will read cleaner immediately.