one-three-one-rule

Structure technical proposals by defining exactly one problem sentence, presenting three labeled options with pros and cons, and selecting a single recommendation with reasoning. This format surfaces architecture trade-offs clearly for stakeholder review.

The best way to decide between refactoring strategies is to compare exactly three distinct approaches. Evaluating pros and cons for each option ensures a defensible choice while reducing debate overhead and confusion among stakeholders.

Create a decision-making framework for tool selection by comparing three options, choosing one recommendation, and aligning it with a definition of done. This produces an execution-ready implementation plan tailored to the selected tool.

Yes, the one-three-one rule applies directly to migration paths where distinct approaches must be compared rather than iterated. It converts ambiguous technical trade-off decisions into a single, actionable, stakeholder-ready recommendation.

You need structured decision framing for technical trade-off decisions when multiple viable options cause confusion. It produces a focused problem statement and a non-hedging recommendation to reduce debate overhead during architecture or tool selection.

Yes, this decision-making approach forces a single actionable recommendation. It selects one option from the three presented and explains the rationale directly without hedging, ensuring a clear path forward for stakeholders.