Track · Product Strategy4 min read
CIOs Split on 'Big T' Transformation as AI Resets the Clock
First Horizon's CIO now reengineers loan-origination sub-workflows instead of running 24-month programs, as AI's monthly pace makes multiyear outcomes stale.

Context
First Horizon CIO Mohan Sankararaman says a 24-month loan-origination reengineering is being broken into sub-workflows
Red Hat launched a multiyear go-to-market transformation in 2022 after piecemeal attempts failed
Julie Averill, former Lululemon global CIO, advocates 'little t' continuous change over start-end programs
BMI Group CIO Jose Baeza warns simultaneous major transformations cause change fatigue
Sankararaman argues AI moves in monthly increments, staling three-year program outcomes
First Horizon CIO Mohan Sankararaman now runs transformations as continuous sub-workflow reengineering, not multiyear programs — because, as he puts it, a two- or three-year program delivers stale outcomes when AI advances in monthly increments.
"The definition of 'transformation' has changed," Sankararaman 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 there is not a start and stop point. It's an ongoing journey that never ends."
For product leaders, his argument is a direct challenge to annual roadmap planning. Old-style transformations measured success in IT metrics — how many apps moved to cloud, how many queued next. Today's smaller changes measure business outcomes such as improved time to market, with teams reengineering one workflow, then the next, inside a larger process.
Why sub-workflows beat one big program
Sankararaman is applying the approach to loan origination, a critical process for every bank. "I could say I want to engineer this whole thing, and it would take 24 months," he says. "But it's made up of multiple sub-workflows, so we're looking at each sub-workflow and reimagining it."
The benefits he claims:
- easier course-correction mid-flight
- faster adoption of evolving technologies
- adaptation to changing business needs
- better use of domain expertise, because business users help reimagine their own daily tasks rather than review companywide processes
He insists this is not small thinking. "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."
What does 'little t' transformation actually mean?
Julie Averill — former EVP and global CIO of Lululemon, now CEO of Gold Thread and author of Chief Impact Officer — frames the shift as a vocabulary problem. "We've all been bedazzled by the word 'transformation,'" she says.
"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," she explains. "But the pace of business has changed. We need not a transformational program but continuous change — transformation with a little 't,' which means iteration and which brings more speed to change, teams close to the business, and continuous learning."
Her caveat matters for anyone tempted to go fully incremental: executives still need a strategic outcome guiding the smaller initiatives. "The companies that I see achieving success still start with a real problem to solve for," she says. "They still understand where they want to be." Little-t without a north star is just tinkering.
When does big 'T' still win?
Marco Bill, senior vice president and CIO of Red Hat, argues some transformations cannot be sliced small. "Sometimes you just have to go for the full heart surgery," he says.
His case: Red Hat's go-to-market stack. Earlier piecemeal attempts failed to gain traction. So in 2022 Bill and his C-suite colleagues launched a multiyear transformation with a dedicated team and a top-down mandate. That structure gave the effort clarity, resources and heft — and won over regional managers who had resisted earlier small-scale attempts.
Critically, the dedicated team built and implemented new technology without maintaining the existing stack, which a separate IT team supported. "We weren't flying the plane and building a new one at the same time," Bill says. The result was faster delivery of business objectives, including lower costs and improved process speed.
His position is not either/or. There is need for both, he says.
Where is the balance point?
Jose Baeza, CIO of BMI Group, a Standard Industries company headquartered in the UK, defines transformation as moments where the business model or operating model changes. Major programs still have a place — an ERP rollout is "an essential platform reset that allows an organization to fundamentally rethink its business processes, operating models, and customer interactions," he says.
But he warns of a hard capacity limit: "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."
His prescription: "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." CIOs, he says, must deliver both types — the capital-T resets and day-to-day excellence in tool adoption, market awareness and culture-building. "Our role as technology leaders isn't just delivering systems. It's creating an ecosystem where continuous, day-to-day innovation can flourish."
The practical takeaway for product teams: pick the transformation size the failure mode demands — heart surgery when piecemeal attempts have already stalled, continuous iteration when AI's monthly cadence will outrun any three-year plan.
via cio.com (Source)
More from Marcus Bennett
Show full bio
Market editor covering regulation, policy and their impact on product management at Roadmap File.
56 articles