one-three-one-rule

Structured technical decision-making evaluates multiple approaches against desired outcomes to clarify complex choices. It breaks down architecture decisions into distinct options with pros/cons to ensure informed selection rather than relying on intuition.

To compare tool selection options, define your problem statement and desired outcomes, then evaluate three distinct approaches. Weighing the specific pros and cons of each option against your goals yields a clear, justified recommendation.

You need structured options analysis for software engineering tasks when facing complex scenarios like architecture decisions, refactoring strategies, or migration paths. It is essential whenever you are unsure of the best approach and must weigh technical trade-offs.

The best way to analyze trade-offs for a technical migration path is using a 1-3-1 format: one problem statement, three distinct options with evaluated pros and cons, and one clear recommendation based on your desired outcomes.

Yes, you can use this structured thinking approach for refactoring strategy decisions. By providing your specific problem statement and desired outcomes, the framework generates three distinct options with trade-offs to guide your final recommendation.