Building a value case for a COO

What the COO is actually measured on

Cost to serve. Throughput and cycle time. Quality, error rates and rework. Service levels and customer outcomes. Capacity utilisation. Operational risk and business continuity. In many organisations, headcount efficiency as volumes grow.

The COO thinks in processes and constraints. If you cannot describe the process you are improving, you are not yet in the conversation.

Anchor everything to a process baseline

The strongest operational value cases start with a measured current state:

• Volume: how many times does this process run per month.
• Effort: how long does each run take, and at what loaded cost.
• Quality: what proportion require rework, and what does an error cost.
• Cycle time: elapsed time from start to finish, including waiting.
• Constraint: which step limits the whole flow.

With those five numbers, value calculates itself and is verifiable. Without them, you are asserting.

Improve the constraint, not the average

An operations leader will discount a case that improves a step which is not the bottleneck, because it produces no additional throughput. Identify the constraint and show your effect on it. If you are improving a non-constraint, be honest that the benefit is cost or quality rather than capacity.

This is a credibility test as much as an analytical one. Getting it right marks you out from vendors selling generic efficiency.

Quality often beats speed

Rework is expensive and invisible in most business cases. Error rates, exception handling, manual reconciliation and the cost of getting it wrong for a customer are frequently larger than the direct labour saving — and they are what keeps a COO awake. Quantify avoided rework explicitly.

Be honest about headcount

Operational cases often imply headcount reduction. Say plainly whether the benefit is cost-out, capacity to absorb growth without hiring, or redeployment to higher-value work. A COO will decide which one applies regardless, and pretending otherwise damages trust. In growing businesses, "absorb 30% more volume with the same team" is usually the more welcome and more achievable claim.

Continuity and operational risk

Single points of failure, undocumented processes, dependency on spreadsheets, staff who alone know how something works — these are live operational risks with real cost. Quantifying what a failure would cost, and how the proposed state reduces exposure, often carries more weight than incremental savings.

What to have ready

• The current-state process, ideally in their own terms.
• Volume and effort data, or a defensible proxy.
• The implementation impact on the operation while it is running.
• Change management: who is affected, and how you avoid disruption.
• A comparable operation of similar scale and complexity.

Common mistakes with COOs

• Presenting efficiency without a measured baseline.
• Improving a step that is not the constraint.
• Ignoring the disruption cost of implementation.
• Being vague about headcount implications.
• Underestimating the change effort in a large operational team.

How Verity helps

Choose the COO persona and Verity frames the dossier operationally: challenges as process and capacity constraints, outcomes as throughput, cost-to-serve and quality metrics with baselines and targets, and an ROI model where every driver names the assumption behind it. You supply the customer's real volumes; the structure is already there.