Facilitation Skills

Key takeaways

• Retrospectives still work. Agile may feel unfashionable, but the practice of pausing to ask "how are we working together?" is one of the most valuable things a team can protect time for.

• Facilitation is a skill, not a personality trait. Someone in the organization needs to be good at it — and product people should be learning it, not just relying on an agile coach or scrum master.

• Team charters go deeper than mission statements. The powerful version isn't "what's our outcome" — it's working hours, communication preferences, and how each person likes to make decisions. Making implicit norms explicit prevents friction before it starts.

• Task conflict vs. relationship conflict. Task conflict is disagreement about the work. Relationship conflict is about how you work together. Team charters address the second; shared discovery addresses the first.

• Task conflict is good. It's how teams get to better problem solving. If there's none at all, that's likely a psychological safety problem, not a harmony win.

• Bring task conflict to the team. What looks like two people disagreeing is often a disagreement others share silently — or one someone else on the team can resolve.

• Relationship conflict starts one-on-one. Try to resolve it directly first; HR or mediation is the escalation path, not the opening move.

• Choose your facilitator deliberately. Ask whether context helps or hurts. An embedded agile coach may know too much history to stay neutral; sometimes the product person — or a senior engineer with strong facilitation instincts — is the better pick.

• Leave your ego at the door. A facilitator writes the headline post-its and nothing else. Skilled facilitators even signal role changes physically — Petra describes one who literally switched chairs to mark "team member" vs. "facilitator."

• When it's opinion vs. opinion, run an experiment. Design a test rather than escalating a debate.

• Joint escalation as a tool. Having both parties write down the conflict together often shrinks it — and gives leadership something concrete when escalation is needed.

Resources & Links:

• Follow Teresa Torres: ProductTalk.org

• Follow Petra Wille: Petra-Wille.com

Mentioned in this episode:

• Team Radar retrospective method “The Secret Weapon of Retrospectives - the Team Radar (petra-wille.com/blog/the-secret-weapon-of-retr…)” — Petra's go-to format for surfacing what the team thinks about a specific tension

• Teresa’s article on how teams can create a team charter: Take a Team Approach to Product Delivery (producttalk.org/taking-a-team-approach-to-prod…)