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

Subscribe to
The Daily Friction

A daily newsletter on automation and eliminating friction

Related Content

Scrum conceals bad teams.

Scrum conceals bad teams. Far too often, we confuse Scrum with a magic wand that transforms any team into a high-performing 'dream team'. It's tempting to believe that the sprint system, with its regular completion and initiation of tasks, gives us an agile and...

read more

🚀 Process Automations in Microsoft Loop!

🚀 Process Automations in Microsoft Loop! Now you can create Power Automate-backed rules to streamline repetitive tasks in your Loop table. See https://insider.microsoft365.com/en-us/blog/streamline-your-workflow-with-automation-in-microsoft-loop Loop is slowly...

read more

You don’t control the truth in Production!

You don't control the truth in Production! Now a days multiple teams/projects are working on the same Dataverse production environment. So thinking you can manage the complete production truth in your ALM pipeline is strange. Not every environment is 💯 equal to...

read more
Share This