one-three-one-rule

To structure technical decisions, use the 1-3-1 format to outline one problem, three options, and one recommendation with rationale. This structured decision-making approach clarifies trade-offs and provides a clear implementation plan for architectural choices.

The 1-3-1 rule is a structured decision-making format that outlines one problem statement, three viable options, and one final recommendation. It helps developers weigh pros and cons to reach a clear technical proposal for architectural choices.

You need structured decision-making for architectural choices when facing complex technical decisions with multiple viable approaches. It is useful for tool selection, refactoring strategies, and database migration paths where evaluating trade-offs is essential.

To generate a 1-3-1 recommendation for a database migration strategy, provide a detailed decision context describing the challenge. The process produces one problem statement, three options, and one recommended migration path with implementation rationale.

Yes, the 1-3-1 format works for tool selection and refactoring strategies. It handles complex technical decisions by evaluating multiple approaches and delivering a single recommended option with a structured rationale and implementation plan.

To get a structured technical recommendation, you must provide a detailed decision context describing the challenge. This input enables the 1-3-1 format to weigh multiple viable approaches and deliver a recommended option with an implementation plan.