The AI Activations Playbook That Makes Adoption Real

There is a problem hiding inside every organization trying to adopt AI right now, and almost nobody is naming it correctly.

Somebody impressive stands at the front of the room, shows something flashy, and the audience nods along while quietly thinking: okay, but what does this have to do with my actual Tuesday?

I have watched this pattern play out dozens of times. And I have spent the last several months building something designed to break it.

Today I am launching AI Activation sessions for teams, built on a playbook I have been developing based on years of facilitation work and deep AI practice. The sessions are hands-on, participatory, and designed to do what most AI rollouts skip entirely: get people's brains moving. Not just moving to gain agreement. Moving toward their own ideas about what this technology can do for them.

That distinction matters more than anything else I will say in this post.

The real reason AI adoption stalls

Most conversations about AI adoption treat it as an information problem. If people just understood the tools better, they would use them. If we identify the right workflow optimizations, adoption will follow.

So organizations invest in training. They run lunch-and-learns. They send around newsletters full of prompts and tips.

And then very little changes.

Here is the thing: the people selling AI adoption services already know that relevance matters. They try to show the technology connected to real work. They try to demonstrate time savings. The good ones even tailor their examples to the audience. So why does it still stall?

Because showing people relevance and getting people to experience relevance are fundamentally different things.

You can demonstrate a workflow improvement to a room full of people and have every single one of them agree that it looks useful. They will nod. They will say the right things in the debrief. And most of them will go back to their desks and do exactly what they were doing before. The demonstration landed intellectually. It never landed in their hands.

The gap is participation. When people sit and watch, they evaluate. When people participate and build, they think. And once someone's brain starts generating their own ideas about where AI fits into their own work, you do not have to convince them anymore. They start trying to convince you to let them keep going.

That is the switch. Instead of pushing adoption onto people, you create conditions where they pull it toward themselves.

Every play in my system is designed to flip that switch.

The operator who reads rooms

My whole career has been about what happens when you get people together and try to make something productive come out of it.

I started learning that craft in places that do not show up on a typical AI consultant's resume. In my 20s I learned from behind a DJ booth, reading energy in real time and adjusting before the room tells you something is off. Behind a bar, managing a dozen overlapping social dynamics at once. In retail sales, discovering over and over that listening beats talking every time.

Those instincts eventually carried me into governance design and strategic facilitation. Into rooms where the stakes were real and the disagreements were deep. Where millions of dollars were at risk. Rooms where getting unstuck was dependent upon making good cross-functional, and sometimes cross-organizational, decisions.

I've spent years working with groups where people held fundamentally different interests and still had to reach agreement.

The kind of work where legitimacy depends on people actually being heard, where the format of the process determines whether you get genuine alignment or just a decision that the loudest voices pushed through.

Collective decision-making, open participatory systems, the challenge of building structures where quieter voices carry real weight: these are the things that fuel my professional passion and purpose.

Then there is the AI depth. I was working with machine learning and natural language processing in production environments before most people had heard of ChatGPT. I led an agent standards project in early 2025, when the broader industry was still figuring out what "agent" even meant. I use these tools deeply in my own work every day, and I have for years.

Plenty of people understand facilitation. Plenty of people understand AI. The convergence of both, combined with an operator's instinct for what actually works under real constraints and a genuine commitment to participatory process, is rare.

And it is exactly what this moment requires.

The AI Activations Playbook I designed

My AI Activations team sessions are fun, hands-on, engaging, and insight-rich sessions that help teams move from curiosity and skepticism to excitement-driven alignment with concrete next steps.

The AI Activations Playbook is a modular facilitation system: 8 session arcs, 30 plays, 31 moves, and growing.

I want to give you a feel for how it works, because the architecture is part of what makes this different from every other workshop.

Here are the core components in my AI Activations Playbook:

ARCS are the session journey. They define where the room starts and where it needs to end up.

During a discovery call, an ARC is defined based on the team's actual situation, not a default agenda. Once a session length and type are decided, I customize a set of PLAYS & MOVES to provide a uniquely enjoyable experience for your team.

PLAYS are the bounded modules of work inside an arc. Each play has a job, and each one produces something tangible the team can use after the session.

MOVES are the AI-first interactive mechanics inside the plays, and this is where the facilitation craft lives.

Built on pressure-tested systems

The whole system draws from established facilitation traditions (Google's design sprints, Liberating Structures, Atlassian's Playbook, etc.) These systems have always been a big part of how I've helped create clarity, movement, and better decisions over the last decade of work with startups, events, and consortia.

The unique part of my playbook is that every piece has been adapted to be AI-native and hands-on. People are not just talking about ideas. They are generating, testing, comparing, and reframing with AI in the room.

Three design principles hold the whole thing together:

  1. Sessions have to be useful, meaning they connect AI to the actual workflows and frictions the people in the room deal with.

  2. They have to be participatory, structured so that everyone contributes, especially the people who normally sit quietly because the meeting format never made space for them.

  3. Most importantly, they have to be fun. People who are enjoying themselves try more things, think more boldly, and build stronger connections between the technology and their own imagination.

Those principles are load-bearing. A session that feels like training produces compliance. A session that feels like play produces curiosity. Curiosity is what carries adoption forward after I leave the room.

The shift that matters

There is a specific transformation I design for, and it is the thing I care about most.

People walk in thinking some version of: how is the company going to set up this new technology for us? Passive. Reasonable. But it produces zero momentum.

A great session should inspire curiosity. They leave, wheels spinning, thinking, "These are the things I could do with this technology!"

From waiting to imagining. From recipient to driver. Their eyes open up. They want to keep going. That energy is self-sustaining in a way that no mandate or training manual can replicate.

People start seeing themselves as someone who uses AI to solve problems they already have.

That is real buy-in. Ownership that people chose because they could finally see themselves in it.

And, on top of that, the sessions are designed to produce tangible artifacts that keep that momentum alive: a use-case backlog tied to actual work, a prioritized next-step path, a readiness snapshot, a quick-win shortlist.

Not vague inspiration. Useful outputs that help the conversation travel beyond the room.

What I write about here

I'll share what I'm learning as I build, facilitate, and work with AI in practice.

My practice: Lessons from designing AI-native facilitation

What I learn about AI-native facilitation as I run these sessions. The participation structures that produce real engagement. Why adoption turns out to be a room-design problem. What happens when collective intelligence actually surfaces in a team that did not know it had it. The practical craft of getting a room full of different people to move together toward something useful.

My passion: Lessons from building agentic systems

What I am building and discovering as I work with AI agents, harnesses, and autonomous systems in my own practice. I use these tools every day to run my business, and the things I learn about how they actually behave under real conditions are different from what most people are writing about. This is where I will share the practitioner view: what works, what breaks, and what changes when you let agents do real work.

My purpose: Accelerating the arrival of the paradigm of collaboration

I have written before about the idea that we are moving from coordination systems built on force and gatekeeping toward ones built on legitimacy and rational participation. That conviction runs underneath everything I do. Occasionally I will write about it directly here: what collective decision-making looks like when it works, why participatory systems matter more than most people realize, and how AI might accelerate the arrival of something better than what we have.

To wrap it up

I have been building toward this work for a long time. The decision to go fully independent, building the AI Activations Playbook, and offering team services is an exciting new chapter.

The team sessions are live now.

If you want to follow along as I share what I'm learning, subscribe on Substack to get new posts delivered to your inbox.

And if you want to support my journey, please share this with someone who may need my services.