one-three-one-rule

The 1-3-1 framework for technical decision-making frames a complex problem by providing three viable options with trade-offs and a single recommended path. It delivers a concise brief containing a problem statement, recommendation, definition of done, and implementation plan.

To structure an architecture proposal with multiple options, define a single problem statement, present three viable options (A, B, C) with pros and cons, and deliver a single recommendation. The brief concludes with a defined definition of done and an implementation plan.

Use a three-option decision brief for software projects when facing architecture choices, tooling selections, refactoring strategies, or migration paths. It provides a structured, repeatable framework to present balanced options with a clear recommendation and implementation plan.

Yes, you can use this decision framing approach for migration planning. It applies directly to migration paths across software projects, delivering three viable options with trade-offs, a single recommendation, a definition of done, and an implementation plan.

The best way to compare tooling selections with trade-offs is using a 1-3-1 decision brief. It frames the tooling selection as a single problem, delivers three viable options with pros and cons, and recommends a single path with a definition of done and implementation plan.

Yes, a 1-3-1 decision brief includes an implementation plan. Alongside the problem statement, three options with trade-offs, and a single recommendation, the brief explicitly requires a defined definition of done and an implementation plan to guide execution.