Operations Metrics

Average order value measures the mean amount spent each time a customer places an order. It is a core e-commerce and retail metric that directly influences revenue, profitability, and customer acquisition efficiency.

Cart abandonment rate measures the percentage of online shopping carts that are created but not converted into completed purchases. It is one of the most impactful e-commerce metrics because it represents revenue that was within reach but lost at the final stage of the buying journey.

Inventory turnover measures how many times a business sells and replaces its inventory during a given period. It is a critical operations and finance metric that reveals how efficiently capital is being deployed in stock.

Order fulfilment cycle time measures the total elapsed time from when a customer places an order to when they receive it. It is a critical operations metric that directly affects customer satisfaction, repeat purchase rates, and competitive positioning.

On-time delivery rate measures the percentage of orders delivered by the promised date. It is a critical customer experience metric that directly affects satisfaction, loyalty, and the organisation's reputation for reliability.

First contact resolution measures the percentage of customer enquiries resolved during the first interaction without requiring follow-up contacts, transfers, or escalations. It is the single most influential metric for customer satisfaction in support operations.

Capacity utilisation rate measures the percentage of total available production or operational capacity that is actually being used. It reveals whether an organisation is underusing its resources or pushing them beyond sustainable limits.

Cycle time measures the total elapsed time from the start to the end of a process. It is a fundamental operations metric used in manufacturing, software development, service delivery, and any context where the speed of a process directly affects throughput, cost, and customer satisfaction.

Throughput measures the number of units produced, tasks completed, or transactions processed in a given time period. It is the fundamental measure of an operation's productive capacity and the primary output metric for manufacturing, logistics, software development, and service delivery.

Deployment frequency measures how often an organisation successfully releases code to production. It is one of the four DORA (DevOps Research and Assessment) metrics that predict software delivery performance and organisational outcomes. Teams that deploy more frequently deliver value to users faster, reduce the risk of each individual release, and create tighter feedback loops between development and production.

Lead time for changes measures the elapsed time from when a developer commits code to when that code is successfully running in production. It is one of the four DORA (DevOps Research and Assessment) metrics and captures the full latency of the software delivery pipeline. Shorter lead times mean faster feedback, lower risk per release, and a tighter connection between engineering effort and user value.

Sprint velocity measures the amount of work a team completes during a sprint, typically expressed in story points, ideal days, or another unit of estimation. It is a planning tool that helps agile teams forecast how much work they can commit to in future sprints based on their historical completion rate. Velocity is one of the most widely used and most frequently misunderstood metrics in agile software development.

Defect density measures the number of confirmed defects per unit of delivered work. In software development, it is typically expressed as defects per thousand lines of code (KLOC) or defects per function point. In manufacturing and other contexts, it is expressed as defects per unit produced. The metric provides a normalised view of quality that allows comparison across projects of different sizes and across time periods with different delivery volumes.

Code churn rate measures the percentage of code that is rewritten or deleted shortly after being written. It captures how much rework occurs within a codebase over a given period, revealing instability in requirements, design decisions, or development practices. A moderate level of churn is normal and healthy, but persistently high churn signals wasted effort and process problems that deserve investigation.

Code review velocity measures the elapsed time from when a pull request is opened to when the review is completed. It captures how quickly a team provides feedback on proposed code changes, which directly influences how fast work moves from development to deployment. Slow reviews create bottlenecks, force context switching, and inflate lead times far beyond what the actual coding effort requires.

Release velocity measures how frequently an organisation ships production releases over a given period. It captures the end-to-end cadence of the software delivery process, from completed work to running in production. Higher release velocity means faster value delivery to users, smaller and safer individual releases, and tighter feedback loops between development and the real world.