Group Facilitation
The Secrets of Facilitation Summary: Plan, Question and Record Well
The Secrets of Facilitation treats a useful meeting as a deliberately prepared process of questioning, shared recording, participation and follow-through, rather than a conversation rescued by a confident chairperson.
One-Sentence Answer
The Secrets of Facilitation treats a useful meeting as a deliberately prepared process of questioning, shared recording, participation and follow-through, rather than a conversation rescued by a confident chairperson.
What The Book Is About
Michael Wilkinson's SMART stands for Structured Meeting And Relating Techniques. The selected second-edition paperback is the October 2012 volume, ISBN 9781118206133, identified by the Wiley publisher record. Its contents range from questions and preparation to recording, disagreement, virtual meetings, larger groups and cross-cultural facilitation.
Wilkinson's own overview adapted from the book describes ten SMART principles. The five themes below are our reading priorities, not a claim that he teaches a five-step method. We concentrate on the communication choices a team can examine before trying the manual's many techniques.
The publisher's authorized opening chapter also emphasizes participants creating, understanding and accepting the result. This guide combines that chapter, the selected-edition contents and the author's public explanation. The distribution-centre example and its questions are original and hypothetical. They illustrate possible applications, not a documented client success, a transcript from the book or a guarantee of consensus.
Who Should Read It
- Team leaders who need participants to help produce an answer rather than merely receive instructions.
- Facilitators who want a practical reference for preparation, question design, recording and closing a session.
- Project staff trying to turn disagreements between functions into a discussable set of facts, options and responsibilities.
- New facilitators willing to rehearse instructions and questions before facing a group.
- Readers seeking confidential mediation, disciplinary procedures or specialist decisions should use the appropriate process and expertise; a workshop does not replace those safeguards.
Main Summary
Wilkinson approaches facilitation as a set of learnable, repeatable choices. A leader cannot simply invite people to participate and assume that useful group thinking will follow. Someone must establish why the gathering is needed, what it should produce, whose knowledge belongs in the room and how the work will proceed. His five Ps of preparation name purpose, product, participants, probable issues and process.
Questions then guide the group through its work. Different questions perform different jobs: establishing information, opening possibilities, comparing alternatives or checking an apparent agreement. The facilitator's task includes knowing which job is needed and giving participants an intelligible route through it. A broad invitation to comment cannot do all those things at once.
Recording is another consequential form of communication. Wilkinson gives attention to the power held by the person writing the group's notes. Leaving an inconvenient comment out, rewriting it into a preferred interpretation or recording only the most authoritative voice can change what the group believes it has said. Useful notes need to remain recognizably the participants' work.
The wider method also addresses the group's dynamics. Preparation can reveal likely friction; observation can detect it early; a suitable intervention can make the problem discussable. Disagreement does not necessarily require the same remedy on every occasion. A missing fact, a different interpretation and a conflict over priorities should first be understood rather than forced through one habitual consensus exercise.
The book is most useful as a resource for designing and improving a real meeting, not as a promise that every meeting needs every technique. Start with one session whose purpose and authority can be explained. Make the questions, records and closing commitments inspectable. The practical benefit is a clearer account of how the group reached its result and what remains unresolved, including matters that the facilitator cannot settle.
Key Ideas
1. Separate the meeting's purpose from its required product
Wilkinson's preparation framework is unusually useful because it distinguishes why people should meet from what they should leave with. An invitation such as “improve handovers” expresses a general ambition. It does not say whether the session should identify problems, choose a process, assign responsibilities or recommend options to someone who has decision authority.
Write the purpose and product separately. For a returns team, the purpose might be to reduce uncertainty between customer support and warehouse staff. The product could be a draft handover containing an agreed list of information fields, plus unresolved questions for the operations manager. This makes the intended conversation more concrete without pretending that the facilitator can authorize every proposed change.
The distinction also helps with invitations. Ask who can describe the work, who will use the output and who can explain constraints. A participant should not discover at the end that the group lacked someone necessary to make its recommendation usable. Conversely, inviting everyone who might be interested can produce a room too large for the actual task.
Probable issues and process complete the preparation. Name likely points of disagreement and decide how the group can explore them. These are hypotheses to check with participants, not labels attached to difficult people. A good preparation note leaves room for correction. It equips the facilitator to explain the session's boundaries and to revise the design when the initial account of the problem turns out to be incomplete.
2. Give each question a job in the conversation
The selected book devotes a chapter to questioning, and Wilkinson's overview treats it as a central facilitation tool. The practical lesson is to connect a question to the kind of thinking the group needs next. Gathering experiences, generating possibilities and evaluating a proposal are related activities, but they ask different things of participants.
Consider “What is wrong with the current handover?” It may produce useful evidence, but it may also invite accusations or jump directly to preferred solutions. A more bounded opening could ask participants to describe the most recent handover that required clarification: what information arrived, what was missing and what they did next. The facilitator can then distinguish several experiences instead of collecting an undifferentiated list of complaints.
Later, ask a question that opens options. Only after people understand the options should the group compare them against a stated requirement. Explain these shifts aloud. Otherwise someone offering a possibility may feel unexpectedly judged, while someone identifying a genuine limitation may be treated as obstructive.
A prepared question is still provisional. If participants cannot answer it, clarify the terms or acknowledge that the necessary information is unavailable. Do not keep rephrasing until they give the answer you wanted. Your question should create a fair opportunity to contribute, not conceal an instruction. The test is whether participants can understand what is being asked and why their answer matters to the work the group is doing.
3. Treat shared notes as something participants must recognize
The power of the pen is a distinctive part of Wilkinson's approach. A visible record can help a group remember, compare and build on its contributions. It can also quietly distort the conversation if the recorder selects only familiar ideas, compresses a concern beyond recognition or presents an interpretation as something everyone agreed.
Ask whether the contributor recognizes the note. A short check such as “Does that preserve your concern?” gives the person a chance to correct the wording before the group builds on it. This is particularly valuable when a long explanation has to become a short heading. Concision should preserve meaning, not simply fit the facilitator's preferred categories.
Keep observations, proposals and decisions distinguishable. “Support does not supply enough detail” is different from “four recent forms lacked a collection window,” and both differ from “add a collection-window field.” Combining them into one bullet can make an inference look like a fact and a suggested remedy look settled.
For the returns example, a concern about missing collection dates should remain visible even if the eventual solution uses a different field name. If someone disagrees with the record, settle the wording or record the disagreement; do not treat the display as an authority independent of the speakers. Shared notes earn their usefulness through correction. Their value is not that they look complete on the wall, but that the group can use them without losing the distinctions it needs to make a responsible choice.
4. Understand the disagreement before choosing an intervention
Wilkinson's public account connects consensus work with understanding why people disagree. For a reader applying that idea, the first task is diagnostic: what exactly are the competing claims? A group may appear stuck on a proposed form when its members are actually answering different questions about workload, customer expectations or responsibility.
Ask each side to identify the part it cannot support and the reason. One participant may need evidence that a new field is used. Another may believe the field solves the wrong problem. A third may accept its usefulness but lack the time or authority to supply it. Repeating an explanation of the field's benefits will not address all three concerns.
Make the decision rule explicit as well. Are participants choosing together, making a recommendation or advising a manager who will decide? Consensus language can be misleading when the result is already constrained or when participants cannot freely disagree. A facilitator should explain those limits before asking for commitment.
Understanding does not ensure that competing priorities can be reconciled within the session. It can produce a more accurate account of the remaining choice: which requirement conflicts with which constraint, what information is missing and who must decide. That is often more useful than a vote taken simply to end discomfort. Use the manual's techniques in service of the actual disagreement, rather than treating an active exercise or a quiet room as evidence that the underlying problem has disappeared.
5. Close by separating decisions, open questions and next actions
The book's attention to closing makes facilitation extend beyond the moment when people stop talking. A productive discussion can still leave participants with different accounts of what happened. One person may believe a proposal is approved, another may think it is an experiment, and a third may be waiting for someone else to obtain permission.
Use the final part of the session to expose those differences. Read back the proposed outcome in plain language. Ask what is settled, what is conditional and what remains open. Do not turn a list of attractive ideas into an action plan unless people have actually accepted the relevant responsibilities.
For each next action, identify an owner and a realistic next point of review. A promise to “look into it” is difficult to follow up because it does not define what information or decision should come back. A narrower commitment might be to check whether the order system can capture a collection window and report the available options at the next handover meeting.
Evaluation should examine the process as well as the result. Which question clarified the work? Which instruction confused people? Did the notes preserve a concern that otherwise might have been lost? These answers give the facilitator something to improve. The objective is not a glowing satisfaction score or an artificial declaration of unity. It is a usable record of the group's work and a clear basis for whatever must happen next.
Practical Takeaways
- Write a purpose sentence and a separate description of the meeting's product before drafting the agenda.
- Check the five Ps with people who understand the work; treat likely issues as preparation hypotheses.
- For each agenda item, decide whether participants are supplying information, creating options, evaluating or deciding.
- Rehearse the first question and the instructions for any breakout activity aloud.
- Ask contributors to confirm compressed notes before treating those notes as shared understanding.
- Keep observations, interpretations, proposed changes and decisions visibly separate.
- State who can authorize the result and what the group's participation can influence.
- Finish with named actions, open questions and a review point that participants can explain in their own words.
How To Apply It
An original example: redesigning a returns handover
Imagine a small distribution centre where customer support records returns requests and warehouse staff arrange the physical receipt. Both groups say the handover is unreliable. Support believes it already supplies what the warehouse asks for. Warehouse staff describe repeated clarification calls. The operations manager asks a facilitator to run a working session.
The facilitator begins before the meeting. In separate short conversations, they ask both teams for a recent example, what made it difficult and what a useful outcome would be. They also check the manager's authority: the group may recommend fields and test a process, but it cannot promise software changes or alter customer commitments on its own.
The purpose becomes “make the information needed for a return easier to provide and use.” The intended product is a draft handover, a proposed trial and a list of questions requiring management or system support. This is more workable than an instruction to make the teams cooperate better.
Open with an intelligible sequence
At the session, explain that the group will first compare examples, then identify requirements, then consider a draft. Invite correction to that sequence. Participants should know that the facilitator is not collecting complaints to decide which team is at fault.
Ask people to describe where a particular request stopped being clear. Record the observable gap separately from the speaker's interpretation. If one person says that support “never thinks ahead,” ask which information was missing in the example and how its absence affected the next step. Do not turn the exchange into a trial of the person's attitude.
A separate column holds possible responses. This lets participants suggest a field or a check without presenting it as the agreed remedy. Where two notes appear to describe the same issue, ask the contributors before combining them. A pickup date and a possible collection window may create different requirements.
Test an apparent agreement
Suppose the group proposes a mandatory collection-window field. Ask each team what it would need to supply or use that field. Support may not always know the answer when the customer first calls. Warehouse staff may need the information only before booking a driver. The disagreement is therefore partly about timing, not whether the information is useful.
An alternative draft might distinguish “not yet known” from a completed field and identify who follows up before booking. That proposal should still be checked against the actual system and customer process. The facilitator's conversation does not establish that the change is technically available or commercially appropriate.
Close by reading back what is being proposed for trial and what remains unapproved. Ask one representative from each team to describe the next step. If their accounts differ, correct the record before ending. The group can then review real examples from the trial instead of relying on whether the original meeting felt harmonious.
Notable Ideas, Paraphrased
- Preparation becomes more useful when purpose and product are not confused.
- The wording of a question influences what kind of contribution becomes possible.
- A group record should preserve participants' meaning rather than the recorder's preferences.
- A good ending makes the status of decisions and next actions understandable.
Original Value: When This Book Is Most Useful
Choose this book when the weak point in a meeting is its design and execution: people do not understand the requested output, questions jump between tasks, notes alter meaning or the close leaves responsibility uncertain. Its breadth makes it useful as a reference to revisit against a particular difficulty. Reading it straight through is not the only way to obtain value.
For a first application, choose one controllable improvement. You might make the product of a session explicit, invite corrections to shared notes or separate a recommendation from an authorized decision. Collect examples of what changed. Avoid claiming that one smoother meeting establishes the whole approach's effectiveness.
It is less suitable as a substitute for specialist dispute handling, organizational justice or a decision-maker's accountability. A well-run process can reveal a limit without removing it. Keep that outcome visible rather than treating it as a failure of participants to engage.
Best Related Books
- Facilitating with Ease! offers another practical facilitation reference; compare the handling of participation and the facilitator's role rather than combining both into a single official method.
- The Skilled Facilitator is a useful contrast when you want to examine the assumptions and reasoning behind an intervention, as well as the activity itself.
- Meeting Design emphasizes designing meetings as experiences with constraints, agendas and interaction choices. It is a useful next step when the overall structure needs rethinking.
- The Art of Focused Conversation offers a more specific conversational sequence through ORID. Choose it when a focused question progression is more useful than a wide toolkit.