We spent two decades drawing swimlanes so that a system of record could execute them. The AI era flips that. The flow of work now sits in the collaboration layer (Teams, Outlook, Copilot, and whatever your organisation runs), and the unit of design is no longer a task in a flowchart but a skill an agent can pick up, with its inputs, its guardrails, its permission level and the memory it needs to do the job properly.
This webinar shares how a multilateral development bank is reworking the future-state processes of one of its most sensitive functions: eight service flows redesigned as experience blueprints, an authority ladder that says how far an agent may act before a human decides, and a catalogue of reusable skills governed like any other enterprise asset. Craig Martin also covers the uncomfortable bits: the data that was never governed, the subject matter experts who wrote the rules while still working in silos, and the IT department that wanted to flowchart it all over again.
For EA and BPM teams the message is direct. Your process repository is about to become the training ground and the rulebook for agents. Design it that way, and the tools you already run become the foundation for enterprise readiness rather than a museum of how work used to be done.
WHAT ATTENDEES WILL TAKE AWAY:
- The five-rung automation ladder: a plain scale of agent authority, from “suggest” to “act and report”, and where the human decision gate sits on it.
- How to turn a level-three process into a skill definition, with a worked example (a case intake process rewritten as a skill, its guardrails and its memory needs).
- What to add to your capability, process and application models today so they survive first contact with an agent: permission level, guardrail IDs, data sensitivity class and the memory each activity reads and writes.
