Thought Patterns

Thought Patterns Orchestration Skill

This skill provides access to a comprehensive library of human cognitive thinking patterns. It includes an intelligent orchestration system that selects and chains appropriate patterns based on task requirements.

Quick Reference: When to Load Which Resource

Orchestration Protocol

Phase 1: Task Analysis

Before selecting a pattern, analyze the task:

Task Type Classification:

• Analytical: Breaking down complex information, logical reasoning → Load foundational
• Creative: Novel ideas, innovative solutions → Load creative
• Exploratory: Investigating possibilities, understanding relationships → Load reasoning
• Strategic: Planning, decision-making, optimization → Load foundational + metacognitive
• Reflective: Learning from experience, examining assumptions → Load metacognitive
• Explanatory: Root causes, generating hypotheses → Load reasoning
• Integrative: Combining perspectives, synthesis → Load multiple resources

Complexity Indicators:

• Single vs. multiple objectives
• Well-defined vs. ambiguous constraints
• Known vs. unknown solution space
• Independent vs. interdependent components

Phase 2: Pattern Selection

Based on task analysis, load the appropriate resource file(s) and select patterns:

• Single Pattern: When task clearly maps to one approach
• Sequential Chain: When one pattern feeds into another (e.g., divergent → convergent)
• Parallel Patterns: When multiple simultaneous perspectives add value
• Iterative Loop: When refinement through repeated application is needed

Phase 3: Execution & Validation

During Execution:

• Explicitly apply the selected pattern(s)
• Show your work when beneficial to user understanding
• Monitor whether the pattern is yielding progress
• Switch patterns if current approach is ineffective

Before Responding:

• Validate completeness: Did you address all aspects of the task?
• Check coherence: Does the output logically follow from the thinking process?
• Assess quality: Does this meet the standard the user expects?

Pattern Selection Heuristics

By Problem Type

Well-Defined Problems → Load foundational-patterns.md

• Sequential, Analytical, Deductive, Convergent patterns

Ill-Defined Problems → Load creative-patterns.md + reasoning-patterns.md

• Divergent, Lateral, Abductive, Design Thinking patterns

Complex Systems → Load foundational-patterns.md

• Systems Thinking, Holistic/Gestalt, Parallel Processing patterns

Creative Tasks → Load creative-patterns.md

• Divergent, Lateral, Associative, Analogical patterns

Learning/Improvement → Load metacognitive-patterns.md

• Reflective, Metacognitive, Double-Loop Learning patterns

Strategic Decisions → Load foundational-patterns.md + reasoning-patterns.md

• Big-Picture, Systems, Counterfactual, First Principles patterns

Detailed Analysis → Load foundational-patterns.md + neurodivergent-strengths.md

• Analytical, Detail-Oriented Pattern Recognition, Critical Thinking

Quick Responses → No resource load needed

• System 1, Pattern Recognition, Associative

Important/Novel Decisions → Load metacognitive-patterns.md + reasoning-patterns.md

• System 2, Critical, Analytical, First Principles patterns

Neurodivergent Pattern Integration

Always consider whether neurodivergent patterns might enhance the solution:

• ADHD patterns (Hyperfocus, Big-Picture): For engaging problems requiring sustained effort or strategic overview
• Autism patterns (Detail-Oriented): For precision, consistency, pattern finding
• Dyslexia patterns (Spatial/Visual): For spatial problems, visual creativity, 3D reasoning
• Non-Linear Associative: For creative breakthroughs, cross-domain insights

→ Load resources/neurodivergent-strengths.md when these would add value

Common Pattern Chains

For complex tasks requiring multiple patterns, see resources/pattern-combinations.md for detailed examples:

1. Creative Problem-Solving: Divergent → Convergent 2. Root Cause Analysis: Analytical → Abductive → Systems 3. Innovation: First Principles → Lateral → Design Thinking 4. Learning: Reflective → Double-Loop → Metacognitive 5. Comprehensive Understanding: Analytical → Gestalt → Systems 6. Strategic Decision: Big-Picture → Analytical → Counterfactual

Resource Files Summary

resources/foundational-patterns.md

• Sequential/Linear Thinking
• Analytical Thinking
• Critical Thinking
• Systems Thinking
• Gestalt/Holistic Perception

resources/reasoning-patterns.md

• Deductive Reasoning
• Inductive Reasoning
• Abductive Reasoning
• Analogical Reasoning
• Counterfactual Reasoning
• First Principles Thinking

resources/creative-patterns.md

• Divergent Thinking
• Convergent Thinking
• Lateral Thinking
• Associative Thinking

resources/metacognitive-patterns.md

• Metacognitive Thinking
• Reflective Thinking
• Double-Loop Learning
• Triple-Loop Learning
• System 1 Thinking (Fast, Intuitive)
• System 2 Thinking (Slow, Analytical)

resources/specialized-patterns.md

• Design Thinking
• Constraint-Based Thinking
• Parallel Processing
• Iterative Refinement

resources/neurodivergent-strengths.md

• ADHD-Associated Patterns (Hyperfocus, Big-Picture)
• Autism-Associated Patterns (Detail-Oriented Pattern Recognition)
• Dyslexia-Associated Patterns (Spatial/Visual Thinking)
• Non-Linear Associative Thinking

resources/pattern-combinations.md

• Detailed examples of pattern chaining
• Multi-pattern execution walkthroughs
• Pattern selection decision tree

---

Remember: This is a tool for enhancing thinking, not a rigid prescription. Stay flexible, monitor effectiveness, and adapt as needed. Load only the resources you need for the current task.

Creative & Exploratory Patterns

This resource covers thinking patterns used for generating ideas, exploring possibilities, and finding innovative solutions.

Divergent Thinking

Description: Generating many possible solutions through spontaneous, free-flowing exploration of possibilities.

When to Use:

• Brainstorming
• Creative ideation
• Exploring solution space
• Overcoming mental blocks

Process: 1. Suspend judgment and evaluation 2. Generate many ideas rapidly 3. Encourage wild and unusual ideas 4. Build on others' ideas (in group settings) 5. Explore unexpected connections

Characteristics:

• Spontaneous and free-flowing
• Non-linear
• Quantity over quality (initially)
• Emergent, unexpected connections
• No "wrong" answers

Guidelines for Effective Divergence:

• Defer judgment completely
• Go for quantity (aim for many ideas)
• Welcome wild ideas
• Combine and improve ideas
• Stay visual and playful

Limitations: Without convergent follow-up, may not reach actionable solution.

---

Convergent Thinking

Description: Focusing on finding the single best solution through logical reasoning, pattern recognition, and systematic analysis.

When to Use:

• Selecting among alternatives
• Finalizing decisions
• Applying known methods
• Optimizing solutions

Process: 1. Gather possible solutions 2. Apply criteria and constraints 3. Eliminate incorrect/inferior options 4. Use logical reasoning to narrow down 5. Identify optimal solution

Cognitive Processes:

• Logical reasoning
• Attention and focus
• Memory retrieval
• Pattern recognition
• Decision-making

Relationship to Divergent: Creativity often requires sequential use:

Divergent (explore) → Convergent (select) → Divergent (refine) → Convergent (finalize)

Limitations: May prematurely close on suboptimal solution; less effective when multiple good solutions exist.

---

Lateral Thinking

Description: Solving problems through indirect, creative approaches; deliberately seeking non-obvious angles.

When to Use:

