liveBook · Manning

Questions that aren't questions

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

Questions that aren't questions are opinion statements expressed as questions and containing implicit judgment, assumptions, or direction.

A question that isn’t a question disguises an opinion as an inquiry. Judgment, assumptions, direction, or disagreement remain hidden inside the wording, often because stating the opinion directly feels uncomfortable. section 8.1.2

A disguised disagreement in EventStorming

While choosing pivotal events, P1 says, “Price was calculated” is certainly pivotal. P2 asks, “Do you think it won’t cause a problem?” After P1 agrees, P2 asks, “Are you sure it won’t be a problem?” P2 is expressing the concealed opinion: “I think this event should not be pivotal.” The questions seek agreement so someone else will voice the disagreement. section 8.1.2

Pay attention to the interaction around the question:

  • Treat repeated questions that challenge an agreed point as possible indirect disagreement. section 8.1.2
  • Notice the power effect: questions that aren’t questions carry more influence when asked by someone with higher rank. section 8.1.2

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

How deep it goes
Defines the pattern and works through an EventStorming example, emphasizing hidden opinions and ranking effects.
Examples
Uses a dialogue about selecting “Price was calculated” as a pivotal event.
What you can do after
Diagnose concealed disagreement and recognize when status makes indirect questions more influential.
How it connects
Connects communication behavior with disagreement, collaborative modeling, EventStorming, domain events, pivotal events, and consensus.
Cover of Collaborative Software Design: How to facilitate domain modeling decisions
liveBookmanning.com
Read Collaborative Software Design: How to facilitate domain modeling decisions on liveBook Get the book at manning.com

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.