Difference between revisions of "Problem Tree Analysis"
From Learning and training wiki
Line 2: | Line 2: | ||
− | '''Why to use it?'''<ref> [http://www.odi.org.uk/RAPID/Tools/Toolkits/Communication/Problem_tree.html](22 October, 2009).</ref> | + | '''Why to use it?'''<ref> [Overseas Development Institute (ODI), http://www.odi.org.uk/RAPID/Tools/Toolkits/Communication/Problem_tree.html](22 October, 2009).</ref> |
* The problem can be broken down into manageable and definable chunks. This enables a clearer prioritization of factors and helps focus objectives; | * The problem can be broken down into manageable and definable chunks. This enables a clearer prioritization of factors and helps focus objectives; | ||
* There is more understanding of the problem and its often interconnected and even contradictory causes. This is often the first step in finding win-win solutions; | * There is more understanding of the problem and its often interconnected and even contradictory causes. This is often the first step in finding win-win solutions; | ||
Line 14: | Line 14: | ||
__NOTOC__ | __NOTOC__ | ||
=='''Step By Step<ref>European Commission, « Aid Delivery Methods : Volume 1 Project Cycle Management Guidelines », March 2004, and NZAID Tools, “Logical Framework Approach”, http://nzaidtools.nzaid.govt.nz/logical-framework-approach/annex-2-problem-tree-analysis (22 October, 2009)</ref>'''== | =='''Step By Step<ref>European Commission, « Aid Delivery Methods : Volume 1 Project Cycle Management Guidelines », March 2004, and NZAID Tools, “Logical Framework Approach”, http://nzaidtools.nzaid.govt.nz/logical-framework-approach/annex-2-problem-tree-analysis (22 October, 2009)</ref>'''== | ||
− | The problem tree should be developed as a participatory group activity. 6 to 8 people is often a good group size. It is important to ensure that groups are structured in ways that enable particular viewpoints, especially those of the less powerful, to be expressed. | + | The problem tree should be developed as a participatory group activity. 6 to 8 people is often a good group size. It is important to ensure that groups are structured in ways that enable particular viewpoints, especially those of the less powerful, to be expressed. |
#Brainstorm problems and identify the focal problem as an individual starter problem. Write it on a card or “Post-it”. This first step can either be completely open (no pre-conceived notions as to what stakeholder’s priority concerns/ problems might be), or more directed, through specifying a “known” high order problem or objective based on preliminary analysis of existing information and initial stakeholder consultations. | #Brainstorm problems and identify the focal problem as an individual starter problem. Write it on a card or “Post-it”. This first step can either be completely open (no pre-conceived notions as to what stakeholder’s priority concerns/ problems might be), or more directed, through specifying a “known” high order problem or objective based on preliminary analysis of existing information and initial stakeholder consultations. | ||
Line 41: | Line 41: | ||
* It may be best to run separate problem analysis workshops with different stakeholder groups. | * It may be best to run separate problem analysis workshops with different stakeholder groups. | ||
* The process is as important as the product and should be seen as a learning experience and an opportunity for different views and interests to be expressed. | * The process is as important as the product and should be seen as a learning experience and an opportunity for different views and interests to be expressed. | ||
− | * The problem tree should be a valid but simple representation of the current negative situation. It cannot (and should not) contain or explain the complexities of every identifiable cause-effect relationship. | + | * The problem tree should be a valid but simple representation of the current negative situation. It cannot (and should not) contain or explain the complexities of every identifiable cause-effect relationship.}} |
− | + | ||
=='''Job Aids'''== | =='''Job Aids'''== |
Revision as of 17:10, 27 October 2009
Problem Tree Analysis |
Problem Tree Analysis is a tool that helps to identify the negative aspects of an existing situation and establish the “cause and effect” relationships between the identified problems.[1] |
Why to use it?[2]
- The problem can be broken down into manageable and definable chunks. This enables a clearer prioritization of factors and helps focus objectives;
- There is more understanding of the problem and its often interconnected and even contradictory causes. This is often the first step in finding win-win solutions;
- It identifies the constituent issues and arguments, and can help establish who and what the political actors and processes are at each stage;
- It can help establish whether further information, evidence or resources are needed to make a strong case, or build a convincing solution;
- Present issues – rather than apparent, future or past issues – are dealt with and identified;
- The process of analysis often helps build a shared sense of understanding, purpose and action.
Developing a Problem Tree Analysis |
Step By Step[3]The problem tree should be developed as a participatory group activity. 6 to 8 people is often a good group size. It is important to ensure that groups are structured in ways that enable particular viewpoints, especially those of the less powerful, to be expressed.
The heart of the exercise is the discussion, debate and dialogue that is generated as factors are arranged and re-arranged, often forming sub-dividing roots and branches.[4]
The problem tree can be converted into an objectives tree by rephrasing each of the problems into positive desirable outcomes – as if the problem has already been treated. In this way, root causes and consequences are turned into root solutions, and key project or influencing entry points are quickly established.[6]
|
Job Aids
References
- ↑ European Commission, « Aid Delivery Methods : Volume 1 Project Cycle Management Guidelines », March 2004.
- ↑ [Overseas Development Institute (ODI), http://www.odi.org.uk/RAPID/Tools/Toolkits/Communication/Problem_tree.html](22 October, 2009).
- ↑ European Commission, « Aid Delivery Methods : Volume 1 Project Cycle Management Guidelines », March 2004, and NZAID Tools, “Logical Framework Approach”, http://nzaidtools.nzaid.govt.nz/logical-framework-approach/annex-2-problem-tree-analysis (22 October, 2009)
- ↑ Overseas Development Institute (ODI), http://www.odi.org.uk/RAPID/Tools/Toolkits/Communication/Problem_tree.html (22 October, 2009)
- ↑ European Commission, « Aid Delivery Methods : Volume 1 Project Cycle Management Guidelines », March 2004, and NZAID Tools, “Logical Framework Approach”, http://nzaidtools.nzaid.govt.nz/logical-framework-approach/annex-2-problem-tree-analysis (22 October, 2009) [Overseas Development Institute (ODI), http://www.odi.org.uk/RAPID/Tools/Toolkits/Communication/Problem_tree.html](22 October, 2009).
- ↑ [Overseas Development Institute (ODI), http://www.odi.org.uk/RAPID/Tools/Toolkits/Communication/Problem_tree.html](22 October, 2009).
- ↑ European Commission, « Aid Delivery Methods : Volume 1 Project Cycle Management Guidelines », March 2004, and NZAID Tools, “Logical Framework Approach”, [1](22 October, 2009).