---

1. Root Cause Analysis (RCA)
Definition: RCA is a structured approach to identifying the fundamental cause of a problem rather than simply treating its symptoms.

• How to Use It:
    1) Identify symptoms or issues.
    2) Trace these symptoms back to the likely root cause.
    3) Validate or confirm the root cause using data or testing.
    4) Develop corrective strategies to fix the underlying cause.
• When to Use It:
    - If issues recur despite initial fixes.
    - In quality management scenarios.
    - When aiming for long-term solutions, not short-term patches.
• Formula-Like Approach:
  
  Code Select Expand
  Problem -> (Why?) -> (Why?) -> (Why?) ...
Stop at the 'deepest' cause that can be acted upon.
You can also apply 5 Whys or a Fishbone Diagram (Ishikawa) as a step-by-step technique to isolate the root cause.
• Example:
  
  Code Select Expand
  Symptoms: Production delays at a factory.
Root Cause Analysis:
1) Delays caused by machine breakdowns.
2) Breakdowns caused by overheated motors.
3) Overheating due to lack of scheduled maintenance.
Long-Term Fix: Implement weekly lubrication + monthly inspection plan.


---

2. Design Thinking
Definition: A human-centered approach to innovation and problem-solving, focusing on empathy with users and iterative prototyping.

• Key Phases (Typical):
    - Empathize: Understand the user's context, pain points, and desires.
    - Define: Frame the core problem in user-centric terms.
    - Ideate: Brainstorm a wide range of possible solutions.
    - Prototype: Quickly build or sketch solutions to gather feedback.
    - Test: Validate ideas with real users and refine as needed.
• When to Use It:
    - Creating user-centric products/services.
    - Complex, unclear challenges requiring fresh perspectives.
    - Driving creativity and innovation across teams.
  
• Formula-Like Representation:
  
  Code Select Expand
  Solution(user) = f(Empathize, Define, Ideate, Prototype, Test)
Where each phase loops back for improvements until the solution aligns with user needs.
• Example:
  
  Code Select Expand
  Scenario: A software company notices low user engagement.
Design Thinking steps:
1) Empathize: Interview users; find they prefer simpler navigation.
2) Define: "Improve the app's navigation flow to reduce confusion."
3) Ideate: Brainstorm multiple UI changes.
4) Prototype: Wireframe a new layout.
5) Test: Users find the revised layout more intuitive; incorporate feedback before final launch.


---

3. Six Thinking Hats
Definition: This is a parallel thinking method developed by Edward de Bono to foster comprehensive viewpoint exploration within a group.

• Hats (Metaphorical):
    - White (facts/data)
    - Red (emotions)
    - Black (risks/caution)
    - Yellow (optimism/benefits)
    - Green (creativity/alternatives)
    - Blue (process control/overview)
  
• How to Use It:
    1) In a group discussion or meeting, participants wear each "hat" in turn.
    2) White Hat: Focus on facts and figures.
    3) Red Hat: Express emotional viewpoints.
    4) Black Hat: Highlight potential pitfalls.
    5) Yellow Hat: Look for optimistic or positive angles.
    6) Green Hat: Suggest creative ideas or solutions.
    7) Blue Hat: Manage the thinking process.
• When to Use It:
    - Making complex decisions with multiple variables.
    - Brainstorming sessions needing diverse perspectives.
    - Enhancing communication and idea generation in teams.
• Mini-Formula:
  
  Code Select Expand
  Decision Quality = Σ(Insights from all Hats)
Collecting different angles systematically leads to more balanced outcomes.
• Example:
  
  Code Select Expand
  Team discussing a marketing campaign:
- White: "Sales data shows a 10% drop in Q2."
- Red: "I'm concerned customers feel disconnected."
- Black: "Budget constraints might limit our reach."
- Yellow: "Opportunity to pivot and tap new digital channels."
- Green: "Let's pilot a social media mini-campaign first."
- Blue: "We have 30 minutes; let's finalize steps based on the hats' input."


---

4. SWOT Analysis
Definition: SWOT stands for Strengths, Weaknesses, Opportunities, Threats. It's a strategic planning framework for assessing internal and external factors that influence success.

• How to Use It:
    1) List Strengths (S): Internal attributes that give an advantage.
    2) List Weaknesses (W): Internal limitations or vulnerabilities.
    3) Identify Opportunities (O): External factors that can be leveraged.
    4) Note Threats (T): External factors that risk project or business goals.
    5) Formulate strategies to capitalize on S & O while addressing W & T.
• When to Use It:
    - Strategic business planning
    - Entering new markets or launching products
    - Competitive analysis
    - Adapting or pivoting existing strategies
• Matrix Representation:
  
  Code Select Expand
           S (internal, positive) | W (internal, negative)
         ------------------------------------------------
         O (external, positive) | T (external, negative)
Focus on synergy between S+O to create advantage, and find ways to mitigate W+T.
• Example:
  
  Code Select Expand
  Company's SWOT:
S: Strong R&D team
W: Limited marketing budget
O: Growing demand for eco-friendly packaging
T: New competitor with aggressive pricing

Strategy: Use R&D (Strength) to develop cost-effective eco-friendly solutions (Opportunity),
while addressing limited marketing budget by targeting niche sustainability-focused campaigns.


---

5. Value Stream Mapping (VSM)
Definition: A Lean method to visually map out how materials and information flow through a process, identifying inefficiencies and waste.

• How to Use It:
    1) Map all steps in the process end-to-end (from supplier to customer).
    2) Identify and categorize wastes (e.g., waiting, excess inventory, rework).
    3) Develop an improved or streamlined process flow that cuts out non-value-added steps.
    4) Implement changes and monitor results.
• When to Use It:
    - In manufacturing, logistics, or service sectors for improved efficiency.
    - Early in process redesign or continuous improvement initiatives.
    - Whenever reducing cycle time, cost, or material usage is a priority.
• Formula-Like Representation:
  
  Code Select Expand
  Total Lead Time = Σ(Processing Time + Waiting Time + Transport Time + Other Wastes)
Value Stream Mapping aims to minimize non-value-added time.

• Example:
  
  Code Select Expand
  A distribution center VSM:
Current: 3 days wait time between receipt and picking, 1 day shipping label backlog.
Future State: Remove manual label printing, integrate with scanning -> reduce lead time by 2 days.


---

Bringing It All Together
Each of these 5 tools offers a unique lens on problem-solving:

[ul]

• Root Cause Analysis (RCA): Drill down to why the issue exists, fix it at the source.
• Design Thinking: Innovate around human-centric insights, prototype quickly, and refine.
• Six Thinking Hats: Foster parallel thinking for richer group decision-making.
• SWOT Analysis: Map out internal strengths & weaknesses vs. external opportunities & threats.
• Value Stream Mapping: Visualize process flows, eliminate waste, and increase efficiency.

[/ul]

By selecting the right approach—or combining several—leaders can address problems holistically and drive effective, sustainable solutions for their teams and organizations.