A decision memo without decision rights is a collaboration artifact. It may create discussion, collect comments, and document context, but it may not produce a decision. Many companies confuse broad input with authority. The memo circulates, everyone reacts, and nobody knows who can actually say yes, no, not yet, or change the scope.
Decision rights should be explicit before the memo is written. Who is the decision-maker? Who recommends? Who must be consulted? Who has veto power? Who executes? Who needs to be informed after the call? Without those roles, the document becomes a magnet for unmanaged opinions.
This matters because different readers have different jobs. A subject-matter expert should improve the evidence. A finance leader may test the economics. A legal or security reviewer may identify constraints. A team lead may assess execution load. The decision owner should weigh the tradeoffs and make the call. If everyone behaves as if they are the decider, review turns into politics.
A good memo names the decision owner near the top. It also names the expected decision date and the kind of decision required. Is this an approval? A recommendation? A choice among options? A request for more evidence? A checkpoint before a staged commitment? That framing helps reviewers respond at the right altitude.
Ambiguous decision rights create two common failure modes. The first is false consensus. Everyone comments, nobody objects loudly, and the team assumes alignment. Later, when execution starts, hidden disagreement returns as delay, rework, or passive resistance. The second is invisible veto. A person who was never named as a decision owner quietly blocks the work through budget, staffing, architecture, legal risk, or executive access.
Writing can expose both problems early. If someone has veto power, the memo should say so. If a function can block execution, that function should be consulted before the decision is declared. If the decision owner can override a concern, that should be explicit too. The goal is not to remove power. The goal is to make power legible enough that people can operate around it.
Decision rights also protect speed. When ownership is clear, the memo does not need endless alignment theater. The right people contribute, the decision-maker decides, and the organization moves. When ownership is unclear, every comment can reopen the whole question.
The decision owner has responsibilities too. They should not use the memo process as a way to outsource courage. If the tradeoff is real, the decision-maker has to own it. If the recommendation is unpopular, they need to explain the judgment. If the evidence is incomplete but action is required, they need to accept the risk. A written memo should make that accountability clearer, not diffuse it across a comment thread.
There is a difference between deciding and ratifying. Some memos ask for a real decision. Others document a decision that has effectively already been made. Ratification is not always wrong, but it should be honest. If the company is only asking for acknowledgment, say that. Do not invite debate after the real decision window has closed.
Written culture also helps prevent decision laundering. That happens when a team uses a memo to make a decision appear collective even though the recommendation is really driven by one leader's preference, a political constraint, or a hidden commitment. The fix is not cynicism. The fix is clearer decision rights and clearer reasoning.
Cross-functional decisions need special care. A product decision may create sales promises. A sales commitment may create support burden. A finance decision may change product scope. A people decision may reshape execution capacity. The memo should name which functions are affected and whether they are decision owners, consulted parties, or execution owners.
The best decision systems distinguish input rights from decision rights. People deserve to be heard when their expertise or workload is involved. That does not mean everyone gets equal authority over the final call. Clear written roles make that distinction less personal.
After the decision, the log should record who decided. Not to assign blame cheaply, but to preserve accountability and learning. If the outcome is good, the company can understand the judgment that worked. If the outcome is bad, it can review the reasoning without pretending nobody owned it.
A memo with clear decision rights creates a cleaner social contract. Contributors know what kind of feedback is needed. The decision-maker knows what they must own. The organization knows when the debate is over. That clarity is one of the main reasons written operating culture can make companies faster instead of slower.
A practical decision-rights block can be short. Decision owner: VP Product. Recommender: growth team lead. Required consults: finance, legal, customer success, data. Execution owners: product, lifecycle, sales enablement. Informed after decision: support, account management, executive team. That block prevents a document from pretending every reader has the same role.
It also helps to state the decision rule. Is the owner deciding after consultation? Is the CEO approving a recommendation? Is the group seeking consent unless a blocker is raised? Is this a reversible test where the team lead can decide alone? Different rules create different review behavior. If the rule is hidden, reviewers will invent one.
The rule should match the consequence. A reversible onboarding experiment may only need product and CS input before the owner decides. A pricing change touching renewals, commissions, billing, legal terms, and customer messaging needs a broader consult path and a clearer executive owner. Both can be written decisions, but they should not use the same authority model.
Evidence note: this post uses local Power, Great COO, and Executive Communication decision-rights framing, plus public decision-record context from https://adr.github.io/.
This is part 5 of 10 in Decision Memos and Written Operating Culture.