Most organisations jump straight to booking training. The ones who get the best results start by understanding what they're actually starting from.
The same workshop delivers wildly different results depending on who's in the room. A team with zero AI exposure needs different scaffolding — different pacing, different examples, different psychological safety — than a team that's been quietly using ChatGPT for six months and wants to go deeper.
When you skip the readiness conversation, you're not saving time. You're making a bet that you know the team's starting point well enough to design for it. Sometimes that bet pays off. More often, you end up with a workshop that's too fast for half the room and too slow for the other half, and nobody comes away feeling like their time was well used.
Training without a readiness baseline is guessing. We'd rather spend 30 minutes understanding the team than deliver a session that misses the mark for the group it was designed for.
These aren't a formal survey. They're the five areas we cover in every readiness conversation to build a picture of where a team actually stands.
What tools is the team already using, officially or otherwise? What's the baseline comfort level? Are people enthusiastic, sceptical, or actively resistant? The answers here shape how we frame everything else.
Which repetitive tasks consume the most time in this team's day-to-day? Which are highest leverage for AI — where a 30% time saving translates into real capacity? We want to know where the effort actually goes before recommending where AI should go.
Who are the likely early adopters? Who are the reluctant participants? How wide is the spread between the most curious and the most cautious? The wider the spread, the more deliberately we need to design the session format.
Are there cultural, structural, or individual barriers to AI adoption in this team? "We're not allowed to use AI on client data" is different from "my manager is publicly sceptical" is different from "a few people tried it and had bad experiences." Each requires a different response.
What training has been tried before? What formats have worked well with this team? What hasn't landed? Understanding the team's learning history helps us avoid repeating what didn't work and build on what did.
What's the business reason this training is happening now? Is this driven by a mandate from above, genuine team appetite, a specific productivity target? The motivation shapes which outcomes to design for and how to measure success.
It starts with a 20–30 minute conversation. No formal survey, no diagnostic software, no consulting engagement before the training engagement. Just a direct conversation — with the L&D lead, the people manager, or the CHRO — about the team's current state.
We ask the five dimensions above in plain language. We listen for what's said and what isn't. We ask follow-up questions where the picture is unclear. And we push back if the brief doesn't match what we're hearing about the team.
From that conversation, we put together a simple readiness summary — not a 40-page report, but a clear paragraph on where the team is starting from — and a recommended training approach. That summary is the foundation for scoping everything else: the format, the depth, the examples we use, the build challenges we set.
This is part of how we scope every engagement. It's not an extra step. It's the step that makes the rest of the engagement worth doing.
At the end of the readiness conversation, you'll have:
To be completely direct: the readiness conversation is not a gatekeeping exercise. It is not a prerequisite we use to justify a longer consulting engagement before we'll agree to run training. If you've already decided on the format, know your team's needs, and want to book — we can start there.
But the conversation consistently improves training outcomes. L&D managers who have it consistently report that the session felt more targeted, the build challenges were more relevant, and the team got more from the day. We've never had someone say it was a waste of 30 minutes.
It's free. It takes half an hour. And it makes the training better. That's the case for doing it, stated as plainly as we can.
No. The readiness conversation is a standard part of our scoping process and is included at no cost. It's how we make sure the training we design is actually worth your team's time. There's no invoice, no engagement letter, and no obligation to proceed with training after the call.
That's completely fine — we don't need you to arrive undecided. Even if you know you want a half-day workshop, the readiness conversation still helps us calibrate the content, the build challenges, and the framing to your team's specific starting point. You make the format call; we make it as effective as possible within that format.
No. We've found that formal assessment tools add friction and don't reliably surface the information that actually changes training design. A direct conversation with someone who knows the team produces better signal faster. We're not opposed to organisations that use benchmarking tools separately — we just don't make that a part of our process.
Then we move quickly. The readiness conversation can be shortened to 15 minutes if you have a clear brief. We'll confirm our understanding of the team context, agree on the training design, and proceed from there. Knowing what you want is a good starting point — we just want to make sure the design matches the reality of the team receiving it.
Yes. We've run it with CHROs, heads of department, business owners, and occasionally the team lead directly. The best results come when the person on the call actually knows the team — their workflows, their attitudes, their recent history with training. Title matters less than proximity to the team.
Thirty minutes. Free. No obligation to proceed. Just an honest conversation about where your team is and what training approach makes sense. We'll give you our honest read, not a sales pitch.
Start the Conversation on WhatsApp ↗