Jump to content

Issue tree

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by Biogeographist (talk | contribs) at 14:04, 6 October 2018 (added citation templates, Template:InfoMaps). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

An issue tree showing how a company can increase profitability: A profitability tree is an example of an issue tree. It looks at different ways in which a company can increase its profitability. Starting from the key question on the left, it breaks it down between revenues and costs, and break these down into further details.

An issue tree, also called logic tree, is a graphical breakdown of a question that dissects it into its different components vertically and that progresses into details as it reads to the right.[1]: 47 

Issue trees are useful in problem solving to identify the root causes of a problem as well as to identify its potential solutions. They also provide a reference point to see how each piece fits into the whole picture of a problem.[2]

There are two types of issue trees, diagnostic ones and solution ones, according to professor of strategy Arnaud Chevallier.[3]

Diagnostic trees break down a "why" key question, identifying all the possible root causes for the problem. Solution trees break down a "how" key question, identifying all the possible alternatives to fix the problem.

Four basic rules can help ensure that issue trees are optimal, according to Chevallier:[3]

  1. Consistently answer a "why" or a "how" question
  2. Progress from the key question to the analysis as it moves to the right
  3. Have branches that are mutually exclusive and collectively exhaustive (MECE)
  4. Use an insightful breakdown

The requirement for issue trees to be collectively exhaustive implies that divergent thinking is a critical skill.[4]

See also

References

  1. ^ Chevallier, Arnaud (2016). Strategic thinking in complex problem solving. Oxford; New York: Oxford University Press. doi:10.1093/acprof:oso/9780190463908.001.0001. ISBN 9780190463908. OCLC 940455195.
  2. ^ "Strategy survival guide: Issue trees". interactive.cabinetoffice.gov.uk. London: Prime Minister's Strategy Unit. July 2004. Archived from the original on 2012-02-17. Retrieved 2018-10-06. {{cite web}}: Invalid |ref=harv (help) Also available in PDF format.
  3. ^ a b Chevallier, Arnaud (2 July 2010). "Build issue trees: diagnosis trees and solution trees". powerful-problem-solving.com. Retrieved 2018-10-06. {{cite web}}: Invalid |ref=harv (help) See also: Chevallier, Arnaud (14 December 2010). "Be insightful". powerful-problem-solving.com. Retrieved 2018-10-06. {{cite web}}: Invalid |ref=harv (help)
  4. ^ Chevallier, Arnaud (6 July 2010). "Diverge effectively in your thinking". powerful-problem-solving.com. Retrieved 2018-10-06. {{cite web}}: Invalid |ref=harv (help)

Further reading

  • Chevallier, Arnaud (11 April 2011). "Don't get lost in the terminology". powerful-problem-solving.com. Retrieved 2018-10-06. Issue trees, issue maps, logic trees, how trees, why trees, diagnostic trees, solution trees, decision trees, fact trees, hypothesis trees... How should you call your trees?... Call your tree what you want it to do. {{cite web}}: Invalid |ref=harv (help)
  • Chevallier, Arnaud (19 February 2011). "Use your issue tree as a decision tree". powerful-problem-solving.com. Retrieved 2018-10-06. {{cite web}}: Invalid |ref=harv (help)
  • Culmsee, Paul; Awati, Kailash (2013) [2011]. "Visualising complexity". The heretic's guide to best practices: the reality of managing complex problems in organisations. Bloomington: iUniverse, Inc. pp. 159–167. ISBN 9781462058549. OCLC 767703320. {{cite book}}: Invalid |ref=harv (help)