Let's take a look at more root cause analysis techniques

Root cause analysis (RCA) is a technique used to identifies underlying reasons: Each RCA method is suited to different problems; Here are some major methods of RCA
Fishbone diagram (Ishikawa diagram): a visualization using a fish skeleton shaped diagram to show a problems's potential causes and cause categories
5 Whys: Just ask "why" and whatever the answer is, ask the "why" of that, 5x
Fault tree analysis (FTA): a deductive, top-down approach using a visual diagram to identify what could lead to a particular problem or failure
Failure modes and effects analysis (FMEA): Identifies potential failures and assesses their consequences to prioritize them
Statistical process control (SPC): use statistics and control charts to hypothesize root causes of a problem
Pareto analysis: a method that prioritizes potential root causes of a problem based on their frequency or impact
Causal factor trees: uses a tree diagram to hypothesize causes and contributing factors to a problem

Failure Modes and Effects Analysis (FMEA)

Step 1: State what is to be analyzed: Processes, products, systems, specific functions, etc. - FMEA is flexible!; Process: registering for classes; Product: car; System: UA Little Rock (or any university); Specific function: Drip hot water over coffee grounds (what else?)
Step 2: State the failure modes: Hot water dispenser arm not above coffee grounds (what else?); Let's list a few for each example above
Work individually or in groups of two
Step 3: State the effects of the failure mode: No coffee appears in cup (what else?); Let's list a few for each example above
Step 4: Evaluate the severity of each effect: Typically, use official AIAG scale; Do it for a few
Step 5: Determine cause(s) of each effect: User forgot to move arm over cup (what else?); Do it for a few
Step 6: Rate the occurrence number: Typically, use official AIAG scale; How to rate the coffee pot problem?; Do it for some of the effects identified above for other problems
Step 7: Find the detection ranking (rate the detectability) of the cause: Detection rankings from AIAG are common; What is the detection ranking for causes of the coffee pot problem?; What are the detection rankings for causes in some of the effects identified above
Step 8: Calculate the Risk Priority Number (RPN): Just multiply severity x occurrence x detection; What RPN do we get for the coffee maker problem?; How about for some of the other problems?
Step 9: Recommend actions: What do you suggest for the coffee maker problem?; We could play what they said; What do you recommend for other problems?

5 Whys

: Simple technique for finding root causes; Just keep asking "why?" until you get the root cause; Getting the root cause makes it possible to fix it; This cures the problem itself rather than just covering it up
Some steps in 5 whys: Clearly identify the problem to be understood; Ask "Why?", and then ask "why?" about the answer, repeating 5 times; Document each "Why?" and its answer.; Keep going until the root cause is found. Might not be exactly 5x
Some benefits: Gets to the root cause; reduces fixation on the more obvious symptoms; It is simple and straightforward, usable by anyoneo; Step by step approach helps to systematically and thoroughly examine a problem; Root cause identification enables fixing a problem in a deeper and more effective way
Some limitations: Might not work on complex problems with multiple causes; Depends on the users having sufficient information, expertise and experience on the system and problem
Conclusion: The 5 Whys is a useful technique for identifying the root cause of a problem and developing a plan for addressing it; Simple structure makes it easy to use; Find a useful or interesting fact about 5 whys; How applicable is 5 whys to the problem of interest?

