ROI & costs

How to prioritise data use cases by ROI

A simple method to prioritise data initiatives by impact, effort and data availability, and focus investment where it returns most.

DLData Layer Team Jun 14, 2025 4 min read
How to prioritise data use cases by ROI

Key takeaways

  • Prioritising avoids scattering resources on low-return initiatives.
  • A simple method crosses business impact, effort and data availability.
  • Start with high impact, low effort and available data.
  • Prioritisation should be reviewed, not fixed once.
  • The impact-effort matrix surfaces the obvious priorities.

Ideas for what to do with data usually abound; what is missing is the criteria to decide where to start. Without prioritisation, resources scatter and the highest-return projects get stuck among dubious ones.

What it means

Prioritising data use cases means ordering initiatives by the value they bring and the cost of achieving them, to concentrate investment where the return is greatest and fastest.

The three axes

  1. Business impact: how much value it generates (revenue, savings, risk avoided).
  2. Effort: cost, time and complexity of implementation.
  3. Data availability: whether the needed data exists and is reliable.

The impact-effort matrix

A simple, effective tool is placing each case on an impact-versus-effort matrix. High impact, low effort are the obvious priorities; high impact and high effort, projects to plan; low impact, discardable. Data availability acts as a filter.

High impact + low effort
→ Do first
High + high
→ Plan
Low impact
→ Discard
The impact-effort matrix surfaces the obvious priorities; data availability filters them.

Starting well

Start with a high-impact case of reasonable effort and available data. That first success validates the approach and funds the next. Review the prioritisation regularly: as the data layer matures, previously unviable cases become accessible.

Start where impact is high, effort is reasonable and the data already exists — then let success fund the rest.

In summary

Prioritise data use cases by crossing business impact, effort and data availability. The impact-effort matrix surfaces obvious priorities; start with a high-impact, available-data case to validate and fund the next, and review the order as the data layer matures.

Sources & further reading

Frequently asked questions

How do I prioritise among many data ideas?

By crossing three axes: business impact, implementation effort and data availability. Start with high impact, low effort and available data.

What is the impact-effort matrix?

A tool that places each case by its value and cost, helping identify obvious priorities and discard low-return work.

Is prioritisation final?

No. It should be reviewed: as the data layer matures, cases previously unviable for lack of data become accessible.

Why does data availability matter?

An ideal case with no reliable data is not viable short-term. Availability acts as a filter on the impact-effort matrix.

Where should I start?

With a high-impact case of reasonable effort and available data — a quick win that validates the approach and funds the next.

What happens without prioritisation?

Resources scatter across dubious initiatives and the highest-return projects get stuck, delaying value.

Turn this data into results

Tell us what you want to achieve. Data Layer connects, processes and delivers the result up and running, with no infrastructure for you to manage.