one-three-one-rule

To structure an architecture decision for stakeholder communication, frame exactly one problem sentence, outline three distinct options with pros and cons, and deliver a single recommendation with rationale, definition of done, and an implementation plan.

The best way to write a technical proposal for a migration plan is to use a one-three-one structure: define one problem, compare three viable approaches, and select one recommendation with an aligned implementation plan and definition of done.

To choose between competing refactoring strategies, evaluate exactly three labeled options with explicit pros and cons, then resolve the ambiguous trade-offs by selecting a single approach with a matching implementation plan.

Yes, you can generate a definition of done and implementation plan for tool selection decisions by reframing the technical trade-offs into a single recommended option, which includes actionable guidance for execution.

You need a structured recommendation format for technical proposals when multiple viable architecture approaches exist, trade-offs must be clearly communicated, and stakeholders require confident, actionable guidance to evaluate and execute the decision.