Averages are useful for reporting. They can be dangerous for redesign.
In large operations, leaders often look at average cost per transaction, average productivity, average cycle time, or average service level. Those metrics matter, but they can also hide the truth.
The average is often the best of the worst and the worst of the best. It smooths out the variation leaders most need to understand.
That is why cost-to-serve matters.
When you look at a business through a cost-to-serve lens, you stop asking only, “What does the average transaction cost?” and start asking better questions.
Better cost-to-serve questions include:
- Which transaction types create disproportionate cost?
- Which work requires extra labor, space, packaging, inventory, or management attention?
- Which customer or product segments consume more capacity than their volume suggests?
- Which parts of the operating model still create value?
- Which parts are adding complexity without enough benefit?
Not every transaction belongs in the same model
A broad operating strategy may be directionally right. Centralize more work. Improve consistency. Reduce field burden. Lower inventory. Increase scale. Those are all reasonable goals.
But not every transaction belongs in the same operating model.
Some transaction types look small by volume but large by cost. They may require special handling, additional touches, constrained capacity, more complex inventory rules, or more exception management.
When those transactions are blended into the average, the complexity can disappear. When they are viewed through cost-to-serve, the economics become much clearer.
Ask which volume belongs
The better question is not always, “How do we push more volume through the model?”
The better question is, “Which volume actually belongs in this model?”
That distinction matters.
A high-performing operating model is not built by forcing every transaction through the same path. It is built by understanding the work, segmenting the work, and designing the right path for the right type of work.
The answer may be different by segment:
- Sometimes the answer is centralization.
- Sometimes the answer is automation.
- Sometimes the answer is a different labor model.
- Sometimes the answer is changing inventory rules.
- Sometimes the answer is redesigning logistics.
- Sometimes the answer is renegotiating vendor economics.
- Sometimes the answer is removing work from a process where it no longer belongs.
Vendor economics need to match the work
This is also where vendor relationships become clearer.
A vendor may be important to the business, but importance alone does not make them a true partner. A true partner is willing to look at the full operating model, understand how the economics have changed, and help solve for mutual value.
When the work changes but the economics do not, leaders need to be willing to challenge the model.
That does not mean every vendor disagreement should become a confrontation. It means the operating facts should be visible enough for both sides to evaluate whether the model still makes sense.
Simplicity is a strategic choice
The goal is not complexity for its own sake. The goal is simplicity that works.
The best operating improvements often come from seeing what the average hides. A small part of the business may be creating an outsized share of cost, friction, waste, or delay.
Once leaders see that clearly, they can redesign the work in a way that improves performance without hurting the customer experience.
That is the real discipline of scale.
The Scale That Works takeaway
Do not just ask what the average says.
Ask what the work is actually costing, where the complexity is coming from, and whether the current model still makes sense.
Averages can help leaders report performance. Cost-to-serve helps leaders decide where to act.
Want to apply this to your operation?
Share the operating challenge, growth priority, or execution gap you are working through, and let’s compare notes.