A candid discussion on bridging the gap between technology spending and business impact.
The Boardroom Challenge
Last month, I sat in a boardroom with a Fortune 1000 CXO who asked a question I hear increasingly often. I am paraphrasing, using a general dollar amount, but it still represents the sentiment:
“We’ve spent $200 million on cloud and AI initiatives. Where’s the ROI?”
The silence that followed wasn’t about failure. It reflected a fundamental disconnect between technology investment and impact measurement, a challenge present in nearly every large enterprise today.
Executives are realizing that substantial cloud and AI investments aren’t automatically delivering the expected business outcomes.
The technology works. The teams are capable. Yet the returns remain elusive.
The Multi-Cloud Mirage
A lot of the CXOs/leaders I am talking with are facing an uncomfortable reality: significant investments in AWS, Azure, and GCP haven’t produced the business clarity they expected. Teams generate mountains of cloud cost and utilization data, stay busy with optimization projects, and maintain strong vendor relationships. Yet leadership still struggles to answer basic questions about value creation.
The root cause? Cloud spending is fragmented across business units, regions, and product lines. Tagging standards are inconsistent. Governance exists in pockets but not holistically. Most critically, there’s no clear line of sight between cloud expenditure and business outcomes.
We witness a similar adoption and implementation curve with DevOps. Everyone was buying DevOps tools but not implementing the operational rigor or culture of a true DevOps strategy. Why? Because it’s difficult—however, when DevOps is implemented, it’s transformative. The blog from Bunnyshell back in 2021 provided a great view on this as well. https://www.bunnyshell.com/blog/challenges-of-devops/
Let me give you an example: one global manufacturing client discovered they were spending 40% more on cloud infrastructure than necessary. The problem wasn’t technical inefficiency but organizational: no unified visibility into what was being purchased and why. Different teams were solving the same problems independently, duplicating costs, and creating vendor lock-in without strategic intent.
Simply put, the rise of advanced technology with huge upsides always requires effort — but at scale, transformational work is hard. It’s supposed to be. If it were easy, it wouldn’t be transformational.


Leave a comment