Skip to main content

Gartner: 60% of Employees Experience Frustration with New Software

Over Half of Users Have Wished Management Would Re-Instate Old Systems

More than half (60%) of workers said new software had occasionally or frequently frustrated them within the past 24 months, according to a new survey by Gartner, Inc.

In fact, 56% of users said new software had made them wish management would bring the old system back.

"The democratization and consumerization of IT has resulted in employees who have more discretion over what software they use and how they use it," said Craig Roth, Research VP at Gartner. "Software product leaders often focus on adding new features to keep up with competitors, but this leads to overly complex products with poor user experience (UX)."

The global Gartner survey revealed three ways in which users can impact enterprise software adoption:

1. Personal Adoption

The survey found that 81% of software users have taken some kind of action — positive or negative — after a notable experience with software. For example, 40% of users have resisted using applications after a negative experience by using minimal features, avoiding or delaying use. After a positive experience with an application, however, 41% of users spent more time delving further into its features.

"Depth of application usage can have a significant impact on the value an organization receives from software. That perceived value becomes important when renewal or upgrade time rolls around," said Roth. "Consumption of new features helps technology providers increase the stickiness of a product, but when users ignore advanced features, vendors have less influence to secure upsells or renewals and stay ahead of competition."

2. Influencing Others to Adopt or Avoid

The survey also found that users frequently share their opinions on software with peers, with IT and with business leaders, either proactively or in response to requests for input. This "word of mouth" can start a chain reaction that influences whether others adopt or avoid applications.

For example, 42% of survey respondents said they have complained to peers after a negative software experience, while 38% have recommended an application to peers after a positive experience.
Additionally, 42% have shared negative experiences with IT, and 25% have shared those experiences with business management.

Social media is also becoming an important outlet for sharing opinions on software, with 10% of respondents indicating they had left reviews on social media or review websites after a negative experience with an application.

When users were asked what actions software vendors could take to make them more likely to recommend their products to peers, IT or business leaders, the top answer was to make products easier to use, cited by 51% of respondents. Adding missing features was a distant third place, cited by 30%.

3. Self-Purchasing

Enterprise software users can also act as buyers in certain instances. The Gartner survey found that 34% of users say their IT department allows them to choose most of the software they use. In some instances, users may also self-acquire software through personal or business credit cards, or users will be billed based on consumption, although these arrangements are not yet commonplace.

"With SaaS revenue growing faster than the overall software industry, providers increasingly find themselves in a continuous purchase cycle," said Roth. "In this competitive market, maintaining high-value application usage by making UX a core competency is critical for generating positive business outcomes."

Methodology: The Gartner 2021 User Influence on Software Decisions Survey was conducted from April through June 2021 among 4,953 respondents in organizations with at least 100 employees in the US, France, Germany and Singapore. Respondents were required to be full-time workers or staff (i.e., not managers) who use technology products and services for their day-to-day work.

The Latest

Two years ago, almost every customer conversation about AI started with the same questions: Which model should we use? What can it do? Is it ready for the enterprise? Today, those discussions have moved on. CIOs are far more interested in how to govern AI, integrate it with existing systems, prepare their workforce and make it part of everyday operations. The challenge is no longer to prove that AI can deliver value. It's instead about how to embed AI into the business in a way that's secure, scalable and delivers measurable outcomes ...

 

Two things happened to production incidents between 2023 and now, and they did not happen at the same speed. The first is that a class of dependency that barely existed three years ago now accounts for one incident in ten. Incidents disclosed by AI model and AI application providers rose from 1.7% of all disclosed unplanned incidents in 2023 to 10.7% in 2026 year to date, roughly a sixfold rise; that counts only incidents at AI companies themselves, so the true share is higher. The second is that the time to close an incident has not come down ...

When an AI assistant gives an incomplete or incorrect answer, teams often blame the model. They adjust prompts, switch models, increase context windows or test a new retrieval strategy. However the model may not be a problem. In many enterprise AI workflows, the problem begins inside the document-ingestion pipeline ...

If you talk to any security or observability teams right now, they're all fighting the same fire: their tooling was built to ingest X, but their sources are pumping Y and soon to be doing Z. The knee-jerk reaction is always the same: we need more platform. However, this reaction is wrong. Let me explain why, because the solution to this problem is foundational, not financial. Instead of hurling yet more money at the problem, make sure you've done what's needed upstream ...

