one-three-one-rule

Structure technical proposals using a 1-3-1 format: define one problem statement, compare three options with pros and cons, and select one recommendation with success criteria and implementation steps.

The best way to present tool selection options is a structured decision framework comparing three distinct approaches with trade-off analysis, definition of done, and a recommended path forward.

Create a decision-making framework for migration strategies by framing the problem, evaluating three competing approaches with trade-offs, and selecting a recommendation with defined success criteria and implementation planning.

Yes, you can use this structured options analysis for refactoring approaches. It evaluates competing technical choices by comparing three options with pros, cons, and implementation steps before committing to a direction.

You need a 1-3-1 format for technical decision-making when teams face ambiguous architecture choices, migration paths, or tool selections and require clear trade-off analysis to choose a recommended path forward.

A recommendation for backend architecture changes should include one problem statement, three evaluated options with pros and cons, one selected path, success criteria, and implementation steps to guide stakeholder proposals.