liveBook · Manning

Value-based heuristic

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

A value-based heuristic is a rule that shapes attitudes and behavior toward design, work, or the surrounding world.

A value-based heuristic shapes design behavior: periodically remind yourself not to fall in love with a model, and accept discarding it when new information shows it no longer fits. section 11.3.2 section 11.5

Use the heuristic to protect collaborative decisions from attachment and premature commitment:

  • Treat feedback loops as opportunities to adjust or replace the model, not merely extend it. section 11.3.2
  • Watch for availability bias: the first design can feel better simply because it is easier to recall. section 11.3.2
  • Design models in different ways to gather more information, reduce uncertainty, and avoid forcing the problem into an existing model. section 11.3.2
  • When creating an ADR, freeze the model and use copies for subsequent iterations. section 11.5

Replace the first model

A team receives feedback that its initial model rests on weak assumptions. Instead of deforming the model with extensions, it redesigns or discards it and uses the new information to choose a better fit. section 11.3.2

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

How deep it goes
Explains attachment, availability bias, and model fitting, but stops short of a detailed facilitation procedure.
Examples
Uses initial and revised models, discarded designs, and frozen ADR copies as concrete applications.
What it assumes
Assumes familiarity with models, collaborative modeling, feedback loops, and architecture decision records.
What you can do after
Evaluate models more objectively and redesign or discard them when feedback indicates a better fit.
How it connects
Connects collaborative modeling with feedback loops, availability bias, model fitting, and architecture decision records.

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.