Skip to main content

Gartner: Digital Business Requires Growth Mindset - Not Just Technology

When embarking on a digital business transformation, too often organizations ignore the need to change the mindset of their staff, according to Gartner, Inc. A technology shift not backed up by a corresponding cultural shift puts the success of a digital business initiative at risk.

"For any transformation to be successful, people need to buy into your vision," said Aashish Gupta, Research Analyst at Gartner. "The culture aspect and the technology demand equal attention from the application leader, because culture will form the backbone of all change initiatives for their digital business transformation. Staff trapped in a "fixed" mindset may slow down or, worse, derail the digital business transformation initiatives of the company."

While every organization has its own unique culture, it must understand the nuance of attracting and retaining talent with values and mindsets aligned to the mission and culture of the organization. "This requires a healthy and psychologically safe team environment within a growth mindset organizational culture," said Gupta.

"Psychologically safe" means making co-workers and team members feel that they will not be punished or humiliated when taking interpersonal risks, such as asking for help, admitting mistakes and vulnerabilities, or expressing concerns.

Applying a growth mindset culture has been a success in well-known online companies

Applying a growth mindset culture has been a success in well-known online companies. An online clothes and shoe retailer instructs all of its new hires to experience its call center. The involvement, which includes training and time spent on answering customer calls, allows employees to gain a holistic view of the business and understand that customer service is the backbone of it.

"Cultural change requires significant investment," said Gupta. "Organizations need a way to measure the value that investment is delivering."

To help application leaders implement mindset change among their staff, Gartner has developed a four-step plan to instigate mindset change:

1. Vision

Create a compelling vision that can be shared as a story to inspire and motivate desire for the change. Everybody should understand what is meant by a growth and product mindset.

"A growth mindset demands people to be comfortable with the speed of the digital era, and they must be willing to make quick and risky bets instead of slow and safe bets. A product mindset requires people to own what they create and take full responsibility in its success and failure," said Gupta.

2. Define

Define key behavioral attributes that reflect the intended mindset change. These can be individual accomplishments that contribute to the team, business or customer results; a greater number of projects owned; or acquiring new skills.

3. Implement

HR should be involved to ensure that performance metrics, as well as the descriptions of roles and responsibilities, are updated to include these key behavioral attributes, before rolling them out to all departments.

"Acceptance will happen only if the change is visible throughout the organization. You should incentivize people to share knowledge or learn new skills," noted Gupta.

4. Measure, Monitor and Wait

Allow some time for the changes to percolate. Continuously measure and monitor the changes through anonymous surveys.

"You can ask employees if they understand the company's messaging around culture, or if they see their leaders practicing it and if they find their colleagues taking the initiative seriously," said Gupta. "Also, remember to track performance measures."

"Be patient. Fostering a growth mindset culture that requires behavior changes among your staff takes time," Gupta concluded. "However, the rewards are considerable as everyone perseveres, learns, grows and accepts that potential is nurtured, not predetermined."

The Latest

Like most digital transformation shifts, organizations often prioritize productivity and leave security and observability to keep pace. This usually translates to both the mass implementation of new technology and fragmented monitoring and observability (M&O) tooling. In the era of AI and varied cloud architecture, a disparate observability function can be dangerous. IT teams will lack a complete picture of their IT environment, making it harder to diagnose issues while slowing down mean time to resolve (MTTR). In fact, according to recent data from the SolarWinds State of Monitoring & Observability Report, 77% of IT personnel said the lack of visibility across their on-prem and cloud architecture was an issue ...

In MEAN TIME TO INSIGHT Episode 23, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses the NetOps labor shortage ... 

Technology management is evolving, and in turn, so is the scope of FinOps. The FinOps Foundation recently updated their mission statement from "advancing the people who manage the value of cloud" to "advancing the people who manage the value of technology." This seemingly small change solidifies a larger evolution: FinOps practitioners have organically expanded to be focused on more than just cloud cost optimization. Today, FinOps teams are largely — and quickly — expanding their job descriptions, evolving into a critical function for managing the full value of technology ...

Enterprises are under pressure to scale AI quickly. Yet despite considerable investment, adoption continues to stall. One of the most overlooked reasons is vendor sprawl ... In reality, no organization deliberately sets out to create sprawling vendor ecosystems. More often, complexity accumulates over time through well-intentioned initiatives, such as enterprise-wide digital transformation efforts, point solutions, or decentralized sourcing strategies ...

