Start with the decision, not the presentation
A research report can describe what customers said and still leave a team unsure what to do. Before translating findings into recommendations, name the decision at hand. Is the team choosing which audience to serve first, which part of an experience to improve, or which message to test? A clear decision question gives the analysis a purpose and helps keep interesting but unrelated observations in their proper place.
Also identify the boundaries of that decision. A team may have a fixed budget, a short implementation window, or an existing product that cannot be redesigned all at once. These constraints do not make research less valuable; they define which actions are realistic. Write them alongside the decision question so readers can see why an attractive idea may not be an immediate option.
Separate observations from interpretations
Before proposing actions, distinguish what the research directly shows from what the team infers. An observation might be that several interview participants struggled to compare two plans. An interpretation might be that the plan descriptions use distinctions customers do not find meaningful. A proposed action might be to rewrite the comparison page. Each step can be useful, but they carry different levels of certainty.
This separation matters because one finding can support more than one response. If people struggle to compare plans, the team could simplify the language, change the page layout, or offer a guided choice. The research may reveal a problem clearly without establishing which solution will work best. Labeling that uncertainty makes the resulting options more honest and easier to evaluate.
Build a small set of distinct options
Aim for a few meaningfully different paths rather than a long list of minor variations. For each option, describe the action, the finding that motivates it, the outcome it is intended to improve, and the effort it may require. Options should be specific enough to discuss: “test a shorter plan comparison with customers” is more useful than “improve clarity.” They should also be genuinely different. Three versions of the same page change do not give decision-makers much choice.
It can help to include options at different levels of commitment. One might be a modest change the team can make soon, another a more involved redesign, and a third a limited test before either change. This is not a ranking disguised as a menu. Each path should have a credible reason to exist, grounded in the findings and the team's constraints.
Make the tradeoffs visible
A useful options summary explains what each path gains and what it leaves unresolved. A quick copy change may be inexpensive but may not address a confusing page structure. A redesign could address the broader experience but take more time and introduce new questions. A small test may reduce uncertainty, although it delays a wider rollout. Stating these tradeoffs helps the team discuss the choice itself instead of debating whether the research was persuasive enough.
Be equally clear about the strength and limits of the evidence. Interviews can show how particular people explain a problem, but they do not by themselves establish how common it is across an audience. A survey may help compare reported needs across groups, yet its usefulness depends on who responded and how questions were worded. Note gaps that could change the decision, without treating every unanswered question as a reason to stop.
Give decision-makers a way forward
Options are most helpful when paired with a practical decision rule. For example, the team might choose the lower-effort change if speed is the priority, or test two approaches if the cost of choosing poorly is high. The researcher can state which option appears best under an explicit set of priorities while leaving room for decision-makers to weigh constraints the research cannot settle.
Close with the next action and the signal that would prompt a reassessment. Who needs to approve the choice? What could the team observe after a change, such as whether customers can explain the difference between plans? What result would suggest trying another path? This turns research into an ongoing learning process. The goal is not to avoid making a recommendation; it is to show the reasoning behind a choice and preserve workable alternatives when circumstances or evidence change.
