All use cases
Optimize

Find where work waits in your delivery pipeline, from data you already have.

Process mining that turns your existing event logs into BPMN diagrams + bottleneck heatmaps in hours.

Enterprise process-mining suites such as Celonis are sold through sales and built for company-wide processes. For a software-delivery team, the diagnostic value of process mining (finding where lead time is actually spent) doesn't need enterprise BI: Stride mines your Stride activity, or any event log you can export as CSV or XES, into process maps and bottleneck heatmaps.

Why don't delivery dashboards show where the time goes?

Engineering leaders sense their teams are slow but can't pinpoint where the time goes. Dashboards show velocity, throughput, and cycle time, but not the wait between stages. The bottleneck is usually a specific step (code review, QA scheduling, design handoff) and dashboards don't surface which. Process mining is the right diagnostic, but an enterprise process-mining suite is a large purchase for one team's delivery pipeline.

Can Stride mine BPMN diagrams from the event logs you already have?

Stride's Optimize module mines event logs: your Stride story history (status changes, plus pull-request link, merge and close events from GitHub or GitLab) or a CSV or XES log you upload. An uploaded log becomes a process model you can open as a BPMN diagram, and a discovered map shows every path work actually took. A heatmap colours each step by how long work sits there before moving on, so the slowest steps stand out.

  • BPMN process models mined from uploaded CSV or XES event logs (no manual modelling)
  • Variant analysis: what % of cases follow the dominant path vs deviations
  • Bottleneck heatmap: each step coloured by measured time before work moves on (red = slowest)
  • Bottleneck and automation-opportunity insights with an estimated yearly cost, which you can turn into a story or an automation item
  • Process simulation: what-if scenarios for proposed interventions
  • Date-range filter for any period, plus an alert when median cycle time rises 20% against the previous 30 days
Best for

Engineering organisations (50+ people) where leadership wants to find specific bottlenecks worth fixing, not just track aggregate metrics.

Not for

Highly regulated industries needing auditable process compliance evidence (Fortune-100 finance, healthcare). Celonis is the right tool there. Also not the right fit if your process has zero variance. Process mining is for cases with deviations to analyse.

Frequently asked

What event log format works?
A CSV or XES file (XES is the IEEE 1849 event-log standard) with a case ID, an activity and a timestamp for each event; other columns, such as resource, are ignored for now. Stride's own story history feeds in with no setup: status changes, plus pull-request link, merge and close events if GitHub or GitLab is connected. Jira transition history isn't imported; to mine it, export it as a CSV event log with case, activity and timestamp columns.
Can I mine non-engineering processes (HR onboarding, customer support)?
Yes, if you can produce the event log. Anything with case-level state transitions in a database is mineable. Stride's primary use case is software delivery, but the underlying BPMN engine is generic.
How are bottlenecks found?
Bottlenecks are flagged by rules, not AI: a step is flagged when its 95th-percentile time is at least twice the process's typical step time across at least 10 visits, with an estimated yearly cost. Your team decides the fix and can turn the insight into a story or automation item. Separately, Redesign with AI in the Process Designer proposes a restructured model you can compare and simulate.
How long to first useful diagram?
Upload a CSV or XES log and Stride mines it into a process model in a background job, so the first diagram needs little more than the upload. Your Stride history needs no upload at all, but it covers only work tracked in Stride, the last 90 days by default.
Defined in our glossary