one-three-one-rule

A 1-3-1 format structures technical decisions into one problem statement, three options with pros and cons, and a single recommendation. It frames complex architecture choices by making trade-offs and actionable next steps obvious to stakeholders.

To structure architecture decisions, frame the problem, present three options with pros and cons, and state a single recommendation. Complete the brief by adding a Definition of Done and an implementation plan to align stakeholders on actionable next steps.

Yes, the 1-3-1 format suits migrations and refactoring where multiple viable approaches exist. It produces a concise brief that frames the problem, compares three options, and provides a recommendation with an implementation plan and testable criteria.

Yes, the 1-3-1 brief includes both a Definition of Done and an implementation plan. This ensures verifiable outcomes and testable criteria are specified alongside the problem statement, three options, and single recommendation.

Avoid the 1-3-1 structure for decisions lacking multiple viable approaches. It is designed for technical proposals, architecture choices, tool selections, migrations, and refactoring where comparing three distinct options with trade-offs adds value.

Frame a problem statement by clearly defining the technical decision needed, such as an architecture choice or tool selection. The 1-3-1 brief then follows with three options, a single recommendation, a Definition of Done, and an implementation plan.