• Stuck on problem with standard approaches
• Innovation needed
• Challenging assumptions
• Seeking breakthrough insights

Process: 1. Identify the dominant thinking pattern 2. Deliberately challenge it 3. Use provocations and random input 4. Make unexpected connections 5. Restructure problem

Techniques:

Random Entry

• Introduce random word/concept
• Force connections to problem
• Discover new angles

Provocation (Po)

• Make deliberately provocative statement
• "What if cars had square wheels?"
• Use absurdity to escape conventional thinking

Challenge Assumptions

• List all assumptions about the problem
• Systematically question each one
• Ask "Why does it have to be this way?"

Reversal

• State the opposite of the problem
• "Instead of making customers come to us, what if we went to them?"

Analogy

• Find analogous situations in different domains
• Transfer solutions across contexts

Relationship to Divergent: Divergent thinking encourages lateral thinking in its processes.

Limitations: Can seem unfocused; may generate many non-viable ideas.

---

Associative Thinking

Description: Making connections between seemingly unrelated concepts through mental networks.

When to Use:

• Creative problem-solving
• Ideation and brainstorming
• Finding unexpected solutions
• Connecting disparate knowledge

Process: 1. Start with focal concept 2. Allow mind to make loose connections 3. Follow associative chains 4. Identify surprising connections 5. Evaluate relevance to problem

Association Types:

• Semantic: Words with related meanings
• Phonetic: Words that sound similar
• Experiential: Concepts linked through experience
• Emotional: Concepts with shared emotional tone
• Structural: Patterns that share form

Note: Particularly strong in some neurodivergent individuals (non-linear associative patterns). See neurodivergent-strengths.md for more.

Limitations: Can be scattered without disciplined focus.

---

The Divergent-Convergent Cycle

Most creative work requires cycling between these modes:

┌─────────────┐     ┌─────────────┐
│  Divergent  │────▶│  Convergent │
│  (Explore)  │◀────│  (Select)   │
└─────────────┘     └─────────────┘
       │                   │
       │    ┌─────────┐    │
       └───▶│ Iterate │◀───┘
            └─────────┘

Phase 1: Diverge

• Open up possibilities
• No judgment
• Quantity matters
• Wild ideas welcome

Phase 2: Converge

• Apply criteria
• Evaluate feasibility
• Select best options
• Refine choices

Phase 3: Iterate

• Prototype/test
• Gather feedback
• Diverge again on improvements
• Converge on final solution

---

Pattern Combinations

Quick Reference

Foundational Analytical & Systems Patterns

This resource covers the core analytical and systems thinking patterns used for breaking down problems, systematic evaluation, and understanding complex wholes.

Sequential/Linear Thinking

Description: Step-by-step progression through a problem, where each step builds on the previous one.

When to Use:

• Procedures with defined steps
• Tasks requiring specific ordering
• Following algorithms or protocols
• Debugging (trace execution flow)

Process: 1. Identify starting point and end goal 2. Break down into ordered steps 3. Execute each step before moving to next 4. Verify each step before proceeding

Limitations: May miss non-obvious connections; struggles with circular dependencies or emergent properties.

---

Analytical Thinking

Description: Breaking down complex problems into constituent components for detailed examination.

When to Use:

• Understanding complex systems
• Root cause analysis
• Data interpretation
• Technical troubleshooting

Process: 1. Decompose whole into parts 2. Examine each part in detail 3. Understand relationships between parts 4. Synthesize findings

Limitations: Can lose sight of emergent whole-system properties; may over-focus on details.

---

Critical Thinking

Description: Systematic evaluation of information, claims, and arguments for validity and reliability.

When to Use:

• Evaluating sources and evidence
• Detecting logical fallacies
• Assessing argument strength
• Making informed decisions

Process: 1. Identify claims and assumptions 2. Evaluate evidence quality 3. Examine logical structure 4. Consider alternative interpretations 5. Form reasoned judgment

Limitations: Can be time-intensive; may lead to analysis paralysis.

---

Systems Thinking

Description: Understanding how components interact within larger wholes, focusing on relationships, feedback loops, and emergent properties.

When to Use:

• Interconnected problems
• Unintended consequences analysis
• Long-term impact assessment
• Organizational or ecosystem challenges

Process: 1. Identify system boundaries 2. Map components and relationships 3. Identify feedback loops (reinforcing/balancing) 4. Recognize delays and non-linearities 5. Consider emergence and system behavior 6. Use DSRP framework: Distinctions, Systems, Relationships, Perspectives

Key Skills:

• Dynamic thinking: Understanding how systems evolve over time
• System-as-cause thinking: Recognizing system structure drives behavior
• Holistic thinking: Seeing whole systems, not just parts
• Operational thinking: Understanding how things actually work
• Closed-loop thinking: Recognizing feedback effects
• Stock-and-flow thinking: Distinguishing accumulations from flows

Limitations: Can be overwhelming with complex systems; requires significant cognitive load.

---

Gestalt/Holistic Perception

Description: Processing entire patterns and configurations rather than individual components; the whole is different from the sum of parts.

When to Use:

• Pattern recognition tasks
• Visual/spatial problems
• Understanding overall meaning or structure
• Insight problems requiring restructuring

Process: 1. Take in the whole configuration 2. Identify overall patterns and structures 3. Notice relationships and groupings (proximity, similarity, continuity) 4. Allow holistic understanding to emerge 5. Restructure problem elements if needed

Gestalt Principles:

• Similarity: Similar elements are grouped together
• Proximity: Close elements are grouped together
• Continuity: Elements on a line/curve are related
• Closure: Incomplete shapes are perceived as complete
• Figure-ground: Distinguishing foreground from background

Limitations: May miss important details; can be influenced by perceptual biases.

---

Pattern Combinations

These patterns work well together:

Quick Reference

Metacognitive & Learning Patterns

This resource covers patterns for thinking about thinking, learning from experience, and the dual-process model of cognition.

Metacognitive Thinking

Description: Thinking about one's own thinking; awareness and regulation of cognitive processes.

When to Use:

• Learning new skills
• Improving problem-solving
• Monitoring understanding
• Self-regulation

Process: 1. Monitor your thinking processes 2. Evaluate effectiveness of strategies 3. Identify strengths and weaknesses 4. Adjust approach as needed 5. Reflect on learning

Key Aspects:

Metacognitive Knowledge

• Person: Understanding your own cognitive abilities
• Task: Understanding what different tasks require
• Strategy: Knowing which strategies work for which situations

Metacognitive Monitoring

• Awareness of comprehension
• Detecting errors
• Recognizing when you're stuck
• Assessing confidence

Metacognitive Control

• Selecting strategies
• Allocating resources (time, effort)
• Adjusting approach when needed
• Knowing when to seek help

Relationship to Systems Thinking: Metacognition is an important aspect of systems thinking; requires "deliberately structuring one's thoughts."

Limitations: Can create cognitive overhead; may interfere with flow states.

---

Reflective Thinking

Description: Carefully considering experiences, actions, and their outcomes to derive understanding.

When to Use:

• Learning from experience
• After completing projects
• Processing feedback
• Continuous improvement

Process: 1. Describe: What happened? What did I do? 2. Analyze: What happened and why? 3. Evaluate: What went well? What didn't? 4. Consider: What alternatives existed? 5. Plan: How will I apply this learning?

Gibbs' Reflective Cycle:

Description → Feelings → Evaluation → Analysis → Conclusion → Action Plan

Questions for Reflection:

