All posts
AFFiNE
Toeverything·Originally published Aug 15, 2026 · Updated Oct 5, 2026
Three project-workflow options, two-week sprints, Kanban with WIP limits and six-week cycles, feeding a weighted decision matrix with six criteria and weights; Kanban leads with 3.40 against 3.20 and 3.00, while a fixed-scope plan is screened out at a must-have gate

Free Decision Matrix Template With a Worked Example

A decision matrix template is a table for comparing a short list of options against the same criteria. In the weighted version, each criterion gets a weight, and the weights add up to 100%. You score every option from 1 to 5 on each criterion and multiply each score by its weight. Add those products and divide by 100 to get a total on the same 1–5 scale.

The total supports a decision. It does not make it. It is worth taking seriously only after two more checks: whether a reasonable change to the weights would change the winner, and whether a written record explains why the team chose what it chose.

This page gives you both. It has a free template in three formats and a fully worked example in which every score and calculation is shown. It also has a sensitivity check that finds the exact weight at which the winner changes, and a decision record you can copy.

Free downloads (no sign-up):

When a decision matrix helps, and when it is too rigid

A decision matrix works best when you already have two to five realistic options and several factors that pull in different directions. It also helps when different people value those factors differently. Writing the criteria and weights down turns a vague argument ("Kanban feels better") into a specific one ("you weighted predictability at 20%; I think it is 30%").

It is the wrong tool in other situations:

SituationBetter approach
You do not have options yet, only a pile of ideasCluster the ideas first with an affinity diagram, then shortlist
One factor decides it (a legal requirement, a hard budget cap)Treat that factor as a pass/fail gate and pick among whatever passes
The choice is cheap and easy to reverseTry one option for a short period; a matrix costs more than it saves
The choice is a chain of if/then outcomes with probabilitiesUse a decision tree
You are ranking tasks, not choosing between alternativesUse an Eisenhower matrix or an impact–effort grid
Criteria interact (A is only good if B is also high)Adding up weighted scores assumes the criteria are independent, so discuss the combinations directly
The decision is mainly an ethical or values judgmentUse the matrix to structure the discussion, not to produce the answer

Government decision-analysis guidance makes the same point. The UK Government Analysis Function describes multi-criteria analysis as a tool that helps decision-makers, not a complete way of making the decision (Analysis Function, 2024).

Copy-ready decision matrix template

The template has six parts. Fill them in order, because each one constrains the next.

Annotated blank weighted decision matrix with six numbered parts: must-have gates marking options A to D pass or fail, criteria, a column for what a 5 and a 1 mean, weight cells that must add up to 100 percent, 1 to 5 score cells for options A, B and C, and a total row computed as the sum of weight times score divided by 100, with a 5 to 1 scoring scale underneath
The six parts of the template, in the order you fill them. Gates come first so that a failed must-have can never be outweighed by high scores elsewhere.

1. Gates (must-haves). Mark each option pass or fail. An option that fails any gate is removed and gets no score.

Gate (must-have)Option AOption BOption C
G1:Pass / FailPass / FailPass / Fail
G2:Pass / FailPass / FailPass / Fail

2–6. Criteria, anchors, weights, scores and totals.

CriterionWhat a 5 and a 1 look likeWeight (%)EvidenceOption AOption BOption C
C15 = … / 1 = …
C2
C3
C4
C5
Total100

Each option's total is Σ(weight × score) ÷ 100.

Scoring scale. Use the same scale for every criterion and write the anchors before anyone scores.

ScoreMeaning
5Exceeds the requirement, with evidence you could show someone
4Meets the requirement well; minor gaps
3Meets the minimum you wrote down
2Partly meets it; needs a workaround
1Does not meet it

A 1–5 scale is usually enough. Wider scales such as 1–10 invite debates about whether something is a 6 or a 7, without the evidence to settle them.

For "lower is better" criteria such as cost or effort, flip the wording so that 5 is always good. For example, write "Adoption effort (higher = easier)". That way, a higher total always means a better option.

Simple vs. weighted decision matrix

A simple (unweighted) decision matrix adds up the scores, so every criterion counts equally. A weighted decision matrix multiplies each score by how much that criterion matters before adding up.

Simple matrixWeighted matrix
CalculationSum of scoresΣ(weight × score) ÷ 100
AssumesEvery criterion matters equallySome criteria matter more, and the team agrees by how much
Best forQuick first pass, low-stakes choicesChoices where priorities genuinely differ
Main riskMinor criteria can outvote the critical oneWeights can be tuned to produce a preferred winner

The example below shows why the difference matters. With no weights, two-week sprints and Kanban tie at 20 points each. Weighting by the team's agreed priorities breaks that tie.

