Benefits Breakdown Structure

In public administration, we often encounter the belief: “This project has no benefits – we have to do it because it is required by law.” While this approach is understandable, it is also problematic. In practice, it leads to situations where:

  • projects are delivered for compliance rather than value,
  • outcomes are not clearly defined,
  • impact is not measured,
  • opportunities to genuinely improve institutional performance are lost.

At the same time, project and program management standards clearly state that projects are tools for creating value and delivering benefits—not just producing outputs. This raises a key question:

👉 how can we systematically approach defining benefits—especially in regulatory projects?

One of the most effective tools is the Benefits Breakdown Structure (BBS).

What is Benefits Breakdown Structure?

Benefits Breakdown Structure is a framework that shows the logical relationship between:

  • strategy → benefits → outcomes → activities → outputs

It reverses typical project thinking. Instead of starting with:

👉 “what do we need to implement?”

we start with:

👉 “what value do we want to achieve?”

Why is BBS particularly important in the public sector?

In commercial projects, benefits are often obvious (e.g. revenue, profit). In public administration:

  • projects are often compliance-driven,
  • benefits are distributed and intangible,
  • stakeholders are diverse (citizens, administration, the state).

Without a structure like BBS, it is very easy to stop at the level of:

👉 “we implemented the system”

👉 “we complied with the regulation”

…and never reach the question:

👉 “what has actually changed?”

How does BBS logic work in practice?

Let’s look at a simplified example from tax administration.

Strategic objective

Increase the effectiveness of the tax system

Benefits

  • higher budget revenues,
  • reduced tax gap,
  • faster detection of irregularities.

Outcomes (changes)

  • automated data analysis,
  • shorter audit cycles,
  • improved data quality.

Activities

  • implementation of analytical tools,
  • changes in audit procedures,
  • staff training.

Outputs

  • IT systems,
  • new procedures,
  • reports and analytical models.

The key mindset shift

BBS enforces a fundamental shift:

👉 outputs are not the goal of the project

👉 outputs are only a means to achieve benefits.

This is a critical distinction. Because:

  • an IT system ≠ a benefit,
  • implementing a regulation ≠ a benefit.

A benefit only emerges when:

  • 👉 the way of working changes,
  • 👉 and that change creates value.

Benefits in regulatory projects – where to find them?

In projects driven by legislation, benefits should be analyzed from three perspectives:

  1. Citizen
    • simpler procedures,
    • shorter service times,
    • greater accessibility of services.
  2. Administration
    • automation,
    • fewer errors,
    • higher efficiency.
  3. State
    • improved systemic control,
    • more effective regulation,
    • better data for decision-making.

Categories of benefits – not only financial

One common mistake is focusing solely on financial benefits. In the public sector, equally important are:

  • financial – savings, increased revenues,
  • efficiency – time, productivity,
  • social – quality of services for citizens,
  • reputational – trust in institutions,
  • strategic – the state’s capability to act.

BBS helps capture all these dimensions.

Common mistakes without BBS

Without a structured approach, we often observe:

  • ❌ confusing outputs with benefits,
  • ❌ lack of alignment with strategy,
  • ❌ lack of measurement,
  • ❌ no ownership of benefits.

The result? The project is delivered—but its value remains unknown.

What does BBS bring in practice?

In organizational practice, BBS:

  • ✔ structures thinking about value,
  • ✔ helps justify regulatory projects,
  • ✔ enables defining measurable indicators,
  • ✔ increases team engagement,
  • ✔ supports decision-making (e.g. prioritization).

Summary

The biggest problem with public sector projects is not the lack of benefits. 👉 The real problem is the lack of conscious benefit definition. Benefits Breakdown Structure helps answer the key question:

“Why are we really doing this project?”

And only when this question is answered does a project stop being an obligation… and become a tool for real change.

Are you interested in projects, programmes or portfolios? Sign up for our courses and training sessions. Our events are a great opportunity not only to explore the subject in greater depth or prepare for certification, but above all to gain practical experience. To learn more on benefits, sign up for the Program Management Professional (PgMP)® Exam Prep Course.

Sign up for our newsletter. Each week you will receive a letter from us with articles worth reading, tools for working with teams, tips and interesting facts about project management.