---
name: "cross-domain-thinking-toolbox"
description: "Apply 25 professional mental models to solve complex problems. Use when: (1) facing multi-faceted challenges that require diverse perspectives, (2) stuck in single-minded approaches, (3) need innovative solutions, (4) making major decisions with multiple stakeholders, (5) understanding complex human behavior, or (6) seeking to break cognitive biases and adopt alternative viewpoints."
---

# Cross-Domain Thinking Toolbox

Borrow thinking tools from 25 different professions to approach problems from fresh angles.

## Quick Reference: The 25 Thinking Tools

| #   | Profession         | Core Question                                    | Best For                               |
| --- | ------------------ | ------------------------------------------------ | -------------------------------------- |
| 1   | **Artist**         | What makes this unique and interesting?          | Creative blockers, innovation needs    |
| 2   | **Economist**      | How do people respond to incentives?             | Behavior prediction, system design     |
| 3   | **Engineer**       | Can I model and calculate this?                  | Prediction, data-driven decisions      |
| 4   | **Entrepreneur**   | What works if I try many things?                 | Uncertainty, rapid experimentation     |
| 5   | **Doctor**         | What's the diagnosis from symptoms?              | Root cause analysis, troubleshooting   |
| 6   | **Journalist**     | Have I verified from independent sources?        | Information validation, research       |
| 7   | **Scientist**      | Does this withstand controlled testing?          | Hypothesis validation, beliefs testing |
| 8   | **Mathematician**  | Can I prove this rigorously?                     | Logic, error detection                 |
| 9   | **Programmer**     | What patterns can I automate?                    | Process optimization, simplification   |
| 10  | **Architect**      | What will this look like at full scale?          | Future visualization, planning         |
| 11  | **Salesperson**    | What do people really want beneath stated needs? | Understanding motivations, negotiation |
| 12  | **Soldier**        | What procedure must I follow exactly?            | Risk prevention, error avoidance       |
| 13  | **Chess Master**   | What happens next if I simulate this?            | Strategic foresight, scenario planning |
| 14  | **Designer**       | Does this intuitively suggest how to use it?     | UX, communication design               |
| 15  | **Teacher**        | How do I build knowledge in a learner's mind?    | Explanation, knowledge transfer        |
| 16  | **Anthropologist** | Can I understand this group from inside?         | Culture analysis, unfamiliar contexts  |
| 17  | **Psychologist**   | Does my model predict actual behavior?           | Human behavior understanding           |
| 18  | **Critic**         | How can I build on others' work?                 | Analysis, synthesis, improvement       |
| 19  | **Philosopher**    | What happens when I push this idea to extremes?  | Finding flaws, revealing principles    |
| 20  | **Accountant**     | What ratios reveal hidden truths?                | Metrics analysis, efficiency           |
| 21  | **Politician**     | What will people believe about this?             | Perception, communication strategy     |
| 22  | **Novelist**       | Does my story make coherent sense?               | Narrative structure, communication     |
| 23  | **Actor**          | Can I actually feel the state I need?            | Emotional management, presence         |
| 24  | **Plumber**        | What would I find by examining directly?         | Hands-on investigation, debugging      |
| 25  | **Hacker**         | What's really happening underneath?              | Understanding systems deeply           |

## Usage Patterns

### Pattern 1: Problem Diagnosis

When user describes a problem:

1. Identify the problem type
2. Recommend 2-3 most relevant thinking tools
3. Explain why each tool fits
4. Provide guiding questions for application

### Pattern 2: Multi-Angle Analysis

When user needs diverse perspectives:

1. Pick 3-5 diverse tools for the problem
2. Analyze from each perspective
3. Synthesize insights
4. Highlight trade-offs between approaches

### Pattern 3: Perspective Shift

When user is stuck in one mode:

1. Identify their current approach
2. Suggest 2-3 contrasting tools
3. Explain what each would reveal differently
4. Encourage genuine exploration, not just acknowledgment

### Pattern 4: Practical Application

When user wants to apply a specific tool:

1. Explain the tool's core principle
2. Provide concrete steps
3. Give worked examples
4. Note limitations and when not to use

## Core Principles

- **Don't give answers directly** — guide thinking with questions
- **Each tool has limits** — no tool fits all situations
- **Combine tools** — powerful insights come from mixing perspectives
- **Iterate** — apply tools, reflect, refine
- **Stay practical** — focus on actionable insights

## Common Problem Types and Tool Recommendations

| Problem Type               | Recommended Tools                    |
| -------------------------- | ------------------------------------ |
| Need creativity/novelty    | Artist, Entrepreneur, Designer       |
| Understanding behavior     | Economist, Psychologist, Salesperson |
| Making predictions         | Engineer, Chess Master, Scientist    |
| Debugging issues           | Doctor, Plumber, Engineer            |
| Improving processes        | Programmer, Accountant, Architect    |
| Communication challenges   | Novelist, Teacher, Designer          |
| Decision under uncertainty | Entrepreneur, Scientist, Politician  |
| Understanding people       | Anthropologist, Psychologist, Actor  |
| Finding hidden assumptions | Philosopher, Mathematician, Critic   |
| Risk management            | Soldier, Accountant, Engineer        |

## When to Ask Follow-Up Questions

Before applying thinking tools, clarify:

- What type of problem is this? (creative, analytical, interpersonal, etc.)
- What approaches have already been tried?
- What outcome does the user want?
- Are there constraints or stakeholders involved?