one-three-one-rule

To frame a technical decision with trade-offs, decompose the scenario into a 1-3-1 proposal: one problem statement, three options with pros and cons, and one recommendation. This structured format includes a Definition of Done and implementation plan to enable faster alignment.

The 1-3-1 framework for architecture decisions is a structured format that outputs one defined problem statement, three distinct options labeled A, B, and C with concise pros and cons, and a single defendable recommendation to guide tool selection.

Structure an options analysis for a software migration by evaluating three actionable options with pros and cons, selecting a recommended path, and defining a concrete Definition of Done and implementation plan to guide the execution.

You need a defined problem statement and three options for recommendation framing when selecting architectures, tools, refactors, or migrations. This process is required for any multi-option task demanding clear trade-offs and a defendable recommendation.

The 1-3-1 rule for options analysis requires no specific dependencies or environment setup. It is a repeatable format applicable to any multi-option technical decision requiring clear trade-offs, a recommendation, and an implementation plan.

The best way to document a recommendation and Definition of Done is to use a concise 1-3-1 proposal. This format pairs a single defendable recommendation with a concrete Definition of Done and an implementation plan for faster execution.