Some English words resist translation into German. “Facilitation” is one of them.
The closest German equivalent is probably “Moderation”. But not quite. Maybe my linguistic sensibilities are just being precious. When I think “Moderator”, I picture a journalist questioning politicians, making more or less successful topic transitions. Maybe cutting off particularly long-winded contributions. Often having their own opinion they share for maximum audience impact.
I don’t want to be that kind of moderator. So I’m sticking with the English word “Facilitator”. A facilitator stays neutral, makes no decisions for the group, leads minimally. It’s about people and processes. Ideally, the facilitator “reads” the room, hears what’s said and what isn’t, and nurtures the magic that emerges when smart, cooperative, relaxed people work together. A facilitator creates an atmosphere where everyone feels comfortable enough to drop their mask a little.
As a Scrum Master, I wear different hats. There’s the advisor role, the guide for various Scrum events like Sprint Planning, Daily Scrum, Sprint Review and Retrospective — and that’s where most Scrum Masters focus. An important role is the facilitator. Unfortunately, it’s misunderstood. Everyone leans back and expects the Scrum Master to animate. But it’s never about the Scrum Master. Always about the group.
Anyone hunting for facilitation methods won’t find much in Marsha Acker’s “The Art & Science of Facilitation: How to Lead Effective Collaboration with Agile Teams”. This isn’t about methods. It’s about the mindset you need as a facilitator to actually move the group forward. Not just mindset — the “soft skills” too (I hate that term, why should these be “soft” abilities?).
What I learned from this book: Build trust, lead by example, stay curious but neutral. Above all, stand brave in the storm, help the group work through conflicts without going to pieces yourself. Recommended.
My notes:
- Respect clear role division: Facilitator owns the process, team owns the content.
- Standing firm in storms: During conflicts or divergent opinions, stay with it. Don’t distract or change topics. On the other side of conflict comes clarity of thinking, new ideas, fresh impulses.
- Many voices add value: Different perspectives create clarity, discernment, deeper understanding, energy. Without these, collaboration becomes less effective.
- Build trust and create space: The group has its own wisdom and everything else it needs to be creative, innovative, solve its own problems. Group members just need space to access what they need.
- Serve the group: Facilitators should constantly ask: “How can I best serve this group? What does this group really need right now?”
- Pause when stuck: Plant feet firmly, breathe deeply, say slowly and thoughtfully: “May I ask you a question? What’s happening here right now?”
- Be neutral, not passive: Take your own position, use perspective to ask curious questions that give the group food for thought. Neutrality offers the gift of “not knowing”. “I’m your sherpa. I’ll guide you up this mountain. There’s a specific process we’ll follow, but you have to do the work yourself.”
- Never forget the process vs content distinction: Facilitator provides process and space so the group can do their best work with the content.
- Rule of thumb for preparation: Spend 2.5 times the meeting duration on planning and design. Example: two-hour meeting = 5 hours for planning and design.
- Standing in storms: Storms are places of energy. When emotions (maybe even your own) run high, the storm is there. Work through conflicts and differences — different perspectives create clarity, discernment, deeper understanding. When a group survives a storm, they gain collective trust and confidence in each other. Standing in the storm is inner work. You must master yourself so the group can emerge on the other side in a collective, productive state. When you want to flee or change topics, be curious instead. Really good ideas often live just on the other side of breakdown, frustration, confusion.
- Trust group wisdom: The group doesn’t need to be taught. It’s worth creating and tapping into collective intelligence. This means focusing full attention on group needs, pushing your own needs aside. Ask: “What’s the highest and best use of our time together?”
- It’s not just about outcomes, but team development: How quickly a team progresses on their agile journey or reaches productive results isn’t necessarily a measure of your value and abilities as a facilitator. Sometimes the better path to efficiency is taking a pause. Slowing action to maintain momentum.
- Note the difference between agile doing and agile being: By their actions you will know them… Observation: top leadership teams in particular are often unable to discuss meaningful topics and develop new thoughts and ideas — it’s the biggest obstacle to agility, adaptable companies, innovative thinking.
- Live your values: Getting teams, especially top teams, to be honest, vulnerable, open with each other is major progress. But also a major challenge for the facilitator.
These book notes are just for me. They might read a bit cryptic. Just read it yourself. More book notes here.
From the archives of reinergaertner.de, running since 1997. Translated with AI help and my questionable bilingual proofreading. If you spot a Germanismus — that’s a feature, not a bug.