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

In MEAN TIME TO INSIGHT Episode 24, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses network observability tool sprawl ... 

In cloud-native systems, scaling is often as simple as moving a slider. For on-premise databases, the stakes are different. Over-provisioning hardware is expensive. Under-provisioning leads to performance bottlenecks that are difficult to fix once the equipment is in the rack ...

When most people think about cybersecurity, they picture firewalls, encryption, and access controls — technical tools designed to protect systems and data. But beneath the technology lies a deeper set of principles about trust, decision-making, and resilience ... The best leaders don't eliminate risk. They manage it intelligently. And in many ways, cybersecurity offers a surprisingly useful playbook for doing exactly that ...

Many organizations assumed their infrastructure strategy was settled. It had been implemented, optimized and built into long-term plans. Recent changes in technology and vendor consolidation are forcing a second look. Cloud outages and licensing changes have exposed how much dependency exists on a small number of platforms. As a result, organizations are reevaluating whether those decisions still hold up under current conditions ...

Edge AI is strategically embedded in core IT and infrastructure spending across industries, according to the 2026 Edge AI Survey from ZEDEDA. The research shows that 83% of C-suite and IT executive respondents say edge AI is important to their core business strategy ...

As AI adoption accelerates, operational complexity — not model intelligence — is becoming the primary barrier to reliable AI at scale, according to the State of AI Engineering 2026 from Datadog ... The report highlights a compounding complexity challenge as AI systems scale ... Around 5% of AI model requests fail in production, with nearly 60% of those failures caused by capacity limits ...

For years, production operations teams have treated alert fatigue as a quality-of-life problem: something that makes on-call rotations miserable but isn't considered a direct contributor to outages. That framing doesn't capture how these systems fail, and we now have data to show why. More importantly, it's now clear alert fatigue is a symptom of a deeper issue: production systems have outgrown the current operational approaches ...

I was on a customer call last fall when an enterprise architect said something I haven't been able to shake. Her team had just spent four months trying to swap one AI vendor for another. The original plan said three weeks. "We didn't switch vendors," she told me. "We rebuilt half our integrations and discovered what we'd actually been depending on." Most enterprise leaders don't expect that to be the experience ...

Ask any senior SRE or platform engineer what keeps them up at night, and the answer probably isn't the monitoring tool — it's the data feeding it. The proliferation of APM, observability, and AIOps platforms has created a telemetry sprawl problem that most teams manage reactively rather than architect proactively. Metrics are going to one platform. Traces routed somewhere else. Logs duplicated across multiple backends because nobody wants to be caught without them when something breaks. Every redundant stream costs money ...

80% of respondents agree that the IT role is shifting from operators to orchestrators, according to the 2026 IT Trends Report: The Human Side of Autonomous IT from SolarWinds ...

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

In MEAN TIME TO INSIGHT Episode 24, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses network observability tool sprawl ... 

In cloud-native systems, scaling is often as simple as moving a slider. For on-premise databases, the stakes are different. Over-provisioning hardware is expensive. Under-provisioning leads to performance bottlenecks that are difficult to fix once the equipment is in the rack ...

When most people think about cybersecurity, they picture firewalls, encryption, and access controls — technical tools designed to protect systems and data. But beneath the technology lies a deeper set of principles about trust, decision-making, and resilience ... The best leaders don't eliminate risk. They manage it intelligently. And in many ways, cybersecurity offers a surprisingly useful playbook for doing exactly that ...

Many organizations assumed their infrastructure strategy was settled. It had been implemented, optimized and built into long-term plans. Recent changes in technology and vendor consolidation are forcing a second look. Cloud outages and licensing changes have exposed how much dependency exists on a small number of platforms. As a result, organizations are reevaluating whether those decisions still hold up under current conditions ...

Edge AI is strategically embedded in core IT and infrastructure spending across industries, according to the 2026 Edge AI Survey from ZEDEDA. The research shows that 83% of C-suite and IT executive respondents say edge AI is important to their core business strategy ...

As AI adoption accelerates, operational complexity — not model intelligence — is becoming the primary barrier to reliable AI at scale, according to the State of AI Engineering 2026 from Datadog ... The report highlights a compounding complexity challenge as AI systems scale ... Around 5% of AI model requests fail in production, with nearly 60% of those failures caused by capacity limits ...

For years, production operations teams have treated alert fatigue as a quality-of-life problem: something that makes on-call rotations miserable but isn't considered a direct contributor to outages. That framing doesn't capture how these systems fail, and we now have data to show why. More importantly, it's now clear alert fatigue is a symptom of a deeper issue: production systems have outgrown the current operational approaches ...

I was on a customer call last fall when an enterprise architect said something I haven't been able to shake. Her team had just spent four months trying to swap one AI vendor for another. The original plan said three weeks. "We didn't switch vendors," she told me. "We rebuilt half our integrations and discovered what we'd actually been depending on." Most enterprise leaders don't expect that to be the experience ...

Ask any senior SRE or platform engineer what keeps them up at night, and the answer probably isn't the monitoring tool — it's the data feeding it. The proliferation of APM, observability, and AIOps platforms has created a telemetry sprawl problem that most teams manage reactively rather than architect proactively. Metrics are going to one platform. Traces routed somewhere else. Logs duplicated across multiple backends because nobody wants to be caught without them when something breaks. Every redundant stream costs money ...

80% of respondents agree that the IT role is shifting from operators to orchestrators, according to the 2026 IT Trends Report: The Human Side of Autonomous IT from SolarWinds ...