Nearly every conversation about AI eventually circles back to compute. GPUs dominate the headlines while cloud platforms compete for workloads and model benchmarks drive investment decisions. But underneath that noise, a quieter infrastructure challenge is taking shape. The real bottleneck in enterprise AI is not processing power, it is the ability to store, manage and retrieve the relentless volumes of data that AI systems generate, consume and multiply ...

The 2026 Observability Survey from Grafana Labs paints a vivid picture of an industry maturing fast, where AI is welcomed with careful conditions, SaaS economics are reshaping spending decisions, complexity remains a defining challenge, and open standards continue to underpin it all ...

The observability industry has an evolving relationship with AI. We're not skeptics, but it's clear that trust in AI must be earned ... In Grafana Labs' annual Observability Survey, 92% said they see real value in AI surfacing anomalies before they cause downtime. Another 91% endorsed AI for forecasting and root cause analysis. So while the demand is there, customers need it to be trustworthy, as the survey also found that the practitioners most enthusiastic about AI are also the most insistent on explainability ...

In the modern enterprise, the conversation around AI has moved past skepticism toward a stage of active adoption. According to our 2026 State of IT Trends Report: The Human Side of Autonomous AI, nearly 90% of IT professionals view AI as a net positive, and this optimism is well-founded. We are seeing agentic AI move beyond simple automation to actively streamlining complex data insights and eliminating the manual toil that has long hindered innovation. However, as we integrate these autonomous agents into our ecosystems, the fundamental DNA of the IT role is evolving ...

AI workloads require an enormous amount of computing power ... What's also becoming abundantly clear is just how quickly AI's computing needs are leading to enterprise systems failure. According to Cockroach Labs' State of AI Infrastructure 2026 report, enterprise systems are much closer to failure than their organizations realize. The report ... suggests AI scale could cause widespread failures in as little as one year — making it a clear risk for business performance and reliability.

The quietest week your engineering team has ever had might also be its best. No alarms going off. No escalations. No frantic Teams or Slack threads at 2 a.m. Everything humming along exactly as it should. And somewhere in a leadership meeting, someone looks at the metrics dashboard, sees a flat line of incidents and says: "Seems like things are pretty calm over there. Do we really need all those people?" ... I've spent many years in engineering, and this pattern keeps repeating ...

Gartner: Digital Business Requires Growth Mindset - Not Just Technology

When embarking on a digital business transformation, too often organizations ignore the need to change the mindset of their staff, according to Gartner, Inc. A technology shift not backed up by a corresponding cultural shift puts the success of a digital business initiative at risk.

"For any transformation to be successful, people need to buy into your vision," said Aashish Gupta, Research Analyst at Gartner. "The culture aspect and the technology demand equal attention from the application leader, because culture will form the backbone of all change initiatives for their digital business transformation. Staff trapped in a "fixed" mindset may slow down or, worse, derail the digital business transformation initiatives of the company."

While every organization has its own unique culture, it must understand the nuance of attracting and retaining talent with values and mindsets aligned to the mission and culture of the organization. "This requires a healthy and psychologically safe team environment within a growth mindset organizational culture," said Gupta.

"Psychologically safe" means making co-workers and team members feel that they will not be punished or humiliated when taking interpersonal risks, such as asking for help, admitting mistakes and vulnerabilities, or expressing concerns.

Applying a growth mindset culture has been a success in well-known online companies

Applying a growth mindset culture has been a success in well-known online companies. An online clothes and shoe retailer instructs all of its new hires to experience its call center. The involvement, which includes training and time spent on answering customer calls, allows employees to gain a holistic view of the business and understand that customer service is the backbone of it.

"Cultural change requires significant investment," said Gupta. "Organizations need a way to measure the value that investment is delivering."

To help application leaders implement mindset change among their staff, Gartner has developed a four-step plan to instigate mindset change:

1. Vision

Create a compelling vision that can be shared as a story to inspire and motivate desire for the change. Everybody should understand what is meant by a growth and product mindset.

"A growth mindset demands people to be comfortable with the speed of the digital era, and they must be willing to make quick and risky bets instead of slow and safe bets. A product mindset requires people to own what they create and take full responsibility in its success and failure," said Gupta.

2. Define

Define key behavioral attributes that reflect the intended mindset change. These can be individual accomplishments that contribute to the team, business or customer results; a greater number of projects owned; or acquiring new skills.

3. Implement

HR should be involved to ensure that performance metrics, as well as the descriptions of roles and responsibilities, are updated to include these key behavioral attributes, before rolling them out to all departments.