Converting relative weights to percentages. Many templates use weights like 3, 2 and 1. To convert them, divide each by their sum and multiply by 100. With 3 + 2 + 1 = 6, the weights become 50%, 33.3% and 16.7%.

The ranking does not change, but percentages are easier to audit. Everyone can see that the first criterion carries half the decision, and the sensitivity check later on is easier to read.

Worked decision matrix example: choosing a project workflow

This example is fictional. The team, scores and outcome were made up to teach the method. They are not a claim that one workflow is better than another in general, and they do not describe a real AFFiNE customer.

The decision. A 12-person product team must decide how to run project work for the next two quarters. Three to five customer escalations a week pull engineers off planned work. Leadership wants dated estimates for two milestones that carry external commitments.

The options. The team shortlisted four:

  • Two-week sprints. Scrum-style. The Scrum Guide sets sprints at one month or less, and this team chose two weeks.
  • Kanban with WIP limits. Continuous flow with an explicit limit on how much work is in progress at once. The Kanban Guide describes this as actively controlling work in progress.
  • Six-week cycles. Modeled on Basecamp's Shape Up, with a two-week cool-down after each cycle.
  • Fixed-scope two-quarter plan.

Step 1: Apply the gates

GateSprintsKanbanCyclesFixed plan
G1: Scope can change at least once a quarter without steering-group re-approvalPassPassPassFail
G2: Runs with current people and tools (no new hires or paid software before Q2)PassPassPassPass

The fixed-scope plan fails G1 and leaves the comparison. However well it might score on predictability, it cannot buy back a requirement the team has declared non-negotiable.

Step 2: Agree criteria, anchors and weights before scoring

#CriterionWhat a 5 and a 1 look likeWeight
C1Responsiveness to new priorities5 = a new top priority can start within 2 days; 3 = within 2 weeks; 1 = waits more than 6 weeks25%
C2Forecastable delivery dates5 = can give dated ranges for quarterly milestones from the team's own history; 1 = no basis for a date20%
C3Protection from interruptions5 = weekly escalations are absorbed without breaking planned work; 1 = every escalation breaks the plan20%
C4Adoption effort (higher = easier)5 = no new roles or meetings; 3 = a few new routines one person has run before; 1 = new roles and skills nobody has15%
C5Stakeholder visibility5 = stakeholders see working results every 2 weeks or more often; 1 = only on request10%
C6Documentation and handoff fit5 = the method itself produces written scope and decisions; 1 = relies on memory and chat10%
Total100%

Step 3: Score, then calculate

Each cell shows the 1–5 score and its weighted contribution (weight × score ÷ 100).

CriterionWeightTwo-week sprintsKanban with WIP limitsSix-week cycles
Responsiveness25%3 → 0.754 → 1.002 → 0.50
Forecastable dates20%4 → 0.802 → 0.404 → 0.80
Interruptions20%2 → 0.404 → 0.803 → 0.60
Adoption effort15%3 → 0.454 → 0.602 → 0.30
Visibility10%5 → 0.503 → 0.304 → 0.40
Documentation10%3 → 0.303 → 0.304 → 0.40
Weighted total100%3.203.403.00
Simple sum (no weights)202019

The arithmetic in full:

  • Two-week sprints: (25×3 + 20×4 + 20×2 + 15×3 + 10×5 + 10×3) ÷ 100 = (75 + 80 + 40 + 45 + 50 + 30) ÷ 100 = 320 ÷ 100 = 3.20
  • Kanban with WIP limits: (25×4 + 20×2 + 20×4 + 15×4 + 10×3 + 10×3) ÷ 100 = (100 + 40 + 80 + 60 + 30 + 30) ÷ 100 = 340 ÷ 100 = 3.40
  • Six-week cycles: (25×2 + 20×4 + 20×3 + 15×2 + 10×4 + 10×4) ÷ 100 = (50 + 80 + 60 + 30 + 40 + 40) ÷ 100 = 300 ÷ 100 = 3.00
Heatmap of the worked decision matrix example: six weighted criteria in rows and three options in columns, each cell showing the 1 to 5 score and its weighted contribution, with weighted totals of 3.20 for two-week sprints, 3.40 for Kanban with WIP limits and 3.00 for six-week cycles, and an unweighted sum that ties sprints and Kanban at 20
Kanban leads at 3.40, but only by 0.20 over sprints. Without weights, the two tie at 20, so the result depends entirely on the weights.

Provisional result: Kanban with WIP limits leads with 3.40, ahead of two-week sprints at 3.20 and six-week cycles at 3.00. A 0.20 margin on a 1–5 scale is small. The next step is to check whether it holds up.

