The AI Facilitator: What Is It and How Can You Become One (with Dana Vetan)
What an AI Facilitator actually does, who the role is for, how to step into it from where you are today, and an exercise you can run in your next meeting.
Work is changing faster than any of us planned for, and not just the work or the tools. The whole industry is shifting with it: what companies hire for, what the market rewards, where the value sits. It’s all in transformation at once. Which brings up a question I keep hearing from people around me:
How is my role going to change, and who do I become on the other side of it?
The noise around the tools is loud right now. The marketing, the launches, the FOMO.
It’s easy to get swept into which app to learn next.
It can feel like there’s one prescribed path. You design, so you become a design engineer. I think there’s more to it than that, and it’s worth keeping your eyes and your mind open. The tools will keep changing. What matters is where the work itself is heading, and which parts of it get more valuable as the making gets cheaper and faster.
And with that comes the opportunity to shift, to evolve, to pivot.
New Roles, New Opportunities
AI tools are part of everyone's workflow now, and the lines between roles are dissolving. A lot of the production and execution will be automated, which pushes people from operating tools toward doing the thinking: strategy, judgment, direction.
New roles are forming around this shift: AI product managers, AI product engineers, design engineers, agentic UX designers, forward deployed designers, and many more.
What strikes me is they don’t all point the same way. Some go deeper into building, with designers and PMs now shipping in code. Some shape how AI behaves. Some exist to govern it: ethicists and compliance leads, a role the EU AI Act is pushing companies to create. There’s no single path here, which is exactly the point: more than one way to grow from where you are.
And then I heard the term AI Facilitator.
I knew it had be discussed.
I asked Dana Vetan, who trains AI Facilitators for a living, to talk it through with me: what an AI facilitator is, where the role came from, who it's for, and whether it could be where our work is heading.
Meet Dana 👋🏽
Dana Vetan is Head of Training, AI Facilitator, and Co-founder at Design Sprint Academy, where she designs and runs high-stakes decision workshops for companies like Google, SAP, HSBC, RGA, and Stepstone. She's spent over a decade coaching cross-functional teams through the moments where smart people can't agree on what to do next, and these days she's rebuilding those methods for when AI is in the room.
She’s the author of AI + Facilitation, where she talks about facilitation remapped for the AI era, helping teams make high-stakes decisions once AI enters the room.
+ a very close friend of mine and collaborator! 😀
You can find, follow, and connect with Dana, here:
Let's Ask Dana 💬
1. Who are you, what do you do, and how did you get here?
I’m Dana Vețan, co-founder and Head of Training at Design Sprint Academy.
I design learning experiences and workshops for cross-functional teams during their high-stakes moments, especially when smart people are stuck in the wrong conversation, circling the same problem, or struggling to reach a decision everyone stands behind.
I didn’t start out with this work in mind. My background is in psychology, and I spent over a decade in a digital agency. Over time, I noticed I kept being pulled toward the human side of the work: how conversations take shape, why decisions stall, and what helps a group move forward.
So I turned those questions into a practice. Then a company. Now I train others to facilitate those moments with more clarity, structure, and care.
These days, much of my work focuses on rebuilding these methods for situations where AI enters the conversation, because AI changes the room in ways people often underestimate.
2. How has AI changed your work and services?
In three ways.
First, demand has shifted. For years, organizations brought me in to help with alignment, strategy, and solution validation. That work is still there, but AI has become the thing teams are organizing around. It brings fear and hype into the same room.
So the facilitation requests we get at DSA now focus on reducing uncertainty. What should our teams do with AI? Where should we focus? How do we know people will use what we build?
Second, the room has changed. AI work brings together people with different definitions of success. Engineers, data leads, legal and compliance teams, UX, research, people and culture, PMs, business leaders, and strategists all see a good outcome from a different angle. No single group holds the full answer.
That means the work is less about getting buy-in and more about building shared judgment.
Third, speed has changed. AI has made the build phase much faster, so high-stakes decisions need to happen sooner. At the same time, teams need more confidence in those decisions, not less. That tension is now part of the work.
My old workshop methods got me part of the way there, but they were built for a different kind of uncertainty. AI brings up questions that often appear too late in the build cycle. Where does human judgment still matter? What risks are we ignoring? What would make users trust this enough to adopt it?
Over the past two years, I rebuilt my methods around those questions: AI Problem Framing, the AI Workflow Sprint, and the AI Design Sprint. They were designed for exactly these rooms, where the stakes are high, the expertise is distributed, and the team needs a decision they stand behind and defend.
3. You train designers, design leads, product managers, and innovation teams for a living. From where you stand, how are these roles changing as AI moves in?
I see these roles starting to overlap. The lines are getting blurry.
Building is becoming more accessible. For people who couldn’t build before, it feels like a superpower. I understand why teams are excited by it. Designers build. PMs build. Engineers build. More people are able to make the thing, not only describe it.
The risk is this: many roles are changing by accident.
We’re letting the tools redraw the work without pausing to redesign the roles around them. Everyone is focused on what AI makes possible, while fewer leaders are asking what the job now requires.
What does good look like for a designer with building power? What should a PM own when prototyping takes minutes? Where should engineering judgment sit when more people are producing working versions of ideas?
This matters because underperformance often comes down to one of three gaps: capability, motivation, or license. People need the skills to do the work, the drive to stay engaged, and the permission to act with enough autonomy.
When someone gets a bigger slice of the pie without clarity, the result is not always empowerment. They don’t know what the job is now. They don’t know the bar. They don’t know how much they are allowed to decide. They don’t always have the skills to carry the new responsibility well.
So instead of becoming more effective, they start to struggle. Motivation drops. Their sense of identity at work gets weaker. The role starts to feel unclear, and with it, the energy they used to bring begins to fade.
That’s the part I don’t want us to miss. These roles are changing, no question. The real question is whether we treat that change as something to design on purpose, or something we let happen while everyone is busy testing the tools.
4. What is an AI facilitator, and how is it different from a workshop facilitator?
An AI Facilitator is a workshop facilitator who helps a cross-functional group make a confident, evidence-based decision about AI in a defined amount of time.
The output is concrete. It might be a use case worth funding, a redesigned workflow, or a build-or-stop decision backed by user evidence.
The first thing I always clarify: an AI Facilitator is not the builder.
They are not there to design, build, or redesign the AI solution. That belongs to the team in the room. The facilitator needs enough AI fluency to understand what AI is good at, where it breaks down, and where the technical details matter. They need to follow the conversation without pretending to be the expert.
The second misunderstanding is the word “AI.” It does not mean the person runs the workshop through AI, or spends the session prompting a tool. AI is the subject of the decision. The facilitator’s job is to hold the room around it.
And these rooms are different. They are usually more cross-functional, more technical, and more politically sensitive than a standard workshop. You have people looking at risk, value, feasibility, ethics, operations, customer behavior, and adoption from completely different angles. The facilitator has to help them build shared judgment across all of those perspectives.
So the difference comes down to three things.
The first is the method. AI Facilitators use specific structures, like AI Problem Framing, the AI Workflow Sprint, or the AI Design Sprint, because open discussion is not enough for this kind of decision.
The second is the outcome. A general workshop facilitator might help a group align, generate ideas, or make progress. An AI Facilitator has to land a clear decision the team stands behind.
The third is the work around the room. There is more consulting, more systems thinking, and more preparation involved. You need to understand the workflow, the decision context, the risks, the users, and the business pressure before the workshop starts.
So an AI Facilitator is not a new name for someone who uses AI tools in workshops. It is a specialist facilitator for AI-related decisions, where the room is complex, the stakes are high, and the team needs more than a good conversation.
5. Who can become an AI facilitator? What skills carry over from what they already do today, and what do they need to build from scratch?
More people than you’d expect.
The people who do this well come from different places: design, consulting, L&D, product, research, sales, agile coaching. The common thread is not one job title. It’s the experience of getting people into the same conversation, helping a group make progress, and keeping the work moving when the conversation gets messy.
A lot carries over.
Reading the room. Holding a process under pressure. Hearing what’s not being said. Sequencing a conversation so it goes somewhere. Staying neutral when everyone else has a stake in the outcome.
If you’ve run a workshop, a retro, a discovery session, or even an informal strategy conversation, you already have part of the foundation.
The new part comes in two areas.
The first is AI fluency. Not technical depth. Fluency. You need enough understanding to know what the team is deciding. What’s the difference between AI used to automate, assist, or augment? What does data readiness mean? Is this a real use case, or a solution looking for a problem? Where does AI add value, and where does it add risk?
You don’t need to code or build models. You need to understand enough to guide the decision without pretending to be the technical expert.
The second part is the method. The structured workshops. The prep discipline. The research, artifacts, and data gathered before the team comes together. The way you onboard the decider and the team so everyone knows what they’re there to decide.
And this is the most teachable part. You learn the method by running the method, reflecting on what happened, and getting sharper each time.
6. Any advice for anyone going through a role transition?
The first thing I’d tell anyone thinking about this move is: don’t treat it like adding one more skill to the job you already have.
Treat it like a new role.
The sooner you do, the easier the transition becomes. It needs time, focus, energy, and, inside an organization, a clear mandate from leadership. People need the license to do the work, not only the encouragement to explore it.
Right now, I’m working with an organization in the UAE making AI Facilitation an official role inside their AI innovation program. It comes with real incentives, clear performance metrics, and permission to run these workshops across the organization. That’s the version that works.
What doesn’t work is treating it like a side project, a pet initiative, or something squeezed into a relaxed Friday. For the role to have real impact, it needs to be seen, funded, and measured as the role it is.
The second piece is mindset, and this is the part I care about most.
The question is always: what do I need to do so the people in this room do their best thinking?
An AI Facilitator is not the person with all the answers. They’re the person who creates the conditions for the group to think better together. Their job is to draw out the collective intelligence already in the room, then help the group turn it into a decision.
The third piece is practice.
Start small and get a lot of repetitions in. Facilitate a session for a team that wouldn’t otherwise have one. Run a structured decision exercise inside a project you’re already part of. Co-facilitate with someone more experienced and ask for honest feedback.
Volume matters more than perfection at the start. Every real session teaches you something. Confidence follows action, not the other way around.
How to "hijack" a meeting and turn it into a workshop (without asking permission)
Take the next step with Dana
Pick the next meeting on your calendar where smart people tend to disagree. You know the kind. Everyone talks. The conversation expands in five directions. People leave with different versions of what happened, and no real decision gets made.
You don’t need a formal facilitation role to change the meeting. You need a marker, a stack of sticky notes, and a wall.
The goal is simple: turn a “talk” meeting into a “do” meeting, without making a big announcement about it.
Before the meeting
Get clear on the one decision this meeting needs to produce.
Not the topic. Not the agenda. The decision.
Then ask yourself: what would a good outcome look like by the end of the hour?
That becomes your north star.
1. The setup
Show up prepared, with stickies and a marker nearby.
Don’t ask, “Can I facilitate this?” That question makes people hesitate. Instead, just stand up and say: “I’ll capture this so we don’t lose the thread.”
2. Visual listening
As people talk, write down one point per sticky note and place each one on the wall.
This does two things. First, it shows people you’re listening in a way everyone in the room sees. Second, it moves the idea out of the person’s mouth and onto the wall. Now the group responds to the sticky note, not the colleague who said it.
That small shift lowers defensiveness and makes the conversation easier to work with.
3. The relevance check
Draw a line across the board.
On the left, write: “Here now”. On the right, write: “Goal for this meeting”.
Pick up each sticky and ask the group: “Does this keep us here, or move us toward the goal?”. Place each sticky on the left or the right. Keep moving.
By the end, the room has a smaller, clearer set of points on the right. Those are the things worth acting on. The decision stops feeling like a blur and starts becoming visible.
That’s the work in miniature. You brought focus to a messy meeting without waiting for someone to hand you authority. You helped the group move from talking around the issue to seeing what needs attention.
Notice how it feels. And if running the room was the best part of your day, take that as a sign that facilitating decisions might be a path worth following.
Are you watching your role change by accident, or are you actively designing the next version of it?
Dana said something early on that I haven’t been able to shake: many roles are changing by accident. Her answer to that is to treat the change as a real role. Not a side skill or an experiment.
A real role takes up space. Time on the calendar, permission to act, a clear reason to exist. Without that, the new work gets piled on top of the old job, and people start to struggle in roles that used to come naturally to them.
If running the room is the part of the work that lights you up, AI facilitation might be the version of your role worth designing on purpose.
Thanks for reading! 🫶
Become a paid subscriber and access all the premium resources! 💎
👉 Subscriber-only posts, prompts and frameworks.
👉 Access to online workshops focused on AI-powered workflows.
👉 Process breakdowns of projects and experiments, from idea to prompts.
More UX + AI Reads 👇🏽
Let’s Collaborate 💫
I help teams design and build digital products, AI experiences and systems. Let’s chat!
Open to Substack collaborations. I’m one DM away!
I’m Ileana Marcut, founder of Creative Glue Lab, a design + development studio focused on digital products, AI-native tools, and systems. I write UX+ AI, a newsletter for designers and product builders that want to design with and for AI, use AI with confidence, and unlock what comes next.
Got something in mind? Email: ileana@creativegluelab.com
 | A guest post by
|