Adoption Workshop. Patterns, not tools.
For teams that already have AI installed and nobody uses it. One or two days in-company: your team leaves with workflows built on their real processes and clear criteria for what to delegate to AI and what not to.
What it is
The adoption problem is almost never the tool: it's that nobody translated the tool into the team's real work. The workshop works on your processes and your cases. Each area leaves with concrete workflows built during the session, not a generic demo.
We train patterns that survive tool changes: how to structure context, when to delegate to AI and when not to, how to verify output before it reaches a client. Adoption failures are about people and processes before technology, so the workshop works on the people and the processes.
Who it's for
- Teams with paid AI licenses and low real usage
- Post-Sprint companies wanting to extend usage beyond the delivered system
- Non-technical areas: administration, sales, operations
- Leadership wanting common criteria for safe use across the company
What you get
- 01Workflows built during the session, per area and on real cases
- 02A pattern playbook applied to your processes, not a generic manual
- 03Explicit criteria for what not to delegate to AI
- 04A list of usage risks detected during the workshop
How we work
- Before
Survey
Short questionnaire per area: processes, installed tools, cases where AI isn't used today or is used badly.
- Day 1
Patterns on real cases
Work per area on the surveyed cases. Each group builds concrete workflows during the session.
- Day 2 (optional)
Deep dive
Second pass per area: workflow refinement, verification criteria, accumulated questions from day 1.
What it does NOT include
- It is not a tool demo or a generic prompting course.
- It does not build systems: that is the MWP Sprint.
- It does not define the company's risk posture: that is the AI Governance Briefing.
Specific questions
Is it useful if we haven't bought any tool yet?
Yes, and it's usually the better moment: the workshop defines patterns and criteria before paying for licenses, which avoids buying on hype.
Is it for technical or non-technical profiles?
Mixed, and no code. Groups are organized by area and each one works on its own processes.
How many people can participate?
Up to 30, in groups by area. Beyond that, we split it into two workshops.