A few months ago, at Gartner Digital Workspace I watched a presentation from former colleague. The concept that really stuck with me was experience anchors. The idea behind it is that digital workspace leaders can, instead of improving your entire digital workspace at once, identify the moments where friction is genuinely unacceptable and use those as your filter for every decision.
As someone who is passionate about context and doesn’t speak digital workspaces fluently, I loved how experience anchor isn't rooted in metrics FIRST. It is an experience a real person actually lives through. It's the first-hand experience behind the dashboards. It humanizes the technology, and it humanizes the path to fixing it. Before you can define a KPI, experience anchors forces organizations to agree on the moment the KPI is trying to capture.
So, I started asking questions, specifically, “does DaaS have its own version of this?” What are the moments in a managed virtual desktop environment where friction isn't just annoying, it's unacceptable?
The people I work with have been running these environments for a long time. Here are a few experience anchors that the experts I work with recommended to help perpetuate progress over perfection for DaaS environments:
Imagine the scene: a new hire is excited to get started at their job and then ends up sitting idle for two days waiting for access to the systems with which they need to work. Or let’s say it’s a highly paid contractor who needs to hit the ground running on day one but can’t get the apps they need. This experience sets the tone for everything that follows, not just operationally, but in terms of how the user feels about the environment from that point forward.
First impressions in a DaaS environment are stick around.
Research has shown that organizations have lost hundreds of millions in productivity from poor onboarding — not because systems didn't work, but because nobody agreed on what "ready" meant. As documented in research cited by LumApps, Amazon lost approximately $678 million over two years due to inadequate onboarding, and Salesforce reportedly experienced $35 million in productivity losses from a single onboarding program. Those aren't technology failures. They're clarity failures.
IT controls Image readiness, profile load time, application availability on first session, and provisioning automation. IT can control whether the environment is genuinely ready, not just technically provisioned, when the user first logs in. The gap between those two things is where the experience breaks down.
Swap "account creation SLA" for "time to productive access." The first tells leadership how fast IT moved. The second tells them whether the person could actually do their job. Those sound similar. They drive completely different behavior across IT, HR, and security.
There's a term for what happens at 8:47 AM on a Monday when everyone logs in simultaneously: the logon storm. I love that it has a name. Trying to login while the system is under peak load deserves one.
Industry practitioners consistently identify undersized provisioning, teams provisioning too lean to save money, then facing a flood of performance complaints at peak, as one of the most predictable and preventable DaaS failure patterns. Predictability doesn't mean it gets prevented. It usually doesn't, until someone names peak load as non-negotiable.
For some, the Monday morning logon storm is quietly accepted as just how things are. For others, acknowledging that it’s the highest-visibility window in the entire week is exactly the kind of friction that experience anchors are designed to surface and fix.
It controls the resource provisioning levels, pre-warming policies, session capacity planning, and monitoring during peak windows. The logon storm is almost always solvable with the right capacity planning and pre-warming strategies. It just rarely gets prioritized until the tickets start rolling in on a Monday morning and someone in the C-suite notices their desktop took four minutes to load.
Replace "average session latency" with "consistent login performance." Averages are comfortable for IT reporting and meaningless to a business leader who watched their team struggle to start work for 20 minutes. Consistency is the standard users actually apply — and it's the one worth committing to.
Application launch within a session is the most underappreciated anchor on this list — and the one that comes with the most important caveat.
Imagine that the radiologist at the hospital is waiting too long for the imaging system to load between patients (with back-to-back appointments). Or consider the analyst who gave up on evaluating a critical trend to advise a client and switched back from a thin client to their personal laptop because of lag. Research from 1E found that 52% of employees say poor digital experience makes them more inclined to leave their jobs. That's not abstract dissatisfaction. That's the accumulated weight of systems that don't work the way work actually requires.
Resource allocation per session, application virtualization configuration, session monitoring, and digital experience management tooling. Here's the caveat our practitioners flagged: IT often gets blamed for slow application launches when the problem lives in the application itself, not the desktop. Although that doesn’t fall onto IT, without making application launch a named experience anchor, there's no structured basis for IT to have that conversation with application owners. You're just trading blame across teams with no shared definition of the problem.
Move from "session establishment time" to "time to working application." Getting into the desktop is step one. The application is where work actually starts — and that's the moment the business is measuring, whether or not IT is.
In a DaaS environment where the virtual desktop is the only path to work, how IT handles the experience of an outage (much like any emergency communications), the communication, the transparency, the visible sense that someone is actually on it, can be damaging. In addition to reputation, an outage can be financially catastrophic.
It’s unlikely you have “extra” budget lying around to account for the impact unplanned downtime has on an organization. EMA Research's 2024 analysis found that unplanned downtime averages $14,056 per minute across organizations of all sizes. ITIC's 2024 Hourly Cost of Downtime Survey found that over 90% of mid-size and large enterprises lose more than $300,000 per hour and 41% lose between $1M and $5M+. For managed DaaS specifically, a single infrastructure failure can affect thousands of users simultaneously. The stakes in recovery speed and communication quality are not theoretical.
IT has impact on the recovery time objectives, incident communication protocols, failover procedures, and post-incident review cadence. For a managed DaaS provider specifically, this is where the value of the relationship should be most visible. Recovery speed and communication quality aren't features, they're commitments. And they only get held to a standard when someone names them as one.
Shift from "uptime percentage" to "time to restoration and quality of communication." A 99.9% uptime figure is invisible to a business leader until the 0.1% happens. What they remember is whether IT was present, clear, and accountable during it.
When it comes to offboarding and access termination I thought that it felt like an HR task. It turns out to be one of the highest-risk moments in a DaaS environment.
Gartner found that only 44% of companies ensure all access rights are revoked within 24 hours of an employee's departure. Ponemon Institute research found that 20% of data breaches involve former employees within six months of leaving. And BetterCloud's 2025 State of SaaS Report found that 48% of IT teams worry that incomplete offboarding is actively leaving their organization vulnerable. In regulated industries like healthcare, finance, and government this isn't just operational risk. It's a compliance and legal liability with a short fuse.
IT can control the automated deprovisioning workflows, access audit trails, integration with HR systems, and compliance reporting. There’s also an opportunity to utilize virtual desktop environments to make clean, immediate, verifiable access termination easier than traditional endpoint models — because the data never lived on the device in the first place. The capability is there. It just only gets used consistently when offboarding is named as a moment that matters.
Replace "offboarding checklist completion" with "verified access termination." The checklist tells HR that the process ran. Verified termination tells security, compliance, and legal that the risk is actually closed.
The thing that kept striking me as I talked through these with our team is how many of them are moments where IT carries accountability for outcomes it doesn't fully control. My inner empath hates that. Using the experience anchors, naming the moments that people encounter changes that unfair dynamic.
When first login becomes an experience anchor, IT isn't just provisioning accounts. They're co-owning a definition of "ready" with HR and security. When recovery becomes an anchor, the standard isn't uptime, it's the full experience of what the business goes through when something breaks. When offboarding becomes an anchor, DaaS stops being infrastructure and starts being a compliance tool.
That reframe came from people who have been running these environments for years. But it maps back to what stuck with me in that conference room: experience anchors work because they start with the human moment, not the metric.