Skip to main content

Think You've Heard Everything About the Debate over RTO? Here's the Big Thing Leaders Are Missing

Daren Goeson
Ivanti

Almost half (48%) of employees admit they resent their jobs but stay anyway, according to research from Ivanti. That's the kind of statistic that stops me cold. It doesn't take a top-notch workplace behavior analyst to guess that resentful employees are unlikely to bring their A-game (or B-game, or C-game) to work.

We've all heard the term "quiet quitting," but this goes deeper. Resenteeism describes workers who actively dislike their roles yet remain trapped by economic uncertainty, benefits or limited options. Nearly four out of 10 employees also engage in presenteeism — showing up physically or virtually without truly working.

This has obvious consequences across the business, but we're overlooking the massive impact of resenteeism and presenteeism on IT. For IT professionals tasked with managing the backbone of modern business operations, these numbers spell big trouble.

When IT Workers Check Out, Everyone Feels It

The IT problem is two-pronged: On one side, unfocused employees create significant risks and gaps that IT has to manage.

On the other side, IT workers themselves are susceptible to the same resenteeism and presenteeism as everyone else. In some cases, likely more so because of the added pressures in prong one.

64% of IT workers say they're feeling pressure from employers to return to the office, despite 83% considering flexible work to be of high value or essential to their roles.

This creates a dangerous disconnect. When the people responsible for keeping systems running, securing networks and solving technical problems become disengaged, the ripple effects touch every corner of the organization.

IT professionals report a 58-point gap between their desired flexibility and what their employers actually provide. Compare that to the 50-point gap in the experience of non-IT office workers, and you will see why technical talent feels particularly squeezed.

Only 25% of IT professionals describe their workplace as highly flexible. Yet these same people manage the technology that makes remote work possible for everyone else.

Here's where it gets complicated. Nearly half of IT workers say collaborating with colleagues and getting their manager's attention is easier inside the office. This creates a genuine tension between personal preferences and professional effectiveness.

But rather than solving the underlying problem, many organizations default to mandating office presence. This is treating a symptom while ignoring the disease.

The real issue? Many companies still struggle to provide effective out-of-office work experiences. When collaboration tools feel clunky, when getting help takes too long or when technical problems slow everyone down, of course being in the office seems more efficient.

The Automation Opportunity We're Missing

Companies are taking steps to improve remote work effectiveness, but they're not going far enough. 48% provide self-service resources for IT requests. 43%,  monitor device and application performance. Another 43% use automation for ticket resolution.

These efforts help, but they barely scratch the surface of what's possible with modern technology.

Despite 86% of IT professionals agreeing that AI-powered technology is important for making IT operations more efficient, actual deployment lags badly. Fewer than half use AI and automation for predictive IT maintenance or detecting usage anomalies — scenarios where these tools are highly effective.

Root-cause analysis and intelligent ticket escalation indicates that fewer than one in three organizations deploy AI for these critical functions. Not great.

Meanwhile, 38% of workers use unauthorized AI tools, suggesting they're finding ways to be more productive despite organizational inertia.

Things Are Getting … Shadowy

The disconnect between what IT professionals need and what they're getting creates more than workplace dissatisfaction. Resentful, disengaged IT workers make poor security decisions. They take shortcuts. They stop proactively monitoring systems or suggesting improvements.

When technical problems pile up and response times slow down, everyone suffers. Sales teams can't access CRM systems. Customer service representatives struggle with system outages. Remote employees lose productivity to technical glitches. Employees start being able to get away with rampant "shadow IT," where they rely on their preferred tools and applications even though those tools and applications aren't sanctioned, aren't disclosed to IT and therefore IT can't manage them. Shadow IT is always a problem, but resenteeism and presenteeism make it worse.

The human cost compounds the business impact. Talented IT professionals start looking elsewhere for roles that offer better work-life balance. Organizations lose institutional knowledge and face expensive recruitment cycles. Poor retention of top professionals adds to a truly unpleasant downward spiral.

Promoting Flexibility and Engagement

