one-three-one-rule

To structure a technical proposal for architecture decisions, use a 1-3-1 format: define one clear problem statement, list three distinct options with pros and cons, and conclude with one concrete recommendation. This ensures all trade-offs are evaluated systematically before committing to an implementation plan.

The best way to compare technical options for tool selection is to evaluate three distinct approaches side-by-side, documenting the specific pros and cons of each. This structured decision-making approach clarifies trade-offs and leads directly to a concrete, defensible recommendation.

You can create a decision-making document with a definition of done by generating a structured technical proposal. This document includes a concrete recommendation, an implementation plan, and clear criteria for completion to guide the engineering team effectively.

You need a structured trade-off analysis for software engineering when you must choose between multiple approaches for a technical project, such as selecting an architecture pattern or implementing a new application feature. It provides a clear problem statement and three viable options.

To generate a 1-3-1 technical proposal, you need to provide the specific problem you are facing and the relevant context of your technical project. This allows the structured decision-making process to output accurate options and a tailored recommendation with an implementation plan.