Beyond the copy/paste economy: put AI inside the workflow
Workday's latest research sharpens the enterprise AI question: are we making isolated tasks faster, or removing the manual joins between systems, decisions, and approvals?
The next productivity breakthrough will not come from giving every employee another AI window. It will come from removing the work people perform between windows: reconciling data, translating context, re-entering information, checking policies, and chasing approvals. Workday's research gives leaders a useful test for every AI investment—does it accelerate a task, or improve the end-to-end flow of work?
The signal: employees are still the integration layer
Workday's global study of 6,100 active AI users found that 82% spend significant time translating, copying, and pasting information between systems. Only 27% said their organizations had embedded AI into core business workflows. The outcome gap is important: where AI is embedded in core systems, 60% report time savings of 25% or more; where it sits outside, fewer than one in four report savings at that level.
The practical Workday opportunity
Start with a high-friction process that crosses Workday and another enterprise system—onboarding, absence, payroll exceptions, benefits eligibility, approval routing, or financial close. Use deterministic Workday business rules, security, approvals, and audit trails as the control plane. Apply AI where reasoning helps: interpreting an exception, assembling context, recommending the next action, or guiding a user. Extend, Orchestrate, APIs, and agent-ready tools can then connect the experience without weakening accountability.
Design the boundary between AI and automation
Not every step should be agentic. Stable validations, calculations, transformations, and regulatory controls belong in deterministic logic. AI is most useful where the work is ambiguous, language-heavy, or context-dependent. A strong architecture makes that boundary explicit, keeps consequential decisions reviewable, and records what the AI recommended, what the system enforced, and who approved the outcome.
Why this matters in the GCC
The regional implication is an inference, not a reported Workday statistic: organizations modernizing quickly across multiple entities, jurisdictions, languages, and service providers should prioritize cross-system friction. The practical starting point is a portfolio of measurable workflow interventions—each with a local process owner, data boundary, control design, adoption plan, and value baseline—rather than a broad mandate to deploy copilots everywhere.
- Fund AI use cases around end-to-end process friction, not the novelty of the interface.
- Keep Workday rules, security, approvals, and auditability as the deterministic control plane.
- Measure hours removed from reconciliation, re-entry, exception handling, and approval latency.