"Acceptance will happen only if the change is visible throughout the organization. You should incentivize people to share knowledge or learn new skills," noted Gupta.

4. Measure, Monitor and Wait

Allow some time for the changes to percolate. Continuously measure and monitor the changes through anonymous surveys.

"You can ask employees if they understand the company's messaging around culture, or if they see their leaders practicing it and if they find their colleagues taking the initiative seriously," said Gupta. "Also, remember to track performance measures."

"Be patient. Fostering a growth mindset culture that requires behavior changes among your staff takes time," Gupta concluded. "However, the rewards are considerable as everyone perseveres, learns, grows and accepts that potential is nurtured, not predetermined."

The Latest

Like most digital transformation shifts, organizations often prioritize productivity and leave security and observability to keep pace. This usually translates to both the mass implementation of new technology and fragmented monitoring and observability (M&O) tooling. In the era of AI and varied cloud architecture, a disparate observability function can be dangerous. IT teams will lack a complete picture of their IT environment, making it harder to diagnose issues while slowing down mean time to resolve (MTTR). In fact, according to recent data from the SolarWinds State of Monitoring & Observability Report, 77% of IT personnel said the lack of visibility across their on-prem and cloud architecture was an issue ...

In MEAN TIME TO INSIGHT Episode 23, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses the NetOps labor shortage ... 

Technology management is evolving, and in turn, so is the scope of FinOps. The FinOps Foundation recently updated their mission statement from "advancing the people who manage the value of cloud" to "advancing the people who manage the value of technology." This seemingly small change solidifies a larger evolution: FinOps practitioners have organically expanded to be focused on more than just cloud cost optimization. Today, FinOps teams are largely — and quickly — expanding their job descriptions, evolving into a critical function for managing the full value of technology ...

Enterprises are under pressure to scale AI quickly. Yet despite considerable investment, adoption continues to stall. One of the most overlooked reasons is vendor sprawl ... In reality, no organization deliberately sets out to create sprawling vendor ecosystems. More often, complexity accumulates over time through well-intentioned initiatives, such as enterprise-wide digital transformation efforts, point solutions, or decentralized sourcing strategies ...

Nearly every conversation about AI eventually circles back to compute. GPUs dominate the headlines while cloud platforms compete for workloads and model benchmarks drive investment decisions. But underneath that noise, a quieter infrastructure challenge is taking shape. The real bottleneck in enterprise AI is not processing power, it is the ability to store, manage and retrieve the relentless volumes of data that AI systems generate, consume and multiply ...

The 2026 Observability Survey from Grafana Labs paints a vivid picture of an industry maturing fast, where AI is welcomed with careful conditions, SaaS economics are reshaping spending decisions, complexity remains a defining challenge, and open standards continue to underpin it all ...

The observability industry has an evolving relationship with AI. We're not skeptics, but it's clear that trust in AI must be earned ... In Grafana Labs' annual Observability Survey, 92% said they see real value in AI surfacing anomalies before they cause downtime. Another 91% endorsed AI for forecasting and root cause analysis. So while the demand is there, customers need it to be trustworthy, as the survey also found that the practitioners most enthusiastic about AI are also the most insistent on explainability ...

In the modern enterprise, the conversation around AI has moved past skepticism toward a stage of active adoption. According to our 2026 State of IT Trends Report: The Human Side of Autonomous AI, nearly 90% of IT professionals view AI as a net positive, and this optimism is well-founded. We are seeing agentic AI move beyond simple automation to actively streamlining complex data insights and eliminating the manual toil that has long hindered innovation. However, as we integrate these autonomous agents into our ecosystems, the fundamental DNA of the IT role is evolving ...

AI workloads require an enormous amount of computing power ... What's also becoming abundantly clear is just how quickly AI's computing needs are leading to enterprise systems failure. According to Cockroach Labs' State of AI Infrastructure 2026 report, enterprise systems are much closer to failure than their organizations realize. The report ... suggests AI scale could cause widespread failures in as little as one year — making it a clear risk for business performance and reliability.

The quietest week your engineering team has ever had might also be its best. No alarms going off. No escalations. No frantic Teams or Slack threads at 2 a.m. Everything humming along exactly as it should. And somewhere in a leadership meeting, someone looks at the metrics dashboard, sees a flat line of incidents and says: "Seems like things are pretty calm over there. Do we really need all those people?" ... I've spent many years in engineering, and this pattern keeps repeating ...