Rapid AI adoption and the unique ways AI workloads operate is redefining the scope and structure of what these teams must deliver. This shift is forcing organizations to rethink how they manage scale, automation, and control, according to The State of SRE and Platform Engineering 2026, a new report from Dynatrace ...

AI is usually talked about as a software tool, but it also depends heavily on the network behind it. Whether a company is using AI for chatbots, automation, monitoring, analytics, or employee support, all of that information has to move across the network in a reliable and secure way. That means AI is not just an application decision. It is also an infrastructure decision. Before organizations rush into AI, they should ask a simple question: Is our network ready to support it? ...

Enterprise AI often lacks governed access to where business processes actually execute. Without that access, AI agents may be able to reason, but they cannot operate reliably across enterprise workflows. For AI agents to effectively carry out workflows, they will require integration-layer context and controls. Organizations can implement these prerequisites by providing AI with managed access to the middleware layer ...

Enterprise networks rarely behave the same way for very long. A routing adjustment in one region may unexpectedly alter application performance in another. A cloud migration may introduce hidden dependencies that go unnoticed until an outage occurs. All the while, the network is managed by several different teams, each of whom use different tool sets — and as a result, have different views of the network ... There’s usually an engineer who remembers why traffic fails over a certain way between sites, or which transparent firewall was added where. The problem is that human memory cannot scale alongside enterprise-scale networks ...

Ask an infrastructure team how confident they are in their ability to govern AI, and most will tell you they've got it handled. A recent survey of 406 IT decision-makers and platform engineering leaders found 86% expressing exactly that confidence. Ask the same group whether they have a formal written AI governance policy, and the number drops to 30%, according to Spacelift's Infrastructure Automation Report ...

In MEAN TIME TO INSIGHT Episode 27, Shamus McGillicuddy, EMA VP of Research, Network Infrastructure and Operations, and Parker Hathcock, EMA Research Director covering IT Service/Operations (ServiceOps), discuss observability unification in modern IT operations ... 

Gartner: 60% of Employees Experience Frustration with New Software

Over Half of Users Have Wished Management Would Re-Instate Old Systems

More than half (60%) of workers said new software had occasionally or frequently frustrated them within the past 24 months, according to a new survey by Gartner, Inc.

In fact, 56% of users said new software had made them wish management would bring the old system back.

"The democratization and consumerization of IT has resulted in employees who have more discretion over what software they use and how they use it," said Craig Roth, Research VP at Gartner. "Software product leaders often focus on adding new features to keep up with competitors, but this leads to overly complex products with poor user experience (UX)."

The global Gartner survey revealed three ways in which users can impact enterprise software adoption:

1. Personal Adoption

The survey found that 81% of software users have taken some kind of action — positive or negative — after a notable experience with software. For example, 40% of users have resisted using applications after a negative experience by using minimal features, avoiding or delaying use. After a positive experience with an application, however, 41% of users spent more time delving further into its features.

"Depth of application usage can have a significant impact on the value an organization receives from software. That perceived value becomes important when renewal or upgrade time rolls around," said Roth. "Consumption of new features helps technology providers increase the stickiness of a product, but when users ignore advanced features, vendors have less influence to secure upsells or renewals and stay ahead of competition."

2. Influencing Others to Adopt or Avoid

The survey also found that users frequently share their opinions on software with peers, with IT and with business leaders, either proactively or in response to requests for input. This "word of mouth" can start a chain reaction that influences whether others adopt or avoid applications.

For example, 42% of survey respondents said they have complained to peers after a negative software experience, while 38% have recommended an application to peers after a positive experience.
Additionally, 42% have shared negative experiences with IT, and 25% have shared those experiences with business management.

Social media is also becoming an important outlet for sharing opinions on software, with 10% of respondents indicating they had left reviews on social media or review websites after a negative experience with an application.

When users were asked what actions software vendors could take to make them more likely to recommend their products to peers, IT or business leaders, the top answer was to make products easier to use, cited by 51% of respondents. Adding missing features was a distant third place, cited by 30%.

3. Self-Purchasing

