AI enablement workshop · Two half days
Your team is already using AI. Nobody has decided how.
Two half days with your team. We learn how the work actually gets done, find where AI would genuinely help, and leave you with recommendations, guardrails and a plan you can start on Monday.
Why this exists
Most AI adoption goes the same way. A licence, a lunchtime demo, then silence.
Someone bought the licences. Someone ran a session. A few enthusiasts now use it every day, most people tried it twice and went back to the old way, and at least one person is pasting client information into a free tool nobody approved.
The problem is rarely the technology. It is that nobody started from the work. Which tasks eat the week, which ones people dread, which ones are copy, paste and check, over and over.
We do it the other way round. Processes first, tools second, and only where the time saved is real.
What you leave with
A shortlist, the guardrails, and a team that has already tried it.
- A map of where the time goes. Role by role, the recurring work that eats the week, drawn from the people who actually do it.
- A prioritised shortlist. The handful of places AI will make the biggest difference, scored by time saved against effort, with the first three clearly marked.
- The right tool for each job. Often one you already pay for. And an honest list of the things AI should not be doing in your business.
- Simple guardrails. A one-page guide to what is safe to share, what always needs a human check, and who to ask when unsure.
- Hands-on practice. Your team works through the top recommendations on their own real tasks, in the room, before anyone has to remember a training session.
- A 90-day plan. What starts first, who owns it, and how you will know whether it is working.
All of it written up and sent to you within a week of the second session.
The agenda
First we listen. Then we recommend.
The two sessions sit about a week apart. In between, we test tools against your actual tasks, so nothing we recommend is theoretical.
Day one · How the work actually gets done
-
01
The week, mapped
Each role talks us through a normal week. Where the hours go, what gets repeated, what gets copied from one system into another, and what is still done by hand because it always has been.
-
02
Where it hurts
The bottlenecks, the handovers that stall, the task everyone quietly dreads. This is usually where the best opportunities are, and it is rarely where leadership expects.
-
03
What is already happening
An honest look at how people are using AI today, approved or not. Who has found something that works, what they are putting into which tools, and where that is a risk you did not know you were carrying.
Day two · What to do about it
-
04
The recommendations
What we found, what we tested, and what we recommend. Each one tied to a specific task, a specific tool and a realistic estimate of the time it gives back. Then the room decides which to start with.
-
05
Hands on
Everyone works through the chosen use cases on their own real work, with us beside them. The fastest way from sceptical to convinced is seeing a dreaded task take ten minutes instead of an afternoon.
-
06
The guardrails
Client confidentiality, personal data, and the outputs that must always be checked by a person. Agreed together, so the rules make sense to the people who have to follow them.
-
07
The plan
Ninety days, sequenced. Who owns each change, who the internal champions are, and the one or two measures that will tell you whether it is working.
How we run it
The work first. The tools second.
We talk to the people who do the work, not only the people who manage it. They know where the time goes, and they are the ones who decide whether a new way of working sticks.
We are independent. We do not resell software or take commissions, so we recommend whatever fits, and quite often that is something you already pay for and nobody has switched on.
And we are straight with your team about what this is for. Most people are quietly worried AI is coming for their job. The honest answer, and the one that gets adoption, is that it should be taking the part of the job they least want to do.
Practicalities
The questions you were going to ask.
- Format
- Two half days, about a week apart. The gap is where we test tools against your real tasks and build the recommendations.
- Who should be there
- The people who do the work, across as many roles as you can. Six to twelve is ideal. At least one person who can say yes to a new tool or process.
- Technical knowledge
- None. If your team can use email, they can do this. The enthusiasts will get something from it too.
- Preparation
- A short questionnaire for each person about their week, and a list of the software you already use. Twenty minutes each, at most.
- Which tools
- Whatever fits the work. We are independent and take no commissions. Often the answer starts with tools you already have, such as the AI built into Microsoft 365 or Google Workspace.
- What you get afterwards
- The written recommendations, the prioritised shortlist, the one-page guardrails and the 90-day plan. Sent within a week of the second session.
- Investment
- Quoted per workshop, based on the size of the team and the preparation involved. You will have the number before you have to ask twice.
Contact
Find out where AI would actually help.
Thirty minutes on how your team works and what is taking the time. Free, and useful whether or not you book anything.