liveBook · Manning

Competing heuristic

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

A competing heuristic is a valid decision rule that directs action differently from another valid heuristic in the same situation.

A competing heuristic is a valid decision rule that directs action differently from another valid rule in the same situation. The conflict is not between right and wrong choices; it is between valuable outcomes, such as speed and completeness. section 3.2.2

Balancing speed and minority wisdom

During Big Picture EventStorming with more than ten people, splitting participants between pivotal events can improve progress and speed. Keeping everyone together can preserve complete and minority perspectives. A practical compromise is to work in subgroups, converge centrally about every 30 minutes, and ask who can relate to each part of the timeline. section 3.2.2

Use competing heuristics as a prompt to make trade-offs explicit:

  • Name the valid heuristics and the different outcomes they favor. section 3.2.2
  • Choose a workable combination when both outcomes matter, then refine it as recurring experience adds nuance. section 3.2.2

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

How deep it goes
Explains the conflict through a worked EventStorming trade-off and a convergence pattern, without developing a general selection procedure.
Examples
Uses subgrouping, timeline enforcement, central convergence, and minority-wisdom prompts in Big Picture EventStorming.
What it assumes
Assumes familiarity with heuristics and collaborative modeling while using Domain Events and pivotal events as working context.
What you can do after
Apply competing heuristics by balancing progress and completeness, then refine the facilitation pattern through recurring experience.
How it connects
Connects heuristics with EventStorming, Domain Events, pivotal events, group convergence, and minority wisdom.

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.