Clean Language: Facilitation Questions That Don't Lead the Group

What Clean Language is and where it comes from

The questions you ask in a workshop are never neutral. Every time you paraphrase a participant's answer, introduce a new concept, or offer a category for them to sort their thinking into, you are shaping what gets said next. Clean Language is a facilitation method built on taking that problem seriously.

Developed by New Zealand psychotherapist David Grove in the 1980s, Clean Language began as a therapeutic technique. Grove noticed that when practitioners paraphrased or reframed client language, they subtly redirected the client's thinking away from their own meaning-making. His solution was radical in its minimalism: ask questions that contain only the speaker's own words.

Penny Tompkins and James Lawley systematised Grove's approach in their 2000 book Metaphors in Mind and, on their Clean Language overview, identified a small set of questions that direct attention to the speaker's own words and symbols without adding new information. Caitlin Walker later extended this into group and organisational settings through Systemic Modelling, showing that the same minimal-assumption questioning approach could surface collective intelligence in teams.

Here is the simplest illustration of what makes a question "clean." A coach using conventional active listening responds to "I feel stuck in this project" with "It sounds like you're overwhelmed." A Clean Language facilitator instead asks: "And what kind of stuck is that stuck?" The word "overwhelmed" is the coach's interpretation. The word "stuck" belongs to the speaker. That distinction is the entire method.

The core Clean Language questions

There are twelve canonical Clean Language questions, and you do not need all of them to get started. The questions practitioners reach for most often are:

• And what kind of X is that X? — invites differentiation without suggesting categories
• And is there anything else about X? — non-assumptive; allows a "no" without awkwardness
• And where is X? / Whereabouts? — useful for spatial or embodied experience
• And what happens just before X? — surfaces sequence and causality
• And then what happens? — follows a process forward without directing it
• And what would you like to have happen? — opens desired outcomes

In every question, X is replaced verbatim with the speaker's own word or phrase. The grammatical structure is deliberate. Beginning with "And" signals continuation rather than interruption. "Is there anything else" is designed to allow a clean exit — you can say "no" and that is a complete answer. "What kind of" invites the speaker to make distinctions, but offers no taxonomy to slot into.

You can find the full reference list of twelve questions on the Lawley and Tompkins site. Print it. Use it as a prompt card until the questions feel natural in your mouth, because the most common beginner mistake is tacking on explanatory options: "And what kind of stuck is that stuck — like a mental block, or more of a process issue?" The parenthetical immediately reintroduces your assumptions. The question is no longer clean.

Stage Clean Language, developed by Caitlin Walker for group facilitation, adds a spatial dimension: participants physically position themselves in a room to represent their answers. This makes implicit group dynamics visible and reduces the dominance of the loudest voice, which is a persistent problem that no amount of dot-voting fully solves.

Why facilitator bias operates through question wording

The linguistic priming effect in facilitated workshops is well-documented. Elizabeth Loftus and John Palmer's 1974 study, published in the Journal of Verbal Learning and Verbal Behavior, showed that substituting a single verb in a question — "smashed" versus "contacted" — changed participants' numerical estimates of a car's speed by an average of 9 mph. One word. A 25% variance. In an eyewitness memory task.

The same priming effect operates when a facilitator asks "Were communication issues the main problem this sprint?" Most of the team nods. Three people who were privately thinking about technical debt say nothing, because the question has already named a culprit and asking them to contradict it requires more social risk than agreeing does. That is not a hypothetical. It is what groupthink dynamics look like in practice.

Facilitator bias is also a power problem. In hierarchical organisations, group members defer to the framing offered by whoever holds the room. The HiPPO effect — where the Highest Paid Person's Opinion becomes the anchor — operates partly through question framing. When the facilitator introduces a concept, they are exercising authority whether they intend to or not.

Clean Language creates a structural constraint against this. The facilitator's only valid raw material for the next question is what the participant just said. There is no mechanism by which the facilitator's preferred interpretation enters the conversation, because the questions are not designed to carry interpretation.

Applying Clean Language in user research and stakeholder interviews

User research is where confirmation bias does the most quiet damage. Teams design discussion guides that test their existing hypotheses, then report back that the research "validated" the direction they had already chosen. Clean Language disrupts this because each question is generated from what the participant has just said, not from a pre-written script.

When a participant says "the dashboard feels cluttered," asking "And what kind of cluttered?" can surface whether they mean visual noise, information overload, or irrelevant data. Those are three different design problems requiring different solutions. A conventional follow-up question — "Is it that there's too much information on the screen?" — has already answered for them.

A UX research team working on a UK public sector benefits portal used Clean Language during discovery interviews and uncovered that users described the experience as "like going through a maze" — a spatial metaphor that directly informed the information architecture overhaul. The team replaced a category-based navigation with a journey-based one. That insight came from following the participant's own language, not from the research team's hypotheses about what the problem might be.

