Decision-makingAlso called Weighted scoring, Pugh matrix
Decision Matrix
Score every option against the same weighted criteria, so people can see where they disagree.
In one look
- 1Agree what matters.
- 2Weight it before you score.
- 3Score every option the same way.
Nobody invented weighted scoring. Engineers and operations researchers kept arriving at it through the middle of the twentieth century. The best-known named version is Stuart Pugh's, a design engineer who in the 1980s compared concepts against a reference option, one criterion at a time.
The problem it solves
A third meeting is booked.
Two options and a team split on instinct. One side says the work is stronger, the other says they're easier to work with, and neither argument can beat the other because they're about different things. A matrix rarely overturns anyone's gut. It shows which criterion the disagreement is about.
Try it yourself
No sign-up, a few minutes. Three CRMs, four criteria. You set the weights and watch the winner change.
The same choice, scored
Two agencies pitching for a rebrand, and a leadership team split down the middle.
- In the meetingThe work is stronger.
becomes Five criteria, weighted before anyone scores: creative 30%, chemistry 20%, price 20%, sector experience 15%, capacity 15%.
- In the meetingThey're easier to work with.
becomes Agency A wins on the numbers.
- In the meetingLet's book another meeting.
becomes Chemistry carries 20% of a seven-figure decision, so they meet A's delivery team before signing.
Good times to run it
- Vendor and platform selections
- Hiring, when the panel keeps splitting on "fit"
- Ranking projects against a fixed budget
- Any choice you'll have to explain to a board in six months
When to skip it
- When you already know which option you want. You'll find weights that pick it.
- When everyone already agrees. The spreadsheet adds nothing.
- New kinds of bet, where what matters most isn't a criterion anyone would have listed.
Teams we've run sessions with:
More frameworks
- Decision-makingPre-MortemBefore the work starts, the team imagines the project has already failed and explains why.
- Prioritization80/20 RuleA small share of clients, products or tasks usually produces most of the result. Find that share before you plan.
- Decision-making5 WhysAsk why the problem happened, then ask why again of each answer, until you reach a cause worth fixing.