For 15 years, enterprises have been executing digital workplace migrations; physical-to-virtual migrations, Cloud PC adoption, and on-prem to hybrid to cloud strategies, to name a few.
Whilst the readiness and orchestration challenges remain, the technical pathways have largely been solved.
These programs are typically planned as a mapping from the current state to the target state. Virtual desktop users get a Cloud PC, and laptop users get a laptop if they are mobile and a virtual device if they work from the office.
This approach gets the program done: the cutover is complete, the migration targets are met, and the success criteria are ticked. But after each mass migration, a common question goes unanswered:
"Are our users on the right/most suitable operating environment?"
One example comes from a recent customer conversation with a large insurance and financial services enterprise. Over the past few years, the organization has undertaken several major workplace migrations, most recently transitioning from Vendor A’s end-user computing platform to Vendor B’s, driven primarily by the significant cost savings associated with Vendor B’s offering.
On paper, the projected savings were compelling. The IT team was highly experienced in delivering these types of migrations, and, like many programs before it, the project was delivered on schedule, with the workforce successfully transitioned to the new environment.
With the migration complete, the team took time to review lessons learned. Their review showed that the cutover was successful, the operational metrics looked positive, and the projected savings appeared accurate on paper. Yet an uncomfortable question began to emerge from their leadership, whether that's the Head of Digital Workplace, the Head of EUC, or the CFO:
Have we actually placed people in the right operating environment? And once the hidden support burden of an incorrectly aligned workforce is considered, have the promised savings genuinely materialized?
The program was designed to execute the migration efficiently, not to determine whether the destination platform was the best fit for each individual or user group. As a result, the organization now finds itself with a workforce that has been migrated successfully, but not necessarily optimized.
This customer's experience isn’t unique. The execution problem was largely solved. If you asked the same team to perform another migration tomorrow, they'd pull it off. The tooling involved has matured, and the capability of moving large workforces from one platform to another is no longer the problem it was five years ago.
But the inefficiencies of an unoptimized workforce are now more visible than ever. The true cost of different operating environments isn't just about the raw infrastructure overheads. The suitability of that environment for the person using it is a key dimension. Cloud PC is more expensive than a mid-tier laptop for some users but cheaper for others. AVD multi-session has economic advantages that depend on usage patterns.
And the raw cost is only part of the picture. Suboptimal placement also drives ongoing operating cost: higher support volumes, more exception handling, and more remediation when deployments don't land. Selecting the wrong operating environment isn't just a budget issue; it has a genuine impact on user experience and on the cost of running the workforce.
New operating environments keep emerging, and the number that an enterprise supports simultaneously is increasing. A decade ago, the choice might have been desktop, laptop, or VDI. Historically, the choice for most users was a desktop or a desktop. But back then, everyone worked Monday to Friday, 9-5, in the office. Today's offerings have expanded to include Cloud PC, thin laptops, AVD multi-session, persistent VDI, enterprise browser, Mac, and BYOD — that's before we get to mobile.
The portfolio of operating environments has expanded faster than enterprises' ability to intelligently allocate users to them.
The workforce's expectations are rising too, with employees increasingly comparing their work tech stack to the consumer tech they use at home and finding the former falls short. This has fuelled the rise of DEX tooling, with Gartner stating that "organizations must have a strategy to measure and improve DEX to attract and retain talent to improve employee engagement and maximize discretionary effort and intent-to-stay". IT teams are increasingly measuring productivity and sentiment signals, surfaced through surveys and ticket pattern analysis.
In April 2026, Gartner analysts Tom Cipolla and Stuart Downes published an Innovation Insight defining a new category: Digital Workplace Operations Automation, or DWOA. The category sits one layer above existing endpoint and asset management, ITSM, DEX, and identity tools. It's positioned as a control plane, coordinating workflows across the digital workplace tool stack. Five years ago, this category wouldn't have made sense: there weren't enough environments, the cost differentials weren't visible, and DEX expectations weren't high enough to make optimization urgent. Today, that is no longer true.
Cipolla and Downes emphasize orchestration. The category description repeatedly mentions workflow automation, multi-system coordination, agentic AI workflows, the MCP, and A2A protocols that let agents talk to tools and to each other. The framing is correct. DWOA tools will need to do all of this, and orchestration is how they will operate.
The harder question is what they are for. Vendors who will lead the DWOA category five years from now won't be those who orchestrate the workflow best. They will be the ones who provide the intelligence layer that tells enterprises what to do and why.
This is where we see the deeper story emerging: Portfolio Intelligence: a continuous monitoring capability that evaluates the suitability of operating environments for each person in the workforce and, importantly, drives positive change.
To make the right recommendations, a tool in the DWOA space must provide Portfolio Intelligence. Portfolio Intelligence requires two things: a deep understanding of how a person actually works, and a model of the operating environments available to them.
Employees are often described by their job title or role. It's the label that HR systems assign and can feel like a convenient way to group them into neat buckets. However, as anyone who has tried to retrofit personas to an existing workforce will know, this is far from reality.
For decisions about environment suitability, the role title is almost irrelevant. What matters is how someone actually works. Behavioral clustering helps rediscover what the workforce actually delivers by revealing patterns the organizational chart hides. To be truly successful, it will also take into account that observed behavior may be influenced by the operating environment itself.
These behaviors must be observed over time. How an employee works today can be very different from, or very similar to, what they did last month, last quarter, or last year. Portfolio Intelligence needs to build this picture over time and distinguish when a change in behavior is a one-off or a trend worth reacting to.
The array of operating environments available in the enterprise today is vast, and each has its own unique suitability criteria. Some will have geographical limitations (Cloud PC vendor blocked in users' regions), some are rooted in usage patterns and roles (shift workers, remote workers, 3rd-party vendors, and executives), some are technical (GPU, NPU, and RAM-intensive applications), and some are bound by business requirements (availability, recovery, and stability).
A tool in the DWOA arena needs to understand all these criteria and be able to map each to real-world data points to make a coherent case for change.
Digital workplace technology decisions today are largely assigned by role. Alex is a new Marketing Analyst — assign them the marketing analyst stack and applications.
Portfolio Intelligence will make an individual-level recommendation based on observed behaviors of how that specific person actually works. It will produce a defensible explanation, transparent enough to be repeated to a skeptical user who asks, "Why am I getting a Cloud PC?"
The way people work evolves and changes over time. Never has that been truer than with how AI is rapidly redefining the skills, experience, and time needed to perform functions.
The operating environments on offer change too, as new technologies emerge, new operating systems are released, and new vendor deals are struck.
Portfolio Intelligence must continuously monitor the workforce and re-evaluate its recommendations, learning from previous outcomes and surfacing opportunities as they emerge.
Critically, it must also learn from its own recommendations to avoid change fatigue. If the recommendation for an individual changes week to week, it's not doing its job.
Portfolio Intelligence is a necessary capability for any credible DWOA tooling. The harder problem could be adapting the enterprise's current operating model to fully take advantage of the insight. How does the role of the IT admin change when DWOA tools are making and acting upon recommendations? Who approves the actions, and with what governance and change-management methodology? I'll dive deeper into the operating model in a follow-up article.
Taking Portfolio Intelligence as a core competency of a DWOA tool has interesting implications for the current landscape. The vendors named by Gartner as representative providers come from different heritages — ITSM, digital workplace transformation, service desk, IT operations, agentic AI, and DEX — each has a natural angle into the category, and each has some structural gaps.
Vendors from an ITSM heritage will have strong process orchestration, but could be weaker on the deep workforce signals: seeing tickets but not behaviors.
Vendors from a DEX heritage will have rich endpoint telemetry. They'll be strong on the data foundations but weaker on the portfolio reasoning. They might see real-time experience, but not target state recommendations or continuous optimization. Their natural growth into the category is from below.
Vendors from a digital workplace transformation heritage have workforce data and change methodologies, but they are built for program planning rather than continuous monitoring and improvement. They will need to evolve from helping enterprises execute migrations to helping them decide which migrations to execute.
Vendors with agentic AI heritage will be strong in workflow and automation, but weaker on the underlying foundational workforce data that portfolio intelligence requires.
No vendor is naturally positioned for all of it. The category will form through the vendors who can either build broadly enough or partner well enough to span workforce data, target-state intelligence, recommendation capability, change orchestration, and the operating model to deploy them.
The way these tools evolve will also shift who buys them. Program execution tools sell to the transformation leads, but portfolio intelligence sells to the head of digital workplace, the head of EUC, and the CFO. This shift in buyer persona itself will be an important signal for the new category.
None of this is straightforward to build, and the early DWOA platforms will likely overpromise on capability before they deliver on intelligence.
DWOA is what comes after mass migration. The first generation of workplace platforms helped enterprises execute change. The next generation will help enterprises decide which changes are worth executing.
A different product with different capabilities bought by a different persona, all supported by a different operating model.
The execution era of digital workplace operations is largely solved. The intelligence era is just beginning.