liveBook · Manning

Debate

As explained in Collaborative Software Design: How to facilitate domain modeling decisions

A debate is a structured exchange in which participants present and examine opposing positions on an issue.

A debate is a structured exchange that keeps opposing viewpoints focused on ideas rather than personal conflict. In facilitation, framing disagreement as dialogue or debate helps preserve openness, neutrality, and collaborative inquiry. section 8.3.1

Use debate as a facilitation move when disagreement begins to harden:

  • Distinguish task-based conflict from relationship conflict by asking whether emotion is helping or hindering progress. section 8.5
  • Replace right-versus-wrong language with questions about competing ideas and perspectives. section 8.3.1
  • Investigate your own strong opinions so personal bias does not compromise facilitation neutrality. section 8.5
  • Ask whether anyone sees an issue differently, making less-visible opinions conscious in the group. section 8.5

A Kubernetes disagreement

A facilitator who believes Kubernetes is rarely useful may label opposing views as wrong, collect confirming evidence, interrupt, or lobby against the technology. Reframing the exchange as a debate keeps attention on the idea and helps the facilitator remain open to other perspectives. section 8.3.1

Figure 8.4 An example of how our bias blind spot can lead to shadows and demons getting entangled with the group in a software design EventStorming session at BigScreen. Not being aware of how your own bias interplays with that of the group might lower your effectiveness as a facilitator.

Use the bias-blind-spot illustration to examine how a facilitator’s judgments can become entangled with group conflict during a software design EventStorming session. section 8.3.1

How Collaborative Software Design: How to facilitate domain modeling decisions covers it

How deep it goes
Explains conflict framing, confirmation bias, facilitator self-monitoring, and practical prompts without defining formal debate rules.
Examples
Uses Kubernetes disagreement, bias during EventStorming, conflict interviews, movement exercises, and requests for differing opinions.
What it assumes
Assumes participation in facilitated group discussions and teaches learners to distinguish task conflict from emotional relationship conflict.
What you can do after
Practice reframing disagreements, checking personal bias, eliciting alternatives, and identifying when conflict requires intervention.
How it connects
Connects debate with dialogue, conflict resolution, confirmation bias, facilitation, interviews, and EventStorming.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Collaborative Software Design: How to facilitate domain modeling decisions. The section links point to the parts of the book it draws on.