one-three-one-rule

The 1-3-1 rule is a technical decision-making format that produces one clear problem statement, three distinct solution options, and one concrete recommendation with an action plan to compare and choose technical solutions.

Structure your technical proposal by defining a single problem statement, evaluating three alternative approaches with trade-offs, and selecting one recommendation with a detailed action plan to guide architectural decisions.

You need a structured framework for evaluating tool selection trade-offs when multiple viable approaches require detailed evaluation to support complex problem framing, architectural decisions, or refactoring decision processes.

Yes, the 1-3-1 proposal format is designed to meet requirements in architectural, tool selection, and refactoring decision processes by offering structured options and recommendations that support informed decision-making.

The best way to document strategy recommendations is using a structured format that compares multiple technical solutions by framing the problem, detailing alternatives with trade-offs, and providing a single actionable recommendation.

Yes, this decision-making framework works for high-performance web service scenarios, such as choosing an API client retry strategy, by systematically comparing viable approaches and proposing a concrete action plan.