The problem is on multiple fronts, so the solution needs to be, too. Better digital employee experience (DEX) tools, which is how employees interact with their organization's digital environment, make remote work smoother and more productive. This encompasses the hardware and software employees use to perform their daily tasks, as well as the level of access and support they receive. By continuously measuring employee satisfaction and productivity within digital work environments, DEX has become a critical driver of success and growth in the era of hybrid, remote or in-office work. Additionally, for IT teams it helps reduce ticket volumes and frees up time to work on more impactful projects that nurture their professional development.

Automation handles routine tasks, freeing IT professionals to focus on strategic work that requires human judgment and creativity. Engagement improves when people feel their skills are valued rather than wasted on repetitive problems.

The flexibility gap won't close overnight, but organizations can start by measuring what matters to their IT teams and systematically addressing the biggest pain points.

This means investing in tools that make distributed work genuinely effective, not just possible. It means automating processes that currently require manual intervention. It means trusting technical professionals to manage their own productivity rather than monitoring their every move.

Daren Goeson is SVP Product Management at Ivanti

The Latest

Production incidents rarely announce themselves as database problems. They appear as slow transactions, timeouts, rising response times, or an application struggling under a workload it previously handled. APM provides an essential starting point. It can identify a slow transaction path, highlight an affected service, and show that a database dependency is consuming more time than expected. But identifying the database as part of the problem is not the same as explaining what is happening inside it ...

Cloud teams are under constant pressure to reduce spend without slowing development or increasing operational risk. They are deploying autoscalers, rightsizing workloads, enforcing resource requests, reviewing utilization dashboards, and building FinOps processes around cloud-native environments. Yet the results often disappoint ...

Ask most IT leaders about their biggest concern with AI and you'll hear the same answer: hallucinations ... Today, however, the conversation has shifted ... As organizations move beyond chatbots and experiments, they are increasingly deploying AI agents that perform multi-step tasks. These systems retrieve documents, query databases, call APIs, generate reports, write code, and make recommendations. The issue is not whether the model can reason. The issue is whether the organization can see, verify, and govern the decisions being made along the way ...

While organizations want to take control of their telemetry, building telemetry pipelines from scratch can be a very daunting, complicated task, even when leveraging open-source standards like OpenTelemetry. It requires specialized knowledge across distributed systems, data engineering, and security. This fragmented approach across systems causes higher operational costs; it puts a strain on resources and reduces efficiency as teams have to work with different interfaces and processes ...

For decades, enterprise networks were designed around a simple assumption: work happened inside the office. Applications lived in centralized data centers, employees connected through internal infrastructure, and security focused on protecting the perimeter that surrounded everything ... But the way organizations operate today bears little resemblance to that environment. Cloud platforms host critical applications, employees connect from homes and airports as often as they do from offices, and partners collaborate through shared systems that exist far beyond corporate walls. In short, the corporate network no longer resembles the environment it was designed to protect ...

As an analyst who researches how IT organizations design, build, and operate their networks, I find that network data is a constant source of pain. Network teams struggle with data quality, fragmentation, authority, access, and trust. And these issues undermine everything they try to do. Here are the numbers: Only 45% of network teams are completely confident in the accuracy of their network source of truth, which documents the intent of their network ...

The 2026 Global Data Center Survey from Uptime Institute reveals an industry navigating workforce constraints, escalating outage expenses, even as rising costs remain the top concern for management teams ...

The next observability gap may not be in the code. It may be under the rack. That sounds strange until you think about how AI incidents actually feel in the middle of an investigation ... The application dashboard may be accurate. It may also be stopping at the wrong boundary. AI systems depend on software, but they also depend on a dense physical stack: racks, power paths, thermal margin, maintenance activity and, in many environments, liquid cooling. Those physical dependencies can change slowly before they look like a software incident ...

Certificate expiration is the rare outage you can see coming. Every TLS certificate carries the date it stops working, so the moment it will begin breaking connections is knowable in advance. That's what makes an expired certificate such a frustrating way to lose a service. What's changing now is how often that date comes around ...

Enterprises operate different combinations of workloads across cloud, hybrid and multicloud environments. For business-critical workloads, teams need to consider monitoring and observability early so they can detect health issues, investigate failures, and understand operational impact. Organizations place workloads on cloud platforms based on a combination of technical requirements, economics, existing dependencies, organizational standards, and business priorities. Their monitoring priorities therefore depend on what they operate and where those systems run. Those priorities will not look the same for every organization ...

