Difference between revisions of "Problem Tree Analysis"
From Learning and training wiki
(34 intermediate revisions by 6 users not shown) | |||
Line 1: | Line 1: | ||
− | {{Term| | + | {{Term|PROBLEM TREE ANALYSIS|A tool that helps to identify the negative aspects of an existing situation and establish the “cause and effect” relationships between the identified problems.<ref> European Commission, « Aid Delivery Methods : Volume 1 Project Cycle Management Guidelines », March 2004.</ref> |
− | '''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 www.odi.org.uk] (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 9: | Line 9: | ||
* Present issues – rather than apparent, future or past issues – are dealt with and identified; | * 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. | * The process of analysis often helps build a shared sense of understanding, purpose and action. | ||
+ | |||
+ | |||
+ | See also: [[Needs Assessment]]; [[Audience Analysis]]; [[Stakeholder Analysis]]; [[Focus Groups]]}} | ||
{{Tool|Developing a Problem Tree Analysis| | {{Tool|Developing a Problem Tree Analysis| | ||
__NOTOC__ | __NOTOC__ | ||
− | =='''Step By Step<ref>European Commission, « Aid Delivery Methods : Volume 1 Project Cycle Management Guidelines », March 2004, | + | =='''Step By Step<ref>European Commission, « Aid Delivery Methods : Volume 1 Project Cycle Management Guidelines », March 2004, NZAID Tools, “Logical Framework Approach”, [http://nzaidtools.nzaid.govt.nz/logical-framework-approach/annex-2-problem-tree-analysis nzaidtools.nzaid.govt.nz] (22 October, 2009), and Overseas Development Institute (ODI), [http://www.odi.org.uk/RAPID/Tools/Toolkits/Communication/Problem_tree.html www.odi.org.uk] (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 24: | Line 28: | ||
# Copy the problem tree onto a sheet of paper to keep as a record, and distribute (as appropriate) for further comment/ information. | # Copy the problem tree onto a sheet of paper to keep as a record, and distribute (as appropriate) for further comment/ information. | ||
− | 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. | + | 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. |
+ | |||
+ | |||
+ | '''Discussion questions might include''' | ||
+ | * Does this represent the reality? Are the economic, political and socio-cultural dimensions to the problem considered? | ||
+ | * Which causes and consequences are getting better, which are getting worse and which are staying the same? | ||
+ | * What are the most serious consequences? Which are of most concern? What criteria are important to us in thinking about a way forward? | ||
+ | * Which causes are easiest/ most difficult to address? What possible solutions or options might there be? Where could a policy change help address a cause of consequence, or create a solution? | ||
+ | * What decisions have we made, and what actions have we agreed? | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | + | The problem tree can be converted into an objectives tree by rephrasing each of the problems into positive desirable outcomes – as if the problem had 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. | |
− | |||
− | + | '''Key points to remember''' | |
− | * | + | * The quality of output will be determined by who is involved in the analysis and the skills of the [[facilitator]]. Involving [[stakeholder]] representatives with appropriate knowledge and skills is critical. |
− | * | + | * 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 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 | + | =='''Job Aid'''== |
+ | [[Image: pdf.png]] [[Media:Toolkit_Template_Problem_Tree.pdf|Problem Tree Analysis]] | ||
− | |||
− | [[ | + | {{Example|Example of Problem Tree Analysis |
+ | |[[image:pdf.png]] | ||
+ | [[Media:ProblemTreeAnalysisExample.pdf|Example of Problem Tree Analysis]] developed by Overseas Development Institute (ODI), analyzing the outbreak of cholera in Kingstown.}} | ||
− | |||
− | |||
− | {{ | + | {{Addlink|Below you have a list of selected web-sites where you can find additional information about Problem Tree Analysis.}} |
− | }} | + | {|border=1; width= 100% |
− | {|border=1 | + | !Link |
− | + | !Content | |
− | + | ||
|- | |- | ||
− | |[ | + | |[http://assets.sportanddev.org/downloads/problem_tree_analysis.pdf MDF Tool: Problem Tree Analysis] |
− | | | + | |Problem Tree Analysis explaned by MDF with a demonstration case |
|- | |- | ||
− | |[ | + | |[http://www.idrc.ca/en/ev-132998-201-1-DO_TOPIC.html IDRC/Problem Tree] |
− | | | + | |A chapter of the book ''SAS2: A Guide to Collaborative Inquiry and Social Engagement'', available on the website of International Development Research Center, presenting the Problem Tree Process with an example of a demonstration case in India |
|} | |} | ||
Latest revision as of 10:09, 3 October 2013
PROBLEM TREE ANALYSIS |
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]
|
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.
|
Job Aid
Example of Problem Tree Analysis |
Example of Problem Tree Analysis developed by Overseas Development Institute (ODI), analyzing the outbreak of cholera in Kingstown. |
Web Resources |
Below you have a list of selected web-sites where you can find additional information about Problem Tree Analysis. |
Link | Content |
---|---|
MDF Tool: Problem Tree Analysis | Problem Tree Analysis explaned by MDF with a demonstration case |
IDRC/Problem Tree | A chapter of the book SAS2: A Guide to Collaborative Inquiry and Social Engagement, available on the website of International Development Research Center, presenting the Problem Tree Process with an example of a demonstration case in India |
References
- ↑ European Commission, « Aid Delivery Methods : Volume 1 Project Cycle Management Guidelines », March 2004.
- ↑ Overseas Development Institute (ODI), www.odi.org.uk (22 October, 2009).
- ↑ European Commission, « Aid Delivery Methods : Volume 1 Project Cycle Management Guidelines », March 2004, NZAID Tools, “Logical Framework Approach”, nzaidtools.nzaid.govt.nz (22 October, 2009), and Overseas Development Institute (ODI), www.odi.org.uk (22 October, 2009)