• What was I trying to achieve?
• What did I actually achieve?
• What surprised me?
• What would I do differently?
• What did I learn about myself?

Limitations: Requires honesty and time; can be uncomfortable.

---

Double-Loop Learning

Description: Not just improving how you execute (single-loop), but questioning and modifying the underlying assumptions and goals.

When to Use:

• Persistent problems despite efforts
• When assumptions may be flawed
• Organizational learning
• Deep improvement needed

Process: 1. Identify the problem/gap 2. Examine current approach (single-loop: "Am I doing this right?") 3. Question underlying assumptions (double-loop: "Is this the right thing to do?") 4. Test validity of assumptions 5. Modify goals or decision rules as needed 6. Implement revised approach

Single-Loop vs Double-Loop:

Example:

• Single-loop: "How can I write faster documentation?"
• Double-loop: "Why are we writing so much documentation? Is it being read? Do we need a different approach entirely?"

Relationship to First Principles: May use first principles thinking to challenge assumptions.

Limitations: Challenging; may threaten established beliefs or practices.

---

Triple-Loop Learning

Description: Beyond questioning assumptions, examining and potentially transforming the context, principles, and purpose itself.

When to Use:

• Paradigm shifts needed
• Fundamental transformation
• Strategic reorientation
• Deep systemic change

Process: 1. Engage in double-loop learning 2. Question the wider context and principles 3. Examine "Why do we do what we do?" 4. Consider purpose and identity 5. Transform fundamental understanding

The Three Loops:

Single-Loop:  Actions → Results → Adjust Actions
Double-Loop:  Actions → Results → Question Assumptions → Change Rules
Triple-Loop:  Actions → Results → Question Assumptions → Transform Context/Purpose

Questions for Triple-Loop:

• Why does this organization/system exist?
• What are we fundamentally trying to achieve?
• Are our core values still appropriate?
• What would a completely different approach look like?

Limitations: Rare; can be destabilizing.

---

System 1 Thinking (Fast, Intuitive)

Description: Automatic, rapid, unconscious processing based on pattern recognition and heuristics.

When to Use:

• Familiar situations
• Time-pressured decisions
• Pattern recognition
• Intuitive judgments

Characteristics:

• Fast and automatic
• Effortless
• Emotional
• Relies on heuristics
• Parallel processing
• Always "on"

Strengths:

