Your team, your tenant, seven dimensions. Not a course about AI in general. A working session on whether your Workday configuration can actually carry agents, and what breaks first if it cannot.
No single person holds the whole picture. Readiness sits with whoever owns Workday security, whoever owns the business process framework, whoever owns financial controls, and whoever owns the budget. In most organisations those are four different people who have never been in the same room about this.
The workshop puts them there. That is most of the value, and it is why this is a team session rather than a seat you buy for one person.
Each module works through your real configuration rather than a demo tenant. You complete the readiness assessment beforehand, and the session is built around where you actually scored badly.
Which agents are generally available against limited release against merely announced. Which ones need modules you do not license. Mapping agents to business processes you genuinely run, and naming an owner for each.
Which security groups agents operate under. Reviewing domain security policies for every domain an agent touches. Whether your custom security groups accommodate agent identities without granting excess access, and who holds the consumption console domain.
The trap that generates most of the noise: the BP policy and the step definition must carry the same security group. Condition rules that silently misroute agent actions. Delegation compatibility. Identifying steps that need judgement an agent cannot supply.
An agent reading a messy supplier master produces confident nonsense. Worktag consistency across the objects agents touch. Orphaned ledger accounts an agent might select. Whether your spend category structure supports the decisions you are asking an agent to make.
Producing evidence of what an agent did for a given transaction. Whether your audit trail distinguishes agent actions from human ones. Segregation of duties when an agent both initiates and completes. What your external auditor will ask, and when to brief them.
Reading the rate card properly. Forecasting by action type rather than blended average, and why the seven-hundred-and-fifty-to-one spread makes averages useless. Allocating consumption to cost centres through worktags. Setting thresholds below the platform defaults.
Who may enable an agent and through what approval. Writing an acceptable use policy that is short enough to be followed. Review cadence after enablement. Escalation when an agent behaves unexpectedly, and assigning accountability to a role rather than to the platform.
A scored readiness assessment across all seven dimensions. A written gap list ranked by what breaks first. A named owner against each gap. And a draft enablement policy you can take to whoever signs it off.
The kit is included, so the consumption model and the contract checklist come with it.
This is a working session on your own configuration, not a training course, and it carries no completion certificate or Workday credential. Only Workday certifies people. What you leave with is a scored assessment, a ranked gap list and a named owner against each gap.
Nobody should approve $4,500 off a web page. Fifteen minutes is usually enough to work out whether a workshop is the right shape for what you need, and I will tell you plainly if it is not.
Both go to saintilcoconsulting@gmail.com. Send your rough team size and the modules you care most about and I will come back with times.