The Tuesday morning question
Most AI programs begin with access. Licences go live, a senior leader sends an optimistic email and people attend a session showing what the tool can do.
Then Tuesday morning arrives. There is a queue of actual work, a manager asking for the usual report and no shared view of where AI belongs, what a good result looks like or how much checking is enough.
The workshop may have been useful. It was just being asked to carry an organisational change it could never carry on its own.
Capability is not content people completed
AI capability is the ability to recognise a suitable task, provide the right context, use an approved tool, judge the result and take responsibility for what happens next.
That ability is contextual. Writing a social post, summarising a safety incident and preparing a workforce decision do not need the same evidence, privacy boundaries or human review.
A prompt library can help. It cannot make those decisions for every role. People need practice in the work itself, with standards that match the consequence of being wrong.
Start with one repeated piece of work
Choose a task people already do. Something repeated enough to matter and contained enough to test safely. Map how it happens now before adding the technology.
What arrives? Who decides? Which information is needed? Where does time disappear? What errors matter? What should never be entered into an external tool?
Once the workflow is visible, the useful role for AI is usually easier to see. It might create a first draft, compare two documents, retrieve relevant guidance or check a result against a standard. It may also be the wrong tool. That is a useful finding too.
Build practice around a shared standard
People need examples of acceptable work, not only instructions about features. Give them a real task, a boundary, an example and a way to compare the AI-assisted result with the current approach.
Let them find failure modes while the stakes are controlled. Discuss what they trusted too quickly, what context changed the answer and where human judgement added value.
The aim is not confidence for its own sake. It is calibrated confidence: knowing when the tool is useful, when to check harder and when not to use it.
- One real workflow, not ten hypothetical use cases.
- An approved tool and clear data boundaries.
- A visible standard for a good result.
- Time to practise, compare and improve.
- A follow-up decision based on evidence from the work.
The environment will beat the workshop
If a manager keeps asking for the old process, the old process wins. If the approved tool is slow to access, people use something else. If experimentation creates more work and no recognition, experimentation quietly stops.
Budgets, time, systems, leadership attention and promotion decisions teach people what really matters. That hidden curriculum is running every day, long after the facilitator leaves.
AI capability work has to include the environment around the person. Otherwise we train one behaviour and reward another.
Measure what changed in the work
Attendance tells you who attended. It does not tell you whether the work improved.
Measure the thing that justified the effort: time to complete the task, quality, rework, risk, customer experience, decision speed or whether people returned to use the new approach without being chased.
That evidence gives the organisation a real next decision: stop, adapt, expand or invest. It also turns AI capability from a learning activity into part of how the business improves work.
A tool becomes useful when it changes the work, not when everybody gets a licence.