CEO Weekly

How to Lead IT Initiatives That Build Competitive Advantage

How to Lead IT Initiatives That Build Competitive Advantage
Photo Courtesy: Nick F. Hernandez

By: Natalie Johnson

Most IT initiatives keep the lights on: patching, upgrades, and maintaining systems, all necessary work that every competitor is also doing, and that differentiates nobody. The organizations pulling ahead are building technology that is hard to copy, grows more valuable over time, and changes what the business can actually do.

Nick F. Hernandez, a technology leader with deep experience driving competitive advantage through IT strategy, draws a precise line between the two categories, and the test he applies is unambiguous. “Does this just cut a cost or speed something up, or does it change what the business can actually do?” Hernandez states. “If it’s a one-time gain, it’s maintenance. If it builds something competitors can’t easily copy, that’s an advantage.”

Build What Competitors Cannot Easily Replicate

The edge in competitive IT rarely comes from the technology itself. It comes from the data built up over time, the depth of the tool’s integration into how people actually work, and the behavioral change it drives across the organization. Hernandez cites a custom platform he helped design that enables rapid addition of new tools and functionality without having to rebuild from scratch each time. Individually, any one of the tools is unremarkable. The platform underneath is the differentiator. “Every new capability we add makes the next one easier,” he reflects. “We can build and adapt a far faster, more competitive system than if we stitched together off-the-shelf products from scratch every time a need came up.”

That dynamic is precisely what separates a strategic IT investment from a maintenance expense. Off-the-shelf products are available to every competitor. A platform built around how a specific organization works, layered with proprietary data and deeply embedded in daily operations, is not. The question every technology leader should be asking before committing resources is not whether a project will save money or accelerate a process; it is whether the asset will be worth more in three years than it is today.

Sell the Bet, Not the Business Case

Winning executive backing for an initiative whose payoff is competitive advantage rather than visible cost savings requires an entirely different framing. “The mistake is trying to sell an advantageous case using a cost-savings model,” Hernandez states. “It always loses because the savings case looks cleaner and safer on paper.” The alternative is to anchor the conversation in what the chief executive officer (CEO) already cares about: growth, customer retention, fending off a specific competitor, and putting honest numbers on what can be quantified, rather than making precision claims that collapse under scrutiny.

The investment itself needs to feel safe to approve. Hernandez breaks initiatives into stages with agreed-upon stopping points and delivers an early win before asking for more capital. That approach transforms the board’s decision from a blank-check commitment into a small, contained bet. “Executives say yes far more easily when the downside is limited, and the upside is tied to something they already answer for,” he notes. The goal is not to get a large initiative funded in one motion; it is to get the first stage approved with enough credibility to secure the next.

AI Returns Require the Right Question

The trap in AI investment reporting is that progress is easy to fake. Tokens consumed, queries run, seats deployed: these metrics go up consistently and mean nothing about business value. “My discipline starts with refusing to celebrate usage,” Hernandez reflects. “The question isn’t how much AI we’re using. It’s what made the business faster, cheaper, or better. If I can’t answer that, I treat the spend as a cost to cut, not a win to report.”

Bold AI bets are funded in stages: a small initial investment, with additional capital only once real business impact is demonstrated, and a pre-agreed exit point if the evidence does not materialize. That structure enables risk-taking without the organizational inertia that builds around sunk costs. Fail fast and cheap, then redirect capital to what is actually working. The chief information officer (CIO) who operates this way builds the credibility to take bigger bets over time, because the board has seen that when something is not working, the resource conversation happens early rather than after significant damage is done.

Follow Nick F. Hernandez on LinkedIn for more insights on IT strategy, competitive advantage, and building the technology initiatives that drive lasting business results.

Spread the love

This article features branded content from a third party. Opinions in this article do not reflect the opinions and beliefs of CEO Weekly.