Enterprise software users can also act as buyers in certain instances. The Gartner survey found that 34% of users say their IT department allows them to choose most of the software they use. In some instances, users may also self-acquire software through personal or business credit cards, or users will be billed based on consumption, although these arrangements are not yet commonplace.

"With SaaS revenue growing faster than the overall software industry, providers increasingly find themselves in a continuous purchase cycle," said Roth. "In this competitive market, maintaining high-value application usage by making UX a core competency is critical for generating positive business outcomes."

Methodology: The Gartner 2021 User Influence on Software Decisions Survey was conducted from April through June 2021 among 4,953 respondents in organizations with at least 100 employees in the US, France, Germany and Singapore. Respondents were required to be full-time workers or staff (i.e., not managers) who use technology products and services for their day-to-day work.

The Latest

Two years ago, almost every customer conversation about AI started with the same questions: Which model should we use? What can it do? Is it ready for the enterprise? Today, those discussions have moved on. CIOs are far more interested in how to govern AI, integrate it with existing systems, prepare their workforce and make it part of everyday operations. The challenge is no longer to prove that AI can deliver value. It's instead about how to embed AI into the business in a way that's secure, scalable and delivers measurable outcomes ...

 

Two things happened to production incidents between 2023 and now, and they did not happen at the same speed. The first is that a class of dependency that barely existed three years ago now accounts for one incident in ten. Incidents disclosed by AI model and AI application providers rose from 1.7% of all disclosed unplanned incidents in 2023 to 10.7% in 2026 year to date, roughly a sixfold rise; that counts only incidents at AI companies themselves, so the true share is higher. The second is that the time to close an incident has not come down ...

When an AI assistant gives an incomplete or incorrect answer, teams often blame the model. They adjust prompts, switch models, increase context windows or test a new retrieval strategy. However the model may not be a problem. In many enterprise AI workflows, the problem begins inside the document-ingestion pipeline ...

If you talk to any security or observability teams right now, they're all fighting the same fire: their tooling was built to ingest X, but their sources are pumping Y and soon to be doing Z. The knee-jerk reaction is always the same: we need more platform. However, this reaction is wrong. Let me explain why, because the solution to this problem is foundational, not financial. Instead of hurling yet more money at the problem, make sure you've done what's needed upstream ...

Rapid AI adoption and the unique ways AI workloads operate is redefining the scope and structure of what these teams must deliver. This shift is forcing organizations to rethink how they manage scale, automation, and control, according to The State of SRE and Platform Engineering 2026, a new report from Dynatrace ...

AI is usually talked about as a software tool, but it also depends heavily on the network behind it. Whether a company is using AI for chatbots, automation, monitoring, analytics, or employee support, all of that information has to move across the network in a reliable and secure way. That means AI is not just an application decision. It is also an infrastructure decision. Before organizations rush into AI, they should ask a simple question: Is our network ready to support it? ...

Enterprise AI often lacks governed access to where business processes actually execute. Without that access, AI agents may be able to reason, but they cannot operate reliably across enterprise workflows. For AI agents to effectively carry out workflows, they will require integration-layer context and controls. Organizations can implement these prerequisites by providing AI with managed access to the middleware layer ...

Enterprise networks rarely behave the same way for very long. A routing adjustment in one region may unexpectedly alter application performance in another. A cloud migration may introduce hidden dependencies that go unnoticed until an outage occurs. All the while, the network is managed by several different teams, each of whom use different tool sets — and as a result, have different views of the network ... There’s usually an engineer who remembers why traffic fails over a certain way between sites, or which transparent firewall was added where. The problem is that human memory cannot scale alongside enterprise-scale networks ...

Ask an infrastructure team how confident they are in their ability to govern AI, and most will tell you they've got it handled. A recent survey of 406 IT decision-makers and platform engineering leaders found 86% expressing exactly that confidence. Ask the same group whether they have a formal written AI governance policy, and the number drops to 30%, according to Spacelift's Infrastructure Automation Report ...

In MEAN TIME TO INSIGHT Episode 27, Shamus McGillicuddy, EMA VP of Research, Network Infrastructure and Operations, and Parker Hathcock, EMA Research Director covering IT Service/Operations (ServiceOps), discuss observability unification in modern IT operations ...