Most bad decisions are not made because nobody considered the preferred option. They are made because the company never took the alternatives seriously. A team argues for a launch, a hire, a platform, a pricing change, or a reorg, but the memo quietly treats every other path as obviously worse. That is not decision quality. It is advocacy with formatting.
A useful decision memo makes options real. It should show the reader that the company is choosing among plausible paths, each with benefits, costs, risks, and timing implications. If there is only one serious option, the memo should say that directly and explain why. Pretending to compare options wastes trust.
The "do nothing" option deserves special attention. In many companies, inertia is the default decision. Teams keep the current product direction, current pricing, current customer segment, current org design, or current vendor because changing feels expensive. A strong memo makes that option visible. What happens if we defer? What cost continues? What opportunity decays? What risk compounds? Sometimes doing nothing is right. It should still be chosen consciously.
Tradeoffs are where the memo earns its keep. Saying yes to one path means saying no, not yet, or less to something else. A new market consumes product attention. A strategic customer changes roadmap gravity. A senior hire changes the leadership system. A platform migration spends engineering trust. A new AI workflow increases review and governance needs. If the memo cannot name the cost of yes, the organization is likely to discover it later through overload.
Good tradeoff writing is concrete. "This may create complexity" is weak. "This adds two support paths, requires migration tooling before Q3, and delays the onboarding rewrite by at least one quarter" is useful. The reader can argue with the second sentence. That is the point. The memo should make disagreement possible at the right level.
The best options sections also separate reversible and hard-to-reverse choices. Some decisions are easy to test. Others create commitments that become expensive to unwind: contracts, customer promises, public positioning, data models, compensation plans, team structure, platform dependencies. A memo should not treat those choices as equal. Reversibility changes the standard of evidence.
Opportunity cost needs its own line. Companies often approve work as if capacity is infinite. Each decision looks sensible in isolation. Together, the decisions create a portfolio no team can execute. A memo should ask what work this decision displaces. If the answer is "nothing," the memo is probably lying or the team has unused capacity worth investigating.
Options also reveal strategy. If every option tries to preserve every customer, every segment, every channel, and every feature path, the company may not be making a strategic decision at all. It may be avoiding loss. Written options force the organization to confront whether it is choosing or merely layering.
There is also a politics benefit. Many debates become personal because alternatives are not represented fairly. The person who dislikes the recommendation becomes "negative." The person who raises a constraint becomes "not strategic." A strong memo gives the alternative its best case. That makes dissent less about identity and more about judgment.
This does not mean every memo should include exhaustive analysis. The goal is not to build a consulting deck. The goal is to make the live options clear enough that the decision-maker can see what is being bought and sold. Three serious options are usually better than eight shallow ones.
The recommendation should come after the options, not before them. If the memo opens with the answer and uses the rest of the document to support it, readers will often inspect the logic defensively. If the memo first frames the decision and options honestly, the recommendation has more credibility because the reader can see the path that led there.
A good options section often includes disconfirming evidence. What would make option A fail? What would make option B smarter than it appears? What assumption makes option C too risky? This is where the memo moves from preference to judgment.
The cost of saying yes should be visible after the decision too. If the company approves the recommendation, the memo should name the commitments that are now real. Which priorities move down? Which metrics matter? Which risks need monitoring? Which old debate is now closed unless new evidence appears?
This is how written culture prevents decision debt. Decision debt accumulates when companies say yes without recording what the yes displaced. Months later, everything is urgent and nobody remembers why the portfolio became impossible. A good memo leaves a receipt.
The operating standard is not that every decision has a perfect answer. It is that the company can see the answer it chose, the alternatives it rejected, and the cost it accepted. That visibility makes execution cleaner and learning more honest.
A useful memo can make this visible in a small table: option, upside, cost, reversibility, evidence strength, and what must stop if this option is chosen. The "what must stop" column is often the most important one. It turns strategy from additive ambition into actual choice.
The author should also name the decision's second-order effects. A new enterprise segment may require security work, implementation capacity, different sales talent, procurement support, and slower roadmap cycles. A new self-serve motion may require product-led onboarding, pricing clarity, support automation, and different analytics. The immediate choice is rarely the whole choice.
Evidence note: this post uses local strategy and executive-communication framing, including ICP decision-memo patterns, and public context from decision-record practices such as https://adr.github.io/.
This is part 3 of 10 in Decision Memos and Written Operating Culture.