one-three-one-rule

Structure technical proposals using the 1-3-1 format: one concise problem statement, three distinct options with pros and cons, and a single recommendation. Include a measurable definition of done and step-by-step implementation plan.

The 1-3-1 rule for decision-making enforces summaries with exactly one problem sentence, three labeled options, and one explicit recommendation. It balances technical trade-offs by pairing pros and cons with a single actionable path forward.

Write an engineering RFC by applying the 1-3-1 format to your architecture decisions. Generate one problem statement, three viable options with pros and cons, one recommendation, a definition of done, and implementation steps for stakeholder review.

You can use 1-3-1 recommendations for tool selection, refactoring strategies, and migration planning. The format requires comparing three distinct options with balanced pros and cons before issuing a single recommendation and implementation plan.

A trade-off analysis should include one problem statement, three options with pros and cons, one recommendation, a measurable definition of done, and step-by-step implementation steps. This ensures architecture decisions are justifiable and executable.

You need a structured decision summary when multiple viable technical approaches exist for architecture selection or refactoring. It helps stakeholders make justifiable decisions by enforcing balanced options and a single recommendation.