Slide Title: Fault Tree Analysis Slide Content: 1. Introduction: o Fault Tree Analysis (FTA) is a structured and systematic method for identifying and analyzing the potential causes of a failure or accident. o It involves creating a visual representation of the interrelationships between different components, events, and conditions that can contribute to a failure or accident. 2. Components of Fault Tree Analysis: o Gates: Gates represent logical relationships between events, such as AND, OR, and NOT. They are used to represent the interrelationships between events and conditions. o Events: Events represent specific occurrences or conditions that can contribute to a failure or accident. Events can be either basic events (occurrences that cannot be further decomposed) or intermediate events (occurrences that can be decomposed into other events). o Cut sets: Cut sets are groups of events that, if they all occur, will result in the top event (the failure or accident being analyzed). Cut sets represent the minimum set of conditions or events required to cause the top event. o Event trees: Event trees are diagrams that represent the progression of events from the initial occurrence of a failure or accident to the ultimate consequences. 3. Steps in the Fault Tree Analysis Process: o Define the top event: Start by defining the top event, which is the failure or accident you want to analyze. o Identify potential causes: Identify all of the potential causes or events that could contribute to the top event. o Create a fault tree diagram: Use gates, events, and connecting lines to create a fault tree diagram that represents the interrelationships between the potential causes and events. o Evaluate risk: Evaluate the risk associated with each potential cause and event. o Develop strategies for managing risk: Develop strategies for managing risk based on the results of the analysis. 4. Benefits of Fault Tree Analysis: o FTA provides a structured and systematic approach to analyzing and understanding the causes of failures or accidents. o It helps to identify areas for improvement, evaluate risk, and develop strategies for managing risk. o FTA can be used to evaluate complex systems and to understand how different components, events, and conditions can interact to contribute to a failure or accident. o By using visual representations, FTA helps to communicate complex information and to engage stakeholders in the process of risk management. 5. Limitations of Fault Tree Analysis: o FTA can be time-consuming and resource-intensive, especially for large or complex systems. o It may be limited by the information and data available, as well as the expertise and experience of the people using it. o FTA may also be limited by the assumption of independence between events, which may not always be accurate in real-world situations. 6. Conclusion: o Fault Tree Analysis (FTA) is a valuable tool for identifying and analyzing the potential causes of failures or accidents. o By using gates, events, and cut sets, FTA provides a structured and systematic approach to understanding the interrelationships between different components, events, and conditions. o By using visual representations and engaging stakeholders in the process, FTA helps to facilitate communication and to support informed decision-making. o However, like any analysis method, it has limitations and may not be suitable for all types of systems and problems. Slide Title: Causal Factor Trees in Root Cause Analysis Slide Content: 1. Introduction: o Root cause analysis (RCA) is a systematic approach to identifying the underlying causes of a problem or failure. o One method of RCA that can be used to identify root causes is the Causal Factor Tree (CFT). o A CFT is a visual representation that graphically depicts the relationships between symptoms and underlying causes. 2. Steps in the CFT Process: o Identify the problem: Start by defining the problem or failure that you want to analyze. o Identify symptoms: Identify the symptoms or observable effects of the problem. o Develop a CFT: Create a CFT that shows the relationships between the symptoms and the underlying causes. o Map out the relationships: Map out the relationships between the symptoms and the underlying causes. Start with the symptoms and work your way down to the root causes. o Evaluate root causes: Evaluate the root causes to determine which are the most significant and which require immediate attention. o Develop recommendations: Develop recommendations for addressing the root causes and improving the system to prevent future problems. 3. Benefits of CFTs in RCA: o CFTs provide a structured and systematic approach to identifying the underlying causes of a problem. o They help to identify areas for improvement and to evaluate the significance of each root cause. o CFTs can be used to evaluate complex systems and to understand how different components, events, and conditions can interact to contribute to a failure. o By using visual representations, CFTs help to communicate complex information and to engage stakeholders in the process of RCA. 4. Limitations of CFTs in RCA: o CFTs can be time-consuming and resource-intensive, especially for large or complex systems. o They may be limited by the information and data available, as well as the expertise and experience of the people using them. o CFTs may also be limited by the assumption of causality, which may not always be accurate in real-world situations. 5. Conclusion: o Causal Factor Trees (CFTs) are a valuable tool for Root Cause Analysis (RCA). o By using a structured and systematic approach, CFTs provide a proactive method for identifying root causes and developing recommendations for improvement. o By using visual representations and engaging stakeholders in the process, CFTs help to facilitate communication and to support informed decision-making. o However, like any analysis method, CFTs have limitations and may not be suitable for all types of problems and systems.

Let's Take a Look at Process Mapping

For each:: check the web for an interesting fact to share; let's discuss: could it be used to improve the IT system in question?
Process mapping: using some technique for creating visual representations of business processes
Here are some important process mapping visualization methods
Flowcharts: diagram using graphical symbols for process steps, information flow & decision points
Swimlane diagrams: chart visualizing separate columns for different roles or departments (actors)
Gantt charts: bar graph showing process tasks, timeline, and (to some extent) dependencies
Activity network diagrams: graph showing the order and interdependence of tasks in a project
Block diagrams: Visualization showing major system parts or functions as blocks connected by lines for relationships
Business Process Model and Notation (BPMN): బిజినెస్ ప్రక్రియ మోడల్ మరియు నాటేషన్ (BPMN): BPMN ప్రక్రియలను వీడియోగా ప్రతిన
Event-Driven Process Chain (EPC): visualization focusing on the flow of events and their relationships in a business process
Data flow diagram (DFD): visual representation of the flow of data within a system
State transition diagram: visually represents the different states an object can be in, plus the events triggering change from one state to another

Data Flow Diagrams

Visualizations of the movement of data (or things)
They show how organizations' processes transform data (or other things)
They help understand complex systems, find improvement possibilities, and communicate system structure

Data flow diagrams have external entities: Sources or destinations of data, such as customers, suppliers, or outside systems; Processes: actions that transform data, such as data entry or calculations; Data stores, such as databases and files; Data flows: arrows showing the flow of data among processes, data stores, and external entities
DFDs and "levels": A DFD can be expanded into multiple "levels," each providing a more detailed view of the system; The top level provides a high-level view of the system; Lower levels provide progressively more detail on the system or parts of the system; Each high level process can be detailed more with a lower level DFD
Data flow diagram advantages: DFDs provide clear visualizations of the processes and their data flows; They help to identify bottlenecks and inefficiencies in the processes; They help communicate among parties involved; They help system analysis and improvement planning systematically consider all the possibilities
Conclusion: Visualization that promotes understanding, communication, and systematic analysis for improvement; Find a useful or interesting fact about DFDs; How applicable are DFDs to the problem of interest?