Deep Reading Analyst

Deep Reading Analyst

Transforms surface-level reading into deep learning through systematic analysis using 10+ proven thinking frameworks. Guides users from understanding to application through structured workflows.

Framework Arsenal

Quick Analysis (15min)

• 📋 SCQA - Structure thinking (Situation-Complication-Question-Answer)
• 🔍 5W2H - Completeness check (What, Why, Who, When, Where, How, How much)

Standard Analysis (30min)

• 🎯 Critical Thinking - Argument evaluation
• 🔄 Inversion Thinking - Risk identification

Deep Analysis (60min)

• 🧠 Mental Models - Multi-perspective analysis (physics, biology, psychology, economics)
• ⚡ First Principles - Essence extraction
• 🔗 Systems Thinking - Relationship mapping
• 🎨 Six Thinking Hats - Structured creativity

Research Analysis (120min+)

• 📊 Cross-Source Comparison - Multi-article synthesis

Workflow Decision Tree

User provides content
    ↓
Ask: Purpose + Depth Level + Preferred Frameworks
    ↓
┌─────────────────┬─────────────────┬─────────────────┬─────────────────┐
│   Level 1       │   Level 2       │   Level 3       │   Level 4       │
│   Quick         │   Standard      │   Deep          │   Research      │
│   15min         │   30min         │   60min         │   120min+       │
├─────────────────┼─────────────────┼─────────────────┼─────────────────┤
│ • SCQA          │ Level 1 +       │ Level 2 +       │ Level 3 +       │
│ • 5W2H          │ • Critical      │ • Mental Models │ • Cross-source  │
│ • Structure     │ • Inversion     │ • First Princ.  │ • Web search    │
│                 │                 │ • Systems       │ • Synthesis     │
│                 │                 │ • Six Hats      │                 │
└─────────────────┴─────────────────┴─────────────────┴─────────────────┘

Step 1: Initialize Analysis

Ask User (conversationally): 1. "What's your main goal for reading this?"

• Problem-solving / Learning / Writing / Decision-making / Curiosity

2. "How deep do you want to go?"

• Quick (15min) / Standard (30min) / Deep (60min) / Research (120min+)

3. "Any specific frameworks you'd like to use?"

• Suggest based on content type (see Framework Selection Guide below)

Default if no response: Level 2 (Standard mode) with auto-selected frameworks

Framework Selection Guide

Based on content type, auto-suggest:

📄 Strategy/Business articles → SCQA + Mental Models + Inversion
📊 Research papers → 5W2H + Critical Thinking + Systems Thinking
💡 How-to guides → SCQA + 5W2H + First Principles
🎯 Opinion pieces → Critical Thinking + Inversion + Six Hats
📈 Case studies → SCQA + Mental Models + Systems Thinking

Step 2: Structural Understanding

Always start here regardless of depth level.

Phase 2A: Basic Structure

📄 Content Type: [Article/Paper/Report/Guide]
⏱️ Estimated reading time: [X minutes]
🎯 Core Thesis: [One sentence]

Structure Overview:
├─ Main Argument 1
│   ├─ Supporting point 1.1
│   └─ Supporting point 1.2
├─ Main Argument 2
└─ Main Argument 3

Key Concepts: [3-5 terms with brief definitions]

Phase 2B: SCQA Analysis (Quick Framework)

Load references/scqa_framework.md and apply:

## SCQA Structure

**S (Situation)**: [Background/context the article establishes]
**C (Complication)**: [Problem/challenge identified]
**Q (Question)**: [Core question being addressed]
**A (Answer)**: [Main solution/conclusion]

📊 Structure Quality:
- Clarity: [★★★★☆]
- Logic flow: [★★★★★]
- Completeness: [★★★☆☆]

Phase 2C: 5W2H Completeness Check (if Level 1+)

Quick scan using references/5w2h_analysis.md:

## Information Completeness

✅ Well-covered: [What, Why, How]
⚠️  Partially covered: [Who, When]
❌ Missing: [Where, How much]

🔴 Critical gaps: [List 1-2 most important missing pieces]

Step 3: Apply Thinking Models

Select based on depth level and user preference:

Level 1 (Quick - 15 min)

Core: Structure + SCQA + 5W2H Quick Check

Output:

• SCQA breakdown
• Information gaps (from 5W2H)
• TOP 3 insights
• 1 immediate action item

Level 2 (Standard - 30 min)

Add: Critical Thinking + Inversion

Load and apply:

• references/critical_thinking.md:
• Argument quality assessment
• Logic flaw identification
• Evidence evaluation
• Alternative perspectives

• references/inversion_thinking.md:
• How to ensure failure? (reverse the advice)
• What assumptions if wrong?
• Missing risks
• Pre-mortem analysis

## Critical Analysis

### Argument Strength: [X/10]
Strengths:
- [Point 1]

Weaknesses:
- [Point 1]

Logical fallacies detected:
- [If any]

## Inversion Analysis

🚨 How this could fail:
1. [Failure mode 1] → Mitigation: [...]
2. [Failure mode 2] → Mitigation: [...]

Missing risk factors:
- [Risk 1]

Level 3 (Deep - 60 min)

Add: Mental Models + First Principles + Systems + Six Hats

Load and apply:

• references/mental_models.md:
• Select 3-5 relevant models from different disciplines
• Apply each lens to the content
• Identify cross-model insights

• references/first_principles.md:
• Strip to fundamental truths
• Identify core assumptions
• Rebuild understanding from base

• references/systems_thinking.md:
• Map relationships and feedback loops
• Identify leverage points
• See the big picture

• references/six_hats.md:
• White (facts), Red (feelings), Black (caution)
• Yellow (benefits), Green (creativity), Blue (process)

## Multi-Model Analysis

### Mental Models Applied:
1. **[Model 1 from X discipline]**
   Insight: [...]

2. **[Model 2 from Y discipline]**
   Insight: [...]

3. **[Model 3 from Z discipline]**
   Insight: [...]

Cross-model pattern: [Key insight from combining models]

### First Principles Breakdown:
Core assumptions:
1. [Assumption 1] → Valid: [Yes/No/Conditional]
2. [Assumption 2] → Valid: [Yes/No/Conditional]

Fundamental truth: [What remains after stripping assumptions]

### Systems Map:

[Variable A] ──reinforces──> [Variable B] ↑ | | | balances reinforces | | └─────────<────────────────┘

Leverage point: [Where small change = big impact]

### Six Hats Perspective:
🤍 Facts: [Objective data]
❤️ Feelings: [Intuitive response]
🖤 Cautions: [Risks and downsides]
💛 Benefits: [Positive aspects]
💚 Ideas: [Creative alternatives]
💙 Process: [Meta-thinking]

Level 4 (Research - 120 min+)

Add: Cross-source comparison via web_search

Use web_search to find 2-3 related sources, then:

• Load references/comparison_matrix.md
• Compare SCQA across sources
• Identify consensus vs. divergence
• Synthesize integrated perspective

## Multi-Source Analysis

### Source 1: [This article]
S-C-Q-A: [Summary]
Key claim: [...]

### Source 2: [Found article]
S-C-Q-A: [Summary]
Key claim: [...]

### Source 3: [Found article]
S-C-Q-A: [Summary]
Key claim: [...]

## Synthesis

**Consensus**: [What all agree on]
**Divergence**: [Where they differ]
**Unique value**: [What each contributes]
**Integrated view**: [Your synthesis]

Step 4: Synthesis & Output

Generate based on user goal:

For Problem-Solving:

## Applicable Solutions
[Extract 2-3 methods from content]

