Logical framework approach

This article is about the management tool. For the automated theorem proving approach, see logical framework.

The Logical Framework Approach (LFA) is a management tool mainly used for designing, monitoring, and evaluating international development projects. Variations of this tool are known as Goal Oriented Project Planning (GOPP) or Objectives Oriented Project Planning (OOPP).

Background

The Logical Framework Approach was developed in 1969 for the U.S. Agency for International Development (USAID). It is based on a worldwide study by Leon J. Rosenberg, a principal of Fry Consultants Inc.[1] From 1970 to 1971, 30 countries adopted the method under the guidance of Practical Concepts Incorporated, founded by Rosenberg.[2]

It has been widely used by multilateral donor organizations, such as AECID, GIZ, SIDA, NORAD, DFID, SDC, UNDP, EC and the Inter-American Development Bank. Some non-governmental organizations offer LFA training to ground-level field staff.[3] It has also gained popularity in the private sector. Terry Schmidt has been active in extending the LFA.

The Logical Framework Approach continues to gain adherents, though it is a management tool invented more than 40 years ago. This phenomenon has been the subject of several doctoral theses.

In the 1990s, it was often mandatory for aid organizations to use the LFA method in their project proposals. However, its use has become increasingly optional in recent years.

The Logical Framework Approach is sometimes confused with Logical Framework (LF or Log frame). The Logical Framework Approach is a project design methodology, whereas the Logical Frame is a document.

Description

The Logical Framework takes the form of a four-by-four project table. The four rows describe four different types of events that take place as a project is implemented: Activities, Outputs, Purpose and Goal (from bottom to top on the left hand side — see EC web site under external links). The four columns provide different types of information about the events in each row. The first column is used to provide a Narrative description of the event. The second column lists one or more Objectively Verifiable Indicators (OVIs) of these events taking place. The third column describes the Means of Verification (MoV) where information will be available on the OVIs, and the fourth column lists the Assumptions. Assumptions are external factors that could have an influence, whether positive or negative, on the events described in the narrative column. The list of assumptions should include the factors that have a potential impact on the success of the project, but which cannot be directly controlled by the project or program managers. In some cases these may include what could be killer assumptions, which if proved wrong will have major negative consequences for the project. A good project design should be able to substantiate its assumptions, especially those with a high potential to have a negative impact.

Temporal logic model

The core of the Logical Framework is the "temporal logic model" that runs through the matrix. This takes the form of a series of connected propositions:

These are viewed as a hierarchy of hypotheses, with the project or program manager sharing responsibility with higher management for the validity of hypotheses beyond the output level. Thus, Rosenberg brought the essence of scientific method to non-scientific endeavors.

The "Assumptions" column is important in clarifying the extent to which the project or program objectives depend on external factors, and greatly clarify "force majeure" — of particular interest when the Canadian International Development Agency (CIDA) at least briefly used the LFA as the essence of contracts.

The LFA is also used in other contexts, both personal and corporate. When developed within an organization, it can articulate a common interpretation of the objectives of a project and how they will be achieved. The indicators and means of verification force clarifications as one would for a scientific endeavor, as in "you haven't defined it until you say how you will measure it." Tracking progress against carefully defined output indicators provides a clear basis for monitoring progress; verifying purpose and goal level progress then simplifies evaluation. Given a well constructed logical framework, an informed skeptic and a project advocate should be able to agree on exactly what the project attempts to accomplish, and how likely it is to succeed—in terms of programmatic (goal-level) as well as project (purpose-level) objective.

One of its purposes in its early uses was to identify the span of control of 'project management'. In some countries with less than perfect governance and managerial systems, it became an excuse for failure. Externally sourced technical assistance managers were able to say that all activities foreseen have been implemented and all required outputs produced, but because of the sub-optimal systems in the country, which are beyond the control of the project's management, the purpose(s) have not been achieved and so the goal has not been attained.

Handbooks

The Logical Framework Approach, Handbook for objectives-oriented planning, Fourth edition, NORAD, 1999, ISBN 82-7548-160-0.

Strategic Project Management Made Simple: Practical Tools for Leaders and Teams, by Terry Schmidt. (Wiley, 2009) ISBN 978-0-470-41158-2

The Logical Framework: A Manager's Guide to a Scientific Approach to Design and Evaluation, by Practical Concepts, Incorporated, 1979

References

  1. ↑ Final Report, Contract csd-2510, July 24, 1970
  2. ↑ Practical Concepts Incorporated, "Guidelines for Teaching Logical Framework Concepts"
  3. ↑ Fernando, Renuka. "Getting on With It: Monitoring and Evaluation in the Third Sector" Risk and Regulation. London School of Economics. Winter 2012.

External links