3 ms·
The matrix for effort vs. impact is something I find myself drawing in meetings a lot. Effort Low High
by hbosch 4y ago
The matrix for effort vs. impact is something I find myself drawing in meetings a lot.
Effort
Low High
┌───────────┬───────────┐
I │ │ │
m Low │ Ok │ Bad │
p │ │ │
a ├───────────┼───────────┤
c │ │ │
t High │ Perfect │ Ok │
│ │ │
└───────────┴───────────┘
- jrochkind1 4y agoThe best simple way to prioritize a backlog. Engineering team is responsible for assigning "effort" dimension; product/stakeholder team is responsible for assigning "impact" dimension. Then we see what's in high impact/low effort, and that's what we're gonna work on.
- travisjungroth 4y agoI came up with almost the same activity but didn't think of having different groups decide the dimensions. Some random stuff: Use stack ranking. Avoids "everything is a priority" and related mistakes. Effort and impact both have a long tail distribution, something like power law. It's probably power law because it's easy to be off by an order of magnitude. "Impact" is easier to get wrong because it's going to the high end. Don't think most impactful and second most impactful have a similar impact because they're close in rank. It's easy for #1 to be 10-100x #2.
- jventura 4y agoSo, it pays off to keep effort low most of the times, right? I agree with the matrix, so I cannot find another conclusion..