Enterprise AI Activation Readiness: The Complete Guide
Workday Flex Credits, SAP Joule entitlement, Oracle AI Agents — every HR vendor now sells AI as a checkbox on the renewal. The problem isn't the AI. It's the tenant underneath it. This is the complete guide to the five universal blockers that prevent AI from activating, how each platform compounds the problem differently, and the order in which to fix them.
1. The MIT finding Workday cited at Rising 2025
At Workday Rising 2025, Workday cited MIT research showing that despite billions spent on enterprise AI in 2024, only 5% of organisations saw measurable return. The reason was not the model. It was that AI was deployed in piecemeal pilots, disconnected from how work actually gets done, and layered on top of foundational data and process problems that nobody had cleaned up first.
The tenant underneath the AI was never ready.
2. The a16z analysis (May 2026)
a16z noted in May 2026 that 'most organisations have no idea these [Workday Illuminate] capabilities exist, let alone how to activate them.' Long-time Workday admins describe Illuminate as 'the same manual admin work with a chat surface bolted on' — because the underlying configuration was never cleaned up before AI was layered on top.
Signing Flex Credits is a procurement transaction. It is not a tenant readiness solution.
3. The five universal AI activation blockers
- Foundational data quality — worker records with missing positions, supervisory orgs pointing to terminated managers, job profiles with no skills.
- Role and skill structure — incomplete job profiles and skill taxonomies mean AI agents have no structured context to reason over.
- Process and routing health — broken business process approval chains mean every agent action routes to a dead end.
- Security and data exposure — agents inherit the security model. Unconstrained groups mean the agent surfaces compensation data to managers who should not see it.
- Integration trust — failing payroll integrations mean agent-generated payroll data corrupts downstream systems silently.
4. Platform specifics
Workday Illuminate runs an 800B-parameter LLM trained on 1T+ annual transactions across 11,000+ customers. It requires clean job profiles, healthy BP routing, scoped security, and ISU credential hygiene before any agent works in production.
SAP Joule requires SuccessFactors integrated to IAS, Employee Central Quick Actions configured, the correct BTP subaccount in an allowed region (EU10, EU30, US10, AP10), and an unbroken IAS trust chain — three to five places where a multi-year deployment will have drifted.
Oracle AI Agents inherit fast formula errors, broken approval rules, and value set validation gaps. OTBI reports the agent queries must not error. HCM Extracts the agent reads from must not reference deprecated data groups.
5. When to scan for AI readiness
- Before signing the Illuminate / Joule / Oracle AI contract.
- Before any AI proof of concept.
- After tenant cleanup but before agent activation.
- Before each new agent or use case goes live.
- After every major Workday / SAP / Oracle release.
- Continuously on a quarterly cadence as part of AI governance.
Continue reading
Find out what's broken in your tenant
Free first scan. Read-only access. Results in under 2 hours.
Start Your Free Scan