liveBook · Manning

Sustainable design decision

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

A sustainable design decision is a software design choice that a group can maintain and support while remaining aligned with business needs over time.

A sustainable design decision selects the software alternative with the best sociotechnical tradeoff: business fit, user value, maintainability, team understanding, and organizational consequences. It emerges from a series of smaller decisions, refined through feedback as new information appears. section 1.2.1 section 9.1.5

Make the decision durable by:

  • Compare alternative designs and identify their benefits, drawbacks, and practical fixes. section 11.7
  • Ask how decisions are made, who can decide, what creates buy-in, and what happens when people disagree. section 9.1.5
  • Invite relevant stakeholders to express viewpoints and surface concerns before resistance appears later. section 9.2.3
  • Capture context, decision, status, and consequences in an Architectural Decision Record, then revisit it as circumstances change. section 11.7

The BigScreen redesign

A redesign aligned to the “Anytime, anywhere” campaign uses kickoff and follow-up sessions to connect business context, architectural pain points, stakeholder perspectives, and feature quality. Collaborative modeling creates shared language and helps the group reach a decision it can support. section 1.2.1

Figure 1.7 Lurking in the group’s shadows, called the unconsciousness of the group, are a lot of social dynamics, such as ranking, cognitive bias, conflicts, and polarities, that can block the flow of a session and stop the group from moving forward and making sustainable design decisions.

Use the group’s hidden social dynamics as a diagnostic lens: ranking, cognitive bias, conflict, and polarities can block shared understanding and informed decisions. Facilitation makes these dynamics visible while preserving group neutrality. section 1.3.3

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

How deep it goes
Explains decision criteria, buy-in, facilitation, tradeoffs, and documentation, while deferring detailed treatment of specific social-dynamic techniques.
Examples
Uses the BigScreen redesign, collaborative modeling sessions, Pros-Cons-and-Fixes lists, ADRs, and group facilitation scenarios.
What it assumes
Assumes participation in collaborative software design and teaches decision framing, stakeholder involvement, tradeoff analysis, and documentation.
What you can do after
Apply it via collaborative modeling, facilitated buy-in, tradeoff analysis, feedback loops, and Architectural Decision Records.
How it connects
Connects collaborative modeling, stakeholder alignment, sociotechnical tradeoffs, Deep Democracy, feedback loops, cognitive bias, conflict, and Architectural 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.