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

Backlog: The Black Hole of ideas

Backlog: The Black Hole of ideas Is your backlog turning into an ever-expanding universe of forgotten dreams? We all know that mix—a jumble of big ideas and tiny tasks waiting for their day in the sun. Some items linger for years. Why do backlogs grow? Because we...

read more

The Trade-off Between Budgets and Quality ⚖️

The Trade-off Between Budgets and Quality ⚖️ In my previous post, I talked about shifting from Estimates to Budgets for feature development 💡. Let's dive deeper. Using a Budget instead of an Estimate introduces a trade-off: Scope and Quality adjust to fit the time...

read more

Budgets instead of Estimates

Budgets instead of Estimates Estimating a feature is difficult and is often a guess (or even a lie). An Estimate is for a fixed scope. So, you need to think deeply how to implement the feature, before giving an Estimate. The business can then use the Estimate to...

read more