STEP 2

Rationale: Why derive project outputs and what it brings to the process 

Project outputs are something that the project produces that others use to address the issues or problems that the project is working on, i.e.: the project determinants. In short, project outputs are project deliverables which the donor is paying for and it is important to identify them.

The co-development and use of project outputs by next users and end users is the project's main impact strategy.
The output itself doesn't tackle the problem - it is the use of the output by the next users and the end users which tackles it.

An output can be: a database, a technology such as a new variety, a machine, publications, workshops involving next users and end users (not internal), training courses, capacity built in the members of the next users, and end users groups.

An output cannot be: internal workshops, internal financial reports, and other internal documentation. However, it is important to highlight that the production of these may well be progress markers towards the delivery of one or more outputs.

Preparation for the exercise

15 minutes

HOW TO SET IT UP:

This is a follow on from the problem tree, i.e., you need to have done the problem tree first to identify the outputs

TIP:

Projects generally have 3 to 5 main outputs. As a rule of thumb, don't go above seven.

HOW TO DERIVE PROJECT OUTPUTS:

Ask the participants to identify what their projects are going to produce that will be used by others to tackle the project determinants.

Click here for a PowerPoint slide of an exercise on deriving project outputs.

Yellow River (CPWF) workshop participants at work 

Look at our FAQ if you have any further questions on deriving project outputs.

Next step: iii. Creating a Vision