## Application Plan
Problem: [User's specific issue]
Relevant insights: [From analysis]

Action steps:
1. [Concrete action with timeline]
2. [Concrete action with timeline]
3. [Concrete action with timeline]

Success metrics: [How to measure]

## Risk Mitigation (from Inversion)
Potential failure points:
- [Point 1] → Prevent by: [...]
- [Point 2] → Prevent by: [...]

For Learning:

## Learning Notes

Core concepts (explained simply):
1. **[Concept 1]**: [Definition + Example]
2. **[Concept 2]**: [Definition + Example]

Mental models gained:
- [Model 1]: [How it works]

Connections to prior knowledge:
- [Link to something user already knows]

## Deeper Understanding (First Principles)
Fundamental question: [...]
Core principle: [...]

## Verification Questions
1. [Question to test understanding]
2. [Question to test application]
3. [Question to test evaluation]

For Writing Reference:

## Key Arguments & Evidence
[Structured extraction with page/paragraph numbers]

## Quotable Insights
"[Quote 1]" — Context: [...]
"[Quote 2]" — Context: [...]

## Critical Analysis Notes
Strengths: [For citing]
Limitations: [For balanced discussion]

## Alternative Perspectives (from Mental Models)
[What other disciplines would say about this]

## Gaps & Counterfactuals
What the article doesn't address:
- [Gap 1]
- [Gap 2]

For Decision-Making:

## Decision Framework

Options presented: [A / B / C]

Multi-model evaluation:
- Economic lens: [...]
- Risk lens (Inversion): [...]
- Systems lens: [...]

## Six Hats Decision Analysis
🤍 Facts: [Objective comparison]
🖤 Risks: [What could go wrong]
💛 Benefits: [Upside potential]
💚 Alternatives: [Other options not considered]
💙 Recommendation: [Synthesized advice]

## Scenario Analysis (from Inversion)
Best case: [...]
Worst case: [...]
Most likely: [...]

Step 5: Knowledge Activation

Always end with:

## 🎯 Immediate Takeaways (Top 3)

1. **[Insight 1]**
   Why it matters: [Personal relevance]
   One action: [Specific, time-bound]

2. **[Insight 2]**
   Why it matters: [Personal relevance]
   One action: [Specific, time-bound]

3. **[Insight 3]**
   Why it matters: [Personal relevance]
   One action: [Specific, time-bound]

## 💡 Quick Win
[One thing to try in next 24 hours - make it TINY and SPECIFIC]

## 🔗 Next Steps

**To deepen understanding:**
[ ] Further reading: [If relevant]
[ ] Apply framework X to topic Y
[ ] Discuss with: [Who could add perspective]

**To apply:**
[ ] Experiment: [Test in real context]
[ ] Teach: [Explain to someone else]
[ ] Combine: [Mix with another idea]

## 🧭 Thinking Models Used
[Checkboxes showing which frameworks were applied]
✅ SCQA ✅ 5W2H ✅ Critical Thinking ✅ Inversion
□ Mental Models □ First Principles □ Systems □ Six Hats

Quality Standards

Every analysis must:

• ✅ Stay faithful to original content (no misrepresentation)
• ✅ Distinguish facts from opinions
• ✅ Provide concrete examples
• ✅ Apply frameworks appropriately (not force-fit)
• ✅ Connect to user's context when possible
• ✅ End with actionable steps
• ✅ Cite specific sections (paragraph numbers, quotes)

Avoid:

• ❌ Overwhelming with all frameworks at once (respect depth level)
• ❌ Academic jargon without explanation
• ❌ Analysis without application
• ❌ Copying text verbatim (always reword for understanding)
• ❌ Using frameworks superficially (go deep, not wide)

Interaction Patterns

Progressive questioning:

• Understanding: "What do you think the author means by X?"
• Critical: "Do you see any gaps in this argument?"
• Application: "How might you use this in your work?"
• Meta: "Which thinking model helped you most? Why?"

Adapt to signals:

• User asks "what's the main point?" → They want conciseness, use SCQA
• User challenges your analysis → Lean into Critical Thinking + Inversion
• User asks "how do I use this?" → Focus on application + First Principles
• User wants "multiple perspectives" → Use Six Hats or Mental Models
• User mentions "risks" → Apply Inversion Thinking
• User asks "how does this connect?" → Use Systems Thinking

Framework suggestions during conversation:

• "Would you like me to apply [X framework] to this point?"
• "This seems like a good place for inversion thinking - want to explore failure modes?"
• "I notice several mental models at play here, want me to unpack them?"

Reference Materials

Core Frameworks (All Levels)

• references/scqa_framework.md - Structure thinking (S-C-Q-A)
• references/5w2h_analysis.md - Completeness check (7 questions)

Standard Level Frameworks

• references/critical_thinking.md - Argument analysis
• references/inversion_thinking.md - Risk and failure mode analysis

Deep Level Frameworks

• references/mental_models.md - Multi-discipline model library
• references/first_principles.md - Essence extraction method
• references/systems_thinking.md - Relationship mapping
• references/six_hats.md - Multi-perspective protocol

Output Formats

• references/output_templates.md - Note format examples
• references/comparison_matrix.md - Cross-article analysis

Advanced Usage

Custom Framework Combinations

User can request specific combinations:

• "Use SCQA + Inversion" - Structure with risk analysis
• "Apply Mental Models + Systems Thinking" - Multi-lens system analysis
• "5W2H + Critical Thinking" - Completeness + quality check

Iterative Deepening

Start with Level 1, then ask:

• "Want to go deeper on any part?"
• "Which framework would be most valuable here?"
• "Should we do an inversion analysis of this solution?"

Domain-Specific Optimizations

Business/Strategy: SCQA + Mental Models (economics) + Inversion Technical/Research: 5W2H + First Principles + Critical Thinking Personal Development: Six Hats + Inversion + Systems Decision-Making: Mental Models + Inversion + SCQA Creative: Six Hats + First Principles + Mental Models

---

Remember: The goal is insight, not framework completion. Use frameworks as tools to reveal understanding, not as checklists to complete. Quality of thinking > quantity of frameworks applied.

5W2H Analysis Framework

Overview

5W2H is a systematic questioning method to comprehensively understand any topic, problem, or plan through 7 fundamental questions.

The 7 Core Questions:

• What - Object, goal, content
• Why - Reason, purpose, significance
• Who - People, stakeholders, responsibilities
• When - Timing, schedule, deadlines
• Where - Location, context, scope
• How - Methods, processes, steps
• How much - Cost, quantity, metrics

When to Use

Ideal for:

• 📋 Quickly understanding complete article information
• 🔍 Discovering information gaps and omissions
• 📊 Evaluating plan feasibility
• 💼 Analyzing business cases and proposals
• 📝 Organizing complex information
• ✅ Verifying information completeness

The 7 Questions in Detail

W1: What (Content)

Core Questions: 1. What is the main topic? 2. What are the key claims/conclusions? 3. What solutions are proposed? 4. What core concepts are involved? 5. What are the expected outcomes?

Deep Inquiry:

• What's the real problem?
• What's missing?
• What could go wrong?
• What are the alternatives?

W2: Why (Reasons)

Core Questions: 1. Why discuss this topic now? 2. Why is this solution effective? 3. Why not choose other approaches? 4. Why should the audience care? 5. Why this timing?

Five Whys Technique: Ask "why" 5 times to reach root cause:

Problem: [Surface issue]
→ Why 1: [First layer]
  → Why 2: [Second layer]
    → Why 3: [Third layer]
      → Why 4: [Fourth layer]
        → Why 5: [Root cause] ← Real issue

W3: Who (People)

Core Questions: 1. Who is the target audience? 2. Who are the stakeholders? 3. Who is responsible for execution? 4. Who benefits? Who loses? 5. Whose expertise/cases are cited? 6. Who is the author? (potential biases?)

Deep Analysis:

• Stakeholder mapping
• Decision-makers vs. executors
• Who has veto power?

W4: When (Timing)

Core Questions: 1. When to start? 2. What's the timeline/schedule? 3. When will results appear? 4. How time-sensitive is this? 5. When are key decisions needed? 6. What's the historical context?

Time Trap Identification:

• Unrealistic time expectations?
• Missing key milestones?
• Buffer time considered?

W5: Where (Context)

Core Questions: 1. Where does this apply? (geography, industry, organization) 2. Where is execution happening? 3. Where to get resources? 4. What are the limitations/constraints? 5. What's the scope of impact?

Context Dependency:

• Does it work in different environments?
• Cultural differences?
• Scale considerations?

H1: How (Methods)

Core Questions: 1. What are the specific steps? 2. What tools/methods are used? 3. How to measure progress? 4. How to handle obstacles? 5. How to ensure quality? 6. How to get started?

Process Mapping:

[Start] → [Step 1] → [Decision Point]
                         ↓ Yes / ↓ No
                    [Step 2A]  [Step 2B]
                         ↓         ↓
                    [Step 3] ← [Converge]
                         ↓
                    [End]

H2: How Much (Metrics)

Core Questions: 1. What's the cost? (money, time, opportunity, learning) 2. How many resources needed? 3. What's the expected ROI? 4. What's the scale/magnitude? 5. How big are the risks? 6. What are the target metrics?

ROI Analysis:

Investment:
- Direct costs: [$]
- Indirect costs: [$]
- Total: [$]

Returns:
- Expected benefit: [$]
- Timeframe: [X months]
- ROI = (Benefit - Cost) / Cost × 100%

Worth it?: [Yes/No]

Complete Analysis Template

Quick Version (15 min)

# 5W2H Quick Analysis: [Article Title]

**What**: [One-line topic and solution]
**Why**: [Core motivation and value]
**Who**: [Target audience and executors]
**When**: [Timeline and urgency]
**Where**: [Applicability and context]
**How**: [Key steps (3-5)]
**How much**: [Main costs and expected returns]

## Gap Analysis
Missing information: [List unanswered questions from 5W2H]
Key risks: [Risks based on missing info]

Deep Version (60 min)

# 5W2H Deep Analysis: [Article Title]

## 📋 What - Content Analysis
[Detailed breakdown...]

## 🎯 Why - Reason Analysis  
[Detailed breakdown...]
[Five Whys analysis]

## 👥 Who - People Analysis
[Detailed breakdown...]
[Stakeholder map]

## ⏰ When - Time Analysis
[Detailed breakdown...]
[Timeline visualization]

## 🌍 Where - Context Analysis
[Detailed breakdown...]
[Applicability matrix]

## 🔧 How - Method Analysis
[Detailed breakdown...]
[Process flowchart]

## 💰 How Much - Cost-Benefit Analysis
[Detailed breakdown...]
[ROI calculation]

## 📊 Overall Assessment

### Information Completeness
- ✅ Clearly answered: [X/7]
- ⚠️  Partially answered: [List]
- ❌ Completely missing: [List]

### Feasibility Score
Based on 5W2H completeness: [X/10]

### Risk Level
Based on missing info: [High/Medium/Low]

### Action Recommendations
1. [Specific recommendation based on analysis]
2. [Information needed to supplement]
3. [Priority actions to take]

Practical Example

Example: Remote Work Article

Article Title: "How to Successfully Transition to Remote Work"

## 5W2H Analysis

### What
- Topic: Company transition from office to remote work
- Solution: Phased transition plan
- Goal: Maintain or improve team productivity

### Why
- Background: Post-pandemic work model changes
- Value: Cost savings, increased flexibility
- Rationale: Mature technology + changing work nature
⚠️  Missing: Why not hybrid model?

### Who
- Target: SMB managers
- Executors: HR + IT teams
- Beneficiaries: Employees (flexibility) + Company (cost)
⚠️  Missing: How to handle resisters?

### When
- Recommended: 3-month transition
  - Month 1: Pilot
  - Month 2: Expand
  - Month 3: Full rollout
✅ Clear

### Where
- Applicable: Knowledge work
- Not suitable: Manufacturing, service industries
- Tools: Zoom, Slack, Asana
✅ Clear boundaries

### How
1. Establish remote work policies
2. Configure technical infrastructure
3. Train managers and employees
4. Build virtual collaboration norms
5. Regular evaluation and adjustment
✅ Clear steps

### How Much
- Tool costs: $50/person/month
- Training: 40 hours
- ROI: Office costs ↓50%
⚠️  Missing: Transition period productivity drop costs

## Gap Analysis

Missing critical information:
1. Why - Why not consider hybrid model
2. Who - How to handle change resisters
3. How much - Transition period hidden costs

Risk:
- Medium risk: 80% information complete
- Need supplement: Change management and hidden costs

Recommendations:
1. Research hybrid work models
2. Create change communication plan
3. Budget 15-20% for transition productivity dip

Integration with Other Frameworks

+ Critical Thinking

5W2H → Identify missing information
Critical Thinking → Evaluate quality of existing information

+ SCQA

SCQA → Understand problem framework
5W2H → Analyze solution completeness

+ Inversion

5W2H → Forward analysis of plan
Inversion → For each W/H, ask "what if it's missing?"

Advanced Techniques

1. Prioritized 5W2H

Not all 7 questions are equally important—adjust by article type:

Strategy articles: Why (40%) > What (30%) > How (20%) > Others
How-to articles: How (40%) > What (25%) > How much (20%) > Others
Analysis articles: What (30%) > Why (30%) > Who (20%) > Others

2. Iterative 5W2H

Round 1: Quick scan of all 7 questions (15 min)
Round 2: Deep dive on 2-3 most lacking (30 min)
Round 3: Cross-validate answer consistency (15 min)

3. Extended 5W2H (+ 2H)

Add two more Hows:

• How to measure? (metrics)
• How to sustain? (maintenance)

Common Pitfalls

❌ Surface-Level Analysis

• Wrong: Mechanically answer 7 questions without depth
• Right: Dig 2-3 levels deep on each question

❌ Ignoring Gaps

• Wrong: Only analyze what article provides
• Right: Explicitly note what article doesn't answer

❌ Siloed Thinking

• Wrong: Analyze 7 questions independently
• Right: Look for consistency and contradictions across answers

Practice Tips

1. Print Checklist: Prepare standard 5W2H template 2. Timed Drills: Complete quick analysis in 15 minutes 3. Reverse Validation: Use analysis to reconstruct article—is it complete? 4. Comparative Application: Compare 5W2H across multiple articles on same topic

Summary

5W2H is:

• ✅ Completeness Checker: Ensures no information omissions
• ✅ Quick Understanding Framework: Systematically captures essence
• ✅ Communication Bridge: Standardized analysis language

Best for:

• 📋 Project plan evaluation
• 📊 Business proposal analysis
• 📝 Operational guide comprehension
• 🔍 Information gap identification

---

Remember: 5W2H's value isn't just answering these 7 questions, but discovering which questions aren't answered—and why.

Multi-Source Comparison Matrix

Overview

Use when analyzing multiple articles, papers, or perspectives on the same topic. Systematically compare to synthesize insights.

Standard Comparison Matrix

# Comparative Analysis: [Topic]

## Sources Overview

| Source | Type | Author Expertise | Date | Bias/Lens |
|--------|------|-----------------|------|-----------|
| [Source 1] | [Article/Paper/Book] | [Credentials] | [Date] | [Perspective] |
| [Source 2] | [...] | [...] | [...] | [...] |
| [Source 3] | [...] | [...] | [...] | [...] |

---

## Key Claims Matrix

| Claim/Question | Source 1 | Source 2 | Source 3 | Consensus? |
|----------------|----------|----------|----------|------------|
| [Question 1] | [Position] | [Position] | [Position] | ✅/❌ |
| [Question 2] | [Position] | [Position] | [Position] | ✅/❌ |
| [Question 3] | [Position] | [Position] | [Position] | ✅/❌ |

---

## Evidence Quality

| Source | Evidence Type | Strength (1-5) | Notes |
|--------|---------------|----------------|-------|
| Source 1 | [Data/Anecdote/Study] | ⭐⭐⭐⭐ | [Assessment] |
| Source 2 | [...] | ⭐⭐⭐ | [...] |
| Source 3 | [...] | ⭐⭐⭐⭐⭐ | [...] |

---

## Agreement vs. Disagreement

### Universal Agreement
All sources agree on:
- [Point 1]
- [Point 2]

### Partial Consensus  
Sources 1 & 2 agree on [X], but Source 3 argues [Y]

### Complete Divergence
On [Topic], views split:
- Source 1: [View]
- Source 2: [View]
- Source 3: [View]

---

## Synthesized Insights

### What We Know with Confidence
Based on convergent evidence across sources:
1. [High-confidence insight]
2. [High-confidence insight]

### Open Questions
Where sources disagree or lack data:
- [Unresolved question 1]
- [Unresolved question 2]

### Integrated Framework
Combining the best from each source:
[Synthesis that incorporates multiple perspectives]

---

## Source-Specific Contributions

**Source 1's unique value:**
[What only this source provides]

**Source 2's unique value:**
[What only this source provides]

**Source 3's unique value:**
[What only this source provides]

---

## Recommended Reading Order

For someone new to this topic:
1. Read [Source X] first because [reason]
2. Then [Source Y] to get [complementary view]
3. Finally [Source Z] for [advanced/critical perspective]

---

Method Comparison Matrix

When sources describe different methods/approaches:

# Method Comparison: [Topic]

| Method | Source | Best For | Limitations | Difficulty | Results |
|--------|--------|----------|-------------|------------|---------|
| [Method A] | [Source 1] | [Use case] | [Weakness] | Easy | [Outcome] |
| [Method B] | [Source 2] | [Use case] | [Weakness] | Hard | [Outcome] |
| [Method C] | [Source 3] | [Use case] | [Weakness] | Medium | [Outcome] |

## Recommendation
Use [Method X] when [condition]
Use [Method Y] when [condition]
Combine [X + Y] for [scenario]

---

Viewpoint Spectrum

When sources represent different positions on a spectrum:

# Viewpoint Spectrum: [Topic]

## The Question
[Central question being debated]

## The Spectrum

[Extreme Position A] ←―――――――――――→ [Extreme Position B]
        ↑                    ↑                    ↑
    [Source 1]          [Source 2]          [Source 3]

### Position A (Source 1)
**Core belief:** [What they believe]
**Reasoning:** [Why they believe it]
**Strongest point:** [Best argument]
**Weakest point:** [Vulnerability]

### Middle Position (Source 2)
**Core belief:** [Balanced view]
**Reasoning:** [Why they believe it]
**Strongest point:** [Best argument]
**Weakest point:** [Vulnerability]

### Position B (Source 3)
**Core belief:** [Opposite extreme]
**Reasoning:** [Why they believe it]  
**Strongest point:** [Best argument]
**Weakest point:** [Vulnerability]

## My Position
After reviewing all perspectives:
[Where you land on spectrum and why]

---

Evolution Over Time Matrix

When tracking how understanding of a topic evolved:

# Evolution of Thought: [Topic]

| Period | Representative Source | Key Insight | What Changed Next |
|--------|----------------------|-------------|-------------------|
| [Era 1] | [Source/Author] | [Prevailing view] | [Paradigm shift] |
| [Era 2] | [Source/Author] | [New understanding] | [Next shift] |
| [Era 3] | [Source/Author] | [Current view] | [Open questions] |

## Pattern Analysis
**What stayed constant:** [Enduring truths]
**What repeatedly changed:** [Unstable assumptions]
**Current frontier:** [What we're figuring out now]

## Lessons from History
- [Historical pattern 1 and implication]
- [Historical pattern 2 and implication]

---

Interdisciplinary Comparison

When same topic is analyzed from different fields:

# Multi-Disciplinary View: [Topic]

| Discipline | Source | Core Question | Key Findings | Limitations |
|------------|--------|---------------|--------------|-------------|
| Economics | [Source] | [Question] | [Insight] | [Blind spot] |
| Psychology | [Source] | [Question] | [Insight] | [Blind spot] |
| Sociology | [Source] | [Question] | [Insight] | [Blind spot] |
| Biology | [Source] | [Question] | [Insight] | [Blind spot] |

## Synthesis
**Complementary insights:**
- Economics sees [X], Psychology explains [Y], together they reveal [Z]

**Contradictions:**
- [Field A] assumes [X], but [Field B] shows [not-X]
- Resolution: [How to reconcile]

**Blind spots filled:**
- Economics misses [X] that Sociology provides
- Psychology overlooks [Y] that Biology explains

## Integrated Model
[Diagram or description combining multiple lenses]

---

Practical Comparison

For how-to content from multiple sources:

# Implementation Comparison: [Skill/Method]

## Common Steps (All Sources Agree)
1. [Universally recommended step]
2. [Universally recommended step]

## Variations

| Aspect | Source 1 Approach | Source 2 Approach | Source 3 Approach |
|--------|-------------------|-------------------|-------------------|
| [Aspect 1] | [Method] | [Method] | [Method] |
| [Aspect 2] | [Method] | [Method] | [Method] |
| [Aspect 3] | [Method] | [Method] | [Method] |

## User Reviews/Results

| Source | Reported Success Rate | Common Feedback | My Assessment |
|--------|----------------------|-----------------|---------------|
| Source 1 | [X%] | [What users say] | [Credibility] |
| Source 2 | [Y%] | [What users say] | [Credibility] |
| Source 3 | [Z%] | [What users say] | [Credibility] |

## Personalized Recommendation
For someone like me ([my context]):
- Use [Source X's method] for [reason]
- Skip [Source Y's suggestion] because [reason]
- Test [Source Z's variation] if [condition]

---

Conflict Resolution Template

When sources directly contradict:

# Resolving Contradiction: [Specific Claim]

## The Contradiction
**Source 1 claims:** [Statement]
**Source 2 claims:** [Opposite statement]

## Investigating the Conflict

### Possible Reasons for Disagreement

1. **Different Definitions**
   - Does Source 1 define [term] as [X]?
   - Does Source 2 define [term] as [Y]?
   - → Not actually contradicting if talking about different things

2. **Different Contexts**
   - Source 1 context: [Time/place/population]
   - Source 2 context: [Time/place/population]
   - → Both could be right in their contexts

3. **Different Evidence**
   - Source 1 relies on: [Evidence type]
   - Source 2 relies on: [Evidence type]
   - → Quality difference explains disagreement

4. **Different Values/Goals**
   - Source 1 optimizes for: [Goal]
   - Source 2 optimizes for: [Goal]
   - → Different priorities lead to different conclusions

5. **One is Wrong**
   - [Analysis of which source has flawed reasoning]

### Resolution
[Which source is more reliable for this specific claim and why]
OR
[How both can be true depending on context]
OR
[This remains unresolved; need more evidence]

---

Usage Guidelines

When to use comparison matrices:

• Reading 3+ sources on same topic
• Encountering conflicting information
• Trying to synthesize best practices
• Building comprehensive understanding
• Making informed decisions

How to populate: 1. Read each source independently first (use standard note template) 2. Identify common themes/questions across sources 3. Create matrix structure based on what you're comparing 4. Fill in each source's position 5. Analyze patterns and synthesize

Common mistakes:

• ❌ Forcing false equivalence (not all views equally valid)
• ❌ Cherry-picking to support predetermined view
• ❌ Ignoring publication quality/expertise differences
• ❌ Missing the forest for the trees (over-detailed comparison)

Best practices:

• ✅ Weight sources by credibility
• ✅ Look for convergent evidence
• ✅ Note what's settled vs. debated
• ✅ Identify your own biases in interpretation

Critical Thinking Framework

Argument Quality Assessment

Evidence Evaluation Matrix

Logical Fallacy Checklist

Causal Fallacies:

• [ ] Post hoc (A before B ≠ A caused B)
• [ ] Correlation ≠ Causation
• [ ] Oversimplified cause (single factor explains complex phenomenon)

Evidence Fallacies:

• [ ] Cherry-picking (selective evidence)
• [ ] Survivorship bias (only successful cases visible)
• [ ] Hasty generalization (small sample → broad claim)

Rhetorical Fallacies:

• [ ] Ad hominem (attack person, not argument)
• [ ] Appeal to authority (without expertise in relevant field)
• [ ] Strawman (misrepresenting opponent's position)
• [ ] Slippery slope (extreme outcome without justification)
• [ ] False dichotomy (only 2 options when more exist)

Statistical Fallacies:

• [ ] Base rate neglect (ignoring prior probability)
• [ ] Absolute vs. relative risk confusion
• [ ] Misleading averages (mean hiding distribution)

Critical Questions Protocol

Level 1: Comprehension

• What is the core claim?
• What evidence supports it?
• What are the key assumptions?

Level 2: Analysis

• Is the evidence sufficient for the claim?
• Are there logical gaps?
• What's missing from this argument?

Level 3: Evaluation

• How strong is this argument overall?
• What would strengthen/weaken it?
• What are alternative explanations?

Level 4: Synthesis

• How does this fit with other knowledge?
• Where might the author be correct despite flaws?
• What's the charitable interpretation?

Source Credibility Assessment

Author Background:

• Relevant expertise in the field?
• Potential conflicts of interest?
• Track record of accuracy?

Publication Context:

• Peer-reviewed? Editorial standards?
• Primary source or interpretation?
• Publication date (currency)?

Motivation Analysis:

• What's the author's goal? (inform/persuade/sell)
• Who benefits from this claim?
• What's the intended audience?

Counter-Evidence Search

When analyzing strong claims, actively look for: 1. Studies with opposite findings 2. Expert disagreement 3. Failed replications 4. Boundary conditions (when doesn't it work?)

Balanced Evaluation Template

## Argument Strengths
- [What's well-supported]
- [Strong evidence points]

## Argument Weaknesses  
- [Logical gaps]
- [Weak or missing evidence]

## Unanswered Questions
- [What the argument doesn't address]

## Conditional Truth
This argument is strongest when: [context]
This argument is weakest when: [context]

Steelmanning Practice

Before criticizing, construct the strongest possible version of the argument: 1. Fill in logical gaps charitably 2. Add best possible supporting evidence 3. Address obvious objections 4. THEN evaluate this strongest version

This prevents attacking strawmen and ensures fair evaluation.

First Principles Thinking

Core Concept

Strip away assumptions and conventions to reach fundamental truths, then rebuild understanding from the ground up.

Three-Step Process

Step 1: Identify Assumptions

Ask: "What do we assume to be true about this?"

List all implicit and explicit assumptions in the content:

• Unstated premises
• Inherited wisdom ("everyone knows...")
• Industry conventions
• Historical precedents treated as universal laws

Example from business:

• Assumption: "We need a physical store to sell products"
• Question: Is this fundamentally true or historically convenient?

Step 2: Break Down to Fundamentals

Ask: "What is definitely, provably true?"

Reduce to indisputable facts:

• Physical laws (if applicable)
• Mathematical truths
• Core human needs/behaviors
• Cause-effect relationships you can verify

Sorting Framework:

Claim → Ask: "How do I know this is true?"
    ↓
├─ "It just is" → Probably an assumption, dig deeper
├─ "That's how it's always done" → Convention, not fundamental
├─ "X happens, then Y happens" → Potential fundamental (verify causation)
└─ "Mathematically/physically must be true" → Fundamental

Step 3: Rebuild from Scratch

Ask: "Starting from fundamentals only, what logically follows?"

Reconstruct without importing old assumptions: 1. Begin with verified fundamentals 2. Each step must logically follow from previous 3. Note where you make new assumptions (be explicit) 4. Compare new construction to original concept

Application Template

## Original Concept/Argument
[What the author claims]

## Hidden Assumptions
- Assumption 1: [Something taken as given]
- Assumption 2: [...]

## Verified Fundamentals
- Fundamental 1: [Provably true core fact]
- Fundamental 2: [...]

## Rebuilt Understanding
Starting from fundamentals only:
Step 1: [First logical derivation]
Step 2: [Second logical derivation]
...
Conclusion: [What actually follows]

## Comparison
Original vs. Rebuilt:
- What survived: [Fundamentally sound ideas]
- What doesn't hold: [Based on questionable assumptions]
- New insights: [What rebuilding revealed]

Common First Principles in Different Domains

Business/Economics

• People act in self-interest (with caveats)
• Supply and demand affect price
• Value = willingness to pay
• Scarcity creates value

Psychology/Human Behavior

• Humans seek pleasure, avoid pain
• Social status matters to humans
• Cognitive biases exist (not "people are rational")
• Habits form through repetition

Technology

• Information can be copied at near-zero cost
• Network effects: value ∝ n² (Metcalfe's law)
• Moore's law (transistor density doubles ~every 2 years)
• Computation has energy cost

Physics/Reality

• Energy is conserved
• Entropy increases
• Speed of light is constant
• Cause precedes effect

Red Flags: Pseudo-First Principles

Watch for claims disguised as fundamentals:

• "People always prefer X" (overgeneralization)
• "This is just human nature" (often cultural)
• "Economics proves..." (many schools of economics)
• "Science says..." (which study? replicated?)

Test: Can you point to specific evidence/mechanism, or is it folk wisdom?

Powerful Questions

• "Why is this true?" (repeat 5 times - "5 Whys")
• "What must be true for this to work?"
• "If I couldn't do it this way, what's another path?"
• "What would an alien with no context think?"
• "What if the opposite were true?"

Example: Deconstructing "Need for College Education"

Assumptions:

• Need degree to get good job
• Learning requires formal institution
• 18-22 is the right age
• Four years is optimal duration

Fundamentals:

• Employers want skilled workers
• Skills can be demonstrated
• Learning requires time + practice
• Knowledge can be transmitted

Rebuilt: → Employers want proof of skill → Proof can be: degree OR portfolio OR test OR track record → Therefore, degree is one option, not necessity → Insight: Focus on skill + proof, not credential alone

Practical Use in Reading

When analyzing content: 1. Identify claims that seem absolute 2. Challenge foundations: "Does this HAVE to be true?" 3. Verify causation: "Does A truly cause B, or just correlate?" 4. Rebuild the argument from indisputable facts only 5. Compare what survives vs. what was assumption

This exposes weak arguments and strengthens valid ones.

Inversion Thinking Framework

Overview

Inversion is a powerful mental tool: instead of asking "how to succeed?", ask "how to fail?" then avoid those failure modes.

Core Principle: "Invert, always invert." — Carl Jacobi (German mathematician)

When to Use

Ideal for:

• 🎯 Mitigating risks and avoiding failure
• 🔍 Discovering hidden problems and obstacles
• 💡 Breaking through mental blocks
• ⚠️ Stress-testing plans for fragility
• 🛡️ Building defensive strategies

Three Inversion Modes

1. Goal Inversion

Forward: How to achieve goal X? Inverted: How to guarantee failure to achieve X?

## Goal Inversion Analysis

Forward Goal: [Article's main recommendation]

Inverted Questions:
1. What behaviors guarantee failure?
2. Which factors completely sabotage the plan?
3. What's the worst possible outcome?

Insights:
- Must-avoid behaviors: [List]
- Critical risk points: [Identify]
- Defensive strategy: [Formulate]

2. Assumption Inversion

Forward: If assumption A holds, then conclusion B is valid Inverted: What happens if assumption A doesn't hold?

## Assumption Inversion Test

Article's core assumptions:
1. [Assumption 1]
2. [Assumption 2]
3. [Assumption 3]

Inversion Test:
- If assumption 1 is reversed, how does the conclusion change?
- Under what conditions does this assumption fail?
- Are there counterexamples?

Discovered vulnerabilities: [List]

3. Causality Inversion

Forward: A causes B (cause to effect) Inverted: To get B, what must be true? (effect to cause)

## Causality Inversion

Desired Outcome: [Article's promised result]

Backward Derivation:
- To achieve this, what conditions must be met?
- Are all these conditions mentioned in the article?
- What critical factors are missing?

Necessary Conditions:
✓ [Met conditions]
✗ [Unmentioned necessary conditions] ← Important discovery

Application Method

Step 1: Identify Forward Claims

## Article's Forward Claims

Core thesis: [Extract]
Recommended actions: [List]
Expected results: [Describe]

Step 2: Apply Four Inversion Questions

❌ Q1: How to guarantee failure?

Most effective failure methods:
1. [Opposite of recommendations]
2. [Ignored critical factors]
3. [Problems from over-execution]

Insight: Avoid these traps

⚠️ Q2: When would the advice backfire?

Backfire scenarios:
- Wrong timing: [Explain]
- Wrong context: [Explain]
- Insufficient resources: [Explain]

Prerequisites: [Unstated but necessary conditions]

🔍 Q3: What risks are missing?

Risks article doesn't mention:
1. [Hidden risk 1]
2. [Hidden risk 2]
3. [Hidden risk 3]

Risk mitigation: [Supplement]

🎯 Q4: What's reasonable about the opposite view?

Contrary perspectives:
- [Counter-argument 1]
- [Counter-argument 2]

Merit in opposition:
- [Analysis]
- [When might the opposite be better]

Balanced view: [Synthesized judgment]

Step 3: Build Failure-Mode Checklist

## Failure Prevention Checklist

Based on inversion, avoid:
- [ ] [Failure mode 1] → Prevention: [Specific action]
- [ ] [Failure mode 2] → Prevention: [Specific action]
- [ ] [Failure mode 3] → Prevention: [Specific action]

Early warning signs:
- 🚨 [Signal 1] → Indicates moving toward failure
- 🚨 [Signal 2] → Requires immediate adjustment

Step 4: Restructure Action Plan

## Defensive Action Plan

Original plan: [Article's recommendation]

Optimized plan (with inversion insights):
1. [Original action] + [Risk mitigation]
2. [Added preventive step]
3. [Established safety margin]

Stop-Doing List:
- ❌ [Explicitly what NOT to do]

Practical Examples

Example 1: Productivity Article

Article Claim: "Waking up at 5am is key to success"

Inversion Analysis:

Forward: How to become an early riser? Inverted: How to guarantee the 5am plan fails?

Failure Checklist: 1. Stay up until 3am → Insight: Total sleep matters more than wake time 2. No compelling morning reason → Insight: Need clear morning purpose 3. Inconsistent weekend schedule → Insight: Consistency is key 4. Alarm within arm's reach → Insight: Environmental design matters

Inversion Discoveries:

• ⚠️ Article ignores: Individual chronotype differences ("night owls")
• ⚠️ Fails when: Work requires night shifts
• ⚠️ Backfires: Sleep deprivation reduces productivity

Optimized Recommendation:

• Don't chase wake time, chase:

1. Sufficient sleep (7-9 hours) 2. Consistent schedule 3. High-value morning activities

Example 2: Business Strategy

Article Claim: "Rapid expansion to capture market"

Inverted Q: How to ensure expansion fails?

Failure List: 1. Expand before product-market fit → Insight: Need PMF first 2. Poor cash flow management → Insight: Growth speed ≠ healthy growth 3. Team quality can't keep up → Insight: Organizational capacity is bottleneck 4. Neglect existing customers → Insight: Retention vs. acquisition balance

Necessary Conditions Check:

Prerequisites for rapid expansion:
✓ Proven business model (article mentions)
✗ Adequate funding reserves (article omits)
✗ Replicable operational processes (article omits)
✗ Strong team culture (article omits)

Inversion Insight: Article only discusses "gas pedal", not "brakes". Need to add:

• Expansion stop conditions
• Stage-gate validation
• Retreat plan

Integration with Other Frameworks

+ Critical Thinking

Critical Thinking: Find argument holes
Inversion: What happens if the holes lead to failure?

+ First Principles

First Principles: Strip to essentials
Inversion: Test fragility of essential assumptions

+ Systems Thinking

Systems Thinking: See reinforcing loops
Inversion: Identify negative loops and collapse points

+ Mental Models

Mental Models: Multi-angle analysis
Inversion: Consider the opposite for each angle

Inversion Toolbox

Tool 1: Pre-Mortem

## Pre-Mortem Analysis

Imagine it's 1 year later, the plan completely failed.

Failure causes:
1. [Most likely failure reason 1]
2. [Most likely failure reason 2]
3. [Most likely failure reason 3]

Based on this, current actions should be:
- [Prevention measure 1]
- [Prevention measure 2]

Tool 2: Reverse Engineering

## Working Backwards from Results

Ideal outcome: [Describe]

Reverse steps:
← Step N: [Final step]
← Step N-1: [Previous step]
← ...
← Step 1: [First step]

Article's missing steps: [Identify]

Tool 3: Not-To-Do List

## Not-To-Do List (More Important Than To-Do)

Based on inversion, explicitly avoid:
1. ❌ [Failure-causing behavior 1]
2. ❌ [Failure-causing behavior 2]
3. ❌ [Failure-causing behavior 3]

Stop signals:
When [X signal] appears, immediately stop

Tool 4: Devil's Advocate

## Playing Devil's Advocate

Defending the opposite view:
- Claim: [Contrary position]
- Evidence: [Supporting counter-evidence]
- Context: [When opposite is better]

Balanced conclusion:
Not A or B, but [middle path]

Common Pitfalls

❌ Excessive Negativity

• Wrong: Use inversion to reject everything
• Right: Use inversion to optimize plans, not abandon them

❌ Analysis Paralysis

• Wrong: See too many risks, can't act
• Right: Identify risks → Design mitigations → Act

❌ Ignoring Probability

• Wrong: Treat low-probability risks same as high-probability
• Right: Risk assessment = Probability × Impact

Practice Exercises

Exercise 1: Daily Decisions

For any daily decision, ask:

• "How to ensure this decision is wrong?"
• What blind spots did I discover?

Exercise 2: Inverted Reading

For any advice article, automatically ask:

• "When would this advice be harmful?"
• "What prerequisites are missing?"

Exercise 3: Pre-Mortem Planning

Before any plan, do 15-minute pre-mortem:

• Assume failure, list causes
• Modify plan to avoid these causes

Key Quotes

"It is remarkable how much long-term advantage people like us have gotten by trying to be consistently not stupid, instead of trying to be very intelligent."

— Charlie Munger

"Tell me where I'm going to die, so I'll never go there."

— Carl Jacobi

"If you want to improve, be content to be thought foolish and stupid."

— Epictetus (On how inversion may contradict conventional wisdom)

---

Remember: Inversion's goal isn't pessimism, but robustness. By seeing failure paths, we design better success paths.

Mental Models Framework

Overview

Mental Models is the thinking approach championed by Charlie Munger—applying multiple models from different disciplines to analyze problems, avoiding the limitations of single-perspective thinking.

Core Principle: "To a man with only a hammer, every problem looks like a nail."

When to Use

Ideal for:

• 📊 Understanding complex problems from multiple angles
• 🔍 Avoiding cognitive biases and blind spots
• 💡 Finding innovative solutions
• 🎯 Making important decisions
• 📚 Cross-disciplinary learning and knowledge integration

Core Mental Models Toolkit

1. General Thinking Models

First Principles

• Strip away assumptions to fundamentals
• Rebuild from basic truths
• Application: Analyze article's core assumptions

Compounding

• Long-term accumulation creates exponential growth
• Small improvements compound over time
• Application: Evaluate long-term strategies in content

Opportunity Cost

• Choosing one option means forgoing others
• Evaluate trade-offs
• Application: Analyze the cost of recommended approaches

2. Physics Models

Leverage

• Small force creates large results
• Find the critical leverage points
• Application: Identify key action points in articles

Inertia

• Systems tend to maintain current state
• Change requires additional energy
• Application: Understand resistance to change

Critical Mass

• Qualitative change occurs after reaching threshold
• Accumulation to breakthrough
• Application: Evaluate when tipping points occur

3. Biology Models

Evolution

• Survival of the fittest, continuous iteration
• Small experiments, rapid adaptation
• Application: Analyze adaptive strategies in content

Ecosystem

• Complex networks of interdependence
• Balance and diversity
• Application: Understand systemic issues

Red Queen Effect

• Must keep running to stay in same place
• Continuous progress in competitive environments
• Application: Evaluate competitive strategies

4. Psychology Models

Cognitive Biases

• Confirmation bias, anchoring, availability heuristic
• Systematic thinking errors
• Application: Identify logical flaws in arguments

Loss Aversion

• Motivation to avoid losses > gain benefits
• Asymmetric risk decision-making
• Application: Understand decision motivations

Social Proof

• Herd mentality and group influence
• Others' behavior affects judgment
• Application: Analyze persuasive power of arguments

5. Economics Models

Supply and Demand

• Price determined by market equilibrium
• Scarcity creates value
• Application: Analyze market-related articles

Marginal Utility

• Value of additional units decreases
• Optimal point isn't maximum
• Application: Evaluate resource allocation recommendations

Incentives

• "Show me the incentive and I'll show you the outcome"
• People respond to incentives
• Application: Understand motivations behind behaviors

6. Mathematics/Statistics Models

Normal Distribution

• Most cases cluster around average
• Extreme cases are rare
• Application: Evaluate probabilities and risks

Power Law

• 80/20 rule (Pareto Principle)
• Few factors produce most results
• Application: Identify key factors

Regression to the Mean

• Extreme results tend toward average
• Avoid overreaction to outliers
• Application: Evaluate representativeness of exceptional cases

7. Systems Thinking Models

Feedback Loops

• Positive feedback: amplifying effects
• Negative feedback: balancing stability
• Application: Identify causal relationships

Emergence

• Whole is greater than sum of parts
• System-level properties
• Application: Understand complex systems

Bottleneck

• Critical constraint limiting system performance
• Optimizing bottleneck yields maximum benefit
• Application: Find core problems

Application Method

Step 1: Identify Problem Type

Problem Classification:
- [ ] Decision problem → Use: Opportunity cost, Loss aversion, Incentives
- [ ] System problem → Use: Feedback loops, Emergence, Ecosystem
- [ ] Growth problem → Use: Compounding, Leverage, Power law
- [ ] Competition problem → Use: Evolution, Red Queen effect, Game theory

Step 2: Apply Multiple Models

Rule: Use at least 3 models from different disciplines

## Multi-Perspective Analysis

### Physics Perspective (Leverage)
- Observation: Key actions proposed in article
- Analysis: Which action yields maximum output with minimum input?
- Conclusion: [Identify leverage points]

### Psychology Perspective (Cognitive Biases)
- Observation: Argumentation approach
- Analysis: Any confirmation or survivorship bias present?
- Conclusion: [Evaluate argument quality]

### Economics Perspective (Incentives)
- Observation: Stakeholders involved
- Analysis: Are incentives aligned?
- Conclusion: [Understand behavioral motivations]

Step 3: Find Model Intersections

## Cross-Model Insights

When multiple models point to same conclusion → confidence ↑
When models contradict → need deeper investigation

Intersection discoveries:
1. [Model A] + [Model B] → [Shared insight]
2. [Contradiction] → [Issue requiring further analysis]

Step 4: Synthesize Judgment

## Integrated Conclusion

Based on multi-model analysis:
- ✅ Strongly supported views: [List]
- ⚠️  Proceed with caution: [List]
- ❌ Problematic assumptions: [List]

Meta-cognitive check:
- Did I use sufficiently diverse models?
- Any important perspectives missing?
- Over-reliance on any single model?

Practical Example

Example: Analyzing Startup Article

Article Claim: "Rapid growth is key to startup success"

Multi-Model Analysis:

1. Ecosystem Model (Biology)

• Insight: Too-rapid growth can disrupt organizational "ecosystem balance"
• Risk: Culture dilution, quality decline

2. Critical Mass Model (Physics)

• Insight: Must reach certain scale to survive
• Support: Network effects require user base

3. Marginal Utility Model (Economics)

• Insight: Growth benefits diminish
• Question: Is unlimited growth speed pursuit rational?

4. Feedback Loop Model (Systems)

• Insight: Rapid growth → resource strain → quality drop → user churn (negative feedback)
• Risk: Growth trap

Synthesized Judgment:

• ✅ Article valid: Early stage needs rapid market validation
• ⚠️ Missing: Sustainable vs. growth-at-all-costs
• ❌ Overlooked: Industry/stage-specific growth rhythms

Common Pitfalls

❌ Wrong Usage

1. Model Misuse: Force-fitting irrelevant models 2. Single Dependency: Actually using only one model, pretending it's multiple 3. Over-complexity: Piling models without real insights 4. Ignoring Context: Not considering specific situational differences

✅ Correct Usage

1. Choose Relevance: Select models related to problem essence 2. Apply Deeply: Truly understand model applicability 3. Seek Conflicts: Pay special attention to model contradictions 4. Stay Flexible: Adjust model selection based on new information

Building Your Model Library

Beginner Level (Essential)

• First principles
• Opportunity cost
• Compounding
• Feedback loops
• Cognitive biases

Intermediate Level (Expansion)

• Ecosystem
• Power law
• Emergence
• Red Queen effect
• Game theory

Advanced Level (Specialization)

• Deepen based on your domain
• Cross-disciplinary integration
• Create your own model combinations

Learning Recommendations

1. Broad Reading: Study classics from different disciplines 2. Deliberate Practice: Try applying 3+ models to every problem 3. Build Index: Maintain personal "model → use case" catalog 4. Reflect: Note which model combinations work especially well 5. Teach Others: Explaining models deepens understanding

Recommended Resources

Books:

• "Poor Charlie's Almanack" - Charlie Munger
• "The Art of Thinking Clearly" - Rolf Dobelli
• "Principles" - Ray Dalio
• "Super Thinking" - Gabriel Weinberg

Key Quote:

"You must know the big ideas in the big disciplines and use them routinely—all of them, not just a few."

— Charlie Munger

Integration with Other Frameworks

• Critical Thinking: Mental models help identify argument blind spots
• Systems Thinking: Provides more tools for analyzing systems
• First Principles: Can serve as one of the mental models
• Six Thinking Hats: Complementary multi-perspective method

---

Remember: The goal of mental models isn't using more models, but gaining deeper insights. Quality > Quantity.

Output Templates

1. Standard Learning Notes

# [Article Title] - Learning Notes

**Author:** [Name] | **Source:** [URL/Publication] | **Date:** [When read]  
**Reading Time:** [X minutes] | **My Purpose:** [Why I read this]

---

## 🎯 One-Sentence Summary
[Capture the essence in one sentence]

---

## 📊 Structure at a Glance

**Main Thesis:** [Core argument]

**Supporting Pillars:**
1. [Main point 1]
2. [Main point 2]  
3. [Main point 3]

---

## 💡 Key Insights (Top 3)

### 1. [Insight Name]
**What:** [Description in my own words]  
**Why it matters:** [Significance]  
**How to use:** [Application]

### 2. [Insight Name]
**What:** [Description]
**Why it matters:** [Significance]
**How to use:** [Application]

### 3. [Insight Name]
**What:** [Description]
**Why it matters:** [Significance]
**How to use:** [Application]

---

## 🔍 Critical Analysis

### Strengths
- ✅ [What's well-argued]
- ✅ [Strong evidence]

### Weaknesses
- ⚠️ [Logical gap]
- ⚠️ [Weak support]

### Unanswered Questions
- ❓ [Question 1]
- ❓ [Question 2]

---

## 🔗 Connections

**Reminds me of:**
- [Other book/article/concept]
- [Personal experience]

**Contradicts:**
- [Opposing viewpoint I've encountered]

**Builds on:**
- [Prior knowledge this extends]

---

## 📝 Key Quotes & Context

> "[Quote 1]"

Why notable: [My interpretation]

> "[Quote 2]"

Why notable: [My interpretation]

---

## 🎯 Action Items

**Immediate (This Week):**
- [ ] [Specific action]
- [ ] [Specific action]

**Short-term (This Month):**
- [ ] [Specific action]

**Long-term:**
- [ ] [Specific action]

---

## 🔖 Further Exploration

**To Read:**
- [Related article/book]
- [Author's other work]

**To Discuss:**
- [Question for peers/mentor]

**To Test:**
- [Hypothesis to validate]

---

## 💭 Personal Reflection

[How has this changed my thinking?]
[What surprised me?]
[What will I do differently?]

---

2. Concept Map Template

# Concept Map: [Topic]

## Core Concept
[Central idea in one box]

## Related Concepts

### Direct Connections
[Concept A] ←→ [Core] : [Relationship]
[Concept B] ←→ [Core] : [Relationship]

### Secondary Connections  
[Concept C] ←→ [Concept A] : [Relationship]

## Hierarchy
[Broader concept]
    ↓
[Core concept]
    ↓
├─ [Specific example 1]
├─ [Specific example 2]
└─ [Specific example 3]

## Cross-Domain Parallels
- In [Field A]: This is like [Analogy]
- In [Field B]: This is like [Analogy]

---

3. Argument Analysis Template

# Argument Analysis: [Article Title]

## The Claim
**Main Thesis:** [What author argues]

## The Support

### Evidence Presented
1. [Evidence 1]
   - Type: [Data/Anecdote/Study/Expert opinion]
   - Strength: ⭐⭐⭐⭐⭐ (1-5)
   - Notes: [Assessment]

2. [Evidence 2]
   - Type: [Type]
   - Strength: ⭐⭐⭐
   - Notes: [Assessment]

### Logical Structure
[Premise 1] + [Premise 2] → [Conclusion]

**Valid?** [Yes/No/Partially]
**Sound?** [Yes/No - are premises true?]

## Counter-Arguments

### Acknowledged by Author
- [Counter-point mentioned]
- [Author's response]
- [My assessment of response]

### Not Addressed
- [Missing counter-argument 1]
- [Missing counter-argument 2]

## Alternative Explanations
The data could also mean:
- [Alternative 1]
- [Alternative 2]

## Verdict
**Overall Assessment:** [Rating + reasoning]
**When argument is strongest:** [Context]
**When argument is weakest:** [Context]

---

4. Practical Application Template

# Application Plan: [Concept from Article]

## Current Situation
**Problem I'm facing:** [Specific issue]
**Why this concept is relevant:** [Connection]

## The Concept
[Brief explanation in my words]

## Application Strategy

### Phase 1: Test (Week 1)
**Experiment:** [Small, low-risk test]
**Measure:** [How I'll know if it works]
**Expected outcome:** [Hypothesis]

### Phase 2: Refine (Week 2-3)
**Based on test results:**
- If works: [How to expand]
- If doesn't work: [What to adjust]

### Phase 3: Integrate (Month 2)
**Full implementation:** [How to make it routine]

## Success Metrics
- **Leading indicator:** [Early signal]
- **Lagging indicator:** [Long-term outcome]

## Obstacles & Solutions
| Potential Obstacle | Mitigation Strategy |
|--------------------|---------------------|
| [Obstacle 1] | [How to handle] |
| [Obstacle 2] | [How to handle] |

## Check-in Schedule
- [ ] Day 7: [Review question]
- [ ] Day 30: [Review question]
- [ ] Day 90: [Review question]

---

5. Compare & Contrast Template

# Comparison: [Source 1] vs [Source 2]

## On [Topic/Question]

### [Source 1] Position
**Core claim:** [What they argue]
**Key evidence:** [Main support]
**Assumptions:** [What they take as given]

### [Source 2] Position  
**Core claim:** [What they argue]
**Key evidence:** [Main support]
**Assumptions:** [What they take as given]

## Points of Agreement
1. [Overlap 1]
2. [Overlap 2]

## Points of Divergence
| Aspect | Source 1 | Source 2 |
|--------|----------|----------|
| [Dimension] | [View] | [View] |
| [Dimension] | [View] | [View] |

## Analysis
**Why they disagree:**
- Different values: [Explanation]
- Different data: [Explanation]  
- Different frames: [Explanation]

**Who's more convincing and why:**
[Assessment with reasoning]

**Synthesis:**
[Can we integrate both views? Middle ground?]

---

6. Quick Reference Card

# Quick Ref: [Topic]

## The Concept
[2-3 sentence explanation]

## When to Use
- ✅ [Situation 1]
- ✅ [Situation 2]
- ❌ NOT for [Situation 3]

## Key Steps
1. [Step 1]
2. [Step 2]
3. [Step 3]

## Remember
💡 [Most important insight]
⚠️ [Common mistake to avoid]

## Example
[One concrete scenario showing application]

---

7. Feynman Technique Template

# Teach [Concept]

## Explain Like I'm 5
[Simplest possible explanation, no jargon]

## Key Analogy
[Concept] is like [everyday thing] because [reasoning]

## The Steps (Simple)
1. [First, you...]
2. [Then, you...]
3. [Finally, you...]

## Common Confusion
**People often think:** [Misconception]
**But actually:** [Correction]
**Why the confusion:** [Reason]

## Test Questions
1. [Question to check understanding]
2. [Question to check understanding]

## Gaps I Found
While explaining, I realized I don't fully understand:
- [Gap 1]
- [Gap 2]

**Need to review:** [Specific sections/concepts]

---

8. Decision Matrix Template

# Should I [Action Based on Reading]?

## Options
1. [Option A - fully implement]
2. [Option B - partially implement]
3. [Option C - don't implement]

## Evaluation Criteria

| Criterion | Weight | Option A | Option B | Option C |
|-----------|--------|----------|----------|----------|
| [Impact] | 40% | 8/10 | 5/10 | 1/10 |
| [Effort] | 30% | 3/10 | 7/10 | 10/10 |
| [Risk] | 20% | 6/10 | 8/10 | 10/10 |
| [Alignment] | 10% | 9/10 | 7/10 | 2/10 |
| **Total** | | **X.X** | **X.X** | **X.X** |

## Decision
[Chosen option] because [reasoning]

## Implementation Plan
[If proceeding, link to practical application template]

---

Usage Guide

For Different Goals:

• Just learning: Use Template #1 (Standard Notes)
• Deep understanding: Use Template #2 (Concept Map) + #7 (Feynman)
• Critical evaluation: Use Template #3 (Argument Analysis)
• Taking action: Use Template #4 (Application Plan)
• Comparing sources: Use Template #5 (Compare & Contrast)
• Quick reference: Use Template #6 (Reference Card)
• Making decisions: Use Template #8 (Decision Matrix)

Combine as needed: Many analyses benefit from multiple templates.

SCQA Framework (Structure Thinking)

Overview

SCQA is McKinsey's widely-used structured thinking and communication framework that transforms complex problems into clear narrative structures.

The 4 Elements:

• S (Situation) - Context: background and current state
• C (Complication) - Conflict: problems and challenges
• Q (Question) - Query: the core question
• A (Answer) - Solution: proposed resolution

Core Value: Converting complexity into clarity through narrative structure

When to Use

Ideal for:

• 📊 Understanding article argumentation structure
• 📝 Organizing complex problem logic
• 💼 Analyzing business cases
• 🎯 Evaluating solution reasonableness
• 📋 Restructuring information for logical flow
• 🗣️ Preparing presentations or reports

The Four Elements in Detail

S - Situation (Context)

Definition: Stable, mutually-agreed background facts

Identification Method

## Identifying Situation

Look for "background" descriptions in article:
- Industry status
- Historical development
- Market environment
- Existing consensus
- Basic facts

Extraction formula:
"At [time], [subject] in [field/industry] is in [state]"

Quality Situation Characteristics

• ✅ Objective description, minimal subjective judgment
• ✅ Generally agreed upon
• ✅ Sets stage for upcoming complication
• ✅ Relevant but doesn't delve into details

Example

**Situation**:
"Over the past decade, remote work technology (video conferencing, collaboration tools) has matured.
Many knowledge companies began piloting flexible work arrangements pre-pandemic.
Employee expectations for work flexibility continue rising."

Analysis:
- ✅ States facts
- ✅ Neutral description
- ✅ Establishes discussion scope

C - Complication (Conflict/Challenge)

Definition: Change, problem, or challenge that disrupts balance

Identification Method

## Identifying Complication

Look for "turning point" signal words:
- But, however, yet
- The problem is
- The challenge is
- Concerningly
- X situation emerged

Types:
1. External changes: market, technology, policy shifts
2. Internal problems: resource shortages, capability gaps
3. Expectation gaps: expectations vs. reality
4. Emerging threats: competition, risks

Quality Complication Characteristics

• ✅ Creates tension and urgency
• ✅ Clarifies "why change is needed"
• ✅ Contrasts with Situation
• ✅ Naturally leads to Question

Example

**Complication**:
"However, sudden widespread remote work exposed many problems:
- Managers struggle to assess team productivity
- Employees feel isolated and disconnected
- Company culture faces dilution risks
- Cybersecurity threats significantly increased"

Analysis:
- ✅ Contrasts with Situation
- ✅ Creates urgency
- ✅ Specific and tangible

Q - Question (Core Query)

Definition: The central question arising from the complication

Identification Method

## Identifying Question

Explicit questions:
- Questions article directly poses
- "How to...?"
- "Should we...?"

Implicit questions:
- Derived from S→C logic
- Questions author wants to answer but doesn't explicitly state

Question types:
1. Decision question: Should we do A or B?
2. Method question: How to achieve X?
3. Cause question: Why does Y happen?
4. Prediction question: What will happen?

Quality Question Characteristics

• ✅ Directly stems from Complication
• ✅ Specific and answerable
• ✅ Valuable to readers
• ✅ Sets scope for Answer

Example

**Question**:
"How should companies successfully transition to long-term remote work
while maintaining productivity?"

Analysis:
- ✅ Directly addresses C's problems
- ✅ Specific and actionable
- ✅ Sets scope (remote work)

A - Answer (Solution)

Definition: The solution or conclusion addressing the Question

Identification Method

## Identifying Answer

Look for:
- Article's core recommendations
- Proposed solutions
- Derived conclusions
- Action plans

Structure types:
1. Single solution: "The answer is X"
2. Multiple steps: "Need to do A, B, C"
3. Framework tool: "Use Y framework"
4. Guiding principles: "Follow Z principles"

Quality Answer Characteristics

• ✅ Directly answers Question
• ✅ Actionable or understandable
• ✅ Logically supported
• ✅ Considers implementation feasibility

Example

**Answer**:
"Successful transition requires four key steps:
1. Establish clear remote work policies and expectations
2. Invest in collaboration tech and security infrastructure
3. Train managers in asynchronous management
4. Create virtual social and culture-building mechanisms"

Analysis:
- ✅ Addresses Q's core need
- ✅ Structured and executable
- ✅ Covers multiple C problems

Application Methods

Method 1: Deconstruction Analysis (Understanding Articles)

# SCQA Deconstruction: [Article Title]

## S - Situation
[Extract and summarize article's background setup]
- Key fact 1
- Key fact 2
- Key fact 3

## C - Complication
[Identify problems/challenges article points out]
- Conflict 1
- Conflict 2
- Conflict 3

## Q - Question
[Clarify or infer article's core question]
Explicit: [Direct quote]
Implicit: [Derived from SC]

## A - Answer
[Summarize article's solution]
Core solution: [Summary]
Supporting points: [List]

## 🔍 Assessment

### Logical Completeness
- S→C: Transition natural?
- C→Q: Does question stem from complication?
- Q→A: Does answer address question?

### Quality Scoring
- S objectivity: [1-5]
- C urgency: [1-5]
- Q specificity: [1-5]
- A feasibility: [1-5]

### Identified Issues
- [ ] S too subjective
- [ ] C disconnected from S
- [ ] Q not explicitly stated
- [ ] A answers wrong question
- [ ] Logical leaps

Method 2: Restructuring (Improving Articles)

# SCQA Restructuring

## Original Structure Problems
- Issue 1: [e.g., Unclear Situation]
- Issue 2: [e.g., Jumps to Answer without setup]
- Issue 3: [e.g., Weak Complication]

## Optimized SCQA

### S - Situation (Improved)
[Reframe clearer background based on article info]

### C - Complication (Improved)
[Strengthen conflict, increase urgency]

### Q - Question (Improved)
[Clarify core question, focus discussion]

### A - Answer (Improved)
[Structure answer, enhance persuasiveness]

## Improvement Impact
Before: [Unclear in original]
After: [Clearer after optimization]

Method 3: Comparative Analysis (Multiple Articles)

# SCQA Comparison: Topic [X]

## Article 1
S: [Background]
C: [Conflict]
Q: [Question]
A: [Answer]

## Article 2
S: [Background]
C: [Conflict]
Q: [Question]
A: [Answer]

## Cross-Analysis

### S Differences
- Shared understanding: [What both acknowledge]
- Divergence: [Different perspectives]

### C Differences
- Article 1 emphasizes: [X problem]
- Article 2 emphasizes: [Y problem]
- Insight: Different C leads to different problem framing

### Q Differences
- Article 1 tries to answer: [...]
- Article 2 tries to answer: [...]
- Insight: Question setting determines answer space

### A Differences
- Solution comparison: [Similarities/differences]
- Complementarity: [Combinable parts]
- Conflicts: [Contradictions]

SCQA Variations

1. Standard (S-C-Q-A)

Stable background → Problem emerges → Question posed → Answer given

Use for: Problem-oriented articles

2. Direct Lead (A-S-C-Q-A)

State conclusion first → Explain background → Problem → Question → Detailed answer

Use for: Executive summaries, fast-paced reading

3. Suspense (C-S-Q-A)

Throw out conflict → Explain background → Pose question → Provide answer

Use for: Attention-grabbing, marketing articles

4. Exploratory (S-C-Q-A-Q-A)

Background → Problem 1 → Answer 1 → Deeper problem 2 → Answer 2

Use for: Complex problems requiring layered depth

Practical Example

Example: Startup Article

Article Title: "Why Most Startups Fail"

## SCQA Deconstruction

### S - Situation
Startup ecosystem has flourished over past 20 years.
Venture capital abundant, tech infrastructure mature,
barriers to entry dramatically lowered. Hundreds of thousands of new startups form annually.

### C - Complication
However, statistics show:
- 90% of startups fail within 3 years
- Failure rates rising, not declining
- Even well-funded companies struggle

"Why are failure rates higher today when conditions are better?"

### Q - Question
Implicit core question:
"What fundamental factors cause startup failure?
How to identify and avoid these fatal mistakes?"

### A - Answer
Article identifies three fatal issues:
1. Solving fake needs (42% of failures)
2. Running out of cash (29%)
3. Team problems (23%)

With corresponding solutions...

## Assessment

Logical completeness:
✅ S→C: Sharp contrast, creates suspense
✅ C→Q: Naturally leads to "why"
✅ Q→A: Answer highly targeted

Quality scoring:
- S: 4/5 (objective but could focus more)
- C: 5/5 (data-driven, creates urgency)
- Q: 4/5 (implicit question, should state explicitly)
- A: 4/5 (practical but needs more validation)

Improvement suggestions:
Explicitly state Q after C, don't let readers guess

Integration with Other Frameworks

SCQA + Pyramid Principle

# Structured Expression

SCQA: Set problem framework
├── S-C-Q: Introduce core question
└── A: Pyramid structure expansion
    ├── Point 1
    │   ├── Support 1.1
    │   └── Support 1.2
    ├── Point 2
    └── Point 3

SCQA + Critical Thinking

# Deep Analysis

Layer 1: SCQA identifies argument structure
Layer 2: Critical thinking evaluates each part
- Is S objective?
- Is C real?
- Is Q reasonable?
- Is A effective?

SCQA + 5W2H

# Completeness Check

SCQA: Understand overall structure
5W2H: Check detail completeness
- Is S's background sufficient (When, Where)?
- Is C's problem clear (What, Why)?
- Is A's solution feasible (How, How much, Who)?

Common Questions

Q1: What if article lacks obvious SCQA structure?

A: Proactive reconstruction

Even if article is messy, you can:
1. Extract information fragments
2. Categorize into SCQA buckets
3. Identify missing pieces
4. Reorganize understanding

Q2: Hard to distinguish S from C?

A: Key is "stability vs. change"

S: Stable background, mutually agreed
C: Change or problem disrupting balance

Test method:
- If you remove this sentence, does problem still exist?
  - Yes → Likely C
  - No → Likely S

Q3: Article has multiple SCQAs?

A: Layered analysis

Overall SCQA: Entire article
Sub-SCQAs: Each section

Example:
Overall: S-C-Q-A
└── Section 1: S1-C1-Q1-A1
└── Section 2: S2-C2-Q2-A2

Practice Exercises

Exercise 1: Daily SCQA Deconstruction

Choose one article, spend 10 minutes identifying SCQA

Exercise 2: Elevator Pitch

Use 30 seconds to introduce any topic in SCQA structure:

• 5 sec: S
• 10 sec: C
• 5 sec: Q
• 10 sec: A

Exercise 3: Comparative Reading

For 2-3 articles on same topic, compare SCQA differences

Exercise 4: Restructure Writing

Take your own writing, reorganize using SCQA

Key Quotes

"Structure creates clarity. Clarity creates impact."

"Good structure makes complex ideas simple.

Bad structure makes simple ideas complex."

"SCQA doesn't limit creativity—

it makes your ideas easier to understand."

---

Remember: SCQA is a thinking tool, not a writing formula. Use flexibly to serve clarity and deep understanding.

Six Thinking Hats Framework

Overview

Structured method to examine ideas from six distinct perspectives. Wear one hat at a time to avoid confusion.

Purpose: Separate thinking modes, reduce conflict, ensure comprehensive analysis.

The Six Hats

🎩 White Hat: Facts & Data

Focus: Objective information only

Questions:

• What facts do we have?
• What data is available?
• What information is missing?
• What are the numbers?
• How do we verify this?

Language:

• "According to..."
• "The data shows..."
• "We know that..."
• "We don't know..."

In Content Analysis:

• Extract all factual claims
• Note cited sources
• Identify missing data
• Separate facts from interpretations

Template:

## Known Facts
- [Verifiable fact 1]
- [Verifiable fact 2]

## Missing Information
- [ ] [Gap 1]
- [ ] [Gap 2]

## Data Sources
- [Citation 1]: [Quality rating]

---

🎩 Red Hat: Emotions & Intuition

Focus: Gut feelings, hunches, intuitive responses

Questions:

• What's my immediate reaction?
• What does my gut say?
• What emotions does this evoke?
• What's my intuition telling me?

Language:

• "I feel that..."
• "My gut says..."
• "This makes me uncomfortable because..."
• "I'm excited about..."

In Content Analysis:

• Note emotional response while reading
• Identify what triggers strong feelings
• Trust instincts about credibility
• Recognize persuasive emotional appeals in text

Template:

## Immediate Reactions
- [Emotion] at [specific part]

## Gut Feelings
- Something feels off about: [intuition]
- Exciting/Compelling: [what resonates]

## Emotional Triggers in Text
- Author uses [emotion] to persuade

Important: No justification needed. This is pure feeling.

---

🎩 Black Hat: Caution & Risks

Focus: Critical judgment, potential problems

Questions:

• What could go wrong?
• What are the risks?
• What's unrealistic?
• Where's the weakness?
• What are the downsides?

Language:

• "A problem is..."
• "This won't work because..."
• "The risk here is..."
• "We're overlooking..."

In Content Analysis:

• Identify logical flaws
• Note unsupported claims
• Point out potential failures
• Question feasibility
• Consider unintended consequences

Template:

## Logical Weaknesses
- [Flaw 1] in reasoning

## Risks If Applied
- Risk: [consequence]
- When it fails: [scenario]

## Missing Considerations
- Doesn't account for: [factor]

## Overly Optimistic Claims
- [Claim] seems unrealistic because [reason]

Important: This is critical, not cynical. Necessary for risk assessment.

---

🎩 Yellow Hat: Benefits & Optimism

Focus: Positive aspects, value, opportunities

Questions:

• What's the value here?
• What are the benefits?
• Why would this work?
• What's the best-case scenario?
• What opportunities does this create?

Language:

• "The benefit is..."
• "This could work because..."
• "The value here is..."
• "An opportunity is..."

In Content Analysis:

• Extract valuable insights
• Identify strong arguments
• Note practical applications
• Find novel perspectives
• Recognize what advances the field

Template:

## Key Value Propositions
- Valuable insight: [what's useful]

## Strong Points
- Well-supported: [argument]

## Potential Applications
- Could be used for: [use case]

## Novel Contributions
- New perspective on: [topic]

## Best-Case Outcome
If fully applied: [positive scenario]

Important: Be realistic but generous. Find genuine value.

---

🎩 Green Hat: Creativity & Alternatives

Focus: New ideas, possibilities, innovations

Questions:

• What else is possible?
• How else could we think about this?
• What's a creative alternative?
• What if we combined X with Y?
• What's unconventional?

Language:

• "What if..."
• "Another way to look at it..."
• "We could also..."
• "An alternative is..."

In Content Analysis:

• Extend the author's ideas further
• Generate alternatives to proposed solutions
• Combine with other frameworks
• Apply to new domains
• Challenge assumptions creatively

Template:

## Extensions of Ideas
- Taking [concept] further: [new application]

## Alternative Approaches
Instead of [author's method], what if: [alternative]

## Creative Combinations
- [Idea from text] + [other framework] = [new insight]

## Unconventional Applications
- Apply this to [unexpected domain]

## "What If" Scenarios
- What if [assumption] were reversed?

Important: No criticism in green hat mode. All ideas welcome.

---

🎩 Blue Hat: Process & Meta-Thinking

Focus: Managing thinking, overview, conclusions

Questions:

• What have we covered?
• What thinking mode do we need now?
• What's the summary?
• What's next?
• How should we think about this?

Language:

• "We've covered..."
• "The next step is..."
• "In summary..."
• "We need to focus on..."

In Content Analysis:

• Decide which hats to use when
• Synthesize findings from all hats
• Determine next steps
• Plan learning strategy
• Monitor the analysis process

Template:

## Analysis Process
1. White: Gathered facts
2. Red: Noted reactions  
3. Black: Identified risks
4. Yellow: Found value
5. Green: Generated alternatives

## Synthesis
Combining all perspectives:
- [Integrated insight]

## Next Steps
- [ ] Further research: [area]
- [ ] Practical test: [action]
- [ ] Deep dive: [topic]

## Time Investment
Worth [X] time because [reason]

Important: Blue hat organizes the other hats. It's the conductor.

---

Usage Patterns

Quick Evaluation (15 min)

White → Red → Yellow → Black → Blue

Deep Analysis (60 min)

White → Red → Black → Yellow → Green → Blue → (Revisit any hat) → Blue

Problem-Solving

White → Red → Green → Yellow → Black → Green → Blue

Decision-Making

White → Yellow → Black → Red → Blue

Rules of Engagement

1. One hat at a time - Don't mix modes 2. Everyone wears same hat - Parallel thinking (if group) 3. Separate person from hat - You're not "the critical person," you're wearing black hat 4. Time-box - Set limits per hat 5. Blue hat controls - Decides sequence and timing

Common Mistakes

❌ Mixing hats - "This is good (yellow) but risky (black)" ✅ Separate: Yellow session: "This is good because X." Then Black session: "The risk is Y."

❌ Judging feelings - "That's irrational" during red hat ✅ Accept feelings: All emotions noted without judgment

❌ Weak yellow - "I guess there's some value..." ✅ Genuine optimism: Really find the good

❌ Staying too long - 30 min per hat ✅ Move on: 5-10 min per hat usually sufficient

Application to Reading

When to use which hat:

• Understanding stage: White (facts), Red (reactions)
• Evaluation stage: Black (critique), Yellow (value)
• Application stage: Green (ideas), Blue (synthesis)

Full Cycle: 1. White: What does the text actually say? 2. Red: How do I feel about it? 3. Black: What's wrong with it? 4. Yellow: What's right with it? 5. Green: What else could we do with this? 6. Blue: So what? Now what?

Integration with Other Models

• After First Principles: Use hats to evaluate rebuilt argument
• After Systems Mapping: Use yellow/black on leverage points
• Before Critical Thinking: Use red to surface biases
• During Synthesis: Use blue to organize findings

Output Format

# Six Hats Analysis: [Content Title]

## 🎩 White: Facts
[Objective data]

## 🎩 Red: Feelings  
[Emotional response]

## 🎩 Black: Cautions
[Risks and weaknesses]

## 🎩 Yellow: Benefits
[Value and opportunities]

## 🎩 Green: Possibilities
[Creative extensions]

## 🎩 Blue: Conclusions
[Synthesis and next steps]

Systems Thinking Framework

Core Principle

Understand parts in relation to the whole. Systems are more than the sum of parts due to interactions.

Key System Elements

1. Components (Elements)

The individual parts of the system

2. Relationships (Interconnections)

How components influence each other

3. Purpose (Function)

What the system is designed to achieve

4. Boundaries

What's inside vs. outside the system

Causal Loop Analysis

Reinforcing Loop (Positive Feedback)

Creates exponential growth or collapse

A increases → B increases → A increases further → ...

Examples:

• Network effects: More users → More value → More users
• Panic: Fear → Selling → Price drop → More fear
• Expertise: Skill → Opportunities → More practice → More skill

Symbol: R (Reinforcing)

Balancing Loop (Negative Feedback)

Creates stability and resistance to change

A increases → B increases → A decreases → B decreases → ...

Examples:

• Thermostat: Temp up → Heating off → Temp down → Heating on
• Supply/Demand: Price up → Demand down → Price down
• Homeostasis: Blood sugar up → Insulin up → Blood sugar down

Symbol: B (Balancing)

Mapping Template

## System Components
- Component A: [Role/function]
- Component B: [Role/function]
- Component C: [Role/function]

## Key Relationships

[A] ──+──> [B]  (A increases B)
       |
       └──-──> [C]  (A decreases C)

## Feedback Loops

### Loop 1: [Name] (R/B)
A → B → C → A
Effect: [Exponential growth / Stabilization]

## System Behavior Over Time

Current state: [X]
If X increases: [Trace effects through system]
If X decreases: [Trace effects through system]

Leverage Points

Places to intervene (Donella Meadows' hierarchy, strongest to weakest):

1. Paradigms - Mental models underlying the system 2. Goals - Purpose of the system 3. System structure - Feedback loop architecture 4. Delays - Response time between cause and effect 5. Balancing loops - Strength of stabilizing forces 6. Reinforcing loops - Strength of amplifying forces 7. Information flows - Who knows what, when 8. Rules - Incentives, constraints 9. Buffers - Stabilizing stocks 10. Stock-flow structures - Physical components 11. Parameters - Numbers (least effective)

Insight: Most people tweak parameters (#11), but changing paradigms (#1) is far more powerful.

Cross-Domain Pattern Recognition

Similar System Patterns Across Fields

Tragedy of the Commons:

• Environment: Overfishing
• Digital: Bandwidth congestion
• Social: Public resource depletion
• Organizational: Shared resource competition

Network Effects:

• Technology: Social media platforms
• Economics: Currency adoption
• Language: English as lingua franca
• Standards: USB-C adoption

Limits to Growth:

• Biology: Population dynamics
• Business: Market saturation
• Personal: Skill plateaus
• Resources: Oil production peak

Analysis Questions

Structure

• What are the key components?
• What connects them?
• Where are the feedback loops?

Behavior

• What patterns emerge over time?
• What's amplifying? (Reinforcing loops)
• What's stabilizing? (Balancing loops)

Dynamics

• What happens if X increases 10x?
• Where are delays causing problems?
• What's the bottleneck?

Boundaries

• What's outside this system but affects it?
• Where do we draw the line?
• What external factors matter?

Systems Archetypes

1. Shifting the Burden

Short-term fix → Undermines long-term solution Example: Taking painkillers (symptom) vs. fixing posture (cause)

2. Escalation

Both sides respond to each other, spiraling up Example: Arms race, price wars, social media arguments

3. Success to the Successful

Winner gets advantages that compound Example: Rich get richer, bestseller lists, platform dominance

4. Fixes That Fail

Solution works initially but creates worse problem Example: Antibiotic resistance, traffic lanes inducing demand

5. Growth and Underinvestment

Growth stalls because capacity wasn't built Example: Startup success → Can't scale → Service degrades

Application to Content Analysis

When reading about any topic:

1. Map the system

• List key elements mentioned
• Draw connections between them

2. Identify loops

• What reinforces growth/decline?
• What creates balance/limits?

3. Predict dynamics

• If X changes, what cascades follow?
• Where will this lead in 1 year? 5 years?

4. Find leverage

• Where is the author intervening?
• Are there better leverage points?

5. Connect to other domains

• What similar patterns exist elsewhere?
• Can solutions from other fields apply?

Cross-Reference to Other Fields

## Concept in Article
[Core idea from content]

## Similar Patterns In:

**Economics:** [How this shows up]
**Biology:** [How this shows up]  
**Psychology:** [How this shows up]
**Technology:** [How this shows up]
**History:** [How this shows up]

## Transferable Insights
If this pattern exists across domains, then:
- [Universal principle 1]
- [Universal principle 2]

Warning: Systems Thinking Pitfalls

• Over-complicating: Not everything needs a full system map
• Analysis paralysis: Perfect map vs. good enough understanding
• Ignoring human agency: People can change system rules
• Determinism: Systems have probability, not certainty
• Closed thinking: Real systems have open boundaries

Balance: Use systems thinking to understand dynamics, not to predict perfectly.