Sensitivity check: does the winner survive a change in weights?

A sensitivity check asks one question: if we had weighted things a little differently, would we pick a different option? The UK multi-criteria analysis manual includes it among the steps of a multi-criteria analysis, testing the results against changes in scores or weights (DCLG, 2009). NASA's systems engineering handbook likewise asks analysts to tell the decision-maker how robust a ranking is (NASA SP-2016-6105 Rev2).

Test the weight people argued about. Here, the sales lead argued that dated forecasts deserved more than 20%. To keep the total at 100%, raise predictability by 10 points and take those 10 points from responsiveness. The other four weights stay the same.

BaselineTest
Responsiveness weight25%15%
Predictability weight20%30%
Two-week sprints3.203.30
Kanban with WIP limits3.403.20
Six-week cycles3.003.20

Recalculated with the same scores:

  • Sprints: (15×3 + 30×4 + 20×2 + 15×3 + 10×5 + 10×3) ÷ 100 = 330 ÷ 100 = 3.30
  • Kanban: (15×4 + 30×2 + 20×4 + 15×4 + 10×3 + 10×3) ÷ 100 = 320 ÷ 100 = 3.20
  • Cycles: (15×2 + 30×4 + 20×3 + 15×2 + 10×4 + 10×4) ÷ 100 = 320 ÷ 100 = 3.20

The winner is not robust to this change. At 30% predictability, sprints lead and Kanban drops into a tie with cycles.

Find the break-even weight

A single test tells you that the winner changes. The break-even weight tells you where, which is the number your stakeholders actually need to discuss.

Moving x points from responsiveness to predictability changes each option's total by x × (predictability score − responsiveness score) ÷ 100:

  • Sprints gains 1 point per point moved (4 − 3 = +1), so its total in points is 320 + x.
  • Kanban loses 2 points per point moved (2 − 4 = −2), so its total in points is 340 − 2x.
  • The two are equal when 320 + x = 340 − 2x, so x = 20 ÷ 3 ≈ 6.7 points.

So Kanban stays ahead while the predictability weight is below about 26.7%. If weights are whole percentages, sprints take the lead at 27%.

Line chart of the sensitivity analysis: weighted totals for sprints, Kanban and six-week cycles as the predictability weight rises from 10 to 40 percent while the responsiveness weight falls by the same amount; Kanban leads until a break-even at about 26.7 percent where sprints overtake it, and at the tested 30 percent weight sprints score 3.30 while Kanban and cycles tie at 3.20
The ranking flips once predictability passes about 26.7%. The real decision is about how much date forecasts matter to this team.

The workbook's sensitivity table does this sweep for you. Choose which criterion to raise and which to lower, and it recalculates every option at shifts from 0 to 20 points, showing the leader at each step.

How to read the result. The matrix has turned "which workflow?" into a narrower question: is predictability worth more or less than about 27% of this decision? That question can be answered with facts.

In the example, the head of product confirmed that only two milestones carry external dates. The rest of the roadmap can move. On that basis, the team kept predictability at 20% and wrote the 27% threshold into the decision record as a review trigger.

Non-negotiables, ties, missing evidence and bias

Non-negotiable criteria

Anything you would never trade away belongs in a gate, not in the weights. A weighted total is compensatory: a high score on one criterion can make up for a low score on another. Mandatory requirements should not work that way.

The UK multi-criteria analysis manual makes the same point: where options must reach a minimum acceptable level, those below it are rejected outright, because better performance elsewhere cannot compensate. It also warns that thresholds chosen after seeing how options score can bias the result, so set gates before scoring (DCLG, 2009). Keep gates few and genuinely binary, such as a legal requirement, a hard budget ceiling or a security control. A gate that most options fail is often a preference written too strictly.

Ties and near-ties

Decide your tie rule before you see the totals. A workable order:

  1. Check that the tie is real. Two totals that differ by 0.05 on a 1–5 scale are a tie for practical purposes. The workbook flags any first place within 0.25 as a close result.
  2. Compare on the highest-weighted criterion. The team already said it matters most.
  3. Look at confidence. Prefer the option whose scores rest on stronger evidence.
  4. Gather evidence on the criterion where the options differ most, not on all of them.
  5. Let the owner decide and write down why. Do not adjust weights after seeing the totals to manufacture a winner.

Missing evidence

Do not fill a gap with a guess presented as a fact. Leave the cell blank and mark it, which is what the workbook's "Missing scores" column counts. Or score it conservatively and set the confidence to Low.

