Incident sheet · /transformation

Filed
Read
5 min · 987 words
Severity
Routine

CIOs Split on 'Big T' Transformation as AI Pace Kills Multiyear Plans

First Horizon's CIO says multiyear programs deliver stale outcomes as AI advances monthly, while Red Hat's CIO defends big-bang programs launched in 2022. Both models now coexist.

IT leaders rethink ‘Big T’ transformation for a new era
FeedIT leaders rethink ‘Big T’ transformation for a new era — Pexels / pixabay

Event log

  1. First Horizon CIO Mohan Sankararaman says AI moves in monthly increments, making two- to three-year transformation programs stale on delivery.
  2. His loan origination transformation would take 24 months as one program; he is instead reimagining individual sub-workflows.
  3. Red Hat launched a multiyear go-to-market stack transformation in 2022 after piecemeal attempts failed.
  4. BMI Group CIO Jose Baeza warns that simultaneous major transformations cause change fatigue.
  5. Former Lululemon global CIO Julie Averill now advocates 'little t' continuous change over dated programs.

By Rebecca Stone

Multiyear IT transformation programs now produce stale outcomes because AI advances in monthly increments, according to First Horizon CIO Mohan Sankararaman, who has abandoned large-scale programs in favor of continuous, workflow-level change.

Sankararaman ran transformations for years as monumental multiyear IT programs. He now defines them differently. His transformations target smaller changes to how work gets done.

"The definition of 'transformation' has changed," Sankararaman said. "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."

Why did the old model break?

Past transformations focused on implementing new technologies, with success measured by IT-type metrics, Sankararaman said. Cloud migrations illustrate the pattern. Progress was counted by how many applications IT moved to the cloud and how many waited in line.

Today's smaller transformations work differently. IT and the business use technology — most often AI — to reimagine a single workflow (a discrete task sequence inside a larger business process) to deliver a business outcome such as improved time to market. Teams then reengineer another workflow, and another, to improve that outcome continuously.

The increasing pace of change drives the shift. "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," Sankararaman said. "Three years is a very long time in AI think."

Incremental transformation allows easier course-correction. It also leverages domain expertise better, because business users team with IT to reimagine their daily tasks rather than weigh in on companywide processes.

Sankararaman cited his current work on loan origination, a critical process for every bank. "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 said.

The approach adds agility. It enables course-correction, adoption of evolving technologies, adaptation to changing business needs, and adoption of new processes along the way. He stressed the work is not minor tweaking. "We're doing smaller items, incremental things, but still continuing that journey to a bigger goal," he said. "Small things linked together very nicely achieve a bigger outcome."

What do other CIOs say?

Julie Averill, former EVP and global CIO of Lululemon and now CEO of Gold Thread and author of the book Chief Impact Officer, endorsed the shift. "It's a super important topic right now because we've all been bedazzled by the word 'transformation,'" she said.

Capital 'T' transformation implies a program with a start and end date, outside consultants, and a project plan, she said. "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."

Averill still requires big objectives. Executives must set a strategic outcome to guide smaller initiatives. "The companies that I see achieving success still start with a real problem to solve for. They still understand where they want to be," she said.

Where does big transformation still work?

Marco Bill, senior vice president and CIO of Red Hat, defended large-scale programs. "I think in some cases you need to do big 'T' transformation," he said. "Sometimes you just have to go for the full heart surgery."

Red Hat's go-to-market stack transformation proves his point. Earlier piecemeal attempts failed to gain traction. Bill and his C-suite colleagues then planned a multiyear transformation that launched in 2022 with a dedicated team and a top-down mandate.

The approach delivered clarity, resources and heft, Bill said. Regional managers joined an effort they had resisted before. Dedicated teams built and implemented new technologies and reengineered processes without supporting the existing stack, which a separate IT team maintained.

"We weren't flying the plane and building a new one at the same time," Bill said. The structure delivered lower costs and improved process speed. Bill still sees value in bite-size efforts. Both types are needed, he said.

How do CIOs strike the balance?

Jose Baeza, CIO of BMI Group, a Standard Industries company headquartered in the UK, agreed on the need for both. He defines transformation as moments where the company changes its business model (how it does business) or its operating model (how it organizes itself).

Major programs retain a place. Baeza cited an ERP rollout as "an essential platform reset that allows an organization to fundamentally rethink its business processes, operating models, and customer interactions."

But he called himself "a firm believer in a culture of continuous evolution, where smaller, more manageable transformations lead to big transformations over time." He warned 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."

"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," Baeza said.

CIOs must deliver both types today, he said. "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 said. "Our role as technology leaders isn't just delivering systems. It's creating an ecosystem where continuous, day-to-day innovation can flourish."

via cio.com/feed/ (Source)

Filed under

  • ai-transformation
  • digital-transformation
  • it-leadership
  • incremental-change
Share this article:

More from Rebecca Stone

Rebecca Stone

Show full bio

Senior reporter covering money, funding and market shifts around enterprise information technology and the leaders who run at CIO Monitor.

199 articles

The newsroom digest

One email a day with the stories that matter. No noise.

By subscribing you agree to the privacy policy.

Cross-references

‹ Previous articleNext article ›