• Quick responses
• Efficient for common situations
• Good at pattern matching
• Doesn't deplete cognitive resources
• Excellent for expert intuition (in experts' domains)

Limitations:

• Vulnerable to cognitive biases
• Not good for novel problems
• Can be overconfident
• Susceptible to framing effects
• Mistakes correlation for causation

Common Biases:

• Availability heuristic
• Anchoring
• Confirmation bias
• Halo effect
• WYSIATI (What You See Is All There Is)

---

System 2 Thinking (Slow, Analytical)

Description: Deliberate, conscious, effortful processing involving logical reasoning and analysis.

When to Use:

• Complex problems
• Unfamiliar situations
• Important decisions
• Requiring justification

Characteristics:

• Slow and effortful
• Conscious and deliberate
• Logical
• Rule-based
• Sequential processing
• Limited capacity

Strengths:

• Accurate for complex reasoning
• Can override biases
• Handles novelty well
• Produces justifiable conclusions
• Can follow explicit rules

Limitations:

• Mentally taxing
• Slow
• Limited capacity (can only do one effortful task at a time)
• Lazy (defaults to System 1 when possible)
• Requires motivation to engage

---

System 1 + System 2 Integration

The most effective thinking often involves both systems:

Complementary Use

System 1: Generates intuitions, first impressions
System 2: Checks, validates, reasons through complexities

When to Trust System 1

• You have significant expertise in the domain
• The environment provides rapid, clear feedback
• The situation is similar to past experiences
• Quick response is needed

When to Engage System 2

• The stakes are high
• The situation is novel
• Your intuition feels "off"
• You need to justify your decision
• Time is available for deliberation

Calibration Process

1. Notice your System 1 response 2. Ask: "Should I trust this intuition?" 3. If uncertain or high-stakes, engage System 2 4. Use System 2 to validate or override System 1 5. Over time, train System 1 with System 2 conclusions

---

Pattern Combinations

Quick Reference

Neurodivergent Cognitive Strengths: Research Summary

This document provides detailed research findings on cognitive patterns and strengths associated with neurodivergent conditions. These patterns represent tendencies and strengths, not universal characteristics—neurodivergence is highly individual.

Related Resources: These patterns integrate with all other thinking patterns. See the main SKILL.md for orchestration guidance. Particularly complementary with patterns in foundational-patterns.md (Systems, Gestalt) and creative-patterns.md (Associative, Lateral).

Key Principle: Cognitive Diversity as Strength

Around 15% of people are neurodivergent, meaning their brains function differently from what society considers "typical." This cognitive diversity brings distinct advantages in problem-solving, creativity, and specialized reasoning.

Important: Even when there's a consistent pattern that is statistically more likely in a specific area of neurodivergence, they are not hard and fast rules. Individual variation is substantial.

ADHD-Associated Patterns

Strengths and Characteristics

Creativity and Quick Thinking: Those with ADHD often display high levels of creativity, quick thinking, and the ability to make novel connections across domains.

Big Picture Thinking: Research suggests folks with ADHD often tend to do better on big picture tasks. There is overlap between ADHD and dyslexia in big picture thinking, suggesting this is a shared cognitive strength.

Hyperfocus: When engaged with tasks of high interest, individuals with ADHD can demonstrate exceptional sustained concentration, blocking out distractions and achieving deep immersion. This can lead to extraordinary productivity and insight on engaging problems.

Challenges

• Difficulty with organization and sustained attention on low-interest tasks
• Struggles with sitting still or maintaining focus in unstimulating environments
• Need for external structure and reminders

Optimal Use Cases

• Creative problem-solving requiring novel approaches
• Strategic planning and high-level thinking
• Tasks that are genuinely engaging or personally meaningful
• Situations benefiting from rapid ideation
• Roles requiring quick pattern recognition across domains

Autism-Associated Patterns

Strengths and Characteristics

Exceptional Pattern Recognition: Those with autism often excel at recognizing patterns and attention to detail, especially in fields like mathematics, music, or data analysis.

Detail Orientation: Individuals with autism spectrum disorder (ASD) often possess an exceptional ability to focus on intricate details and identify patterns that others might miss, making them invaluable assets in data analysis, scientific research, and quality control.

Systematic Processing: Natural tendency toward systematic, consistent approaches to problems. High value placed on accuracy and thoroughness.

Deep Focus: Ability to sustain attention on areas of interest with exceptional depth and persistence.

Challenges

• May struggle with ambiguity or "good enough" standards
• Can be time-consuming due to thoroughness
• Preference for clear structure and expectations

Optimal Use Cases

• Data analysis and pattern identification
• Quality assurance and consistency checking
• Debugging and troubleshooting
• Scientific research requiring systematic investigation
• Mathematics, music, and other pattern-intensive domains
• Situations where precision and accuracy are critical

Dyslexia-Associated Patterns

Strengths and Characteristics

Spatial and Visual Thinking: People with dyslexia usually have brains that are better at processing or mentally picturing 3D objects, making them much faster at identifying optical illusions. They have a natural talent for jobs like graphic design and arts, engineering and more.

Advanced Reasoning: 84% of dyslexic people are above average in reasoning, understanding patterns, evaluating possibilities and making decisions.

Big Picture Orientation: Strong tendency toward holistic, overview-level understanding. Natural ability to see the forest rather than getting lost in trees.

Creative Problem-Solving: Enhanced ability to think outside conventional pathways, find novel solutions, and approach problems from unique angles.

Challenges

• May struggle with verbal/textual processing
• Reading and writing can be more effortful
• Need for visual supports and alternative information formats

Optimal Use Cases

• Graphic design, architecture, and engineering
• Spatial reasoning and 3D modeling
• Visual creativity and artistic work
• Strategic planning and big-picture analysis
• Pattern evaluation and decision-making
• Innovation requiring unconventional approaches

Cross-Condition Patterns

Non-Linear Associative Thinking

Present across multiple forms of neurodivergence, this pattern involves making connections across domains in unexpected, non-sequential ways. This can lead to:

• Creative breakthroughs
• Cross-domain insights
• Novel problem solutions
• Innovation through unexpected connections

Variability: There did not seem to be a consistent pattern on visualization with any specific neurodivergence, as folks with ADHD and Autism seemed to be equally likely to say they thought in words, pictures, a combination or something else intangible.

Integration with Neurotypical Patterns

Neurodivergent patterns are not separate from "standard" cognitive patterns—they are additional cognitive strategies that can enhance problem-solving:

Complementary Combinations

1. Detail-Oriented Pattern Recognition + Big-Picture Thinking:

• Combine autistic detail strength with ADHD/dyslexic strategic overview
• Achieve both precision and strategic insight

2. Hyperfocus + Analytical Thinking:

• Use ADHD hyperfocus to sustain deep analytical work
• Achieve exceptional depth on engaging analytical problems

3. Spatial/Visual Thinking + Systems Thinking:

• Leverage dyslexic spatial strength for system visualization
• Understand complex system relationships through visual models

4. Non-Linear Associative + First Principles:

• Use associative creativity to challenge fundamental assumptions
• Generate breakthrough innovations

Practical Guidelines

When to Consider Neurodivergent Patterns

For any task, ask:

• Would exceptional detail-orientation help? → Consider autistic patterns
• Would big-picture or spatial thinking add value? → Consider ADHD/dyslexic patterns
• Is this problem engaging enough to warrant hyperfocus? → Consider ADHD hyperfocus
• Could non-linear connections generate insights? → Consider associative thinking

Creating Neurodiversity-Friendly Approaches

When solving problems, consider:

1. Multiple Modalities: Offer both visual and textual representations 2. Flexibility: Allow for both sequential and non-linear approaches 3. Depth Options: Support both quick overview and deep detail exploration 4. Interest Alignment: Frame problems to maximize engagement where possible

Research Sources

This document synthesizes findings from multiple sources on neurodivergent thinking patterns:

Key Findings Sources

• Neurodivergent Thinking Patterns - Embracing Intensity: Comprehensive overview of ADHD, autism, and dyslexia cognitive styles
• The Neurodivergent Spectrum - Counseling Center Group: Guide to cognitive diversity across conditions
• Neurodiversity Research - Cleveland Clinic, World Economic Forum: Medical and societal perspectives on neurodivergence
• Understanding Neurodivergent Brains - AT4K: Detailed analysis of how neurodivergent cognition differs and why it matters
• Seven Neurodivergent Conditions - The Brain Charity: Comprehensive overview of main neurodivergent conditions

Statistics and Research Data

• 15% prevalence: Approximately 15% of people are thought to be neurodivergent
• 84% above-average reasoning: For dyslexic individuals in pattern evaluation and decision-making
• Individual variation: No consistent universal patterns; high interpersonal variation within each condition
• Shared strengths: Creativity, attention to detail, hyperfocus, and unconventional problem-solving across conditions

Ethical Considerations

Strengths-Based Approach

This resource takes a strengths-based approach to neurodivergence, focusing on cognitive advantages rather than deficits. This doesn't minimize challenges, but recognizes that:

1. Different ≠ deficient 2. Cognitive diversity enhances collective problem-solving 3. Many "symptoms" are assets in the right context 4. Neurodivergent patterns offer legitimate alternative approaches

Avoiding Stereotypes

Remember:

• These are tendencies, not rules
• Individual variation exceeds group differences
• Not all autistic people excel at pattern recognition
• Not all people with ADHD have big-picture thinking
• Not all dyslexic people are visual thinkers
• Neurodivergent individuals are not defined solely by their neurodivergence

Practical Inclusion

When applying these patterns:

• Don't assume someone has or lacks these strengths based on diagnosis
• Offer options rather than prescribing approaches
• Value multiple cognitive styles
• Create space for different processing speeds and modalities

Conclusion

Neurodivergent cognitive patterns represent genuine alternative approaches to thinking and problem-solving. By understanding and leveraging these patterns—whether you are neurodivergent or not—you can:

• Access diverse cognitive strategies
• Solve problems more comprehensively
• Appreciate cognitive diversity
• Build more inclusive and effective approaches

The goal is not to medicalize or categorize, but to expand the cognitive toolkit available for any given challenge.

---

References:

• Neurodivergent Thinking Patterns - Embracing Intensity
• The Neurodivergent Spectrum - Counseling Center Group
• Neurodivergent Symptoms & Types - Cleveland Clinic
• What is Neurodivergence - World Economic Forum
• Understanding Neurodivergent Brains - AT4K

Pattern Combination Examples

This document provides detailed examples of how to chain and combine thinking patterns for complex problem-solving. Each example demonstrates the orchestration process from task analysis through execution.

Related Resources:

- For pattern definitions, see: foundational-patterns.md, reasoning-patterns.md, creative-patterns.md, metacognitive-patterns.md, specialized-patterns.md

- For neurodivergent patterns: neurodivergent-strengths.md

- For orchestration guidance: Main SKILL.md

Example 1: Debugging a Complex Software Issue

Task Analysis

• Type: Analytical, Exploratory
• Complexity: High (multiple interconnected components)
• Optimal Patterns: Sequential → Analytical → Abductive → Systems

Pattern Chain Execution

Phase 1: Sequential Thinking

1. Reproduce the error
2. Identify error message/symptoms
3. Trace execution flow
4. Identify where behavior diverges from expected

Phase 2: Analytical Thinking

Break down the system:
- Component A: User input handler
- Component B: Data processor
- Component C: Output renderer
- Examine each component's state at failure point

Phase 3: Abductive Reasoning

Observations:
- Error occurs only with specific input patterns
- Data processor shows unexpected intermediate state
- No errors in logs before failure

Hypotheses:
1. Input validation missing edge case
2. Race condition in data processor
3. State corruption from previous operation

Best explanation: Edge case in input validation allows invalid data through,
which data processor can't handle

Phase 4: Systems Thinking

Understand system context:
- Why did validation miss this case?
- What are the feedback loops?
- How do components interact?
- Could fixing this break something else?

Insight: Validation was written before processor was updated.
System lacks feedback loop to ensure validation covers all processor requirements.

Outcome: Not only fix the immediate bug, but identify systemic issue (validation-processor sync) and implement solution.

---

Example 2: Developing a New Product Feature

Task Analysis

• Type: Creative, Strategic, User-Centered
• Complexity: High (ambiguous requirements, multiple stakeholders)
• Optimal Patterns: Design Thinking → Divergent → Convergent → Systems

Pattern Chain Execution

Phase 1: Design Thinking - Empathize & Define

Empathize:
- User interviews reveal frustration with current workflow
- Users want faster access to frequently-used items
- Concern about cluttering interface

Define:
"How might we provide quick access to frequent items without adding interface complexity?"

Phase 2: Divergent Thinking - Ideate

Generate many possibilities (suspend judgment):
- Floating action button with recent items
- Customizable quick-access toolbar
- Keyboard shortcuts for top 10 items
- AI-predicted next item popup
- Swipe gestures for frequent actions
- Voice command activation
- Smart menu that learns usage patterns
- Favorites star system
- Recently-used dropdown
- Context-aware suggestions
- (20+ more ideas generated...)

Phase 3: Convergent Thinking - Select

Apply criteria:
- Must not clutter interface
- Should handle variable user needs
- Technically feasible in timeframe
- Fits existing design language

Narrow to top 3:
1. Smart menu that learns usage patterns
2. Customizable quick-access toolbar
3. Context-aware suggestions

Select: Smart menu (best balance of all criteria)

Phase 4: Systems Thinking - Implementation Planning

Consider system implications:
- How does this interact with existing menus?
- What data do we need to collect? (privacy implications?)
- How does this affect performance?
- What happens on new user accounts?
- How do we handle edge cases (all items equal frequency)?
- What's the feedback loop for improvement?

Implementation approach:
- Default to recent items for new users
- Gradually shift to learned patterns
- Provide manual customization option
- Clear privacy policy for data collection
- Performance: calculate patterns server-side, cache locally

Phase 5: Design Thinking - Prototype & Test

Build low-fidelity prototype
Test with 5 users
Iterate based on feedback

Outcome: Feature that solves user problem while maintaining interface simplicity and system integrity.

---

Example 3: Learning from a Failed Project

Task Analysis

• Type: Reflective, Learning
• Complexity: Medium (requires honest self-assessment)
• Optimal Patterns: Reflective → Double-Loop → Metacognitive

Pattern Chain Execution

Phase 1: Reflective Thinking

Describe:
Project aimed to deliver X by date Y.
Delivered 3 weeks late with reduced scope.
Team morale was low.

Analyze what happened:
- Underestimated complexity
- Scope creep mid-project
- Communication breakdowns between teams
- Technical debt from rushed early work

Evaluate:
What went well: Team eventually delivered working product, learned new technology
What went poorly: Timeline, team morale, technical quality

Phase 2: Double-Loop Learning

Single-loop questions (process):
- How can we estimate better?
- How can we prevent scope creep?
- How can we improve communication?

Double-loop questions (assumptions):
- Why did we commit to aggressive timeline? (Assumption: speed impresses stakeholders)
- Why did we accept scope changes? (Assumption: saying no damages relationships)
- Why did we rush early work? (Assumption: visible progress more important than quality)

Test assumptions:
- Do stakeholders actually value speed over reliability?
- Would clear boundaries damage or improve relationships?
- Does rushed visible progress lead to better outcomes?

Findings:
- Stakeholders prefer realistic timelines to missed deadlines
- Clear boundaries respected, not resented
- Technical debt from rushing cost more time than it saved

Modified approach:
- Provide realistic estimates with buffers
- Establish change control process
- Prioritize sustainable pace over visible progress

Phase 3: Metacognitive Thinking

Examine my own thinking:
- Why did I believe aggressive timeline was necessary?
  → Fear of appearing uncommitted or slow
- Why did I not question scope changes?
  → Wanted to be seen as flexible and accommodating
- Why did I not speak up about rushed work?
  → Assumed others knew better

Patterns I notice:
- I prioritize others' perceptions over practical reality
- I make assumptions about what others want without asking
- I defer to authority even when I have concerns

Strategies for improvement:
- Practice stating realistic assessments confidently
- Ask stakeholders directly about priorities
- Voice concerns early with proposed solutions
- Monitor tendency to people-please vs. deliver value

Outcome: Not just process improvements, but deep shift in assumptions and self-awareness for future projects.

---

Example 4: Innovative Solution to Resource Constraints

Task Analysis

• Type: Creative, Strategic, Innovation
• Complexity: High (significant constraints, requires breakthrough)
• Optimal Patterns: First Principles → Lateral → Design Thinking

Pattern Chain Execution

Problem Statement: "We need to serve 10x more users but budget only allows 2x infrastructure increase."

Phase 1: First Principles Thinking

Current approach: Each user request requires full server computation

Break down to fundamentals:
- What are we actually trying to accomplish?
  → Deliver personalized content to users
- What are the true requirements?
  → Content must be relevant, timely, and accurate
- What assumptions are we making?
  → Each request requires fresh computation
  → All users need real-time personalization
  → Server must do all processing

Question each assumption:
- Do we really need fresh computation each time?
  → No, many requests are similar
- Do all users need real-time?
  → No, some content can be slightly stale
- Must server do all processing?
  → No, client devices are capable

Phase 2: Lateral Thinking

Challenge dominant thinking pattern:
Current: "How do we get more servers?"

Provocations:
- What if we had no servers?
- What if we only had one server?
- What if computation was free but bandwidth wasn't?
- What if old content was better than new?

Explore unexpected angle:
"What if we only had one server?" leads to...
- Must cache aggressively
- Must predict common requests
- Must pre-compute popular queries
- Must distribute workload temporally

Phase 3: Design Thinking - Reimagine Approach

Empathize with users:
- Do they need instant real-time? → Usually no, sub-second is fine
- Do they repeat similar requests? → Yes, high overlap
- What do they really value? → Reliability and speed

Ideate solutions:
- Aggressive caching of common requests
- Pre-computation of likely queries
- Client-side processing where possible
- Progressive enhancement: fast basic → enhanced later
- Edge caching for geographic distribution

Prototype:
- 80% requests served from cache (minimal server load)
- 15% requests use pre-computed results (light server load)
- 5% requests require full computation (heavy server load)
- Client devices handle personalization of cached results

Phase 4: Systems Thinking - Integration

Consider system implications:
- Cache invalidation strategy
- How to identify "common" requests?
- Graceful degradation if cache fails
- Monitoring and adaptation
- Edge case handling

Implementation:
- Machine learning to predict common requests
- Multi-tier caching (memory, disk, edge)
- Client-side personalization using cached base data
- Monitoring to identify emerging patterns
- Automatic scaling of cache vs. computation based on load

Outcome: Serve 10x users with only 1.5x infrastructure by completely reimagining the approach from first principles.

---

Example 5: Understanding a Complex Research Paper

Task Analysis

• Type: Analytical, Integrative, Learning
• Complexity: High (dense technical content, novel concepts)
• Optimal Patterns: Sequential → Analytical → Analogical → Systems → Metacognitive

Pattern Chain Execution

Phase 1: Sequential Reading

1. Read abstract
2. Read introduction
3. Examine figures and tables
4. Read methodology
5. Read results
6. Read discussion
7. Read conclusion

Phase 2: Analytical Thinking

Break down the paper:
- Core claim: X
- Evidence presented: Y₁, Y₂, Y₃
- Methodology: Z
- Assumptions: A₁, A₂
- Limitations acknowledged: L₁, L₂

Examine each component:
- Is evidence sufficient for claim?
- Is methodology sound?
- Are assumptions reasonable?
- What limitations aren't acknowledged?

Phase 3: Analogical Reasoning

Find familiar analogue:
- This paper's approach is similar to [previous work I understand]
- The core mechanism is like [familiar concept from different domain]
- The methodology resembles [technique I know]

Map correspondences:
- Their novel technique X ≈ established technique Y
- But adapted for context Z
- The key difference is W

Transfer understanding:
- If Y works because of reason R
- Then X should work because of adapted reason R'

Phase 4: Systems Thinking

Understand in broader context:
- How does this fit into the field?
- What prior work does it build on?
- What are the implications?
- How does it interact with related concepts?
- What feedback loops or emergent properties arise?

Integration:
- This resolves tension between approaches A and B
- But creates new question about C
- Enables future work on D
- Has implications for practical application E

Phase 5: Metacognitive Monitoring

Check my understanding:
- Can I explain the core idea to someone else?
- Can I predict what the authors would say about scenario X?
- What am I still confused about?
- What questions should I investigate further?

Self-assessment:
- Strong understanding: Core mechanism, main results
- Moderate understanding: Methodology details
- Weak understanding: Some mathematical derivations
- Action: Review mathematical appendix, consult supplementary materials

Outcome: Deep, integrated understanding of paper, clear sense of what I know and don't know, ability to apply concepts.

---

Example 6: Spatial Design Problem (Leveraging Neurodivergent Patterns)

Task Analysis

• Type: Spatial, Creative, Optimization
• Complexity: Medium-High (3D constraints, multiple objectives)
• Optimal Patterns: Spatial/Visual (Dyslexia) → Systems → Constraint-Based

Pattern Chain Execution

Problem: Design layout for small office (500 sq ft) to accommodate 6 people, meeting space, and storage while maintaining openness and natural light.

Phase 1: Spatial/Visual Thinking

Mental visualization:
- Picture the space in 3D
- Mentally "walk through" the space
- Visualize different configurations
- Rotate and manipulate mental model
- Notice spatial relationships and flow
- Identify where natural light enters

Generate spatial solutions:
- Configuration A: Desks along perimeter, meeting in center
- Configuration B: Clustered desk pods, meeting in corner
- Configuration C: Linear desk arrangement, meeting near window
- (Rapidly iterate through mental models)

Visual pattern recognition:
- Configuration A blocks light to interior
- Configuration B creates traffic flow problems
- Configuration C maximizes light while enabling collaboration

Phase 2: Systems Thinking

Consider interactions:
- How do people move through space?
- Where are traffic patterns?
- How does sound travel?
- How does light diffuse?
- What are the feedback loops?
  → Cramped → people leave → empty desks → space underutilized
  → Open → people stay → noise → people leave

Balance competing needs:
- Collaboration ↔ Quiet focus
- Openness ↔ Privacy
- Natural light ↔ Glare control
- Flexibility ↔ Permanence

Emergent properties:
- Certain arrangements encourage impromptu collaboration
- Others create natural quiet zones
- Layout affects team cohesion

Phase 3: Constraint-Based Optimization

Hard constraints:
- 500 sq ft total (immutable)
- 6 desks minimum (requirement)
- Meeting space for 4-6 people
- Fire code egress requirements
- Window locations (fixed)

Soft constraints (optimize):
- Maximize natural light distribution
- Minimize noise interference
- Maximize flexibility
- Optimize storage accessibility

Work within constraints creatively:
- Use transparent partitions (maintain light + add acoustic separation)
- Modular furniture (flexibility)
- Wall-mounted storage (preserve floor space)
- Multi-function meeting table (can separate into desk space)
- Strategic placement of sound-absorbing materials

Final design emerges from constraint optimization:
- Linear desk arrangement along non-window wall
- Meeting area near window (best light, not constant use)
- Transparent partition provides acoustic separation without blocking light
- Rolling storage units double as space dividers
- Results in 15% more usable space than traditional layout

Outcome: Optimized spatial design that satisfies all requirements and feels more spacious than square footage suggests, leveraging visual-spatial thinking strength.

---

Example 7: Data Analysis with ADHD and Autism Patterns

Task Analysis

• Type: Analytical, Pattern Recognition
• Complexity: High (large dataset, unclear patterns)
• Optimal Patterns: Big-Picture (ADHD) → Detail-Oriented (Autism) → Analytical → Inductive

Pattern Chain Execution

Problem: Analyze customer behavior data to identify opportunities for improvement.

Phase 1: Big-Picture Thinking (ADHD)

Zoom out to widest view:
- What are the major themes in this data?
- What stands out at overview level?
- What's the overall story?

High-level observations:
- Customer engagement peaks Tuesday-Thursday
- Sharp drop-off at specific point in user journey
- Two distinct customer clusters emerging
- Geographic patterns visible
- Seasonal trends present

Strategic insights:
- Focus on the sharp drop-off point (biggest impact opportunity)
- Understand the two clusters (may need different approaches)
- Consider day-of-week in marketing timing

Phase 2: Detail-Oriented Pattern Recognition (Autism)

Systematic deep examination:
- Examine drop-off point with precision
- Look at every field in the data
- Notice subtle patterns others might miss

Detailed findings:
- Drop-off occurs specifically at step 3 of 5
- Not uniform: varies by customer segment
- Correlation with specific browser types
- Time-on-page before drop-off: exactly 47 seconds (median)
- Small subset completes in <20 seconds (no drop-off)
- Error logs show validation message appears at ~45 seconds
- Pattern: validation message → 2 second delay → 90% abandon

Precision discovery:
- The validation message has a 2-second timeout
- Message is unclear ("Error 203")
- Fast completers don't trigger validation
- Slow completers get frustrated by vague error

Phase 3: Analytical Thinking

Break down the mechanism:
- Step 3 has complex validation
- Validation runs client-side
- Timeout is arbitrary (default setting)
- Error message not user-friendly
- No recovery guidance provided

Component analysis:
- Validation logic: Actually correct
- Timeout: Too short for mobile users
- Error messaging: Technical, not user-focused
- UX: No inline validation, only on submit

Phase 4: Inductive Reasoning

From specific observations to general principle:
- Observation: Users abandon when they get vague errors after waiting
- Observation: Fast users succeed, slow users fail
- Observation: Mobile users disproportionately affected
- Observation: No correlation with data validity (valid data still errors)

General principle:
"Users abandon when they invest time but receive unclear negative feedback on a process that feels arbitrary."

Broader application:
- This pattern likely exists elsewhere in our product
- Audit all timeout-based validations
- Review all error messaging
- Consider progressive validation vs. submit-time validation

Outcome:

• Immediate fix: Remove timeout, improve error message, add inline validation
• Strategic insight: Systematic review of all user feedback mechanisms
• Big win from combining ADHD big-picture (found the drop-off) with autistic detail-orientation (found the exact cause)

---

Example 8: Parallel Pattern Application for Comprehensive Analysis

Task Analysis

• Type: Complex Decision
• Complexity: Very High (multiple stakeholders, high stakes, uncertainty)
• Optimal Patterns: System 1 + System 2 + Analytical + Holistic (Parallel)

Pattern Chain Execution

Problem: Should we pivot product strategy or double down on current approach?

Simultaneous Application of Multiple Patterns:

System 1 (Intuitive) Thread:

Gut check:
- Something feels off about current trajectory
- Market seems to be shifting
- Team energy is low
- Competition is moving faster than we are

Pattern matching:
- This feels similar to [previous situation where we pivoted]
- Market dynamics resemble [historical pattern]
- Team behavior reminds me of [other project that struggled]

Immediate intuition: Lean toward pivot, but need rigorous analysis

System 2 (Analytical) Thread:

Deliberate analysis:
- Gather all relevant data
- Define clear decision criteria
- Evaluate options systematically
- Consider long-term implications
- Run financial models
- Assess risks quantitatively

Findings:
- Current trajectory: 60% chance of moderate success
- Pivot option A: 30% chance of high success, 40% chance of failure
- Pivot option B: 50% chance of moderate success, lower variance

Analytical Decomposition Thread:

Break down the decision:
- Market factors: [analysis]
- Financial factors: [analysis]
- Team factors: [analysis]
- Competitive factors: [analysis]
- Technical factors: [analysis]

Each component examined independently

Holistic/Gestalt Thread:

View as complete picture:
- How do all factors interact?
- What's the overall pattern?
- What does this look like when viewed as whole?
- What's the narrative arc?

Holistic insight:
- Parts suggest pivot
- But whole picture shows momentum could shift with targeted changes
- Current approach isn't fundamentally wrong, execution is

Integration of All Threads:

System 1 said: Something's off, consider pivot
System 2 said: Pivot is risky, current approach has better expected value
Analytical said: Multiple components show issues
Holistic said: The pieces can work together better

Synthesis:
- Don't pivot product
- Do pivot execution approach
- Address specific component issues
- Maintain strategic direction but change tactics
- Monitor closely and set decision points for future pivot consideration

This combines:
- Intuitive warning (System 1)
- Rigorous analysis (System 2)
- Component understanding (Analytical)
- Emergent pattern recognition (Holistic)

Outcome: Decision that leverages multiple thinking modes simultaneously, more robust than any single approach.

---

Key Principles for Pattern Combination

1. Match Patterns to Task Phase

Different phases of problem-solving benefit from different patterns:

• Understanding: Analytical, Systems, Holistic
• Ideation: Divergent, Lateral, Associative
• Selection: Convergent, Critical, Constraint-Based
• Learning: Reflective, Metacognitive, Double-Loop

2. Chain Complementary Patterns

Some patterns naturally feed into others:

• Divergent → Convergent: Generate then select
• Analytical → Systems: Understand parts then whole
• Abductive → Deductive: Hypothesis then test
• Reflective → Metacognitive: Experience then thinking process

3. Use Parallel Patterns for Complex Problems

Multiple simultaneous perspectives reveal more:

• System 1 + System 2: Intuition validates analysis
• Analytical + Holistic: Parts and whole together
• Big-Picture + Detail-Oriented: Strategy and precision

4. Leverage Neurodivergent Strengths Intentionally

Don't forget these valuable patterns:

• Hyperfocus: For deep work on engaging problems
• Big-Picture: For strategy and overview
• Detail-Oriented: For precision and pattern finding
• Spatial/Visual: For spatial problems and visualization
• Non-Linear Associative: For creative breakthroughs

5. Stay Flexible

If a pattern isn't working:

• Switch patterns mid-process
• Add a complementary pattern
• Try a completely different approach
• Chain to a new pattern

6. Validate Before Finalizing

Always include validation step:

• Did I solve the right problem?
• Is the solution complete?
• Does it make logical sense?
• Could another pattern have been better?

---

Pattern Selection Decision Tree

Is problem well-defined?
├─ Yes → Start with Analytical, Sequential, or Deductive
└─ No → Start with Divergent, Abductive, or Design Thinking

Does problem involve complex system?
├─ Yes → Include Systems Thinking
└─ No → Stay focused on direct analysis

Is creativity/innovation needed?
├─ Yes → Use Divergent → Lateral → Convergent chain
└─ No → Use more structured analytical patterns

Is this a learning opportunity?
├─ Yes → Add Reflective → Double-Loop → Metacognitive
└─ No → Focus on solution delivery

Could neurodivergent patterns add value?
├─ Spatial problem → Consider Visual/Spatial thinking
├─ Need precision → Consider Detail-Oriented
├─ Need strategy → Consider Big-Picture
├─ Engaging deep work → Consider Hyperfocus
└─ Creative breakthrough → Consider Non-Linear Associative

Is decision high-stakes?
├─ Yes → Use System 2 + Critical + Counterfactual
└─ No → System 1 may suffice

Multiple valid approaches?
└─ Use Parallel Patterns for comprehensive view

---

These examples demonstrate that the most powerful problem-solving often comes from thoughtful orchestration of multiple thinking patterns rather than relying on a single approach.

Reasoning Patterns

This resource covers formal and informal reasoning patterns used for logical inference, hypothesis generation, learning, and challenging assumptions.

Deductive Reasoning

Description: Moving from general principles to specific conclusions; if premises are true, conclusion must be true.

When to Use:

• Applying known rules or laws
• Mathematical proofs
• Logical inference
• Certain knowledge domains

Process: 1. State general principle/rule 2. Identify specific case 3. Apply rule to case 4. Derive certain conclusion

Example:

• All humans are mortal (general)
• Socrates is human (specific)
• Therefore, Socrates is mortal (conclusion)

Limitations: Only as good as premises; doesn't generate new knowledge beyond premises.

---

Inductive Reasoning

Description: Moving from specific observations to general principles; probabilistic rather than certain.

When to Use:

• Pattern identification from data
• Hypothesis generation
• Trend analysis
• Building general understanding from examples

Process: 1. Collect specific observations 2. Identify patterns and regularities 3. Formulate general principle 4. Test generalization with new cases

Example:

• Observed: Swan 1 is white, Swan 2 is white, Swan 3 is white...
• Conclusion: All swans are white (probabilistic, can be disproven)

Limitations: Conclusions are probable, not certain; vulnerable to sampling bias.

---

Abductive Reasoning

Description: Inference to the best explanation; finding the simplest and most likely explanation for observations.

When to Use:

• Diagnostic problems
• Mystery or puzzle solving
• Scientific hypothesis formation
• Explaining unexpected observations

Process: 1. Observe surprising or puzzling facts 2. Generate possible explanations 3. Evaluate explanations (simplicity, likelihood, explanatory power) 4. Select best explanation 5. Remain open to revision with new evidence

Cognitive Requirements:

• Generate multiple hypotheses
• Evaluate evidence relevance
• Compare competing explanations
• Revise flexibly with new data

Example:

• Observation: The grass is wet
• Possible explanations: Rain, sprinkler, dew, spilled water
• Best explanation (given context): It rained last night

Limitations: Best explanation may not be correct; requires creativity in hypothesis generation.

---

Analogical Reasoning

Description: Drawing connections between a familiar domain (source/analog) and new domain (target) to transfer knowledge.

When to Use:

• Learning new concepts
• Creative problem-solving
• Explaining complex ideas
• Finding solutions by analogy

Process: 1. Identify target problem 2. Recall similar source domain 3. Map correspondences between domains 4. Transfer relationships and solutions 5. Adapt to target context

Example:

• Source: The atom is like a solar system
• Mapping: Nucleus = Sun, Electrons = Planets
• Transfer: Electrons orbit the nucleus like planets orbit the sun

Note: Peirce considered analogy a compound form integrating abduction and induction; important source of human creativity.

Limitations: Analogies can mislead if domains differ in crucial ways.

---

Counterfactual Reasoning

Description: Mental simulation of alternative scenarios; "what might have been" thinking.

When to Use:

• Learning from mistakes
• Contingency planning
• Understanding causation
• Improving future decisions

Process: 1. Identify actual outcome 2. Imagine alternative actions/conditions 3. Simulate alternative outcome 4. Compare factual and counterfactual 5. Extract lessons for future

Types:

• Upward counterfactuals: How it could have been better
• Downward counterfactuals: How it could have been worse
• Additive: Adding something that wasn't there
• Subtractive: Removing something that was there

Functional Purpose: Avoid repeating mistakes; prepare for similar future situations.

Limitations: Can lead to regret or rumination if overused.

---

First Principles Thinking

Description: Breaking down problems to fundamental truths and building up from there; questioning all assumptions.

When to Use:

• Innovation challenges
• Breaking through conventional wisdom
• Fundamental understanding
• When existing approaches fail

Process: 1. Identify current assumptions/beliefs 2. Break down to foundational truths 3. Question everything that isn't fundamental 4. Rebuild understanding from first principles 5. Construct new approach

Example:

• Conventional: "Batteries are expensive"
• First principles: "What are batteries made of? Cobalt, nickel, aluminum, carbon, polymers. What are the raw material costs? How can we acquire or produce these more efficiently?"
• Result: Rethink battery production from fundamentals

Elon Musk's approach: "Boil things down to their fundamental truths and reason up from there, as opposed to reasoning by analogy."

Limitations: Time-intensive; may reinvent wheel unnecessarily for routine problems.

---

Reasoning Type Comparison

Common Chains

1. Scientific Method: Inductive → Abductive → Deductive

• Observe patterns → Form hypothesis → Test predictions

2. Problem-Solving: First Principles → Analogical

• Strip to fundamentals → Find analogous solutions

3. Decision Review: Counterfactual → Inductive

• Simulate alternatives → Extract general lessons

4. Explanation: Abductive → Analogical

• Find best explanation → Explain via familiar analogy

Specialized Problem-Solving Patterns

This resource covers domain-specific and methodological patterns for user-centered design, constrained optimization, parallel analysis, and iterative development.

Design Thinking

Description: Human-centered approach to innovation emphasizing empathy, ideation, and iterative prototyping.

When to Use:

• User-centered problems
• Innovation challenges
• Ambiguous problem spaces
• Requiring creative solutions
• Product/service development

Process:

1. Empathize

Understand user needs deeply:

• Conduct interviews
• Observe behavior in context
• Build empathy maps
• Identify pain points and desires
• Challenge assumptions about users

2. Define

Articulate the problem clearly:

• Synthesize observations
• Create point-of-view statement
• "How might we..." questions
• Focus on user needs, not solutions

3. Ideate

Generate many solutions:

• Brainstorm widely (divergent)
• Build on ideas
• Encourage wild concepts
• Defer judgment
• Combine and improve

4. Prototype

Build representations:

• Low-fidelity first
• Fast and cheap
• Test specific aspects
• Learn through making
• "Fail fast, learn fast"

5. Test

Gather feedback:

• Put prototypes in front of users
• Observe, don't defend
• Ask open questions
• Identify what works/doesn't
• Refine understanding

6. Iterate

Refine based on learning:

• Return to any previous phase
• Multiple cycles expected
• Progressively higher fidelity
• Converge on solution

Key Principles:

• Bias toward action
• Embrace experimentation
• Radical collaboration
• Mindfulness of process
• Show don't tell

Limitations: Can be time-intensive; requires user access.

---

Constraint-Based Thinking

Description: Using limitations as creative drivers and solution frameworks.

When to Use:

• Resource-limited situations
• Focused creativity needed
• Optimization problems
• When constraints clarify direction
• Budget/time restrictions

Process: 1. Identify all constraints

• Resources (money, time, people)
• Technical limitations
• Requirements and must-haves
• Legal/regulatory bounds
• Physical constraints

2. Categorize constraints

• Hard constraints (cannot be violated)
• Soft constraints (prefer to honor)
• Assumed constraints (may be questionable)

3. Treat constraints as creative challenges

• "Because we can't X, we must find another way"
• Constraint forces innovation
• Limitation breeds creativity

4. Generate solutions within boundaries

• Work within hard constraints
• Optimize soft constraints
• Question assumed constraints

5. Question constraint validity

• Is this really a constraint?
• Who imposed it and why?
• What happens if we violate it?
• Can we negotiate or change it?

Creative Constraint Examples:

• "We only have one week" → Focus on MVP
• "Budget is $100" → Find free alternatives
• "Must fit in one screen" → Ruthless prioritization

Strengths: Focus, creativity through limitation, realistic solutions.

Limitations: May miss opportunities from relaxing constraints.

---

Parallel Processing

Description: Simultaneously considering multiple aspects, hypotheses, or approaches.

When to Use:

• Complex multi-faceted problems
• When single-thread insufficient
• Exploring multiple hypotheses
• Comprehensive analysis needed
• Time permits deep exploration

Process: 1. Identify multiple threads to process

• Different aspects of problem
• Competing hypotheses
• Various stakeholder perspectives
• Alternative approaches

2. Hold multiple perspectives simultaneously

• Don't collapse to single view too early
• Maintain uncertainty where appropriate
• Track evidence for each thread

3. Process different aspects in parallel

• Assign mental "resources" to each
• Use external aids if needed (notes, diagrams)
• Switch between threads deliberately

4. Integrate findings

• Look for convergence across threads
• Note contradictions
• Synthesize into coherent picture

5. Identify interactions between threads

• How do aspects influence each other?
• Are there unexpected connections?
• What emerges from the combination?

Note: Connectionist models use parallel processing across web-like structures with top-down and bottom-up processes.

Tools to Support Parallel Processing:

• Mind maps
• Comparison tables
• Multiple hypothesis tracking
• Kanban boards
• Split-screen analysis

Limitations: Cognitively demanding; may require external aids (writing, diagrams).

---

Iterative Refinement

Description: Progressively improving solutions through repeated cycles of execution, evaluation, and modification.

When to Use:

• Complex problems without clear solution
• Creative work
• Software development
• Continuous improvement
• Learning new skills

Process: 1. Create initial version

• Don't aim for perfection
• "Good enough to evaluate"
• Establish baseline

2. Evaluate against criteria

• Define success metrics
• Test with users/stakeholders
• Compare to requirements
• Identify gaps

3. Identify improvements

• What's working well? (keep it)
• What's not working? (change it)
• What's missing? (add it)
• What's unnecessary? (remove it)

4. Implement changes

• Prioritize high-impact changes
• Make one change at a time if debugging
• Document what changed and why

5. Repeat until satisfactory

• Define stopping criteria upfront
• Watch for diminishing returns
• Know when "good enough" is reached

Iteration Strategies:

Timeboxed Iterations

• Fixed time periods (sprints)
• Deliver what's possible in the box
• Regular cadence

Quality Thresholds

• Define minimum quality bar
• Iterate until bar is met
• Raise bar over time

Feedback-Driven

• Each iteration responds to feedback
• User/stakeholder input drives priorities
• Adaptive to changing needs

Limitations: Can be time-consuming; need clear stopping criteria.

---

Pattern Combinations

Quick Reference

Application Examples

Software Development

Design Thinking (understand user) → 
Constraint-Based (technical limits) → 
Iterative Refinement (sprints) → 
Parallel Processing (testing scenarios)

Business Strategy

Parallel Processing (market analysis) → 
Constraint-Based (budget/resources) → 
Design Thinking (customer journey) → 
Iterative Refinement (pilot programs)

Creative Projects

Design Thinking (audience understanding) → 
Iterative Refinement (drafts) → 
Constraint-Based (format limits) → 
Parallel Processing (feedback integration)