one-three-one-rule

Structure technical recommendations by defining one problem statement, comparing three viable options with pros and cons, and concluding with one recommendation, a definition of done, and an implementation plan.

The best way to present tool selection to stakeholders is a 1-3-1 format: one concise problem statement, three distinct approaches with practical pros and cons, and a single actionable recommendation with an implementation plan.

Write a migration proposal by framing the decision as one problem, presenting exactly three options with trade-offs, and selecting one recommendation with a definition of done and an implementation plan.

Yes, you can use this approach for refactoring strategies, architecture choices, tooling trade-offs, and migration planning whenever multiple viable paths exist and trade-offs are not obvious.

You need a formal decision-making format when several valid technical approaches exist and the trade-offs between them are not obvious, requiring structured comparison to reach an actionable recommendation.

Yes, the one-three-one format requires an implementation plan for the recommended option, along with a definition of done, to ensure the technical decision translates into actionable steps.