About Author
Joseph Griffiths is a Presales Educator and Coach dedicated to helping solution engineers, technical sellers, and sales leaders achieve greater success.
My career spans enterprise technology sales, solution architecture, and leadership roles where I built and implemented complex cloud and data center solutions. Along the way, I earned elite certifications such as VMware VCDX-DCV and VCDX-CMA, which give me the technical depth to match my business expertise. This combination of skills allows me to coach sales professionals on not just the how of technology, but more importantly the why — what truly matters to customers and drives business impact.
Through my technical sales coaching and presales training programs, I focus on building confidence, sharpening customer discovery, and creating measurable business value in every conversation. I help sales teams and individual contributors uncover customer priorities, frame solutions effectively, and communicate with impact. My approach blends proven frameworks with real-world experience to equip sellers to move deals forward faster and build stronger customer trust.
Over the past three years, my work as a Staff Solutions Architect at VMware has exposed me to IT strategies across various Fortune 500 companies. One recurring theme in these engagements is the industry’s focus on creating a stable and secure initial state. While crucial, this emphasis often neglects the operational realities post-deployment. Each “initial state” creates operational debt, which compounds over time due to the dynamic nature of IT systems. This debt accounts for approximately 70% of operational spending, limiting innovation and agility in IT organizations.
Three significant factors exacerbate operational debt:
Key Drivers of Operational Debt
1. Automation of Provisioning
Provisioning automation aims to reduce delivery times for development and production assets. While it increases agility, it often accelerates the accumulation of operational debt due to insufficient governance. Enhanced self-service capabilities increase consumption, compounding long-term operational demands.
2. Public Cloud Adoption
Initially adopted for cost savings, public cloud services now appeal for other reasons:
Although public clouds abstract infrastructure components into software and streamline operations, they still focus on the initial state. Operational costs and vendor lock-in remain critical concerns.
3. Dynamic Nature of Containers
Containers promise immutability and agility, but they introduce new challenges:
For example, Google addressed container-driven complexity by creating the Site Reliability Engineer (SRE) role, blending development and operations to scale effectively.
Strategies for Reducing Operational Debt
1. Recognizing the Problem
Operational debt is split into two categories:
2. Identifying Toil Tasks
Use the following criteria to identify toil tasks:
3. Automating Toil Tasks
Once identified, prioritize automation of repetitive tasks. Focus on transitioning these tasks from human operators to automated systems, reducing latency and improving efficiency.
4. Adopting Service-Oriented Models
Operational tasks should be automated as part of the service deployment. This integration minimizes toil and aligns operations with service delivery.
A Roadmap to Address Operational Debt
The steps include:
The Business Impact of Operational Debt Reduction
Organizations that adopt these strategies report up to a 50% reduction in operational costs, allowing IT to shift from a cost center to a strategic business enabler. This approach not only drives innovation but also enhances agility, empowering IT to better support organizational goals.
By proactively addressing operational debt, IT can unlock sustained efficiency gains and long-term value, transforming the enterprise’s approach to technology management.
Share this:
Like this:
Related