The AI Control Plane Handbook
Toolkit contents

Appendix B

Workshop agendas

Eight workshops cover a typical five-week assessment. Combine them for a smaller opportunity, and repeat the process, data and architecture workshops for each additional use case. Send the agenda and the relevant part of the data request with each invitation.

1. Executive framing

Length90 minutes
Participants
  • Executive sponsor, business owner, enterprise architect
  • Engagement lead and lead architect
GoalAgree the use case, goals, scope and the value hypothesis to test.
Agenda
  • Goals and pressures for the next 12 to 24 months (15 min)
  • Candidate use cases scored against the selection criteria (30 min)
  • Chosen use case: trigger, end state, users, systems, out of scope (25 min)
  • Value levers and the data needed to baseline them (15 min)
  • Stakeholders and next workshops (5 min)
Outputs
  • T1 and T2 drafts
  • Stakeholder map
  • Confirmed data request

2. Process and systems walkthrough

Length2 hours
Participants
  • Business owner, process leads from each function, application owners
  • Lead architect
GoalWalk the process end to end and find every system, hand-off and manual step.
Agenda
  • The process today, stage by stage, with real examples (45 min)
  • Systems of record, interfaces and who owns them (30 min)
  • Where time, money and risk leak (30 min)
  • Which steps stay human-led, which are AI-assisted and which AI-led, and why (15 min)
Outputs
  • Stages for T1
  • Applications and integrations for T3
  • Pain points and baselines for T6

3. AI estate inventory

Length2 hours plus tool-assisted discovery
Participants
  • AI platform owners, architects, security
  • Lead architect
GoalFind every agent, model, MCP server, API and policy that the use case touches, including shadow agents.
Agenda
  • Agents in production and in pilot, by platform, owner, sponsor and autonomy, and which native control plane governs each (40 min)
  • Models, providers, contracts, data retention, spend and how spend is attributed (30 min)
  • APIs, events and MCP servers, and how agents reach them today (30 min)
  • Policies, guardrails and approvals already in force (20 min)
Outputs
  • Agents, models, integrations and policies for T3
  • Control-plane KPIs baselined for T6

4. Data and master data

Length90 minutes
Participants
  • Data owners and stewards, MDM and catalog owners
  • Lead architect (Informatica specialist as needed)
GoalEstablish which data the agents depend on and how trustworthy it is.
Agenda
  • Master data domains and golden records the use case needs (30 min)
  • Quality issues, duplicates, hierarchy freshness (25 min)
  • Glossary, lineage and classification (20 min)
  • Access policies, masking and information barriers (15 min)
Outputs
  • Data assets for T3
  • Data requirements for T4
  • Data-quality risks for T12

5. Requirements and security

Length2 hours
Participants
  • CISO or security architect, risk and compliance, enterprise architect
  • Lead architect
GoalAgree the requirements and the controls for every layer, and the autonomy tier for every agent.
Agenda
  • Requirements walkthrough and priorities (35 min)
  • Security by layer: users, agents, A2A, MCP, APIs, models, data, audit, and the threats each control covers (45 min)
  • Autonomy tiers, promotion and demotion rules, and approvals bound to actions (20 min)
  • The kill switch and human takeover: who takes over, with what information (10 min)
  • Regulatory obligations, the standards the client reports against, and evidence (10 min)
OutputsT4 and T5

6. Architecture

Length2 hours
Participants
  • Enterprise and solution architects, platform owners
  • Lead architect (MuleSoft and Informatica specialists as needed)
GoalDesign the north star for the use case and show how it is realized.
Agenda
  • North star: the five layers filled with the client’s assets (40 min)
  • A day in the life and how the components work together (40 min)
  • Realization with MuleSoft Agent Fabric and Informatica, and what stays the client’s choice (30 min)
  • Review against the framework the client uses (10 min)
OutputsT7 to T10

7. Value and phasing

Length2 hours
Participants
  • Business owner, finance partner, sponsor’s delegate, HR or change lead
  • Engagement lead and lead architect
GoalAgree the milestones, the quick wins, the value at each milestone, how value will be reported, and who owns what once the agents are live.
Agenda
  • Baselines and the value method (20 min)
  • Milestones and what goes live in each (30 min)
  • Value, costs and ROI per milestone, against published payback benchmarks (30 min)
  • Reporting: who signs off value, and when (10 min)
  • Operating model: owners, decision rights, skills and adoption measures (30 min)
Outputs
  • T11
  • T13
  • Value and cost inputs for T12

8. Readout

Length60 minutes
Participants
  • Executive sponsor and leadership team
  • The engagement lead chairs and the lead architect presents the architecture
GoalSecure the decisions for the first 90 days.
Agenda
  • Opening: the goal of the meeting and the agenda (3 min)
  • The use case, how the assessment ran and what discovery found (10 min)
  • The value at stake (5 min)
  • Requirements, security and the recommended architecture (17 min)
  • Phased plan, KPIs and value at every milestone (12 min)
  • Decisions and next steps (13 min)
Outputs
  • Decisions
  • 90-day plan
  • Client report and deck