liveBook · Manning

Tradeoff triangle

As explained in Grokking Software Architecture

The Tradeoff Triangle is a decision-making tool for making competing project priorities visible and comparing their relative emphasis.

The Tradeoff Triangle makes competing project priorities visible. Choose three forces that matter to the decision, mark where the decision lands, and explain what the team is prioritizing and accepting. section 2.8

Use it to turn a vague disagreement into a concrete priority check:

  • Label the triangle’s corners with three competing forces, such as Speed to Ship, Cost to Operate, and Ease to Change. section 2.8
  • Place a dot to show the decision’s emphasis, then say aloud what is being prioritized and what is being accepted. section 2.8
  • Choose forces that fit the decision; another project might weigh Security, User Experience, and Performance. section 2.8

A V1 launch

Place the dot near Speed to Ship. The team accepts higher operating cost for the first quarter and less ease of change until users provide feedback. section 2.8

A delivery-safety decision

Compare Speed to Ship, Cost to Operate, and Deployability/Reliability. Skipping pipeline gates for short-term speed means accepting higher change failure rates and longer recovery times. section 13.9.4

Figure 2.11 The Tradeoff Triangle allows you to visualize priorities quickly.

A visual reference for quickly marking competing priorities. section 2.8

How Grokking Software Architecture covers it

How deep it goes
Explains how to label, mark, and discuss a triangle, without prescribing a numerical scoring method.
Examples
Uses a V1 launch tradeoff, a cache-timeout exercise, and a pipeline-gate decision.
What it assumes
Assumes a decision with competing priorities and teaches the basic process from drawing the triangle onward.
What you can do after
Apply the Tradeoff Triangle to name priorities, clarify accepted costs, and align a team’s expectations.
How it connects
Connects the triangle to quality attributes, constraints, and Architecture Decision Records.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Grokking Software Architecture. The section links point to the parts of the book it draws on.