by Esther Shein

5 hot digital transformation trends — and 2 going cold

Feature
Apr 17, 202310 mins
Digital TransformationIT LeadershipIT Strategy

From supporting hybrid work to proliferating micro transformations across the enterprise, digital transformation tactics and strategies are constantly evolving — even the very term itself.

microsoftteams
Credit: Shutterstock

Digital transformation has always been a continuous journey, one that should become an organizational core competency, with the introduction of digital services an ongoing imperative to evolve the business and stave off disruption.

While this may remain the case, subtleties are emerging about how digital transformation should be thought of, impacting how it should be undertaken. Within these schools of thought, what was once called digital transformation should now be viewed as business transformation because such initiatives encompass so much of the way organizations operate, and because technology alone does not a transformation make.

It’s that latter point that may be the biggest change in our perception of digital transformations. A framework for thinking about digital initiatives today is part digital strategy (new capabilities, new markets, and new products), part technology aligned with the strategy, and an ability to adapt to and adopt new processes, resources, and ways of working, according to Deloitte.   

“If you can only do one thing, focus your efforts on technologies aligned to strategy because it drives superior market value,’’ the firm says. 

With that in mind, here are five strategies, approaches, and technologies around digital transformation that are hot and two that have gone cold.

Hot: Debate about the term ‘digital transformation’

Depending on whom you ask, the very concept of digital transformation is either still the raison d’être of IT today — or it’s becoming a thing of the past. And while the discussion around this can seem semantic or even pedantic, there are meaningful impacts arising from the debate.

At Schneider Electric, “we don’t even use the term ‘digital transformation,’” but rather, ‘business transformation,’ says senior vice president and CIO Bobby Cain, who came from the business side of the company. “In order to transform how you work, the business has to lead the transformation.”  

Melanie Kalmar, corporate vice president, CIO, and chief digital officer of Dow, agrees. Speaking in a recent Gartner webcast, Kalmar said that digital transformation goes beyond technology. Further, IT is not going to drive digital transformation on its own, she said.


“The previous perception of being digitally driven was that IT would lead all of the change and that technology would be the driver,’’ Kalmar said. “Digital transformation is really about how people do their work differently and understanding IT wasn’t going to drive this on our own.”

She referred to digital transformation as “a team sport.” At Dow, each business now owns its digital strategy, and digital leaders have been placed in the business units to ensure data quality.

But Isaac Sacolick, founder of digital consultancy StarCIO, believes business transformations are more about mergers and acquisitions and outsourcing, and that digital, AI, and analytics fall under the purview of IT, so CIOs are expected to continue leading digital transformations. Results from the State of the CIO survey concur, as 84% of IT leaders say CIOs are more involved in leading digital transformation initiatives compared to their business counterparts. Moreover, 72% of line of business leaders agree.

Jim Ruga, CIO of Fictiv, a quote-to-order manufacturing provider for mechanical parts, says a lot of businesses in the manufacturing industry struggle with digital transformation because business leaders view it in the context of buying a big ERP system and expecting it to solve a problem.

“It’s the threading together of these systems [and] processes where decisions are made by humans, and you have to introduce machine learning and AI and glue them together to make these things effective,’’ he says. “It’s no longer just buying the software and ‘Wow, we’re digital.’”

Instead, IT needs to take these large systems and make them smart to realize the gains and benefits of labor or cost reduction, Ruga says. “You don’t get that by implementing systems off the shelf.”

Cold: The how of hybrid work

The concept of hybrid work, new for the majority of organizations when the effects of the pandemic reached a point where people started returning to the office on a part-time basis, is far less novel of late, and as such initiatives aimed at making it work have cooled since their apex just a year or so ago.

“People have figured it out based on the resources they have and the tools they have to support it,’’ Cain says. “Honestly, it’s becoming a tiresome conversation. I think it’s losing its relevancy.”

This is not something people need to learn; employees have figured out how they work best, he says.

Future work is focused on what people are doing and how they’re providing value, whereas hybrid work is about how do we continue operating when people won’t be in the office 100% of time, adds Sacolick. Yet, “what’s interesting is over 60% of companies in the tech space remain hybrid.”

In other words, if you haven’t figured out how to make hybrid work by now, you’re still likely not ramping up solutions to address it. In fact, enhancing hybrid work technologies was the No. 1 decreasing priority for IT leaders, according to the State of the CIO survey, and many CIOs have long been unraveling the ‘pandemic debt’ incurred by investing in digital productivity solutions during the height of the pandemic.

Hot: Digital trailblazers and micro transformations

With the CIO role changing to be more business-oriented and focused on both internal and external customer needs, CIOs need more of what Sacolick calls “digital trailblazers” who can act as “lieutenants.” These are people who “understand the lane they’re working in, whether it’s apps or security.” It’s incumbent upon CIOs to groom them to become leaders with “outside-in learning,’’ through a combination of attending nontechnical industry events and finding mentors outside the organization.

The trailblazers should be branched out into the business to run smaller transformation programs, he says.

Dean Kontul, executive vice president and CIO of KeyBank, is also a proponent of implementing micro transformations alongside large-scale transformations. 

The bank uses a pilot test-and-learn approach wherever possible. Along these lines, KeyBank uses consulting and outsourcing partners to accelerate the process. 

“Our most successful transformations rely on leadership across KeyBank and on speed of delivery with multiple impactful components delivered in parallel, versus waiting on a big-bang approach delivered all at once,” Kontul says.

