"We assume we know how our businesses run, but the reality is often messier than a teenager’s bedroom," observed Maxime Vermeir, Vice President of AI Strategy at ABBYY, to UC Today, in a striking indictment of the current state of enterprise readiness for the agentic AI and automation revolution.
We are standing at the precipice of a momentous transition from copilots, assistants that wait for a prompt, to autonomous agents that can reason, plan, and execute. The vendor ecosystem is marketing this as the arrival of the "autonomous enterprise," a frictionless future where digital workers handle the drudgery while humans reap the rewards.
However, the view from the ground is far more complex. Knowledge work is rarely a linear assembly line. It is a tangle of undocumented process steps, tribal knowledge, exceptions, and judgment calls that do not translate cleanly into binary code. Even when AI saves time, those gains often manifest in fragmented shards that do not automatically convert into productivity. Whether in enterprises, SMBs, or contact centers, "more efficiency" can quickly metastasize into "more load," creating an AI productivity paradox that fuels burnout rather than relieving it.
The winners in 2026 and beyond will be those organizations that treat digital labor as a rigorous operations discipline. They will define scope, instrument quality, and redesign work rather than bolt agents onto broken processes.
The "Tribal Knowledge" Trap With Automation
The primary friction point for agentic workflows is not the models' capabilities, but the opacity of the work they are asked to perform. Corporations are built on "Standard Operating Procedures" (SOPs) that often bear little resemblance to how work actually gets done. When an autonomous agent attempts to navigate these undocumented waters, it crashes against the rocks of human intuition.
Vermeir recalled a deployment for a large European financial institution aimed at automating a loan approval process. On paper, the SOP was clear. "But once we started implementation, huge gaps came to light," Vermeir said. "We found missing data, systems refusing to approve valid requests, and customers waiting indefinitely in digital limbo. The so-called 'Standard Operating Procedure' truly depended on the human intuition and understanding, nuances that their AI automation plan hadn't accounted for."
The lesson was expensive but necessary. If you cannot see the reality of the process, including the invisible roadblocks that only humans know how to bypass, automation will fail.
This disconnect is not limited to complex financial instruments. It also plagues routine IT operations. Jeremy Rafuse, Head of Digital Workplace at GoTo, suggested to UC Today that patch management is a classic example where the absence of "tribal knowledge" can cause chaos:
"If important workflow exceptions, like month-end close in Finance or end-of-quarter for sales, aren’t documented or well-known, automation can disrupt critical business moments. We have learned firsthand that missing these blackout windows meant automated reboots happened at exactly the wrong time, affecting productivity and performance."
The implication for IT and operations leaders is that the pre-work for agentic AI is anthropological rather than technical. You must capture the "shadow process" before you can automate it. Rafuse noted that "successful automation depends on capturing and utilizing the human knowledge that guides key operations." Without this, companies are automating their own confusion, scaling errors at the speed of silicon.
The Productivity Mirage With Agentic AI: Redefining ROI
For years, the industry has measured the success of automation in "hours saved." It is a metric that appeals to the CFO, but it is often a mirage. Saving an employee five minutes ten times a day does not necessarily result in fifty minutes of new value creation. It usually results in a fractured workflow, where the employee is constantly context-switching and unable to enter a state of deep work.
Shawn Spooner, CTO at billups, outlined to UC Today that we must look beyond raw throughput to the quality of the workflow:
"The difference between theoretical ROI and actual bottom-line impact comes down to this: are you fragmenting work into AI-assisted micro-tasks, or are you redesigning entire workflows so humans stay in their ‘zone of genius’ while AI handles the mechanical execution?"
Spooner offers a compelling case study from his own organization. Before integrating AI, the billups analytics team could build two custom targeting maps per person per day. "We can now build 14 per person, per day, giving us a seven-fold increase in capacity without adding a single person," Spooner said. "That’s not theoretical productivity. That’s seven times more client deliverables, seven times more strategic conversations, seven times more revenue opportunity from the same team."
