Workshop · For business leaders
The Business AI Roadmap Workshop
One morning that takes a leadership team from "what can AI do for us?" to a ranked list of use cases, an operating playbook and a 30/60/90-day plan.
- Length
- 4 hours, one morning
- Group
- 15–25 leaders
- Format
- On site, remote sites welcome
- Pairs with
- Technical workshop
How it works
Step 1 · Assess
Where are you on your AI journey?
Before the workshop we run a short AI maturity assessment: a five-minute survey for staff, interviews with eight to ten leaders, and a review of your systems and data. We score you on three levels of AI value (personal productivity, automated workflows, revenue and growth) and on the ten parts of our Operational AI Playbook. That baseline sets the workshop agenda and the plan.
- 01Discovery interviews45–60 minutes with eight to ten functional leaders: people, processes and KPIs, data and systems, bottlenecks, and where AI is already being used.
- 02AI usage surveyA five-minute survey for attendees and wider staff, reported only in aggregate.
- 03Systems and data reviewA walk through ERP, CRM, production and reporting systems with their owners, so the ideas on the day are grounded in what is possible.
- A scored baseline across the three levels of value and the ten playbook parts
- Your three weakest areas, with the evidence behind each score
- Recommended first actions, carried straight into the workshop
Step 2 · Workshop
The morning, session by session.
Times are a typical 08:00 start. We tailor the demos and examples to your industry.
-
08:00 15 min
What we heard
Why now, and a read-back of the interviews and survey. Ground rules: ask anything, AI is a team sport, and you own the answers.
-
08:15 60 min
What AI can do now
Six capabilities, each shown live on your own public data: content creation; research and checking; data analysis and dashboards; document and data extraction; process automation and agents; conversation and assistance.
-
09:15 30 min
Your AI showcase
Four or five of your own power users demo, in five minutes each, an AI tool they have already built. Peers proving it, not consultants, and usually the most energising part of the morning.
-
09:45 60 min
Breakout: where can AI help your team?
Cross-functional teams list 5–10 use cases through three lenses (processes, data, capabilities), score each for impact and difficulty, place them on an impact/effort grid and pick their top five. Each team reads back. Typical output: around 50 scored use cases.
-
10:45 45 min
The Operational AI Playbook
People: an AI leadership team, roles and training. Process: a tools register; keep, wrap, build or buy; avoiding lock-in; governance scaled to risk; a value scorecard and an AI budget. Technology and data: secure access, data quality and a single source of truth.
-
11:30 15 min
Next steps: the 30/60/90-day plan
30 days: name the AI team and start the tools register. 60 days: shared skills and code, and four or five quick-win builds. 90 days: secure, real-time data foundations.
The breakout exercise
Impact against effort, decided by your own teams.
Every use case is scored for impact (time, money, quality, revenue, customers) and for difficulty (systems, data, people and process change). The grid separates the quick wins from the big bets, and the teams own the result.
Inside the workshop
The frameworks your team works through.
Step 3 · Plan
What you leave with
Your lowest scores become your first actions. We re-score at 90 days, so you see measured progress, not just activity, tracked on a monthly value scorecard.
What leaders ask
The questions that come up every time.
- Is our data good enough? Poor data in means poor answers out; we show where to fix it first.
- Buy, wrap or build? A simple test on cost, skills, criticality and speed.
- Who maintains what staff build? Ownership, a tools register and shared repositories.
- Can we trust the research? How to check sources and keep a human in the loop.
- How do we keep it on brand? Shared instructions, templates and review.
- What are the guardrails? Instructions can be overridden; role-based permissions cannot.