Skip to content
Back to search results

Results-Based Management

Introduced by
OECD-DAC; United Nations Development Group; aid-effectiveness agenda (Paris Declaration / Accra)
Year
2002
Type
Management and evaluation strategy for development results
Family
Managing for development results
Font size

What does it do?

Results-Based Management (RBM) is a management strategy that orients all the activities, resources, and processes of an organisation or programme toward achieving and demonstrating clearly defined results, rather than merely tracking inputs delivered and activities completed.

Codified in the OECD-DAC's 2002 evaluation glossary and adopted across the United Nations, the World Bank, and bilateral agencies, it embeds a results chain, performance indicators, and continuous monitoring into the full project cycle so that evidence on outcomes feeds back into decisions.

The intuition behind the method

Think of the difference between counting how many seeds you planted and asking whether anyone was eventually fed. Traditional management reports busyness — workshops held, manuals printed, money spent. RBM insists you keep asking 'so what?' up a chain: inputs buy activities, activities yield outputs, outputs trigger outcomes, outcomes accumulate into impact. By choosing indicators, fixing a baseline, and setting targets for each link, the manager turns the abstract promise of 'development' into a measurable trajectory, then steers toward it as the evidence comes in.

History

RBM grew out of results-oriented and performance-management reforms in OECD public administrations during the 1990s, transposed into development cooperation as agencies sought to demonstrate value for aid. The OECD-DAC's 2002 Glossary of Key Terms in Evaluation and Results Based Management standardised the vocabulary — inputs, outputs, outcomes, impact, indicators — across donors. The 2005 Paris Declaration on Aid Effectiveness and the 2008 Accra Agenda for Action made 'managing for development results' a core principle, and the UN Development Group issued RBM handbooks to operationalise it across agencies. It now underpins the results frameworks of the World Bank, UNDP, the Global Fund, and most bilateral donors, and connects directly to monitoring of the Sustainable Development Goals.

When to use it

Use RBM when an organisation or programme must plan, manage, and account for development results across the full cycle and a funder or governing body expects outcome-level evidence rather than activity reports. It suits portfolios and multi-year programmes where indicators can be defined and tracked, and where the management culture allows decisions to be adjusted in response to evidence. It is harder to apply where outcomes are diffuse, attribution to a single actor is weak, or measurement systems are too weak to supply reliable baselines and targets, in which case lighter theory-based or contribution-focused approaches may be more honest.

Limitations and considerations

  • Outcome- and impact-level results are influenced by many actors, so attributing them to a single programme is methodologically difficult and often overstated.
  • It can drive a focus on what is easily measurable, distorting effort toward quantifiable outputs and away from qualitative or hard-to-measure change.
  • Reliable RBM depends on baselines, data systems, and capacity that many implementing organisations and partner governments lack.
  • Applied as upward accountability to donors, it can generate heavy reporting burdens and 'gaming' of indicators rather than genuine learning.

Source conditions do not replace independent scientific review or validation by an analysis engine.

Strengths

  • Shifts accountability from inputs and activities to results, focusing attention and resources on the outcomes and impact that justify the intervention.
  • Provides a coherent results framework with baselines and targets that makes progress measurable and comparable across programmes and over time.
  • Builds a continuous monitoring-and-feedback loop into management, enabling course correction during implementation rather than only post-hoc judgement.
  • Aligns with the international aid-effectiveness agenda (Paris Declaration, Accra Agenda for Action), supporting harmonisation and mutual accountability among partners.

Applications

  • Structuring an agency's country or programme strategy around a results framework with outcome indicators, baselines, and targets.
  • Designing the performance measurement system of a multi-year programme so that monitoring data flow into annual management decisions.
  • Reporting to governing boards and donors on outcome- and impact-level results rather than activity counts.
  • Aligning multiple partners' contributions to shared outcomes under the aid-effectiveness principle of managing for development results.
  • Linking project results frameworks to national development plans and Sustainable Development Goal indicators for coherent reporting.

How it works

How it works

1

RBM begins by articulating the results chain — the causal sequence inputs to activities to outputs to outcomes to impact — that explains how resources are expected to be transformed into the desired development change. Outputs are products and services the programme controls; outcomes are the short- and medium-term behavioural or institutional changes that follow their use; impact is the long-term, higher-order change to which the programme contributes alongside other actors. Making this chain explicit defines what 'results' means at each level and clarifies accountability boundaries.

2

For each level of the chain, performance indicators are selected — ideally SMART (Specific, Measurable, Achievable, Relevant, Time-bound) — and arranged in a results framework or performance measurement matrix. Each indicator is given a baseline value measured before or at the start of the intervention and a target value to be reached by a stated date. The baseline-target pairing converts vague objectives into a verifiable trajectory of expected change against which progress can be assessed.

3

An ongoing monitoring system collects data on the chosen indicators throughout implementation, comparing actual values to baselines and targets and tracking the assumptions and risks that condition the chain. Data come from project records, surveys, administrative systems, and field reporting, and are reviewed at regular intervals so that emerging gaps between expected and actual results are detected early rather than at the end.

4

Periodic evaluation interprets the monitoring evidence to judge relevance, effectiveness, efficiency, and the contribution of outputs to outcomes and impact, distinguishing the programme's effect from external factors. The findings are fed back into management decisions — reallocating resources, revising the results chain, or adjusting delivery — closing the learning loop. This 'managing for results' cycle, central to the Paris Declaration and Accra Agenda, makes RBM iterative rather than a one-off reporting exercise.

Common pitfalls

  • Confusing outputs with outcomes — claiming behavioural or institutional change when only deliverables were produced — which inflates reported results.
  • Setting indicators without measurable baselines, so progress cannot be assessed and targets become arbitrary.
  • Treating monitoring data as a reporting obligation rather than feeding it back into management decisions, so the learning loop never closes.
  • Selecting too many indicators, overwhelming the monitoring system and obscuring the few measures that actually matter for steering.

Frequently asked questions

What is the difference between outputs, outcomes, and impact?

Outputs are the products, goods, and services that a programme produces and directly controls — for example, teachers trained or wells built. Outcomes are the short- to medium-term changes that result when those outputs are used — improved learning, increased access to clean water — and are influenced but not fully controlled by the programme. Impact is the long-term, higher-order change, such as reduced poverty or mortality, to which the programme contributes alongside many other factors. RBM requires distinguishing them precisely because accountability and attribution differ at each level.

How does RBM relate to the Logical Framework Approach?

The two are closely related and often used together. The Logframe is a compact planning matrix that lays out a single project's objective hierarchy, indicators, verification, and assumptions. RBM is the broader management philosophy and cycle — planning for results, monitoring them, evaluating, and adapting — that can govern an entire organisation or portfolio. A logframe or results framework is typically the planning instrument through which RBM is operationalised at the project level.

What makes a good RBM indicator?

A good indicator is usually SMART — Specific, Measurable, Achievable, Relevant, and Time-bound — and is matched to the right level of the results chain (output, outcome, or impact). It should have a clear definition, a feasible and affordable data source, a measured baseline, and a target. Practitioners favour a small number of well-chosen indicators over a long list, because too many indicators overwhelm the monitoring system and dilute the focus needed to manage for results.

Related methods

Sources

  1. OECD-DAC (2002). Glossary of Key Terms in Evaluation and Results Based Management. OECD Development Assistance Committee, Paris.

    Open publication reference
    Copied.
  2. United Nations Development Group (2011). Results-Based Management Handbook: Harmonizing RBM Concepts and Approaches for Improved Development Results at Country Level. UNDG, New York.

    Open publication reference
    Copied.