liveBook · Manning

Two-way door

As explained in Decision Engineering

A decision that can be reversed when circumstances change.

A two-way-door decision is relatively easy to reverse: if the result disappoints, a team can adjust without significant damage. Most technical choices fit this pattern, so lengthy analysis can slow teams without meaningfully reducing risk. section 1.1.2

Examples include:

  • Choosing a feature design or frontend layout. section 1.1.2
  • Prototyping with a new framework or choosing a logging library for one microservice. section 1.1.2

Move quickly: try an option, observe the result, and adjust. For a choice that could become hard to reverse—such as adopting a library across a codebase—first test it in an isolated module. A pilot can inform the later decision about broader adoption. section 1.1.2

Figure 1.1 Decisions that require structured analysis sit in the upper quadrants: high cost of change or high organisational impact.

Use cost of change and organizational impact to distinguish decisions that need structured analysis from those that can move quickly. section 1.1.2

How Decision Engineering covers it

How deep it goes
Defines reversibility, gives examples, and recommends quick trials; contrasts harder-to-reverse choices without detailing their full analysis.
Examples
Uses feature design, frontend layout, framework prototypes, and microservice logging choices as examples.
What you can do after
Apply the distinction to move quickly on reversible choices and test options before broader commitments.
How it connects
Connects two-way-door decisions to one-way-door decisions and technical decision-making.

Also explained in

Compare how 2 books explain two-way door →

Related concepts

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