one-three-one-rule

To structure a technical proposal for evaluating architecture trade-offs, use a 1-3-1 framework: define one problem statement, present three options with pros and cons, and conclude with one recommendation. This prevents analysis paralysis and clarifies communication.

The best way to document database migration options is generating a standardized 1-3-1 analysis, outlining a single problem, three architectural choices with trade-offs, and a concrete implementation plan to ensure stakeholders understand the recommended path forward.

To stop analysis paralysis when choosing API strategies, apply an objective decision-making framework that limits evaluation to three distinct options with defined pros and cons, forcing a structured comparison and yielding a single actionable recommendation.

Yes, the framework works for tool selection scenarios by converting complex technical trade-offs into a standardized format. It evaluates multiple viable paths, generates a Definition of Done, and provides an implementation plan for the selected tool.

To create an implementation plan after deciding on a technical architecture, finalize one recommendation from the evaluated options. The framework automatically generates a Definition of Done and concrete next steps for the selected migration or design path.