one-three-one-rule

The 1-3-1 rule for technical decision making compresses a problem into one sentence, presents three distinct options with trade-offs, and recommends a single path with an implementation plan. It clarifies architecture choices by making trade-offs explicit to stakeholders.

To write a technical proposal with trade-off analysis, frame the decision in one problem sentence, list exactly three viable options labeled A, B, and C with pros and cons, then select one recommendation and define its implementation plan and definition of done.

Yes, you can use the 1-3-1 format for tool selection and migration strategies. It applies to any technical decision with multiple viable choices, including architecture decisions, toolchain selection, refactoring approaches, and migration strategies.

To structure a definition of done for an architecture decision, select your recommended option from the 1-3-1 analysis and outline an actionable implementation plan. The definition of done specifies the exact completion criteria for executing and sharing the chosen path.

You should use a structured recommendation over a simple proposal when making high-stakes technical decisions between multiple viable choices. The 1-3-1 format turns vague choices into explicit trade-offs, making the decision understandable to both engineers and stakeholders.