Problem Tree Analysis - Revision history

User at 17:49, 8 December 2022

2022-12-08T17:49:38Z

Show changes

User at 23:10, 27 April 2021

2021-04-27T23:10:13Z

User at 21:50, 27 April 2021

2021-04-27T21:50:16Z

User at 21:48, 27 April 2021

2021-04-27T21:48:17Z

User at 21:16, 27 April 2021

2021-04-27T21:16:07Z

User at 21:12, 27 April 2021

2021-04-27T21:12:00Z

User at 20:44, 27 April 2021

2021-04-27T20:44:16Z

User at 20:38, 27 April 2021

2021-04-27T20:38:19Z

User: Created page with "A '''Problem Tree Analysis''' is a pictorial representation of a problem, its causes and its consequences. This analysis tool helps the project team get a quick glance of how..."

2021-04-27T20:34:12Z

Created page with "A '''Problem Tree Analysis''' is a pictorial representation of a problem, its causes and its consequences. This analysis tool helps the project team get a quick glance of how..."

New page

A '''Problem Tree Analysis''' is a pictorial representation of a problem, its causes and its consequences. This analysis tool helps the project team get a quick glance of how a range of complex issues contribute toward a problem and how this problem branches out into a set of consequences. Both causes and consequences are fitted into the diagram on a hierarchical preference basis.<ref>Definition - What Does Problem Tree Analysis Mean? [https://www.brighthubpm.com/project-planning/118441-problem-tree-a-comprehensive-analysis-tool/ Bright Hub PM]</ref>

@@ Line 12: / Line 12: @@
 [[File:Problem Tree.jpg|400px|Problem Tree Example]]<br />
 source: MSP Guide
 == Variations of Problem Tree<ref>Variations of Problem Tree [http://www.mspguide.org/tool/problem-tree MSP Guide]</ref> ==

← Older revision		Revision as of 21:50, 27 April 2021
Line 2:		Line 2:

	Problem Tree Analysis (also called Situational Analysis or just Problem Analysis) helps to find solutions by mapping out the anatomy of cause and effect around an issue in a similar way to a Mind map, but with more structure.		Problem Tree Analysis (also called Situational Analysis or just Problem Analysis) helps to find solutions by mapping out the anatomy of cause and effect around an issue in a similar way to a Mind map, but with more structure.
		+
		+	A problem tree analysis:<ref>[http://evaluationtoolbox.net.au/index.php?option=com_content&view=article&id=28& Evaluation Toolbox]</ref>
		+	*Helps the planning of a project
		+	*Provides a guide as to the complexity of a problem by identifying the multiple causes
		+	*Identifies particular lines of intervention and other factors that may need to be tackled with complementary projects
		+	*Provides an outline of the project plan, including the activities that need to be undertaken, the goal and the outcomes of the project.

@@ Line 62: / Line 62: @@
 *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.
+*The process of analysis often helps build a shared sense of understanding, purpose and action.

@@ Line 22: / Line 22: @@
-[[File:Cause Effect Problem Tree.png|300px|Cause Effect Problem Tree]]<br />
+[[File:Cause Effect Problem Tree.png|400px|Cause Effect Problem Tree]]<br />
 source: European Commission 2004
@@ Line 34: / Line 34: @@
-[[File:Means Ends Objectives.png|300px|Means Ends Objectives]]<br />
+[[File:Means Ends Objectives.png|400px|Means Ends Objectives]]<br />
 source: European Commission 2004
@@ Line 48: / Line 48: @@
-[[File:Purpose Objective Results.jpg|300px|Purpose Objective Results]]<br />
+[[File:Purpose Objective Results.jpg|400px|Purpose Objective Results]]<br />
 source: European Commission 2004
 This analytical stage is the most difficult and challenging, as it involves synthesising a significant amount of information and making a complex judgement about the best implementation strategy to pursue. In practice a balance has to be found to deal with the different stakeholders interests, political demands and practical constraints. However, the potential merits and difficulties associated with addressing problems in different ways have to be fully scrutinised before any detailed design work is undertaken. Typical questions that should be asked and answered are: can/should we tackle all the problems identified? Should we select just a few? Which interventions are more likely to bring about the desired results? What would be more beneficial for the target groups? Are these interventions sustainable in a long-term? Are the financial means available? Do we have the technical capacity to implement the actions? (for more detailed information on this issue, (see definition of boundaries]). These and other questions, including environmental, social and economic issues as well as policies and the legal framework, will help to rule-out those strategies which cannot be covered in this project, and those which are realistic and will offer the most benefit for those facing the problems.

@@ Line 4: / Line 4: @@
-[[File:Problem Tree.jpg|300px|Problem Tree Example]]<br />
+[[File:Problem Tree.jpg|400px|Problem Tree Example]]<br />
 source: MSP Guide
 == Variations of Problem Tree<ref>Variations of Problem Tree [http://www.mspguide.org/tool/problem-tree MSP Guide]</ref> ==
 *Objective Tree: Following the problem tree analysis, it is possible to rephrase each of the problems into positive desirable outcomes – as if the problem had already been treated, the problem can be turned into an objectives tree. In this way, root causes and consequences are turned into root solutions, and key project or influencing entry points are quickly established. A Force Field analysis (Tool 16) could be a useful next step.
-*Opportunity Tree: Instead of focusing on ‘problems’ it is possible to use the tree to analyse opportunities. This implies changing the initial question from “what is the problem and what are underlying causes” to “what works well and what are underlying causes”. Can be done after Appreciative story telling (Tool 6).
+*Opportunity Tree: Instead of focusing on ‘problems’ it is possible to use the tree to analyse opportunities. This implies changing the initial question from “what is the problem and what are underlying causes” to “what works well and what are underlying causes”. Can be done after Appreciative story telling.

← Older revision		Revision as of 20:44, 27 April 2021
Line 1:		Line 1:
	A '''Problem Tree Analysis''' is a pictorial representation of a problem, its causes and its consequences. This analysis tool helps the project team get a quick glance of how a range of complex issues contribute toward a problem and how this problem branches out into a set of consequences. Both causes and consequences are fitted into the diagram on a hierarchical preference basis.<ref>Definition - What Does Problem Tree Analysis Mean? [https://www.brighthubpm.com/project-planning/118441-problem-tree-a-comprehensive-analysis-tool/ Bright Hub PM]</ref>		A '''Problem Tree Analysis''' is a pictorial representation of a problem, its causes and its consequences. This analysis tool helps the project team get a quick glance of how a range of complex issues contribute toward a problem and how this problem branches out into a set of consequences. Both causes and consequences are fitted into the diagram on a hierarchical preference basis.<ref>Definition - What Does Problem Tree Analysis Mean? [https://www.brighthubpm.com/project-planning/118441-problem-tree-a-comprehensive-analysis-tool/ Bright Hub PM]</ref>
		+
		+	Problem Tree Analysis (also called Situational Analysis or just Problem Analysis) helps to find solutions by mapping out the anatomy of cause and effect around an issue in a similar way to a Mind map, but with more structure.
		+
		+
		+	[[File:Problem Tree.jpg\|300px\|Problem Tree Example]]<br />
		+	source: MSP Guide
		+
		+	== Variations of Problem Tree<ref>Variations of Problem Tree [http://www.mspguide.org/tool/problem-tree MSP Guide]</ref> ==
		+	*Objective Tree: Following the problem tree analysis, it is possible to rephrase each of the problems into positive desirable outcomes – as if the problem had already been treated, the problem can be turned into an objectives tree. In this way, root causes and consequences are turned into root solutions, and key project or influencing entry points are quickly established. A Force Field analysis (Tool 16) could be a useful next step.
		+	*Opportunity Tree: Instead of focusing on ‘problems’ it is possible to use the tree to analyse opportunities. This implies changing the initial question from “what is the problem and what are underlying causes” to “what works well and what are underlying causes”. Can be done after Appreciative story telling (Tool 6).

← Older revision		Revision as of 20:38, 27 April 2021
Line 1:		Line 1:
	A '''Problem Tree Analysis''' is a pictorial representation of a problem, its causes and its consequences. This analysis tool helps the project team get a quick glance of how a range of complex issues contribute toward a problem and how this problem branches out into a set of consequences. Both causes and consequences are fitted into the diagram on a hierarchical preference basis.<ref>Definition - What Does Problem Tree Analysis Mean? [https://www.brighthubpm.com/project-planning/118441-problem-tree-a-comprehensive-analysis-tool/ Bright Hub PM]</ref>		A '''Problem Tree Analysis''' is a pictorial representation of a problem, its causes and its consequences. This analysis tool helps the project team get a quick glance of how a range of complex issues contribute toward a problem and how this problem branches out into a set of consequences. Both causes and consequences are fitted into the diagram on a hierarchical preference basis.<ref>Definition - What Does Problem Tree Analysis Mean? [https://www.brighthubpm.com/project-planning/118441-problem-tree-a-comprehensive-analysis-tool/ Bright Hub PM]</ref>
		+
		+
		+	== See Also ==
		+	[[Six Thinking Hats]]<br />
		+	[[Rätselvermehrung]]<br />
		+	[[Brainstorming]]<br />
		+	[[Metaplan Method]]<br />
		+	[[Mind Mapping]]<br />
		+	[[Bisociation]]<br />
		+	[[SHARP (Structured, Holistic Approach for a Research Proposal)]]<br />
		+
		+
		+	== References ==
		+	<references/>