Think You've Heard Everything About the Debate over RTO? Here's the Big Thing Leaders Are Missing

Daren Goeson
Ivanti

Almost half (48%) of employees admit they resent their jobs but stay anyway, according to research from Ivanti. That's the kind of statistic that stops me cold. It doesn't take a top-notch workplace behavior analyst to guess that resentful employees are unlikely to bring their A-game (or B-game, or C-game) to work.

We've all heard the term "quiet quitting," but this goes deeper. Resenteeism describes workers who actively dislike their roles yet remain trapped by economic uncertainty, benefits or limited options. Nearly four out of 10 employees also engage in presenteeism — showing up physically or virtually without truly working.

This has obvious consequences across the business, but we're overlooking the massive impact of resenteeism and presenteeism on IT. For IT professionals tasked with managing the backbone of modern business operations, these numbers spell big trouble.

When IT Workers Check Out, Everyone Feels It

The IT problem is two-pronged: On one side, unfocused employees create significant risks and gaps that IT has to manage.

On the other side, IT workers themselves are susceptible to the same resenteeism and presenteeism as everyone else. In some cases, likely more so because of the added pressures in prong one.

64% of IT workers say they're feeling pressure from employers to return to the office, despite 83% considering flexible work to be of high value or essential to their roles.

This creates a dangerous disconnect. When the people responsible for keeping systems running, securing networks and solving technical problems become disengaged, the ripple effects touch every corner of the organization.

IT professionals report a 58-point gap between their desired flexibility and what their employers actually provide. Compare that to the 50-point gap in the experience of non-IT office workers, and you will see why technical talent feels particularly squeezed.

Only 25% of IT professionals describe their workplace as highly flexible. Yet these same people manage the technology that makes remote work possible for everyone else.

Here's where it gets complicated. Nearly half of IT workers say collaborating with colleagues and getting their manager's attention is easier inside the office. This creates a genuine tension between personal preferences and professional effectiveness.

But rather than solving the underlying problem, many organizations default to mandating office presence. This is treating a symptom while ignoring the disease.

The real issue? Many companies still struggle to provide effective out-of-office work experiences. When collaboration tools feel clunky, when getting help takes too long or when technical problems slow everyone down, of course being in the office seems more efficient.

The Automation Opportunity We're Missing

Companies are taking steps to improve remote work effectiveness, but they're not going far enough. 48% provide self-service resources for IT requests. 43%,  monitor device and application performance. Another 43% use automation for ticket resolution.

These efforts help, but they barely scratch the surface of what's possible with modern technology.

Despite 86% of IT professionals agreeing that AI-powered technology is important for making IT operations more efficient, actual deployment lags badly. Fewer than half use AI and automation for predictive IT maintenance or detecting usage anomalies — scenarios where these tools are highly effective.

Root-cause analysis and intelligent ticket escalation indicates that fewer than one in three organizations deploy AI for these critical functions. Not great.

Meanwhile, 38% of workers use unauthorized AI tools, suggesting they're finding ways to be more productive despite organizational inertia.

Things Are Getting … Shadowy

The disconnect between what IT professionals need and what they're getting creates more than workplace dissatisfaction. Resentful, disengaged IT workers make poor security decisions. They take shortcuts. They stop proactively monitoring systems or suggesting improvements.

When technical problems pile up and response times slow down, everyone suffers. Sales teams can't access CRM systems. Customer service representatives struggle with system outages. Remote employees lose productivity to technical glitches. Employees start being able to get away with rampant "shadow IT," where they rely on their preferred tools and applications even though those tools and applications aren't sanctioned, aren't disclosed to IT and therefore IT can't manage them. Shadow IT is always a problem, but resenteeism and presenteeism make it worse.

The human cost compounds the business impact. Talented IT professionals start looking elsewhere for roles that offer better work-life balance. Organizations lose institutional knowledge and face expensive recruitment cycles. Poor retention of top professionals adds to a truly unpleasant downward spiral.

Promoting Flexibility and Engagement