This may not be bleeding edge, he notes, “but we certainly are forward-thinking and adopt new tools quickly and proactivity look to apply lessons learned from small initiatives with emerging technologies to broader use cases.”

Instead of the conversation being about a big, monolithic ERP transformation, CIOs should think about agility, Schneider Electric’s Cain says. “Do you think agile or are you agile? Look at [digital transformation] on a micro-scale and transform the way you work with a modular approach.”

Hot: Business-IT partnerships

Similar to Dow, Schneider’s IT group has been structured to be aligned with specific business domains “to better enable the business and be a better business partner.”

Not everything has to be enabled by technology, Cain adds. “You don’t want to just automate a crappy process — change the process.” Schneider uses an approach called a “power couple,” which pairs a domain or business leader and a digital leader together. They are responsible for the ‘what’ and ‘why’ and the digital leader is responsible for the ‘how’ and the ‘when.’

“When you partner those two people together … it’s very, very powerful and you don’t burn a lot of calories in solutioning and trying to do other people’s jobs and overwhelming people,’’ Cain says. “We utilize [them] in a dual delivery leadership model — the same people, the same rank, the same level and we put them together.”

Hot: Embedding AI in enterprise systems

There was a time when embedding AI and machine learning into enterprise and SaaS platforms fell to data science teams, but now, organizations are expanding those programs, Sacolick says.

“They’re looking to use AI and MI in ways that deliver value … beyond what marketing is saying [these platforms] can do. It’s not about the science but the application and getting the value without having to invest in the skillsets to build the models,” he says.

Take recommendation engines. They have been around for many years inside ecommerce and content management systems, he notes. “The CIO and IT have to make sure the information is presented to [the recommendation engine] in a way so it will make better decisions,’’ Sacolick says. “That often means expanding the context and data available to it.”

Ruga agrees, saying that applying AI or machine learning with “data inputs that make sense” makes large systems more valuable. At Fictiv, IT is doing that for quotes for manufacturing parts.

“Now you have something that has been educated by machine learning that has seen lots and lots of similar examples and can infer the conditions that are necessary to say, ‘This configuration or this design will cost you X dollars to make,’ and makes recommendations,’’ he says. “We are seeing that everywhere.”

Hot: Digitizing the manufacturing supply chain

Digitizing the entire supply chain is at the forefront for BSH, a Munich, Germany-based global provider of home appliances, says Berke Menekli, senior vice president of digital platform services, whose digital strategy tackles four pillars: enterprise processes, manufacturing processes, products, and the consumer journey.

BSH’s approach incorporates Industry 4.0, or I4.0, an IT-fueled strategy for improving efficiency using automation and data-driven operational decision-making.

To achieve this, BSH is investing in inbound/outbound logistics flow to maintain the continuity of production and supply chain automation “to ensure value creation toward our products can be transferred to our consumers,” Menekli says.

Initiatives such as these have become hot, he says, thanks to the advancement of supporting technologies such as machine learning and data lakes, which have become fast and strong enough to be operationally reliable in a manufacturing environment.

Taking that a step further, Ruga says it’s become more important to insulate the manufacturing supply chain, given global socioeconomic conditions.

“If I’m faced with a scenario like COVID or the war in Ukraine, and I have tons of people I employ and tons of vendors that depend on me and all of a sudden COVID hits, my supply chain collapses,’’ he says. Or “maybe I had a manufacturer in Ukraine that was producing unique parts for me, and … that factory got blown up and now I have to find a new vendor, which costs me time and money.”

A new trend is for manufacturers to vet their networks to insulate their supply chain and have the work managed for them, Ruga says.

“It’s not about whether I put Oracle in, it’s whether the collection of systems I’ve put in place insulate my business from risk,’’ he says. “An outsourced insulated supply chain de-risks things like supply chain disruption when COVID hits and a machine shop shuts down.’’

Cold: Traditional RPA

Some IT leaders are finding that robotic process automation is a lever-based approach involving the time-consuming process of collecting financial and operational data, and detailed process mapping, and doesn’t have enterprise scale. Many of the initial bots developed focused heavily on process efficiency, and this has limited opportunities for scalability, observers say.

Organizations must rethink how work is being done with bots that are broader in scope, or the investment in them will underdeliver.

Sacolick thinks RPA has become a band-aid. “I think what we’re doing is scripting on top of broken processes, in some cases, data technologies, and in many cases, a lack of APIs to get a backdoor into digital capabilities.” This is leading to an accumulation of bot debt because “any time I build a bot I have to continue to evolve and support it.”

He believes organizations will soon be talking about RPA more as a set of integrated tools, or what Sacolick calls hyperautomation, using low code and machine learning.  

“A bot is a piece of a solution, not a complete one,’’ he says. A lot of what they do is fill out forms and ‘screen scraping.’ In invoice processing, for example, you can either outsource the work or build a bot that will do some data entry internally instead of having people key the information into an ERP system.

That saves time and money and avoids mistakes and the need to change vendors, he says. But when a vendor changes their system or the company updates its ERP system, the bots will have to be changed, and that causes the debt, especially when the vendor doesn’t have an API the company can use, Sacolick says.

Another approach is to build a low-code system that flows into the ERP system through an API. “RPA is a tool to orchestrate a workflow, low code is a tool to build a workflow, and machine learning is tool so my workflows can be triggered based on analytics,’’ he explains. “RPA will shift from being a platform to a tool. It’s providing one capability; it’s not that powerful alone.”