Facilitation Skills - All Things Product Podcast with Teresa Torres & Petra Wille
Listen to this episode on: Spotify | Apple Podcasts
Conflict on a product team isn't a warning sign — the absence of it usually is.
In this episode of All Things Product, Petra Wille and Teresa Torres tackle a question Teresa hears constantly: what should a product trio do when collaboration breaks down and disagreement turns into friction?
Petra makes the case for something many teams quietly abandoned — the retrospective — and argues that facilitation is a genuine, learnable skill that product people should invest in, not outsource by default. Teresa introduces a framework from academic research on team dynamics: the distinction between task conflict (we disagree on how to do the work) and relationship conflict (something about how we work together puts us at odds). The two require completely different responses, and confusing them is where teams get stuck.
Together they get practical about team charters, when to bring in a neutral third party, how to choose that person, joint escalations, and why running an experiment often beats arguing over opinions.
If your trio is avoiding hard conversations — or having the same one on repeat — this one's for you.
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: https://ProductTalk.org
- Follow Petra Wille: https://Petra-Wille.com
Mentioned in this episode:
- Team Radar retrospective method “The Secret Weapon of Retrospectives - the Team Radar” — 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
Join the Conversation:
Have thoughts on this episode? Leave a comment below.
