one-three-one-rule

Use a 1-3-1 rule response to structure your technical proposal: define exactly one problem statement, present three distinct options with pros and cons, and conclude with one recommended option. This ensures stakeholders can compare architecture decisions meaningfully.

A defensible tool selection recommendation requires framing the decision in one sentence, evaluating three viable options with trade-off analysis, and selecting one option with a clear justification, definition of done, and implementation plan.

Frame your database migration strategy as a 1-3-1 decision: state the migration problem, compare three distinct migration paths with pros and cons, then output a single recommended path with an aligned definition of done and implementation plan.

Yes, the 1-3-1 rule applies to any complex technical decision involving real trade-offs, including refactoring strategies, tool selection, architecture decisions, and migration paths where multiple viable options exist.

Your trade-off analysis likely lacks alignment because it does not compress the decision into a single problem statement or fails to provide exactly three distinct options with a single actionable recommendation and aligned implementation plan.

You should not use a 1-3-1 decision format when your technical proposal has fewer than three viable options to compare or when the decision does not involve meaningful trade-offs requiring a defensible recommendation and implementation plan.