The business case for quality is often reduced to defects. Better quality means fewer defects. Fewer defects mean less rework, fewer incidents and lower support costs.
That is true, but incomplete. A product can contain few defects and still solve the wrong problem. It can function correctly while being difficult to use, expensive to operate or impossible to scale. It can be delivered quickly and reliably while creating little customer or business value. If quality is broader than testing and defect prevention, its business value must also be broader.
DORA measures an important part of the story
DORA metrics help organisations understand how effectively engineering delivers software changes. They provide evidence about speed, stability, recovery and rework within the delivery system. This matters. An organisation that cannot change its product quickly and safely will struggle to respond to customers, risks and opportunities.
But delivery performance is not the same as product quality. DORA can show how well we deliver changes. It does not tell us whether we selected the right changes, whether the product is good enough for its context or whether it achieves the intended outcome.
The broader question is:
How effectively can we turn business intent into a valuable, fit-for-purpose product—and continue improving it sustainably?
Quality reduces the cost of being wrong
When product intent, stakeholder needs and assumptions remain unclear, engineering may deliver exactly what was requested without creating meaningful value. The result may be:
- rarely used functionality;
- solutions to misunderstood problems;
- unnecessary complexity;
- rework caused by late clarification;
- delayed learning about customers.
A broader quality approach makes product reasoning explicit and challenges assumptions earlier. Its value is not only fewer implementation defects. It is less wasted product investment.
Quality reduces the cost of failure and operation
Some weaknesses become incidents, security exposure, data errors or customer complaints. Others become permanent operating costs:
- recurring support contacts;
- manual workarounds;
- unstable services;
- repeated defect correction;
- difficult recovery;
- complicated maintenance.
These costs are often distributed across engineering, operations, support and the business. They may never appear together as the cost of poor product quality. A lifecycle perspective connects them to the product decisions that created them. Its value includes lower risk, lower cost to serve and fewer expensive surprises.
Quality protects the ability to change
Quality also affects how easily the product can be improved tomorrow. Weak maintainability, poor testability, unclear product intent and accumulated technical debt make every future change slower and riskier. The organisation then spends more effort preserving existing behaviour and less effort creating new value.
Quality engineering protects the ability to change through:
- shorter lead times;
- safer releases;
- less rework;
- lower development cost;
- less dependence on individuals;
- greater responsiveness to markets and customers.
This is where DORA becomes part of the wider quality story. It helps show whether engineering can change the product quickly and sustainably.
Quality increases the likelihood of useful outcomes
Quality is not only about reducing cost and risk. A reliable, understandable, responsive and context-appropriate product is more likely to achieve:
- adoption;
- customer satisfaction;
- trust;
- retention;
- productivity improvements;
- business benefits;
- access to more demanding markets.
The causal chain is rarely simple, but it can be made visible:
better product understanding
→ better engineering decisions
→ stronger product behaviour
→ better customer experience
→ improved business outcomes
The aim is not to claim perfect attribution. It is to make the relationship explicit enough to support better decisions.
Quality also has a cost
A broader quality approach requires investment in:
- understanding stakeholders and outcomes;
- defining relevant quality expectations;
- improving testability and observability;
- collecting engineering and operational evidence;
- interpreting that evidence;
- involving specialists;
- improving products and ways of working.
There is also a risk of bureaucracy. If quality modelling becomes a documentation exercise, it can slow delivery without improving judgement. The depth of assessment should therefore reflect the product’s value, risk, complexity and cost of failure. The goal is not maximum quality activity. It is sufficient quality understanding to make responsible business decisions.
A broader business case
The business value of quality can be understood through four effects:
- reducing the cost of being wrong;
- reducing the cost of failure and operation;
- reducing the cost of future change;
- increasing the likelihood of valuable outcomes.
The cost lies in the modelling, measurement, assessment and improvement needed to achieve those effects.
This should not be compressed into one universal quality ROI figure.
Each product needs an explicit quality argument:
Which business risks and outcomes matter?
Which product and engineering qualities influence them?
What evidence shows whether they are improving?
Is the expected value worth the required investment?
DORA provides an important view of engineering delivery.
A broader product-quality model connects that view to customer value, operational cost, business risk and product outcomes. That may be the real business case for quality:
Quality reduces the cost of being wrong, the cost of failure and the cost of future change—while increasing the likelihood that the product achieves its intended purpose.