State the decision in a sentence
Begin with the choice the team needs to make. “Should we test a focused offer with this audience?” is a decision. “What is happening in the market?” is an opening for research, but it does not identify what the research needs to resolve.
Name the owner and the point at which a decision is needed. If there is no meaningful deadline, do not invent urgency. Explain the consequence of postponing the decision as well as the consequence of proceeding with incomplete information.
Keep observations separate from assumptions
An observation might be a pattern in a reviewed set of interviews or a published product description. An assumption might be that the same pattern extends to a wider audience. Write them separately so that a reader can inspect the reasoning.
Record where evidence came from, when it was checked and the limits of the method. A vendor’s public page can establish what the vendor says; it does not prove how well a product performs. A few customer conversations can suggest a useful question without establishing a market-wide rate.
Compare actual options
Include options the team could realistically take, including a small test or a decision to keep the current approach. Apply the same questions to each option. Do not give the preferred option a detailed case and leave the alternatives as vague labels.
For an illustrative example, a team considering a new service might compare a full launch, a limited enquiry page and further customer interviews. The relevant differences could include what each option would teach, the work involved and what would be difficult to reverse.
Use a short memo structure
- Decision: what choice is being made, by whom and when?
- Options: which practical alternatives were considered?
- Evidence: what observations support or challenge each option?
- Uncertainty: what remains assumed, missing or contradictory?
- Next step: what is proposed, with what scope and owner?
- Reconsideration: what evidence or event would cause a review?
Keep the memo as short as the decision allows. Supporting notes can hold detailed research; the memo should make the reasoning accessible.
Make the proposed next step testable
If a small test can resolve the important uncertainty, describe what it will do and what would count as useful learning. A pilot should have a boundary: a defined audience, task, period or deliverable. Explain what it does not establish.
A limited enquiry page, for instance, might test whether the offer is understandable to people who reach it. It would not by itself establish retention, delivery quality or a whole market’s willingness to pay. Keep the conclusion proportionate to the evidence the test can produce.
Preserve disagreement and revisit the result
If colleagues disagree, record which assumption or observation drives the difference. That is more useful than describing the discussion as a lack of alignment. The next piece of research may become obvious once the disputed point is clear.
After the decision, revisit the result against the original reasoning. Update the memo when a significant assumption changes. If the evidence depends on uncertain records, use a focused data audit; if the question needs a conversation, plan an interview about a recent real occasion.
Published by Naltyx. Examples are illustrative; any Naltyx product mentioned is our own. How we write.
Let’s talk