As organizations continue to embrace digital transformation, they are finding that digital business is not as simple as buying the latest technology — it requires significant changes to culture and systems. A recent Gartner, Inc. survey found that only a small number of organizations have been able to successfully scale their digital initiatives beyond the experimentation and piloting stages.
"The reality is that digital business demands different skills, working practices, organizational models and even cultures," said Marcus Blosch, Research VP at Gartner. "To change an organization designed for a structured, ordered, process-oriented world to one designed for ecosystems, adaptation, learning and experimentation is hard. Some organizations will navigate that change, and others that can't change will become outdated and be replaced."
Gartner has identified six barriers that CIOs must overcome to transform their organization into a digital business:
Barrier No. 1: A Change-Resisting Culture
Digital innovation can be successful only in a culture of collaboration. People have to be able to work across boundaries and explore new ideas. In reality, most organizations are stuck in a culture of change-resistant silos and hierarchies.
"Culture is organizational 'dark matter' — you can't see it, but its effects are obvious," said Blosch. "The challenge is that many organizations have developed a culture of hierarchy and clear boundaries between areas of responsibilities. Digital innovation requires the opposite: collaborative cross-functional and self-directed teams that are not afraid of uncertain outcomes."
CIOs aiming to establish a digital culture should start small: Define a digital mindset, assemble a digital innovation team, and shield it from the rest of the organization to let the new culture develop. Connections between the digital innovation and core teams can then be used to scale new ideas and spread the culture.
Barrier No. 2: Limited Sharing and Collaboration
The lack of willingness to share and collaborate is a challenge not only at the ecosystem level but also inside the organization. Issues of ownership and control of processes, information and systems make people reluctant to share their knowledge. Digital innovation with its collaborative cross-functional teams is often very different from what employees are used to with regards to functions and hierarchies — resistance is inevitable.
"It's not necessary to have everyone on board in the early stages. Try to find areas where interests overlap, and create a starting point. Build a first version, test the idea and use the success story to gain the momentum needed for the next step," said Blosch.
Barrier No. 3: The Business Isn't Ready
Many business leaders are caught up in the hype around digital business. But when the CIO or CDO wants to start the transformation process, it turns out that the business doesn't have the skills or resources needed.
"CIOs should address the digital readiness of the organization to get an understanding of both business and IT readiness," Blosch advised. "Then, focus on the early adopters with the willingness and openness to change and leverage digital. But keep in mind that digital may just not be relevant to certain parts of the organization."
Barrier No. 4: The Talent Gap
Most organizations follow a traditional pattern — organized into functions such as IT, sales and supply chain and largely focused on operations. Change can be slow in this kind of environment.
Digital innovation requires an organization to adopt a different approach. People, processes and technology blend to create new business models and services. Employees need new skills focused on innovation, change and creativity along with the new technologies themselves, such as artificial intelligence (AI) and the Internet of Things (IoT).
"There are two approaches to breach the talent gap — upskill and bimodal," said Blosch. "In smaller or more innovative organizations, it is possible to redefine individuals' roles to include more skills and competencies needed to support digital. In other organizations, using a bimodal approach makes sense by creating a separate group to handle innovation with the requisite skill set."
Barrier No. 5: The Current Practices Don't Support the Talent
Having the right talent is essential, and having the right practices lets the talent work effectively. Highly structured and slow traditional processes don't work for digital. There are no tried and tested models to implement, but every organization has to find the practices that suits it best.
"Some organizations may shift to a product management-based approach for digital innovations because it allows for multiple iterations. Operational innovations can follow the usual approaches until the digital team is skilled and experienced enough to extend its reach and share the learned practices with the organization," Blosch explained.
Barrier No. 6: Change Isn't Easy
It's often technically challenging and expensive to make digital work. Developing platforms, changing the organizational structure, creating an ecosystem of partners — all of this costs time, resources and money.
Over the long term, enterprises should build the organizational capabilities that make change simpler and faster. To do that, they should develop a platform-based strategy that supports continuous change and design principles and then innovate on top of that platform, allowing new services to draw from the platform and its core services.
The Latest
APMdigest and leading IT research firm Enterprise Management Associates (EMA) are partnering to bring you the EMA-APMdigest Podcast, a new podcast focused on the latest technologies impacting IT Operations. In Episode 2 - Part 1 Pete Goldin, Editor and Publisher of APMdigest, discusses Network Observability with Shamus McGillicuddy, Vice President of Research, Network Infrastructure and Operations, at EMA ...
CIOs have stepped into the role of digital leader and strategic advisor, according to the 2023 Global CIO Survey from Logicalis ...
Synthetic monitoring is crucial to deploy code with confidence as catching bugs with E2E tests on staging is becoming increasingly difficult. It isn't trivial to provide realistic staging systems, especially because today's apps are intertwined with many third-party APIs ...
Recent EMA field research found that ServiceOps is either an active effort or a formal initiative in 78% of the organizations represented by a global panel of 400+ IT leaders. It is relatively early but gaining momentum across industries and organizations of all sizes globally ...
Managing availability and performance within SAP environments has long been a challenge for IT teams. But as IT environments grow more complex and dynamic, and the speed of innovation in almost every industry continues to accelerate, this situation is becoming a whole lot worse ...
Harnessing the power of network-derived intelligence and insights is critical in detecting today's increasingly sophisticated security threats across hybrid and multi-cloud infrastructure, according to a new research study from IDC ...
Recent research suggests that many organizations are paying for more software than they need. If organizations are looking to reduce IT spend, leaders should take a closer look at the tools being offered to employees, as not all software is essential ...
Organizations are challenged by tool sprawl and data source overload, according to the Grafana Labs Observability Survey 2023, with 52% of respondents reporting that their companies use 6 or more observability tools, including 11% that use 16 or more.
An array of tools purport to maintain availability — the trick is sorting through the noise to find the right one. Let us discuss why availability is so important and then unpack the ROI of deploying Artificial Intelligence for IT Operations (AIOps) during an economic downturn ...
Development teams so often find themselves rushing to get a release out on time. When it comes time for testing, the software works fine in the lab. But, when it's released, customers report a bunch of bugs. How does this happen? Why weren't the flaws found in QA? ...