Problem Tree

You cannot fix a problem you have not properly understood. Logical Framework Analysis starts every project with Problem Analysis — and its main tool for that is the Problem Tree.

The workbook's definition: the Problem Tree "visually maps out the cause-and-effect relationships surrounding the central problem." Picture a tree. The trunk is the core problem. The roots below are its causes. The branches above are its effects.

A Problem Tree does three jobs at once. It clearly defines the central issue, it identifies the underlying causes that need fixing, and it shows the wider consequences the problem has on the community or environment.

By breaking a problem into causes and effects this way, project planners get a clear picture of how big and how tangled the problem really is — and that picture becomes the foundation for everything the project designs afterward.

The Problem Tree is the first step in the Logical Framework Analysis process (Chapter 4, section 4.2.2, Problem Analysis), feeding directly into the next step, Objective Analysis:

1. Problem Tree (Problem Analysis) — map the central problem, its causes (roots) and its effects (branches).
2. Objective Tree (Objective Analysis) — mirror the same tree, but reframe every problem as a positive, solution-oriented objective.

Because the Objective Tree is built by directly flipping the Problem Tree, any gap or error in the Problem Tree carries straight through to the objectives that follow. This is why the workbook treats Problem Analysis as the necessary first step — a project cannot move to setting SMART objectives until the causes and effects of the core problem are properly mapped.

Illustrative case; figures are made up.

An NPO wants to address poor school attendance in a Rajasthan district. Instead of jumping to solutions, it first builds a Problem Tree:

Only after mapping this Problem Tree does the NPO move to Objective Analysis — reframing "long walking distance" into an objective such as reducing average distance to under 2 km, which later becomes a measurable, SMART project objective.

Had the NPO skipped the Problem Tree and gone straight to building toilets, it might have missed that the 4 km walking distance was the bigger driver of absence.

Chapter 4 (Understanding Logic Model in Social Programs for Social Impact Assessment), section 4.2.2 (Problem Analysis), defines the Problem Tree and its three functions. Section 4.2.3 immediately builds the Objective Tree on top of it. Expect a question asking which LFA step comes first, Problem Analysis or Objective Analysis, and what tool each step uses.

• Problem Tree comes before Objective Tree — Problem Analysis is step one; Objective Analysis is step two.
• Roots are causes; branches are effects. A question may test which half of the tree a given fact belongs to.
• The Problem Tree's job is to understand the problem, not to propose solutions — solutions belong to the later Alternatives Analysis step.
• Do not confuse the Problem Tree with a Theory of Change, which maps a pathway from activities to long-term change, not a single problem's causes and effects.