Operations teams keep everyday work moving, from processing requests to delivering orders and resolving bottlenecks. The right KPIs help you see whether that work is getting faster, more reliable and easier to deliver without sacrificing quality.
These ten metrics give you a practical starting point. Choose the measures that match your workflow, agree on how each one is calculated, and establish a baseline before setting targets.
Benefits of using Operations metrics and KPIs
A useful operations dashboard connects delivery speed with quality and cost. Looking at those measures together helps you spot improvements that would be missed by tracking activity alone.
- Find queues and bottlenecks before they delay customers.
- Check whether delivery commitments are being met.
- Reduce avoidable errors and repeat work.
- Understand the cost of delivering a consistent service.
- Give teams a shared baseline for improvement.
Top 10 Operations KPIs and success metrics
#1 On-time Delivery Rate
On-time delivery rate shows how reliably your team meets its commitments. Use the original agreed due date so that moving a deadline does not hide a missed delivery.
How to calculate it: Deliveries due in the period that were completed by their agreed deadline ÷ all deliveries due in the period × 100. Include overdue, unfinished deliveries in the denominator.
Example: If 92 of 100 deliveries due this month were completed on time, the rate is 92%.
How to get this KPI: Compare due dates and completion timestamps in your order, service or work-management system.
#2 Cycle Time
Cycle time measures elapsed time from starting a work item to finishing it. Define those two events consistently and compare similar types of work.
How to calculate it: Completion timestamp − start timestamp for each finished item. Track the median alongside slower cases to understand variation.
How to get this KPI: Use workflow status history. Decide whether you measure calendar time or working hours, and keep that choice consistent.
#3 Throughput
Throughput counts how much work your team finishes during a defined period. Track comparable items separately so a change in work mix does not look like a productivity improvement.
How to calculate it: Count completed items per day, week or month.
Example: An operations team that completes 240 service requests in a week has a throughput of 240 requests per week.
How to get this KPI: Count completion events in your workflow or transaction records, avoiding duplicate completions for reopened items.
#4 Work in Progress (WIP)
WIP counts work that has started and is still unfinished. It helps teams see how much work is competing for attention.
How to calculate it: Count all started, unfinished items at a particular point in time, including blocked items.
How to get this KPI: Take a consistent daily snapshot of active workflow stages. Review it alongside throughput and cycle time before changing work limits.
Cycle time, throughput and WIP use the workflow boundaries described in The Kanban Guide.
#5 First-pass Yield
First-pass yield measures how often work meets its acceptance criteria on the first attempt. It helps distinguish faster delivery from work that needs correcting later.
How to calculate it: Items passing their first quality check without rework ÷ all items receiving a first quality check in the period × 100.
Example: If 180 of 200 first inspections pass, first-pass yield is 90%.
How to get this KPI: Record first inspection outcomes and use consistent acceptance criteria.
#6 Rework Rate
Rework rate measures the share of assessed items that need correction. Define what counts as rework, such as a returned order or a request reopened because the original work was incomplete.
How to calculate it: Items in a defined cohort requiring rework ÷ all assessed items in that cohort × 100. Count each affected item once and use a fixed follow-up window.
How to get this KPI: Link correction records to the original item. Break results down by reason to identify recurring process problems.
#7 Cost per Completed Item
Cost per completed item helps you understand how much it takes to deliver a particular service or output. Compare similar work and keep the cost allocation method consistent.
How to calculate it: Operating costs allocated to that work during the period ÷ items completed during the same period.
Example: $12,000 in allocated costs for 600 completed requests gives a cost of $20 per request.
How to get this KPI: Combine workflow completion counts with agreed labour, tooling and overhead allocations. Review quality alongside cost reductions.
#8 Capacity Utilisation
Capacity utilisation compares actual output with practical available capacity. Define capacity for a specific process, team or machine rather than combining unlike units.
How to calculate it: Actual output ÷ practical available output capacity for the same period × 100.
Example: Processing 800 orders against a practical weekly capacity of 1,000 gives 80% utilisation.
How to get this KPI: Combine output records with capacity estimates that account for planned downtime. Leave room for variation and urgent work instead of treating 100% as a universal target.
#9 Service-level Agreement (SLA) Attainment
SLA attainment measures whether work meets a defined service commitment, such as responding within four working hours. Track different commitments separately.
How to calculate it: Eligible cases meeting the commitment ÷ all eligible cases whose SLA deadline falls in the period × 100. Include open cases that have already breached the deadline.
How to get this KPI: Use service-desk timestamps and the agreed business-hours calendar, pause rules and exclusions.
#10 Backlog Age
Backlog age shows how long accepted requests have been waiting to start. It can reveal neglected work even when current delivery volumes look healthy.
How to calculate it: Current date − acceptance date for each unstarted request. Report the median and the oldest requests, grouped by priority.
How to get this KPI: Use intake timestamps and start-status records. Keep unstarted backlog separate from WIP so you can see where delays occur.
How to use Operations metrics with OKRs
Use KPIs to monitor the health of your operations, then choose an OKR for the improvement that matters most. The distinction between OKRs and KPIs helps you avoid turning every dashboard measure into a separate goal.
For example, an operations team could set the objective Make customer deliveries more dependable with these illustrative key results:
- Increase on-time delivery from 88% to 96% this quarter.
- Reduce median cycle time from five working days to three.
- Reduce rework from 8% to 4% for the same class of deliveries.
These are example targets, not industry benchmarks. Set your own targets from a measured baseline, assign an owner to each result, and review progress weekly. Keep quality and workload measures visible so a faster process does not create problems elsewhere.
Browse the OKR examples library for more ways to connect metrics to team goals.