back_office_ops · saas · workflow
Why Johnny Can't Use Agents: Industry Aspirations vs. User Realities with AI Agent Software
There is growing imprecision about what AI agents are, what they can do, and how effectively they can be used. A systematic understanding of how the tech industry conceives AI agents and how end-users actually experience them in practice is lacking.
How it works
Common implementation structure
How this type of workflow is generally built, generalized across documented cases — not tied to any one vendor's stack. Click any stage to read what happens there. Specific products that implement these stages appear in “Tools commonly seen” below.
Stage 1 · User objective provided
The agent workflow is initiated by a given user objective.
Tools used
OperatorManus
Outcome
A systematic review of 102 commercial AI agents yielded a taxonomy of three umbrella categories (Orchestration, Creation, Insight). A think-aloud usability study on Operator and Manus found users were generally impressed but faced five critical usability barriers.
What failed first
Historical agent designs such as Microsoft Clippy frustrated users by having interfaces that promised more than the underlying AI could deliver, and current commercial AI agents risk repeating these same mistakes.
Results
Volume102
Grounding & classification
Source type: technical build writeup
21 fields verified against source quotes.
agentic workflowai agentcomputer visioncontent generationknowledge basefailure mode describedsource backedtools describedworkflow describedsoftwaretechnical build writeupback office opsagentic task execution