liveBook · Manning

Decision making

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

A decision is a conscious choice between two or more alternatives that irrevocably allocates resources such as time, money, or energy.

A decision is a conscious choice between two or more alternatives that irrevocably allocates resources such as time, money, or energy. It is an actional process rather than an automatic habit: someone must think, choose, and commit resources whose loss makes being wrong costly. section 9.1.1

A decision becomes clearer when you identify its working parts:

  • Alternatives are distinct plans: sets of intended actions aimed at a desired outcome. section 9.1.1
  • Information changes uncertainty and confidence; preferences help evaluate the available alternatives, but framing can influence those preferences. section 9.7
  • A clear problem statement establishes what the decision must address, while logic derives a course of action at a depth suited to its complexity. section 9.7
  • A designated decision-maker needs authority to allocate resources, even when the surrounding process is collaborative. section 9.7

A resolution becomes a decision

Declaring a New Year’s resolution does not necessarily create a decision. If someone never invests time, money, or energy in going to the gym or starting to swim, no irrevocable allocation has occurred. Commitment begins when the chosen plan receives resources and changing course carries a cost. section 9.1.1

In collaborative software design, decisions should be judged by the quality of the initial context and analysis, not only by the eventual outcome. Sustainable solutions require many smaller decisions that account for sociotechnical effects, suitable decision-making styles, buy-in, and conflict. Formalize chosen alternatives and consequences, communicate them, then keep them open to feedback and revision. section 9.7 section 11.1 section 11.3

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

How deep it goes
Defines choices, alternatives, resources, information, preferences, and analysis, then extends them into styles, documentation, and feedback loops.
Examples
Uses New Year’s resolutions, software design choices, collaborative modeling, formalized consequences, and ADRs as teaching artifacts.
What it assumes
Assumes familiarity with ranking, cognitive bias, and conflict while distinguishing deliberate decisions from automatic habits.
What you can do after
Apply it via problem statements, alternatives, information gathering, explicit resource commitment, documented consequences, and iterative feedback.
How it connects
Links decisions with habits, alternatives, cognitive bias, framing effects, conflict, collaborative modeling, and decision-making styles.

Also explained in

Compare how 6 books explain decision making →

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.