Capability domain
AI and workforce capability
Most AI training teaches tools. This teaches people to understand their own work well enough to direct one.
The problem with tool training
A session about a tool produces people who can operate that tool until it changes, which it will, usually within the year.
It also skips the part that actually determines whether AI helps: whether the person can describe what they are doing clearly enough to hand any part of it to anything else. Someone who cannot articulate their own process will get confident, fluent, wrong output and have no way to notice.
That is not a failure of the technology. It is what happens when capability is assumed rather than built.
What these sessions do instead
They start with the work. What this person or this team actually does, in what order, with what judgment applied where — and which of those parts are stable enough to be worth automating at all.
Then AI enters as a specific instrument for a specific step, with the person still holding the decision. Three lines govern all of it: AI informs decisions. People make decisions. AI as translation, not delegation. AI-enabled organizations without AI-dependent people.
Participants leave able to tell the difference between a task AI genuinely helps with and one where it just produces plausible text faster.
What sessions look like
Practical, hands-on, and built from what your people actually do rather than from generic examples. Laptops are open when there is something to try and closed when there is something to think about.
Formats range from a single session to a multi-part program, and can be delivered to a staff team, to a cohort of business owners, or as part of a wider curriculum. The right shape depends on who is in the room and what they need to be able to do afterwards — which is a conversation, not a menu.
There are no tool tutorials and no list of the ten best applications. That material ages in weeks and it teaches the wrong thing.
Why this is instructional design, not a talk
The founder spent nearly twenty years designing learning for hospitals, law firms and nonprofits before building technology for businesses. That background is the reason this work is measured by what people can do afterwards rather than by how the session felt.
Capability transfer is the point. If your staff still need an outside expert six months later, the session did not work, whatever the feedback form said.
Who this is for
Organizations whose people need to use AI well inside their actual jobs — a workforce program, a nonprofit team, a municipal department, a company training its own staff.
It is also the doorway for organizations serving small businesses. Many programs begin here, discover what their participants actually need, and move into implementation from there. If you are responsible for a cohort of businesses rather than a staff team, the organizational engagement is the more direct route.
What is honestly assessed
Whether the work is stable enough for AI to help at all. Some processes are not, and a session that pretends otherwise sets people up to fail in public.
Whether the constraint is capability or infrastructure. Sometimes a team does not need training — it needs systems that stop losing information, and training would be an expensive way to avoid saying so.
You will get that assessment plainly, before anything is scheduled.
A practical next step
Tell us what your team does and what they need to be able to do. The first conversation costs nothing.
Start a conversation about your team