Decision Review Meeting

Overview

A decision review meeting is a structured session designed to evaluate options, weigh trade-offs, and reach a documented conclusion on a specific question or set of related questions. Unlike informal discussions where decisions emerge organically, this format ensures that every viable option is examined against consistent criteria before a choice is made.

The framework is built around three pillars: clarity of options, transparency of evaluation, and accountability for the outcome. By separating the presentation of options from the evaluation and the final decision, the meeting reduces the influence of cognitive biases such as anchoring (fixating on the first option presented) and groupthink (defaulting to the most popular opinion without critical scrutiny).

The ideal duration is 45 to 60 minutes. Shorter sessions risk superficial analysis, while longer ones typically indicate that the problem has not been sufficiently framed beforehand. If the decision cannot be resolved within an hour, it is often a sign that more preparation is needed rather than more meeting time. In those cases, a problem-solving workshop may help the team align on the core issue before reconvening to decide.

When to Use This Framework

This template is most effective when a decision has material consequences for the organisation, when multiple viable options exist, and when the decision-maker wants to ensure that the reasoning is documented for future reference or audit purposes.

• Technology platform or vendor selection where the choice locks in long-term dependencies
• Build vs. buy vs. partner decisions for product capabilities
• Organisational restructuring or team topology changes
• Market entry, pricing model, or go-to-market strategy decisions
• Capital allocation choices where multiple initiatives compete for the same budget, often surfaced during a budget planning meeting
• Policy or process changes that affect multiple departments or customer-facing workflows
• Escalated decisions that have been deferred from other forums due to complexity or disagreement

Who Should Attend

Sample Agenda

Example Use Case

A mid-market B2B SaaS company needs to add payment processing to its platform. The product team has identified three paths: building a custom integration directly with Stripe's API, purchasing a white-label payments module from a specialist vendor, or forming a revenue-sharing partnership with an established fintech provider.

The VP of Product (decision owner) convenes a 50-minute decision review. Three engineers present the build option with a 14-week estimate and a total cost of $180K. The vendor's pre-sales team has supplied a detailed proposal costed at $95K annually. The partnerships lead presents the fintech option, which requires no upfront investment but gives away 0.3% of transaction volume.

The evaluation panel scores each option across five weighted criteria: time to market (25%), total cost over three years (25%), flexibility for future requirements (20%), compliance risk (15%), and engineering capacity impact (15%). The vendor option scores highest on speed and cost but lowest on flexibility. After discussion, the decision owner selects the build option because the company's roadmap includes multi-currency support in Q3, and the vendor's module cannot accommodate it without expensive customisation. The scribe records the decision, the dissenting view from the finance lead who preferred the vendor's lower upfront cost, and the three follow-up actions with owners and deadlines.

Best Practices

• Define criteria before exploring options. Agreeing on what matters (and how much) before seeing the options prevents the evaluation from being reverse-engineered to justify a preferred choice.
• Limit options to three or four. More than four viable options typically means the problem has not been sufficiently narrowed. Use a pre-screening step to eliminate weaker alternatives before the meeting.
• Separate presentation from advocacy. Option presenters should describe each alternative factually. Advocacy and debate belong in the trade-off discussion, not during the presentation.
• Use weighted scoring, not gut feel. Even a simple 1-to-5 scale across four criteria produces a more defensible outcome than an unstructured debate. The scores do not need to be the final answer, but they provide a useful starting point.
• Document dissenting views. If someone disagrees with the final decision, record their reasoning. This creates a valuable reference if the decision is revisited and demonstrates that the process was genuinely open.
• Set a decision deadline. Without a clear deadline, decision meetings often end with "let's gather more data." If the data is not available, decide based on what you know or explicitly defer with a new date.
• Circulate the decision record within 24 hours. Speed matters. The longer it takes to publish the outcome, the more likely attendees will remember the discussion differently. Use Meeting Planner to schedule the follow-up review before everyone leaves.

Common Mistakes

• Arriving without prepared options. If the analysis has not been done before the meeting, the session becomes a brainstorming exercise rather than a decision forum. Preparation is non-negotiable.
• Letting the highest-paid person decide by default. The HiPPO effect (Highest Paid Person's Opinion) undermines the entire framework. The decision owner should hear all perspectives before speaking, and the facilitator should actively draw out quieter voices.
• Confusing consensus with decision-making. Not every participant needs to agree. The goal is informed alignment, where everyone understands the rationale even if they would have chosen differently.
• Evaluating sunk costs. Money already spent should not influence the forward-looking decision. The question is always "given where we are today, which option produces the best outcome from here?"
• Skipping the "do nothing" option. In many cases, maintaining the status quo is a legitimate alternative. Failing to evaluate it explicitly means you cannot demonstrate that action is genuinely better than inaction.
• Reopening decided items. Once a decision is made and documented, it should remain stable unless material new information emerges. Relitigating decisions without new data wastes time and erodes confidence in the process.

Related Templates

Related Tools