The problem is on multiple fronts, so the solution needs to be, too. Better digital employee experience (DEX) tools, which is how employees interact with their organization's digital environment, make remote work smoother and more productive. This encompasses the hardware and software employees use to perform their daily tasks, as well as the level of access and support they receive. By continuously measuring employee satisfaction and productivity within digital work environments, DEX has become a critical driver of success and growth in the era of hybrid, remote or in-office work. Additionally, for IT teams it helps reduce ticket volumes and frees up time to work on more impactful projects that nurture their professional development.

Automation handles routine tasks, freeing IT professionals to focus on strategic work that requires human judgment and creativity. Engagement improves when people feel their skills are valued rather than wasted on repetitive problems.

The flexibility gap won't close overnight, but organizations can start by measuring what matters to their IT teams and systematically addressing the biggest pain points.

This means investing in tools that make distributed work genuinely effective, not just possible. It means automating processes that currently require manual intervention. It means trusting technical professionals to manage their own productivity rather than monitoring their every move.

Daren Goeson is SVP Product Management at Ivanti

The Latest

Production incidents rarely announce themselves as database problems. They appear as slow transactions, timeouts, rising response times, or an application struggling under a workload it previously handled. APM provides an essential starting point. It can identify a slow transaction path, highlight an affected service, and show that a database dependency is consuming more time than expected. But identifying the database as part of the problem is not the same as explaining what is happening inside it ...

Cloud teams are under constant pressure to reduce spend without slowing development or increasing operational risk. They are deploying autoscalers, rightsizing workloads, enforcing resource requests, reviewing utilization dashboards, and building FinOps processes around cloud-native environments. Yet the results often disappoint ...

Ask most IT leaders about their biggest concern with AI and you'll hear the same answer: hallucinations ... Today, however, the conversation has shifted ... As organizations move beyond chatbots and experiments, they are increasingly deploying AI agents that perform multi-step tasks. These systems retrieve documents, query databases, call APIs, generate reports, write code, and make recommendations. The issue is not whether the model can reason. The issue is whether the organization can see, verify, and govern the decisions being made along the way ...

While organizations want to take control of their telemetry, building telemetry pipelines from scratch can be a very daunting, complicated task, even when leveraging open-source standards like OpenTelemetry. It requires specialized knowledge across distributed systems, data engineering, and security. This fragmented approach across systems causes higher operational costs; it puts a strain on resources and reduces efficiency as teams have to work with different interfaces and processes ...

For decades, enterprise networks were designed around a simple assumption: work happened inside the office. Applications lived in centralized data centers, employees connected through internal infrastructure, and security focused on protecting the perimeter that surrounded everything ... But the way organizations operate today bears little resemblance to that environment. Cloud platforms host critical applications, employees connect from homes and airports as often as they do from offices, and partners collaborate through shared systems that exist far beyond corporate walls. In short, the corporate network no longer resembles the environment it was designed to protect ...

As an analyst who researches how IT organizations design, build, and operate their networks, I find that network data is a constant source of pain. Network teams struggle with data quality, fragmentation, authority, access, and trust. And these issues undermine everything they try to do. Here are the numbers: Only 45% of network teams are completely confident in the accuracy of their network source of truth, which documents the intent of their network ...

The 2026 Global Data Center Survey from Uptime Institute reveals an industry navigating workforce constraints, escalating outage expenses, even as rising costs remain the top concern for management teams ...

The next observability gap may not be in the code. It may be under the rack. That sounds strange until you think about how AI incidents actually feel in the middle of an investigation ... The application dashboard may be accurate. It may also be stopping at the wrong boundary. AI systems depend on software, but they also depend on a dense physical stack: racks, power paths, thermal margin, maintenance activity and, in many environments, liquid cooling. Those physical dependencies can change slowly before they look like a software incident ...

Certificate expiration is the rare outage you can see coming. Every TLS certificate carries the date it stops working, so the moment it will begin breaking connections is knowable in advance. That's what makes an expired certificate such a frustrating way to lose a service. What's changing now is how often that date comes around ...

Enterprises operate different combinations of workloads across cloud, hybrid and multicloud environments. For business-critical workloads, teams need to consider monitoring and observability early so they can detect health issues, investigate failures, and understand operational impact. Organizations place workloads on cloud platforms based on a combination of technical requirements, economics, existing dependencies, organizational standards, and business priorities. Their monitoring priorities therefore depend on what they operate and where those systems run. Those priorities will not look the same for every organization ...