The Facilitative Leader in the Age of AI: Why Process Matters When Answers Are Easy

I am sure you will recognize this scenario: A team is working through a difficult decision. People are naming concerns and trying to agree on what matters most. Then someone says, “We could just ask AI.”

Within seconds, they have a plan or a list of options. It might be useful. But the team still has to test it against what they know, hear from the people affected, and decide what to do. Producing an answer is faster than building shared understanding.

That is why facilitative leadership matters.

The answer is not the meeting

Many teams already know the gap between a document and a decision. A plan is approved, but people keep working from old assumptions. A meeting ends with next steps, but no one has worked through the disagreement underneath them.

AI can widen that gap. It gives the group polished language before they have agreed on the problem or the criteria for a good answer. A leader can slow the group down long enough to ask: Does this fit our situation? What is missing? What would we need to commit to?

Help the group think together

Facilitative leaders bring expertise, but they also shape the conversation. They make room for people to notice, question, interpret, and decide before an AI draft becomes the team's plan. There are three tools in my training I turn to in these situations:

Technology of Participation (ToP) offers one way to do this. Its Focused Conversation method follows an ORID sequence: What do we notice? How do we react? What does it mean? What will we do? These questions help a team examine an AI output before choosing a course of action.
The conversation also has a social side. Someone may feel their expertise was bypassed. A junior colleague may spot a flaw but hesitate to challenge an excited senior leader. David Rock's SCARF model names five areas that can shape these responses: status, certainty, autonomy, relatedness, and fairness. Leaders can use that lens to notice who feels heard, who has room to question the draft, and whose reality it leaves out.
Organization and Relationship Systems Coaching (ORSC) adds another lens: the output enters a group with a history of trust, power, and past decisions. Watch who becomes quiet, what conflict the draft might conceal, and whose knowledge the group is treating as authoritative. People need enough safety to challenge the work before they are asked to own it.

Try this: Facilitate the AI moment

The next time your team uses AI in a planning or strategy conversation:

Frame the question together. Name the problem, constraints, and what a good answer must address before showing the output.
Treat the output as a draft. Ask what people notice, how they react, and what it means for the work.
Invite a real critique. Check the draft for evidence, feasibility, equity, stakeholder impact, and what implementation would take. Ask whose perspective is missing.
Check ownership before deciding. Can the people who will carry out the work explain the choice in their words and name what they will do next?

Afterward, ask where AI helped the team think and where it moved the conversation too quickly. Use that answer to shape the next meeting.