Glossary

Decision matrix

Definition

A structured decision-making tool that lists options in rows and evaluation criteria in columns, assigns weights to each criterion, scores each option against each criterion, and computes a weighted total to rank the options.

Decision matrices (also called weighted scoring matrices or Pugh matrices in engineering contexts) convert subjective preference into a defensible, auditable choice. They don't eliminate judgment — the criteria selection and scoring are still human — but they make the reasoning visible and debatable.

How to build one:

  1. List the options you're deciding between (rows).
  2. List the criteria that matter for the decision (columns).
  3. Assign a weight to each criterion — typically 1–5 or 1–10, reflecting relative importance.
  4. Score each option on each criterion — same scale.
  5. Multiply score by weight for each cell; sum the row for the total.
  6. The highest total is the recommended option — but the real value is in the conversation the matrix generates.

Common uses: Technology selection (which database, which cloud provider), feature prioritization, vendor evaluation, go/no-go decisions on product bets.

The conversation is the output: Teams often find that the highest-scoring option isn't the one they pick — because building the matrix surfaces an implicit constraint or a criterion that was left off. That's fine. The matrix makes the reasoning explicit enough to challenge.

On a whiteboard: Decision matrices are drawn on whiteboards constantly — especially in architecture reviews and vendor selection sessions. The rows and columns fit naturally in a grid. Snap it with BoardSnap to capture the weights, scores, and totals before the board gets erased.

Examples

  • An engineering team uses a decision matrix to choose between three state management libraries for a new frontend, weighting performance, community support, and TypeScript compatibility.
  • A product manager builds a decision matrix in a planning session to prioritize which of five proposed features to build in Q3.
  • A founder uses a weighted decision matrix to evaluate three potential CRMs, with sales process fit weighted 3x and price weighted 1x.
  • An architecture review team draws a decision matrix on the whiteboard to choose between a monolith, microservices, and a modular monolith for a greenfield project.

Snap a decision matrix. Ship its actions.

BoardSnap turns any whiteboard — including this one — into a summary and action plan.

Free · 1 project, 30 boards Pro $9.99/mo · everything unlimited Pro $69.99/yr · save 42%
BoardSnap Free on the App Store Get