Longtime IT executive Mohan Sankararaman has transformed how he views transformations.
Sankararaman, CIO of First Horizon, used to run transformations as monumental multiyear IT programs. Today, his transformations are smaller — yet still consequential — changes to how work gets done.
“The definition of ‘transformation’ has changed,” he says. “Ten years ago, it was a large program for IT transformation, where you defined a target state, defined a program with projects under it, and started a two- to three-year initiative you’d execute. But in today’s world, there is not a start and stop point. It’s an ongoing journey that never ends. It’s all about continually changing and building an organization that can adapt and reinvent itself continuously.”
It’s a needed shift, Sankararaman says.
The big transformations in the past focused on implementing new technologies, with success typically measured using IT-type metrics, he explains. Cloud migrations are an illustrative case, with progress and success measured by how many apps IT moved to the cloud and how many were in line for the move.
Compare that with the smaller, more nimble transformations of today where IT and the business use technology — most often AI — to reimagine a single workflow within a larger business process to deliver a desired business outcome, such as improved time to market, which is the measure of success. And then it’s about reengineering another and then another workflow in that process to continuously improve that desired business outcome, he explains.
Linking incremental transformations to bigger outcomes
Sankararaman has persuasive reasons for his updated perspectives on transformation. Topping the list is the increasing pace of change, both in technology (and AI specifically) and in the business environment.
“If you have a two- or three-year big transformation program, when you’re done the outcomes are stale because AI is moving forward in monthly increments,” he says, adding that “three years is a very long time in AI think.”
Smaller, incremental transformations also allow for easier course-correction, he says.
And they better leverage domain expertise in their planning and execution, because business users are teaming with IT to reimagine the tasks they do in their daily work rather than weighing in on companywide processes.
Sankararaman points to his current transformation efforts around loan origination, a critical business process for every bank, to justify his faith in the value of small ‘t’ transformation.
“I could say I want to engineer this whole thing, and it would take 24 months. But it’s made up of multiple sub-workflows, so we’re looking at each sub-workflow and reimagining it,” he says.
That approach brings more agility, he says, not only for course-correction but also to seize on evolving technologies, to adapt to changing business needs, and to ensure adoption of new processes and tools along the way.
Sankararaman stresses that his focus on sub-workflows isn’t about small tweaks and minor changes, because they’re all done in service of the larger objective of transforming the business. “We’re doing smaller items, incremental things, but still continuing that journey to a bigger goal,” he says. “Small things linked together very nicely achieve a bigger outcome.”
Redefining ‘transformation’ as change accelerates
Julie Averill, former EVP and global CIO of Lululemon and now CEO of Gold Thread and author of the book Chief Impact Officer, believes such updated perspectives on transformation are needed.
“It’s a super important topic right now because we’ve all been bedazzled by the word ‘transformation,’” she explains.
“We need to change, because thinking about transformation with a capital ‘T’ implies that it’s a program with a start and end date, that you can bring in consultants to help lead it, and that you can put together a project plan that addresses needs,” she says. “But the pace of business has changed, it has gone up tremendously, so now we need not a transformational program but continuous change. That’s transformation with a little ‘t,’ which means iteration and which brings more speed to change, teams who are close to the business, and continuous learning.”
Although Averill advocates for ongoing, smaller transformation, she still stresses the need for big objectives. Executives, she explains, must have a strategic outcome to guide all the smaller transformational initiatives. “The companies that I see achieving success,” she adds, “still start with a real problem to solve for. They still understand where they want to be.”
What sweeping transformation still gets right
Not all IT leaders believe large-scale transformations are problematic. Marco Bill, senior vice president and CIO of Red Hat, is one of them.
“I think in some cases you need to do big ‘T’ transformation,” he says. “Sometimes you just have to go for the full heart surgery.”
Bill points to transformation of its go-to-market stack as case in point. After trying to transform it piecemeal and failing to get traction, Bill and his C-suite colleagues planned for a multiyear transformation that launched in 2022 with a dedicated team and a top-down mandate for change.
The approach delivered the clarity, resources, and heft the transformation required to succeed, he says. That in turn got regional managers onboard in a way they hadn’t been for prior attempts at small-scale transformation. It also enabled the dedicated teams to build and implement new technologies and reengineer processes without having to support the existing stack, which was supported by an existing IT team.
“We weren’t flying the plane and building a new one at the same time,” Bill says, noting that this facilitated faster delivery of business objectives, including lower costs and improved process speed.
Striking the right transformational balance
But despite his defense of big transformation programs, Bill doesn’t discount the value of more bite-size transformation efforts. There’s need for both, he says.
Jose Baeza, CIO of BMI Group, a Standard Industries company headquartered in the UK, agrees.
Baeza, who defines transformation “as those moments where we change our business model (i.e., how we do business) or our operating model (i.e., how we organize ourselves),” believes there is a place for major transformation.
He points to an ERP rollout as an example, noting that it’s “an essential platform reset that allows an organization to fundamentally rethink its business processes, operating models, and customer interactions.”
But he’s also “a firm believer in a culture of continuous evolution, where smaller, more manageable transformations lead to big transformations over time.” He notes that “organizations have a finite capacity for deep operational shifts. Running major transformations too often or simultaneously can lead to change fatigue, ultimately undermining scope, delivery, and long-term adoption.”
Like other IT leaders, Baeza believes small bets have big payoffs, with continuous evolution yielding large-scale transformations over time while providing other benefits along the way.
“By breaking big visions into iterative building blocks, you give your organization the ability to course-correct in real-time while using technology as a force multiplier for growth,” he explains.
He says CIOs today must be able to deliver both those types of transformation — the capital “T” ones as well as the smaller, incremental ones.
“Just as important as a major transformation is bringing excellence into the day-to-day — driving tool adoption, staying ahead of market shifts, and fostering a high-performance culture,” he adds. “Our role as technology leaders isn’t just delivering systems. It’s creating an ecosystem where continuous, day-to-day innovation can flourish.”