Most organizations can tell you exactly how many licenses they've bought. Far fewer can tell you how many employees would notice if one of those tools disappeared tomorrow.
The Stackmatix Copilot analysis published in April 2026 found that only 35.8 percent of provisioned users actively engaged with the tool. Close to two-thirds of people with a license weren't choosing to use it. Most IT reports don't track that, because the reports measure seats and renewal dates rather than behavior.
Whether that specific figure applies to every other platform is beside the point. Anyone who has watched a collaboration tool get deployed and slowly become a file repository, or an intranet that only gets traffic when someone needs an HR form, has seen the same pattern without the numbers attached. The usual response is more training, sometimes a change management program. But, big surprise: adoption stays flat.
So, the question worth asking is why. And the answer, in most post-deployment reviews, turns out to have very little to do with the technology.
In essence, the issue is very simple. Employees very quickly weigh up whether a tool makes their work easier. When the answer is unclear—or when the effort of learning a new system exceeds whatever time it's supposed to save—they go back to whatever they were using before. This is a practical decision, and a rational one.
Take email, for example. It has survived every platform that was supposed to replace it, for the simple reason that email still works very effectively (and even more so when the right message reaches the right person, instead of everyone getting the same email). IT sees a collaboration tool with better features and wider capability. The employee sees another login, another interface competing for attention, and a learning curve they didn't ask for in exchange for benefits that aren't immediately obvious. The employee wins that argument every time, quietly, by doing nothing.
The same applies to workflow tools, project management platforms, and most other deployments that arrive with ambitious adoption targets attached. The business case is built on the assumption that people will use the technology as designed. When they don't, the return on that investment erodes. And in most organizations, there's no reporting in place that would tell you either way.
Platform sprawl makes everything harder. MuleSoft's 2026 Connectivity Benchmark Report, based on a survey of more than 1,050 IT leaders, found that organizations manage an average of 957 applications, with only 27 percent connected
Under those conditions, a new platform is competing against established habits that already feel familiar. A spreadsheet that does what the employee needs without requiring a new login or a training session will beat a purpose-built workflow tool every time, regardless of what the workflow tool cost.
Constant notifications accelerate the problem. Microsoft's own Work Trend Index research has documented how interruption volume degrades focus and trains people to tune out the platforms doing the interrupting.
New hires face a different version of the same challenge. Presented with a long list of approved tools on day one, most adopt whatever their immediate team already uses and leave the rest untouched. Within weeks, the official platform suite and the one employees actually use have quietly diverged.
Operational reporting catches none of this. Uptime, SLA performance, support tickets, cost per seat—these were designed to measure infrastructure health, and they do that well. A system can run at 99.9 percent availability while close to two-thirds of its licensed users ignore it, and nothing on the standard dashboard will register a problem. The business case stays in its post-deployment folder, its assumptions untested.
That's the gap. Not between the technology and the user, but between what IT measures and what the business needs to know.
Organizations seeing stronger adoption tend to measure different things. Active usage gets compared with licensed seats, broken down by role and department, and tracked over quarters rather than checked once at renewal time. Persistent support problems on a specific platform become a reason to investigate what's going wrong, not a number to absorb into the quarterly report.
When a contract does come up for renewal, someone goes back to the original business case and checks whether it held up. The data for all of this already exists in the support system, the licensing platform, and the analytics the tools provide. Building the reports is a single-quarter project.
The harder question is whether the leadership team wants to see what the reports show. Because the numbers aren't always comfortable, and acting on them sometimes means admitting that an investment hasn't performed.
The more interesting shift is in how decisions get made before deployment. A lot of digital workplace programs start with architecture and procurement and how employees actually do their work enters the conversation late, if it enters at all.
Organizations seeing better results tend to work from the other direction—looking at what employees actually do and where they're losing time, before choosing the technology to address it.
The test is simple. If a tool you've invested in disappeared tomorrow, how many employees would actually notice? If you can't answer that, the rest of the dashboard doesn't matter much.