one-three-one-rule

The best way to structure a technical proposal is using a 1-3-1 format: a clear problem statement, three distinct options with pros and cons, and a concrete recommendation. This ensures all trade-offs are evaluated systematically.

To compare tool selection options, generate a structured document listing three distinct approaches, detailing the specific advantages and disadvantages of each, and concluding with a concrete recommendation to guide your final choice.

Yes, you can use this structured analysis for refactoring strategies by providing a problem statement and asking for a 1-3-1 format analysis, which will outline three distinct refactoring options with pros and cons.

To format trade-offs in a decision-making document, outline a single problem statement, present three distinct technical options, detail the pros and cons for each, and provide a concrete recommendation based on the structured analysis.

You need a structured format for technical decisions when facing a choice between multiple approaches, such as architecture decisions or tool selection, ensuring your technical proposals comprehensively evaluate trade-offs and provide actionable recommendations.

The 1-3-1 rule requires a problem statement as input to generate an options comparison, producing a structured technical proposal with three distinct options, pros and cons, and a concrete recommendation.