Results-Based Management: from Goal to Activity

Results-Based Management (RBM) organizes a programme around a chain of results rather than around a list of activities alone. The idea is simple to state and genuinely hard to do well: an activity should exist because it produces an output, an output should exist because it contributes to an outcome, and an outcome should exist because it moves the programme toward its goal or impact.

A Theory of Change is the explanation of WHY that chain is expected to hold — the assumptions connecting one level to the next ("if farmers receive training AND adopt the practices taught, THEN yields will improve"). A Results Framework is the more structured, often tabular expression of the same logic, usually paired with indicators at each level. The two describe the same underlying logic at different levels of narrative detail; a Results Framework without a Theory of Change behind it is a list of boxes with no explanation of why anyone believes they connect.

Goal or Impact is the highest-level, longer-term change the programme contributes to — often something no single programme could achieve alone, and something that will only be visible well after the programme ends. Outcomes are the medium-term changes in behaviour, practice, or condition among the people or systems the programme targets — the level most programmes are actually accountable for. Outputs are the concrete goods, services, or products the programme itself delivers and directly controls. Activities are the specific tasks staff carry out to produce those outputs.

The test for whether a level is placed correctly is control and timeframe. A programme directly controls whether it delivers an activity and produces an output — it does not directly control whether people change behaviour as a result (that depends on people's own choices, which is exactly why outcomes need real indicators, not assumptions). Conflating outputs and outcomes — claiming credit for a change in behaviour just because a service was delivered — is one of the most common and most damaging weaknesses in programme reporting.

A Results Framework in METRA GET is exactly this hierarchy, modelled as logframe items (goal, outcome, output, activity) that indicators attach to. The platform does not infer or validate whether your programme logic is sound — that judgement stays with the programme team — but it does enforce that every indicator sits at a real level of that hierarchy, so a report can always show which claim (output-level delivery, or outcome-level change) a given number actually supports.