one-three-one-rule

Structuring technical decision making involves defining one clear problem statement, comparing three viable trade-off options with pros and cons, and providing one concrete recommendation with an implementation plan. This 1-3-1 approach ensures architecture choices are easy to review and act on.

The best way to compare tool selection options is to evaluate exactly three viable approaches side by side. Presenting three options with clear trade-offs, pros, and cons makes it easy to share the decision matrix with stakeholders and identify the strongest path forward.

Yes, you can use a 1-3-1 analysis for migration planning and refactoring strategies. It converts open-ended technical choices into a structured response featuring three compared options, a single recommendation, a definition of done, and an implementation plan.

To write a decision recommendation stakeholders can review, provide one actionable path forward from three evaluated options. Include the definition of done and an implementation plan to explain the trade-offs clearly and ensure the chosen architecture or tool selection is easy to act on.

You need a structured framework for evaluating trade-offs when multiple viable paths exist for your architecture or tool selection. It helps frame the problem statement accurately and compare three distinct options so your team can confidently choose one recommendation.