Technology Isn’t a Cost Center. It’s an Enterprise Value Creator.

 

When organizations discuss technology investments, the conversation often begins with cost. Hardware, software, cloud services, licensing, and staffing are all scrutinized because they appear on a budget. It’s understandable. Leaders have a responsibility to manage investments wisely.

The conversation can also become distracted by the latest platform, the newest capability, or whatever technology happens to dominate the headlines. While innovation is important, adopting technology simply because it’s new is no more effective than rejecting it simply because it costs more.

Technology has never created value simply because it costs less or because it’s the latest trend. It creates value by enabling organizations to operate differently, make better decisions, remove constraints, and pursue opportunities that would otherwise remain out of reach.

One example came while leading the modernization of a large enterprise environment. We were preparing to expand into the cloud while continuing to support mission-critical applications running in our existing data centers. The architecture needed to support modern cloud-native applications while maintaining compatibility with existing enterprise systems. It also had to provide high availability across multiple organizations that depended on shared services.

At the time, the cloud provider’s native load-balancing capabilities had not yet matured enough to provide the flexibility we required. We turned to a trusted technology partner whose products had served us well in our on-premises environment and who had begun offering a cloud-based solution. Their initial assessment was straightforward: what we wanted to accomplish wasn’t supported.

For many organizations, that would have ended the discussion. The architecture would have been redesigned around the limitation, and the opportunity to build a more capable foundation would have been lost. Instead, we challenged the assumption—not because we believed the vendor was wrong, but because the business outcome mattered more than accepting the first answer. Our engineers worked alongside the vendor’s engineering team until we developed an approach that supported modern containerized workloads, traditional enterprise applications, and our existing infrastructure as a unified platform. The solution preserved existing investments while creating a scalable path to the cloud. It also improved interoperability across agencies and freed developers to focus on delivering business capabilities instead of engineering around infrastructure constraints.

The architecture quietly continued to pay dividends long after the project was complete. Developers spent less time engineering around infrastructure constraints and more time delivering capabilities to the business. Our CI/CD pipeline became more efficient, operations became simpler, and each successive technology decision became easier because the foundation had been built to evolve with the enterprise instead of holding it back. What began as an infrastructure challenge became a catalyst for enterprise value creation, compounding over time through faster delivery, greater operational efficiency, and the freedom to adapt as business needs changed.

Earlier in my career, I learned the same lesson through virtualization. Most organizations justified virtualization by counting the number of physical servers they could eliminate. The hardware savings were real, but they represented only a fraction of the return. Reducing power consumption, cooling requirements, provisioning time, and operational effort allowed engineering teams to spend less time maintaining infrastructure and more time delivering value. Once again, the greatest return came not from the technology itself, but from the stronger foundation it created for everything that followed.

That’s why I’ve come to believe the greatest return on a technology investment isn’t measured when the project is finished. It’s realized in every capability the organization delivers more quickly, every constraint it no longer has to engineer around, and every opportunity it can pursue because the right foundation was put in place.

Technology should never be viewed as a cost center. Its greatest value isn’t in the systems we deploy, but in what they allow the enterprise to become.

- Tim

Tim Gabaree is a technology executive who writes about enterprise value creation, governance, operational leadership, and the role of technology in helping organizations grow and perform.

When Paying More Costs Less: A Strategy-to-Execution Lesson in 2 Minutes

A client approached us after a cloud modernization and application rationalization program had fallen behind schedule. The initiative supported approximately 3,500 users and included more than 1,500 applications. One year into a planned three-year effort, progress lagged expectations, and budget concerns were growing.

The delivery model relied heavily on junior personnel. Labor rates were low, but the work required experienced practitioners. Rationalization, change management, architecture, and delivery all depended on sound judgment. Discovery and rationalization lacked discipline. Change management was weak. Application modernization decisions often lacked the experience required to execute effectively.

The project appeared inexpensive on paper. Delivery told a different story.

After assessing the program, we recommended a different approach. We introduced experienced business process specialists, change management professionals, application rationalization experts, and senior cloud engineers. Labor costs increased by 50 percent.

The team rationalized more than 1,500 applications to fewer than 500. Approximately 400 applications were modernized and rebuilt for cloud operation. Roughly 40 were migrated through lift-and-shift approaches. Remaining applications were retained on-premises due to business or technical constraints or designated for retirement.

The original plan projected three years to MVP. We joined after the first year and achieved MVP with approximately one year remaining on the original schedule. This means that delivery accelerated by 33 percent. And despite higher labor costs, program spend decreased by 20 percent.

Labor cost and delivery cost are not the same thing. Lower hourly rates often look attractive during procurement, but delays, rework, poor decisions, and deferred value rarely appear on the same spreadsheet.

Experienced personnel cost more per hour. The total cost of delivery often tells a different story. Organizations should evaluate the total cost of delivery rather than the hourly cost of labor because sometimes paying more costs less.

The Last Two Across the Finish Line

 

Many years ago, I attended the Ranger Indoctrination Program (RIP), which is now known as the Ranger Assessment and Selection Program (RASP).

One of the events was a five-mile run that had to be completed within a strict time limit. It was designed to create stress and accelerate attrition. 

About halfway through, I caught up to another candidate who was struggling and out of breath. He was in good physical condition, muscular and built more like a bodybuilder than a runner. He wasn’t a quitter, but this event just wasn’t his strength. I had a choice to keep my pace and finish comfortably, or slow down and help him. I slowed down and stayed with him. We spent the rest of the run pushing each other to finish. By the time we approached the finish line, everyone else had already crossed. Several candidates had already been dropped for not making it in time. The Black Hats (what our instructors were called) saw us coming from a distance. We were the last two across the finish line. And they informed us that we'd both passed. We’d moved on to the next round.

At the time, I didn’t think much about the decision, as during Infantry Basic Training, Advanced Individual Training, and RIP, one lesson was endlessly repeated: 

Never leave your buddy behind.

As you could probably guess at this point, this story isn’t really about running or about my experience as a Rippie. It’s about a lesson that has stayed with me for more than thirty years.

And I’ve seen the same principle apply in business: Some of the best teams I’ve been part of were built by people willing to invest time and energy in helping others succeed, even when there was no immediate benefit to themselves. Likewise, many of the best leaders I’ve worked with understood that their job wasn’t to win alone. It was to help the team cross the finish line together.