one-three-one-rule

To structure technical proposals and evaluate architecture trade-offs, use a 1-3-1 format: define one problem statement, analyze three distinct options with pros and cons, and conclude with one actionable recommendation.

The best way to present tool evaluation options to stakeholders is generating a standardized proposal that explicitly outlines the risks, benefits, and trade-offs of each viable path to eliminate ambiguity and prevent analysis paralysis.

You write a decision-making framework for architecture selection by enforcing objective analysis of competing approaches, requiring a single problem statement followed by three options detailing specific pros and cons before a final recommendation.

You need a structured format for technical decision-making when multiple viable paths exist for scenarios like database migration strategies or strategic planning, and a team is debating competing approaches without clear communication.

Yes, you can use the 1-3-1 format for strategic planning scenarios where multiple viable paths exist, as it enforces well-reasoned architectural decisions by requiring explicit trade-off analysis and a forwardable professional proposal.

Technical decision-making fails without explicit trade-off analysis because ambiguity prevents well-reasoned architectural decisions, leading to analysis paralysis and poor communication with stakeholders regarding the risks and benefits of competing approaches.