Judy Rees, co-author of Clean Language: Revealing Metaphors and Opening Minds, has documented similar applications in organisational interviews and 360-feedback processes, where standard questions reliably produce socially desirable rather than genuine responses.

Using Clean Language in retrospectives

Agile retrospectives are structurally vulnerable to facilitator-led convergence. The facilitator's choice of template, the headings on the sticky-note columns, the summary language used during dot-voting — all of it shapes which problems the team believes are most significant. The format is the agenda, and the facilitator designed the format.

A Clean Language retrospective format works differently. Each person completes the sentence stem: "Something I'd like to have happen is..." The facilitator then uses "And is there anything else?" and "And what kind of X?" to develop each response before the group discusses anything. Themes emerge from the participants' own vocabulary rather than from clusters the facilitator has named.

This is especially useful in psychologically unsafe teams where people are unlikely to contradict a proposed narrative. Because Clean Language questions cannot logically be answered "yes" or "no," they create a gentle obligation to generate original thought. That counteracts passive agreement without requiring the facilitator to call anyone out.

A Scrum Master running retrospectives for a distributed engineering team found that their standard "What went well / what didn't" format consistently produced the same three themes sprint after sprint. After switching to a Clean Language format, the team surfaced a dependency issue with a third-party vendor that had never been named in a retro before. No template had ever pointed at it, so it had never appeared. Caitlin Walker's resources on Clean Language for teams include practical formats that adapt well to this kind of sprint-level reflection.

Using Clean Language in strategy sessions

Strategy workshops are especially prone to anchoring bias. The first framing of a problem, usually offered by the most senior person in the room, becomes the default around which everyone else orients. Clean Language questions disrupt anchoring by preventing the facilitator from paraphrasing or synthesising until all voices have been developed on their own terms.

The desired-outcome questions — "And what would you like to have happen?" followed by "And when that happens, what happens to X?" — map naturally onto the logic of well-formed outcomes in coaching and strategy. You can run a vision-setting or OKR session using these questions without participants needing to learn any new vocabulary or framework. The questions do the structural work invisibly.

Caitlin Walker's Clean Learning organisation has facilitated large-scale Systemic Modelling sessions with NHS teams and educational institutions in the UK. In those sessions, Clean Language questions surfaced how different departments understood the same strategic goal differently, revealing that what looked like a shared vision contained fundamentally incompatible assumptions about priority and resource allocation. The Clean Space technique — where participants physically move between labelled positions to represent different stakeholder perspectives — is particularly effective at externalising those hidden divergences before any synthesis is attempted.

For facilitators using Workshop Weaver to design and document their sessions, Clean Language questions fit naturally into discovery and divergence phases. They require no special materials, no elaborate setup, and almost no explanation to participants beyond a brief note that you'll be listening closely and reflecting their own words back.

Practical tips for getting started

Do not try to convert an entire workshop to Clean Language at once. The questions can feel strange or robotic to participants who are not expecting them, and to facilitators who have not practised them. The method requires contracting: tell the group upfront that you will be repeating their words back precisely and asking minimal questions, and explain why. People generally respond well when they understand that the approach is designed to protect their thinking from your interpretations.

Practise the questions separately from your facilitation. Say them out loud until they feel natural. Judy Rees recommends a "Clean Feedback" practice where managers replace evaluative language in one-to-ones with Clean Language questions. Managers who trialled this in her programmes reported that direct reports began volunteering information that had never surfaced in years of conventional appraisal discussions. That is a low-stakes environment in which to build the habit before using it in a high-stakes workshop.

The single most effective entry point is one question: "And is there anything else?" Used consistently instead of paraphrasing, it reduces facilitator-led closure in almost any meeting format without requiring any other change to your facilitation style. Ask it, wait through the silence, and notice what surfaces that your next prepared question would have closed down.

Try it in your next meeting

Start there. In your next meeting, when someone finishes speaking, ask "And is there anything else?" instead of summarising what they said. Use it two or three times. Notice what you get.

That single question is what Clean Language practitioners mean when they talk about reducing your linguistic footprint. It costs you almost nothing. It gives the speaker more space than almost any conventional facilitation move does.

For the full twelve-question reference, the cleanlanguage.co.uk site run by Lawley and Tompkins is the definitive starting point. Caitlin Walker's Systemic Modelling resources are the best guide to scaling the method into group and organisational contexts.

If you try "And is there anything else?" in a workshop or meeting this week, share what you noticed in the comments below. And if you want the twelve core questions on a single printed page, download the one-page reference card — it's the kind of thing worth taping to your facilitation kit.