How to design LogFrame

LogFrame (Logical Framework) is a widely popular tool for project design, planning, monitoring and evaluation. It is however most often used in the planning or re-planning of a project.  The method was first developed in the early 1970s.  It is used by bilateral and multilateral agencies including the World Bank, the Asian Development Bank, the Food and Agriculture Organisation (FAO), Overseas Development Agency (ODA) and the US Agency for International Development (USAID), and most Non Profit Organizations across the globe today.

Logframe is most useful in helping to identify the elements of a project and the linkages between them in a logical, concise and objective manner.  It introduces order and discipline into the project design process and helps place the project in the larger context of a program or sector plan.  It also serves as a tool for logically identifying inputs, assumptions for success, outputs and indicators for monitoring progress and evaluating performance.

The term LogFrame is often loosely used to refer to both the process or concept of project analysis and the matrix outcome of this process.  The Logframe concept is often referring to the thought process, and the matrix is the visible result. LogFrame involves the following procedures:

• Setting project objectives
• Defining indicators of success
• Identification of key activity groups
• Defining critical assumptions on which project is based
• Identification of verifying project accomplishments
• Defining resources required for implementation.

Basic Steps

The guiding methodology of LogFrame is the concept of causality, or cause and effect.  It suggests in any development activity or project, resource inputs are used with activities to produce outputs; outputs are expected to achieve project purposes; and the achievement of purposes is expected to contribute to the achievement of a higher order goal.

The basic premise is that there is a hierarchy of objectives, and the achievement of success on higher levels in the hierarchy is often subject to factors beyond the control of planners and managers.  As a result, the achievement of a level may not be sufficient for the achievement of the next level.  The linkage or progress from one level to the next is therefore conditional on the continuing validity of stated assumptions.

The following are the basic steps for developing a project design using a Logical Framework.  The basic principle is to go from the general to the specific.  That is, begin with the Narrative Summary and several key assumptions, then try to put indicators and targets on the general statement of objectives.

The Narrative Summary refers to the first 4 steps which include:

1. Define the Purpose
2. Define the Outputs for achieving the Purpose
3. Define the Activity groups or Components for achieving each output
4. Define the overall Goal
5. Verify the vertical logic with the If/then test
6. Define the Assumptions required at each level
7. Define the Objectively Verifiable Indicators (OVI) at Purpose, then Output, then Goal levels
8. Define the Means of Verification
9. Put costs on the Activities: the Performance Budget
10. Consult the Checklist for the Logical Framework
11. Review the Logical Framework design in the light of historical experience with similar efforts

Step 01: Define the Purpose

This is to define WHY the project is being done.  The Purpose describes the desired impact we hope the project will have, or how the situation is envisaged at its completion.

For example, a Purpose typically describes the development expected: to develop sustainable water supplies for the people of a certain village; or to develop a manageable rural health service accessible to all in a certain region.

As a rule of thumb, a project have only one Purpose although a project may have more than one purpose.  The reason for this is practical.  Experience demonstrates that it is easier to focus project Outputs on a single Purpose.  Multiple purposes diffuse project efforts and weaken the design.

Step 02: Define Outputs for Achieving the Purpose

Outputs are WHAT the project is to accomplish, or the direct, identifiable and measurable results expected from the provision of inputs together with the execution of activities.  These are the deliverables or Terms of Reference (TOR) for the project, the results for which the project can be held directly accountable and for which it is given resources.

Step 03: Define the Activity Groups or Components for Achieving Each Output

Activities are the discrete tasks undertaken using resource inputs to achieve defined outputs.  Description of the activities should include the basic actions of the project team: the summary schedule, meetings, monitoring events and evaluations.

Step 04: Define the Overall Goal

The goal is the rationale of the program or project.  The higher-order objective that this project, combined with others, will achieve.  Usually this a program or sector objective.  Very often a portfolio of projects will share a common Goal statement.

Step 05: Verify the If/Then Vertical Logic

By definition, each project has this If/Then or cause and effect logic embedded in it.  If we produce certain outcomes under certain conditions, then we can expect certain other outcomes to result. LogFrame forces the team to make this logic explicit, but it does not guarantee a good design.  The validity of the cause and effect logic depends on the quality and experience of the design team.

Step 06: Define the Assumptions Required at Each Level

Assumptions are statements about the uncertainty factors between each level of objectives, external factors over which the project chooses not to exert or does not have control.  This is the external logic of the project. Determine the Assumptions by asking, what conditions must exist in addition to my objective (Activity, Output, Purpose, Goal) in order to achieve the next level? It is important to clarify Assumptions although there is never 100% certainty of success in any project.  However, the lower the uncertainty, the stronger the project design.

Step 07: Define the Objective Verifiable Indicators (OVI) at Purpose, then Output, then Goal Levels

Objectively Verifiable Indicators (OVI) are performance indicators.  They demonstrate results. Begin with the higher order objective and work backwards through the causal chain: Goal then Purpose, then Outputs, then Activities.            Indicators are often stated in terms of Quantity, Quality and Time (and sometimes place and cost).  The act of putting numbers and dates on indicators is called TARGETING.  It is not true that higher order objectives are not measurable.  We may choose not to put targets on them, but Goals, Purposes and Outputs can all be given indicators and targets.         The fewer indicators the team uses the better.  Use only the number of indicators required to clarify what must be accomplished to satisfy the objective stated in the Narrative Summary.

Step 08: Define the Means of Verification

The Means of Verification (MOV) describes the sources of information that will demonstrate what has ben accomplished. If we decide that a survey is needed, then we may need to add some action steps to the Activities List.  If this costs money, we must add this to the budget. The rule is: the indicators you choose for measuring your objectives must be verifiable by some means.  If they are not, find another indicator.

Step 09: Put Costs on the Activities — the Performance Budget

The budget in the LogFrame should be a simple, line item budget for completing the Activities.  Frequently the budget will be followed up by an attachment of a detailed budget spreadsheet.

Step 10:  Consult the Checklist for the Logical Framework

Use the Design Checklist and ensure that your project meets all the requirement of a well-designed LOGFRAME.

Step 11: Review the Logical Framework Design in the Light of Historical Experience with Similar Efforts

Consult other projects or colleagues in the field and compare your design to similar project designs.  This will give you more insight into your own project.

Note: If you need an external reviewer to go through your LogFrame, feel free to write to me at: manu@manumayank.com I will be happy to help.