Start here
Overview
Measure business outcomes, not tool usage. This guide lists KPI families that resist gaming and align teams.
Core concept
Definition
Automation KPIs include cycle time, first-pass yield, exception rate, cost per transaction, revenue per unit of labor, and customer effort score—chosen per workflow.
Business impact
Why it matters
Wrong metrics fund theater. Right metrics fund expansion and continuous improvement.
Practical model
Framework
Leading vs lagging
Queue age leads revenue; both matter.
Segmentation
By channel, region, product—aggregates lie.
Implementation detail
Detailed breakdown
Control charts
Detect regressions after releases—not only annual reviews.
In practice
Real-world example
A support org tracked first-contact resolution and reopen rate—catching automation regressions within days.
Avoid these
Common mistakes
- Dashboards nobody acts on.
- Incentives that encourage bad data entry.
Engineering layer
Technical patterns
Before/after cohort
- Compare same segment pre/post with seasonality adjustment.
- Attribute savings to automation ID via tagged workflows.
Build patterns
Code examples
Cycle time from events
Uses event log, not status field alone.
export function cycleTimeMs(events, startType, endType) {
const s = events.find((e) => e.type === startType)?.ts;
const e = events.find((x) => x.type === endType)?.ts;
return e && s ? e - s : null;
}System view
System architecture
[Workflow event stream]
→ [Warehouse transforms]
→ [KPI definitions as SQL/views]
→ [Executive dashboard]
→ [Continuous improvement loop]Keep learning
Related topics
Next step
PrimeAxiom defines KPI suites tied to your workflows—book a metrics design session.