Most organisations are blissfully unaware of the sheer amount of waste lurking within their systems. It’s staggering to think about the money they’re haemorrhaging simply because they lack a focus on engineering excellence. In the context of agile and business agility, we need to embrace a continuous mindset, continuous integration, continuous delivery, continuous feedback, and continuous testing. This dynamic nature of operations allows us to identify problems sooner, which means they’re smaller and easier to address. By doing so, we not only eliminate waste but also gather valuable data and telemetry that help us understand our processes better. This understanding is crucial for pinpointing problem areas and taking action before costs spiral out of control.
In my work with various customers, I’ve seen an alarming amount of waste. To illustrate this, I often refer to DORA metrics, which provide a clear picture of how organisations can improve their performance. Let’s break down a few key metrics that can help us understand the return on investment (ROI) for our efforts:
-
Innovation Rate: This metric measures the percentage of time your team spends on innovating versus maintaining existing functionality. On average, organisations see an innovation rate of around 39%. This means that only 29% of the budget is allocated to net new functionality, essentially, new capabilities that can attract new customers or open new markets. This is a dismal figure, highlighting the need for a shift in focus.
-
Product Index: This metric looks at how much time your engineers spend working directly on the product versus other tasks. Typically, about 80% of their time should be dedicated to product development. If we assume this holds true, we’re left with just 23 cents on the dollar in terms of potential ROI.
-
Usage Index: This is a critical metric that reveals what percentage of the features you build are actually used by your customers. The industry average sits at around 35%. This means that a significant portion of your development efforts may be wasted on features that users don’t engage with. It’s essential to ask your engineering teams about their usage index, understanding this can lead to more informed decisions about where to invest resources.
-
Version Adoption: For applications that require installation, it’s vital to know what percentage of your user base is on the latest version. The industry average is about 70%, meaning 30% of users are still on older versions. In many cases, I’ve encountered organisations where this figure is much lower, further diminishing the ROI.
When we piece these metrics together, the picture becomes quite grim. Starting with a dollar, we see that only 29 cents are spent on new functionality, which drops to 23 cents when we factor in the product index. The usage index further reduces this to a mere 8 cents on the dollar. Finally, if we consider version adoption, we might find ourselves with just 6 cents in return for every dollar spent. Is that a good investment? I think not.
So, what can we do about this? The first step is to understand your innovation rate. How much time is your team dedicating to innovation versus maintenance? Next, assess your usage index. Are you collecting the necessary telemetry to understand which features are actually being used? This data is vital for making informed decisions about where to allocate your resources.
Agility plays a crucial role in this narrative. By closing feedback loops and iterating faster, we can improve our cost-to-value ratio. While it may seem like we’re not reducing costs, since the same people are doing the same amount of work, the goal is to deliver more value for the money we’re investing.
In conclusion, it’s imperative that we take a hard look at these metrics and understand the underlying reasons for our low ROI. By focusing on innovation, understanding usage, and embracing agility, we can turn the tide and ensure that our investments yield meaningful returns. Let’s not allow waste to become the norm; instead, let’s strive for excellence in everything we do.
Smart Classifications
Each classification [Concepts, Categories, & Tags] was assigned using AI-powered semantic analysis and scored across relevance, depth, and alignment. Final decisions? Still human. Always traceable. Hover to see how it applies.
What to read next
Maximising ROI in Software Development: Unlocking Value Through Quality and Expertise
Learn how quality, technical expertise, and regular reviews in software development can maximise ROI and ensure your organisation delivers …
Mastering Agility: Balancing Engineering Excellence and Effective Processes in a Rapidly Changing Business Landscape
Explores how to balance engineering excellence and effective Agile processes, highlighting the need for technical skills, continuous …
Maximising Product Value: The Power of Hypothesis-Driven Engineering
Explores how hypothesis-driven engineering helps teams maximise product value by testing ideas, measuring outcomes, and learning from …
Transforming Engineering Excellence: The Power of Naked Agility in Quality and Leadership
Explores how adopting naked agility boosts engineering excellence, quality, and leadership by addressing technical debt, shifting left, and …
Transforming Technical Debt: Unlocking Innovation and Value Through Quality Product Delivery
Explores how managing technical debt enables faster delivery, higher product quality, and greater innovation, highlighting strategies for …
Evidence-based Management: Gathering the metrics
Explains how to gather key metrics for evidence-based management in software organisations, focusing on value delivery, time to market, and …
Detecting agile theatre with real delivery signals
Why Most Companies Operating Models Fail in Dynamic Markets
A concise comparison of Predictive and Adaptive Operating Models, explaining why traditional structures fail in dynamic markets and how …
Don’t Manage Dependencies, Remove Them
Explains why dependencies are a sign of poor system design and outlines steps to eliminate them by aligning teams, clarifying ownership, and …
The Estimation Trap: How Tracking Accuracy Undermines Trust, Flow, and Value in Software Delivery
Tracking estimation accuracy in software delivery leads to mistrust, fear, and distorted behaviours. Focus on customer value, flow, and …
Flow of Value vs Flow of Work – Misnomer or Useful Shorthand?
Compares “flow of value” and “flow of work” in Kanban, explaining why only validated outcomes count as value and stressing the need for …
Why Outsourcing DevOps Fails, and How Real Engineering Excellence Starts With Your Team
Avoid DevOps vendor lock-in, discover how true engineering excellence starts with partnership, not outsourcing. Ready to transform your …
Why Most Companies Operating Models Fail in Dynamic Markets
A concise comparison of Predictive and Adaptive Operating Models, explaining why traditional structures fail in dynamic markets and how …
Don’t Manage Dependencies, Remove Them
Explains why dependencies are a sign of poor system design and outlines steps to eliminate them by aligning teams, clarifying ownership, and …
The Estimation Trap: How Tracking Accuracy Undermines Trust, Flow, and Value in Software Delivery
Tracking estimation accuracy in software delivery leads to mistrust, fear, and distorted behaviours. Focus on customer value, flow, and …
Kendall Guide - A System of Work for AI Adoption
Flow of Value vs Flow of Work – Misnomer or Useful Shorthand?
Compares “flow of value” and “flow of work” in Kanban, explaining why only validated outcomes count as value and stressing the need for …
Estimating Better in an Overloaded System Is a Poor Man’s Strategy
High work in progress (WIP) causes delays and unpredictability; improving estimates won’t help. Limiting WIP and focusing on flow is key to …
Detecting agile theatre with real delivery signals
Don’t Manage Dependencies, Remove Them
Explains why dependencies are a sign of poor system design and outlines steps to eliminate them by aligning teams, clarifying ownership, and …
The Estimation Trap: How Tracking Accuracy Undermines Trust, Flow, and Value in Software Delivery
Tracking estimation accuracy in software delivery leads to mistrust, fear, and distorted behaviours. Focus on customer value, flow, and …
Flow of Value vs Flow of Work – Misnomer or Useful Shorthand?
Compares “flow of value” and “flow of work” in Kanban, explaining why only validated outcomes count as value and stressing the need for …
Why Outsourcing DevOps Fails, and How Real Engineering Excellence Starts With Your Team
Avoid DevOps vendor lock-in, discover how true engineering excellence starts with partnership, not outsourcing. Ready to transform your …
Estimating Better in an Overloaded System Is a Poor Man’s Strategy
High work in progress (WIP) causes delays and unpredictability; improving estimates won’t help. Limiting WIP and focusing on flow is key to …
Why Most Companies Operating Models Fail in Dynamic Markets
A concise comparison of Predictive and Adaptive Operating Models, explaining why traditional structures fail in dynamic markets and how …
The Estimation Trap: How Tracking Accuracy Undermines Trust, Flow, and Value in Software Delivery
Tracking estimation accuracy in software delivery leads to mistrust, fear, and distorted behaviours. Focus on customer value, flow, and …
Getting Started with Objectives & Key Results
Learn how to successfully implement OKRs by aligning clear strategy, fostering transparency, empowering teams, focusing on outcomes, and …
OKR Guide - A Social Discipline for Shared Focus, Measurable Contribution, and Strategic Learning
A certification proves you’ve passed a test
Certifications show test-passing ability but don’t prove real-world product skills. Experience, judgement, and stakeholder influence matter …
Most companies still get Product Ownership wrong
Many organisations misunderstand Product Ownership, treating it as simple backlog management instead of a strategic, accountable role …