one-three-one-rule

Structured technical decision analysis evaluates multiple architectural approaches by defining a problem statement, comparing options with pros and cons, and recommending a course of action. Use it for architecture decisions or tool selection where trade-off analysis is required.

Format a technical proposal using a 1-3-1 structure: one problem statement, three distinct options evaluated with pros and cons, and one recommendation with an implementation plan. This ensures concise and actionable structured communication.

Yes, the 1-3-1 format is designed for software architecture decisions. It helps you evaluate multiple technical approaches by generating a problem statement, assessing three options with trade-offs, and providing a final recommendation with implementation details.

The best way to evaluate technical approaches is using a structured 1-3-1 analysis, which assesses three distinct options with pros and cons against a defined problem statement to deliver a clear, actionable recommendation.

Yes, you must provide problem context to generate a technical recommendation. The analysis requires understanding the problem context and your ability to assess different technical approaches to output an accurate 1-3-1 evaluation.

Avoid the 1-3-1 format when a decision lacks enough viable technical approaches to warrant three distinct options, or when the problem context is too ambiguous to generate a meaningful trade-off analysis and implementation plan.