Then ask whether the gap could change the decision. This is a quick value-of-information test.

  • Six-week cycles, adoption effort (scored 2, low confidence). Nobody on the team has run cycles. Raising the score to 3 lifts cycles to 3.15, and 4 gives 3.30, both still below Kanban. Only a 5 (3.45) would put cycles first, and the anchor says 5 means "no new roles or meetings". This gap is not worth a pilot.
  • Kanban, forecastable dates (scored 2, medium confidence). The team has no cycle-time history yet. If the honest score were 1, Kanban would fall to 3.20 and tie with sprints. If it were 3, Kanban would rise to 3.60. This gap matters, so the decision record makes collecting delivery data a condition of the choice.

Stakeholder bias

Most bias in a decision matrix enters through the weights and through group scoring.

  • Freeze weights before scoring. ASQ's description of the method has the team set weighted criteria first and evaluate options afterward (ASQ). Weights adjusted after the totals are visible are a red flag.
  • Score independently, then compare. In a peer-reviewed experiment, seeing other people's estimates made a group's answers more similar without making them more accurate (Lorenz et al., PNAS, 2011). Collect scores privately, then discuss only the cells where scores differ by two points or more.
    • In the example, the support lead scored sprints a 1 on interruptions and an engineering lead scored them a 3. The escalation log settled the score at 2, and the reasoning went into the evidence column.
  • Separate the advocate from the scorer. Whoever proposed an option should explain it, but not be the only person scoring it.
  • Use neutral labels (Option A, B, C) for the first scoring round if one option is somebody's favorite.
  • Treat the total as input, not a verdict. In US federal bid-protest decisions, the Government Accountability Office describes evaluation ratings, numerical or otherwise, as guides for decision-making and says evaluations should rest on a qualitative assessment (GAO, B-417133, 2019).

Write a decision record that makes the trade-off auditable

A matrix shows how the options scored. A decision record shows what was decided, why, who disagreed and when the question should be reopened. Without one, six months later nobody remembers whether 20% predictability was a deliberate choice or an oversight.

FieldWhat to write
DecisionWhat was decided, in one sentence
Owner and dateWho is accountable, and when
Options consideredEvery option, including any screened out and why
Gates appliedPass/fail requirements checked before scoring
Criteria and weightsMatrix version, and who agreed the weights before scoring
ResultWeighted totals and the margin between first and second
Sensitivity findingWhich weight change would flip the result, and at what point
Missing or weak evidenceLow-confidence scores, and whether they could change the result
Why this optionThe reasoning in plain words, not just the score
DissentWho disagreed, about what
MitigationsWhat will be done about the chosen option's weak scores
Review triggerThe event or date that reopens the decision
Four steps, screen, score, stress-test and record, leading to a decision record for the fictional example: adopt Kanban with WIP limits provisionally until a week-8 review because it absorbs weekly escalations, sprints would win if predictability were weighted 27 percent or more, the sales lead's dissent is noted with fortnightly demos added, and the decision reopens if no date range exists by week 8
The filled record for the worked example. The dissent and the review trigger are what make this decision auditable.

In the example, the record says:

  • Decision. Adopt Kanban with WIP limits for two quarters, provisional until a week-8 review.
  • Mitigations. Two of them address Kanban's weak scores:
    • A stakeholder demo every two weeks, which answers the sales lead's preference for sprints' fixed review cadence.
    • Recording finish dates from week 1, so the team can publish a first date range for both milestones at week 8.
  • Review trigger. The decision reopens if that date range cannot be produced, or if leadership raises the predictability weight to 27% or more.

Mitigations do not change the scores already given. If you want to score "Kanban plus fortnightly demos" as a different option, add it as a new column and rescore it.

Store the record next to the matrix and the evidence it cites. The same principle runs through good project documentation practices: decisions should be findable by people who were not in the room. If the decision belongs to a project's planning stage, file it with the other planning-phase deliverables and link it from the project plan. Track the open risks it creates in a RAID log.

How to create a decision matrix in eight steps

  1. Frame the decision. Write the question, the owner, the decide-by date and the gates. If the goal behind the decision is vague, sharpen it into a SMART goal first.
  2. Shortlist options. Two to five real alternatives. Consider a "do nothing" or staged option where one is realistic, and record any you excluded, and why. A missing alternative is a gap no amount of scoring can fix.
  3. Define criteria and anchors. Five to eight distinct criteria, each with a written 5 and 1. Check for double-counting. For example, "cost" and "budget risk" often measure the same thing.
  4. Set weights. Agree percentages that total 100% before anyone scores, and note who agreed.
  5. Score independently, then reconcile. Each evaluator scores alone. Discuss only large disagreements, and log the evidence for each final score.
  6. Calculate. Weighted score = weight × score ÷ 100, summed per option. Keep the simple sum alongside to see what the weights changed.
  7. Run the sensitivity check. Move points between the weights that were disputed and find the break-even. Test whether any low-confidence score could change the result.
  8. Record the decision. Owner, rationale, dissent, mitigations and a review trigger.

