User:Joie67/issue trees

This is not a Wikipedia article: It is an individual user's work-in-progress page, and may be incomplete and/or unreliable. For guidance on developing this draft, see Wikipedia:So you made a userspace draft.  Find sources: Google (books · news · scholar · free images · WP refs) · FENS · JSTOR · TWL Easy tools: Citation bot (help) | Advanced: Fix bare URLs This page was last edited by [[User:|]] ([[User talk:|talk]] | contribs) 0 seconds ago. (Update timer) Finished writing a draft article? Are you ready to request an experienced editor review it for possible inclusion in Wikipedia? Save your work by pressing the "Publish page" button below, and a button will appear here allowing you to submit your draft for review.

An issue tree, also called a 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.

Issue trees are useful in problem solving to identify the root causes of a problem as well as to identify its potential solutions. They are a popular tool with the strategic consultancies, including McKinsey & Company^[1].

Issue trees have four basic rules^[2]:

1. They consistently answer to "why" or "how"
2. They progress from the key question to the analysis
3. They use a mutually exclusive and collectively exhaustive breakdown
4. They use an insightful breakdown

"Why" trees are diagnostic or root-cause analysis trees; these are sometimes called fault trees^[3]. They answer to a "why" key question by breaking it down into its various dimensions and breaking each dimension into details. They are similar to Ishikawa diagrams although they progress into details as they read from the left to the right. These trees also incorporate the 5 whys approach as they breakdown the key question, each jump to the right corresponding to a level of why.

Issue trees can take a long time to create, sometimes days^[4].