Value/Effort Matrix

by Feb 3, 2023

After trying out different methods of prioritizing, I really like the Value/Effort Matrix.

With minimum effort, it will give you the priority of your features (Backlog Items, etc)

The input are two parameters:

Value (or Impact): What is the value for the Customer and/or the Company.

Effort: How much resources are needed to finish the feature.

For both parameters, I try to keep the options low: Low (2), Medium (4) or High (8).

By using the following calculation, we know the order of features:
Priority = Value / Effort

This will result into the following categories:

Big Projects (high value/high effort) – valuable features that are complex and resource-intensive. These often-long-term projects must be backed by detailed plans.

Quick Wins (high value/low effort – focus on these first, the “low-hanging fruit”, which is a great way to win customers quickly.

Fill-ins (low value/low effort) – this describes features that can be completed during periods of low activity between other project items. The “nice to have” items.

Time sinks (low value/high effort) – features that should be left until last or abandoned altogether.

Value Effort Matrix
Remy van Duijkeren

Remy van Duijkeren

Power Platform Advisor

Microsoft Power Platform Advisor with over 25 years of experience in IT with a focus on (marketing) automation and integration.

Helping organizations with scaling their business by automating processes on the Power Platform (Dynamics 365).

Expert in Power Platform, Dynamics 365 (Marketing & Sales) and Azure Integration Services. Giving advice and strategy consultancy.

Services:
– Strategy and tactics advise
– Automating and integrating

Subscribe to
The Daily Friction

A daily newsletter on automation and eliminating friction

Related Content

AI isn’t asking questions. It’s just making assumptions.

AI isn’t asking questions. It’s just making assumptions. In consulting or sales, you learn fast: What customers want isn’t always what solves their problem. They ask for solutions they know based on limited knowledge. Experienced consultants do something else: They...

read more

Cancel Culture in IT: How Codes of Conduct Became Weapons

Cancel Culture in IT: How Codes of Conduct Became Weapons Cancel Culture is happening in major communities to developers and contributors, like the: Linux Kernel C++ Standard Committee Python NixOS openSUSE Godot And the reasons? Completely absurd: Being Republican...

read more