Skip to content

The one-page decision memo for decisions that keep coming back

Leadership, 7 min read
October 14, 2026
Some decisions land on the founder's desk again and again. A one-page memo makes the call once, records why, and spells out exactly what would reopen it.

Every founder has a few decisions that refuse to stay made. Whether to raise prices for existing customers. Whether to hire a second salesperson or fix the pipeline the first one already has. Whether to keep the product nobody loves but a handful of loyal customers still order. You think it over, talk it through, lean one way, and three weeks later the same question is back on your desk with a slightly different label.

Usually the decision is not especially hard. The trouble is that it was never made in a form anyone could point to. It lived in a conversation, a chat thread or your own head. When nobody can see what was decided, why, and what would change it, people keep asking, and you keep answering.

A one-page decision memo fixes most of this. It takes an hour or so to write, it makes you face the trade-offs honestly, and it gives your team something to refer to other than you.

Why some decisions keep coming back

A handful of patterns explain most of the repeat visitors.

  • The question was never stated clearly. "What should we do about pricing?" is a topic. "Should we raise the monthly plan from $49 to $59 for new customers from January?" is a decision.
  • Nobody wrote down the reasons. When someone pushes back six weeks later, there is no record of what was weighed, so the debate starts again from zero.
  • The decision had no clear owner. If it is unclear who made the call, anyone who disagrees can quietly reopen it.
  • There was no next step. A decision that does not change what someone does on Monday morning tends to drift back into being a discussion.
  • Nobody said what would change the decision. Without that, every new piece of information feels like a reason to reconsider.

None of this is about intelligence or effort. It is about format. Founders often carry decisions around in their heads because writing them down feels like bureaucracy. In a team of 8 or 25 people, the cost of skipping that step is that you become the archive, and every question routes back to you.

The one-page format

Here is the structure. Each section is short. If the whole thing runs past one page, you are probably describing the problem rather than deciding it.

  1. The question. One sentence, phrased so it can be answered yes or no, or with a choice between named options.
  2. Context. Three to five sentences on why this is coming up now: what changed, what is at stake, and any real deadline.
  3. Options. Usually two to four, always including "do nothing."
  4. Criteria. What you will judge the options against, in order of importance.
  5. What would change your mind. The specific evidence that would make you choose differently.
  6. Reversibility. How easy the decision would be to undo, and roughly what undoing it would cost.
  7. The call. Which option you are choosing, with the main reason.
  8. The next step. Who does what, by when.

That is the whole template. The value comes from filling it in honestly, so the rest of this article covers the parts people tend to rush.

Options, including "do nothing"

"Do nothing" belongs on every list. It is often the option you are choosing by default while a decision drags on, so it is better to look at it directly. Sometimes it wins. Waiting a quarter for more information is a perfectly good choice if waiting is cheap and the information will actually arrive.

Write each option as something a person could start doing. "Improve onboarding" is a wish. "Hire a part-time onboarding specialist for three months" is an option. If two options turn out to be versions of the same thing, merge them. If you only have one real option plus "do nothing," check whether you have dismissed a middle path too quickly: a smaller version, a pilot with a few customers, or a delay with a fixed date attached.

Criteria that actually separate the options

Many memos list criteria that every option meets equally well, which turns them into decoration. Useful criteria separate the options. For a hiring decision, "good attitude" probably applies to every candidate you would consider. "Can start before the busy season in March" might rule one out.

Rank your criteria. If cash is tight, cost over the next quarter probably sits above long-term upside, and saying so out loud prevents a lot of circular discussion. A small table helps:

CriterionHire nowContractor for 3 monthsDo nothing
Cost next quarterHighMediumNone
Covers the March peakYesYesNo
Easy to undoNoYesYes
Builds long-term capacityYesPartlyNo

You do not need scores. Plain words are enough to see where the options differ. If the table shows a clear winner, good. If it shows a genuine tie, that tells you the choice matters less than it felt, and you should pick one and move on.

What would change your mind

This is the section that stops decisions from coming back. Write down, as precisely as you can, what you would need to see to choose differently. For example: "If the contractor has not brought the backlog under two weeks by the end of February, we move to a full-time hire." Or: "If cancellations in the 30 days after the price notice are clearly above our usual monthly level, we revisit keeping existing customers on the old price."

Once this paragraph exists, new information has somewhere to go. When someone forwards a competitor's price cut, check it against the memo. If it does not meet the condition you wrote, the decision stands, and you can say so without reopening the whole debate. That one paragraph probably saves more founder time than the rest of the memo put together.

Reversibility and how much care to take

Some decisions are easy to undo: trying a new ad channel for a month, reordering the steps in a sales process, moving a weekly report from Monday to Thursday. Others are slow or expensive to walk back, such as signing a long lease, letting a senior person go, or dropping a product that some customers rely on.

The memo should say which kind this is, because that sets how much effort the decision deserves. A reversible decision can be made quickly on incomplete information, and the memo might be half a page. A hard-to-reverse one deserves more time, a second opinion, and sometimes outside expertise. If the decision has legal, tax or employment consequences, such as changing contracts or how people are paid, get advice from a qualified professional before you make the call, and bring the memo with you so the conversation starts from a clear question.

A useful habit: when a decision is easy to reverse and the options are close, make it within a day. Founders often spend weeks on small reversible choices and too little time on the few that are genuinely hard to undo.

The call and the next step

State the decision plainly. "We will hire a contractor for three months starting February 1, because it covers the March peak at lower cost and is easy to undo." One sentence, with the main reason attached. Keep hedging out of it. If you have doubts, they belong in the section on what would change your mind.

Then write the next step with a name and a date: "Sam posts the contractor brief by Friday." Without that line, the memo is an essay. With it, the decision starts moving.

Finally, put the memo where the team can find it. When the question comes back, and some will, send the memo instead of explaining it all again. Over a few months you build a small library of decisions that shows new hires how the business thinks and reminds you why you chose what you chose.

If you have a decision that keeps landing back on your desk and you would rather someone else structured it, Ilason's Decision Clarity Memo does exactly this: you describe the situation in writing, and the finished memo arrives by email.

This article is general information, not advice for your business. Examples use hypothetical businesses. See our Results Disclaimer.

LET'S WORK TOGETHER

Ready to take your business to the next level?