Decision matrix vs. other prioritization tools

These tools are often confused because several are called "matrices". They answer different questions.

ToolQuestion it answersTypical input
Weighted decision matrixWhich of these options should we choose?2–5 alternatives × several weighted criteria
Impact–effort matrixWhich tasks or ideas should we do first?A backlog plotted on two axes, impact and effort
Eisenhower matrixWhat do I do now, schedule, delegate or drop?Tasks sorted by urgency and importance
Pugh matrixIs each concept better or worse than a baseline?Concepts scored +/0/− against a reference design
Pros-and-cons listWhat are the arguments for and against?One or two options, unscored
RACI chartWho does what in carrying out the decision?Roles × tasks (try the RACI matrix template)

ASQ lists "Pugh matrix" as another name for a decision matrix, but in practice a Pugh matrix usually rates concepts as better, same or worse than a baseline design, while a weighted matrix scores every option on an absolute scale.

When the options differ mainly in money over several years, a cost-benefit analysis template with NPV and payback is usually the better tool, and its result can feed one criterion of your matrix.

The most common mix-up is between the decision matrix and the impact–effort matrix. A decision matrix is for choosing one option from alternatives, using several criteria at once. An impact–effort matrix is for ordering many items by two dimensions only.

They work in sequence. Use the decision matrix to pick the workflow. Then sort the work that follows with an impact–effort matrix template or the Eisenhower matrix template. Where the choice is about which risks to accept rather than which option performs best, a risk assessment template is a better starting point.

Using the template in Excel, Google Sheets or AFFiNE

Excel. Open the .xlsx file. White cells are inputs; shaded cells contain formulas.

The workbook has five sheets:

  • How to use: instructions, the scoring scale and the formulas.
  • Blank matrix and Worked example: both include gates, scores, results and the sensitivity table.
  • Decision record and Example record: the blank and filled decision record.

The Check cell warns when weights do not total 100%, when scores are missing, when there is a tie and when the result is close.

Google Sheets. Upload the .xlsx file to Google Drive and open it with Google Sheets. We checked the workbook by recalculating it in LibreOffice Calc. It uses only standard functions that Excel and Google Sheets also provide (SUMPRODUCT, RANK, INDEX, MATCH, COUNTIF, ROUND), but after opening it in another app, confirm that the "Worked example" sheet shows totals of 3.20, 3.40 and 3.00. The .csv files hold values only and do not recalculate.

AFFiNE. AFFiNE can import Markdown files (Import → Markdown files), and Markdown tables come in as table blocks. Import the .md template to get the blank matrix, sensitivity table and decision record as one editable doc. Each table's header arrives as an ordinary first row.

As of October 2026, AFFiNE tables and databases have no formula columns, so they cannot calculate weighted totals. Do the arithmetic in the spreadsheet and keep the decision in AFFiNE, where you can:

  • Link evidence to the decision. Link related docs, such as vendor notes, meeting minutes and the escalation log, from the record with @ mentions, so the evidence sits next to the decision.
  • Brainstorm criteria first. Use edgeless mode, AFFiNE's whiteboard view of the same doc, to cluster candidate criteria on a canvas before you commit to a list.
  • Reuse the structure. Mark the finished doc as a template, so the next decision starts from the same structure. AFFiNE's template documentation explains how.

Common decision matrix mistakes

  • Too many criteria. Beyond eight or so, each weight becomes small and the totals converge. Merge or cut.
  • Overlapping criteria. Counting the same concern twice under different names quietly doubles its weight.
  • Weights set after scoring. Even well-meant adjustments look like steering once the totals are visible.
  • Unanchored scores. If "4" means different things to different scorers, the total is noise.
  • False precision. Two decimals make 3.40 vs. 3.20 look exact, but the inputs are whole-number judgments. Small margins call for a sensitivity check, not a celebration.
  • No record. Without the rationale and dissent written down, the same debate restarts the next quarter.

Accessibility note. If you share the matrix as an image or color-coded table, print the number in every cell, as the heatmap above does. Do not rely on color alone, and provide the table as text so screen-reader users get the same information.

Sources

Checked on 5 October 2026.

Last reviewed: October 5, 2026. The worked example and every number in it are fictional teaching data. The template files are generated from the same data so that the article, spreadsheet and images stay consistent.