liveBook · Manning

Last responsible moment

The last responsible moment is the latest point at which a decision can be made without jeopardizing the ability to achieve the required outcome.

How 3 Manning books explain it

BDD in Action, Second Edition

The last responsible moment is the latest point at which a decision can be made without jeopardizing the ability to deliver the required outcome.

How it is used
Guides feature and User Story decisions by delaying detail until ongoing conversations support commitment.
How deep it goes
Defines the timing trade-off and links it to Real Options, but stops short of a detailed decision checklist.
Examples
Uses notification stories, configurable incentives, steel purchasing, and airline tickets to illustrate deferred commitment.
What you can do after
Apply the principle by postponing story detail while preserving time for stakeholder discussion before delivery.

Read how BDD in Action, Second Edition explains last responsible moment →

Build High Value Software Systems

A decision-making principle of postponing a decision until the latest point at which it can still be made responsibly, allowing more information to become available.

How it is used
Guides when to commit to architectural decisions so teams can learn before constraining their options.
How deep it goes
Defines a decision trigger, gives a deferral test, and compares reversibility across architectural choices.
Examples
Compares database choice, schema design, API versioning, deployment region, and monolith-versus-microservices timing.
What you can do after
Apply it by testing whether delaying a decision would break code or a contract, then defer if it would not.

Read how Build High Value Software Systems explains last responsible moment →

Software Architecture Decision-Making

The last responsible moment is the latest point at which a decision can be made while preserving sufficient time to act responsibly and avoid unacceptable consequences.

How it is used
Guides architectural timing while balancing delivery, cost, uncertainty, and future flexibility.
How deep it goes
Distinguishes too-early, responsible, and too-late decisions, then supplies questions for testing whether waiting remains safe.
Examples
Uses vendor lock-in, early domain models, premature integration contracts, and ill-fitting technologies as examples of premature commitment.
What you can do after
Evaluate whether to decide now, defer safely, or preserve options through seams, adapters, feature flags, or versioned contracts.

Read how Software Architecture Decision-Making explains last responsible moment →

Related concepts

Questions about last responsible moment

What is last responsible moment?

The last responsible moment is the latest point at which a decision can be made without jeopardizing the ability to achieve the required outcome.

Which Manning books explain last responsible moment?

BDD in Action, Second Edition, Build High Value Software Systems and Software Architecture Decision-Making.

What is the difference between last responsible moment and delay?

The last responsible moment is the latest point at which a decision can be made without jeopardizing the ability to achieve the required outcome. Delay is elapsed time in which work or value delivery is prevented or slowed by the delivery system.

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.