Chaos costs money. In my experience working with various organisations, I’ve seen firsthand how they struggle to manage the chaos that often surrounds the delivery of usable, working products to their customers. The result? Substandard work, a barrage of bugs hitting production, and a frustrating cycle of rework because things simply don’t meet the minimum standards we expect. It’s a familiar tale, and one that I’ve encountered time and again.
Understanding the Shift
When I’m building products, I often find myself in a position where I need to solve a problem. You identify a challenge, envision a solution, and set off in that direction. However, as time passes, the landscape can shift dramatically. This shift might be due to emerging market opportunities or the need to scale operations.
The solution that once seemed perfect can quickly become inadequate. I’ve witnessed this in various sectors, particularly in industries like airlines and car rentals, where technical debt accumulates over time. Choices made years ago can lead to a tangled web of outdated systems that no longer serve the organisation’s needs.
The Dangers of Technical Debt
Take, for instance, a customer I worked with who built their own source control system three decades ago. At that time, the options available were limited, and they had no choice but to create a bespoke solution. Fast forward to today, and it’s clear that this approach no longer makes sense. With robust source control systems like Git readily available, the need to cling to outdated technology becomes a liability.
Investing time and money to transition from legacy systems to modern solutions is crucial. This is where technical leadership and engineering excellence come into play. We must focus on ensuring that our systems and processes are as effective as possible, making our teams’ jobs smoother and more efficient.
The Value of Optimisation
Satya Nadella at Microsoft exemplifies this approach. He prioritises optimising systems so that the best engineers can focus on delivering features rather than wrestling with outdated processes. This investment in system optimisation is not merely a cost; it’s a value centre that supports our ability to innovate and deliver new features.
A prime example of this is the Azure DevOps team. Back in 2012, they were delivering around 25 features to production each year with a workforce of 650 people. Through a commitment to technical excellence and leadership, they transformed their output to over 600 features annually. This remarkable increase was achieved by addressing both technical debt and the accumulation of what I like to call “technical cruft”, the sediment that builds up in systems over time.
The Impact of Testing
One of the pivotal changes they made was shifting from long-running system tests to unit tests. This transition took four years of dedicated effort, but the results were staggering. They reduced the time it took to verify changes from 48 hours to just 3.5 minutes. Imagine the productivity boost if you could instantly know whether a change was successful rather than waiting two days.
This rapid feedback loop allows teams to make smaller, more frequent changes, leading to a better product that is scalable and less reliant on quick fixes. Instead of patching over problems with Band-Aids, teams can focus on building robust solutions that stand the test of time.
Conclusion: The Cost of Chaos
Ultimately, the cost of chaos stems from poor technical leadership and a culture of engineering mediocrity. By empowering your best engineers to focus on optimising systems, you enable every team member to add value more easily. This shift not only enhances productivity but also fosters a culture of excellence that can propel your organisation forward.
In my journey, I’ve learned that addressing chaos is not just about managing the present; it’s about preparing for the future. By investing in the right systems and processes today, we can ensure that we’re not just surviving the chaos but thriving in it.
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
Navigating Technical Debt: How to Transform Challenges into Opportunities for Quality and Efficiency
Explains how managing technical debt and distinguishing it from poor quality can boost product efficiency, reduce costs, and support …
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 …
Transforming Technical Debt: Unlocking Opportunities for Innovation and Value
Explores how addressing technical debt boosts innovation, team morale, and value delivery by enabling agile development, better products, …
Mastering Technical Debt: Strategies to Transform Challenges into Opportunities for Your Development Team
Explains technical debt in software development, its impact on teams, and practical strategies to identify, manage, and reduce it for …
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 …
Stop Hiding Behind Complexity and Start Delivering Continuously
Continuous delivery is achievable for any software, regardless of complexity. Success depends on investment in automation, quality, 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 …
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 …
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 …
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 Big Bang Rewrites Fail: How Sustainable Change and Engineering Excellence Transform Legacy Systems
Ditch the Big Bang rewrite. Discover why sustainable, in-place change drives true engineering excellence and lasting transformation in your …
Is Agile Really Just a Mindset?
Explores Agile as a disciplined system of delivery, emphasizing engineering excellence, CI/CD, observability, and system design over mindset …
Telling People What to Do Is Not Leadership. It’s a Failure of System Design
Explores why real leadership means designing systems that enable team autonomy, flow, and accountability, rather than relying on …
From Legacy Pain to Modern DevOps: My Proven Roadmap for Real Engineering Transformation
Transform legacy engineering with a proven, step-by-step approach, learn how to automate, adapt, and build a resilient, modern DevOps …