creative-thinking-for-research

Creative Thinking for Research

Eight empirically grounded frameworks from cognitive science, applied to computer science and AI research. Unlike ad-hoc brainstorming, each framework here is backed by decades of creativity research — from Koestler's bisociation to Kauffman's adjacent possible. They target distinct cognitive operations: combining, reformulating, analogizing, constraining, inverting, abstracting, exploring boundaries, and holding contradictions.

When to Use This Skill

• Generating genuinely novel ideas, not incremental extensions of prior work
• Feeling trapped in a local optimum of thinking within a single subfield
• Wanting to systematically apply creativity heuristics rather than waiting for inspiration
• Preparing for a research retreat or PhD-level ideation session
• Bridging between fields and seeking structural (not superficial) connections

Do NOT use this skill when:

• You need structured project-level brainstorming workflows (use brainstorming-research-ideas)
• You have a well-defined problem and need execution help (use domain-specific skills)
• You need a literature survey (use scientific-skills:literature-review)

Relationship to Brainstorm skill: The brainstorm skill provides operational workflows (diverge → converge → refine) and practical filters. This skill provides the deeper cognitive engines that power creative leaps. Use them together: creative-thinking to generate raw insight, brainstorm to structure and evaluate it.

Framework 1: Combinatorial Creativity (Bisociation)

Novel ideas arise from combining existing concepts in unexpected ways. Arthur Koestler called this bisociation — connecting two previously unrelated frames of reference, as distinct from routine association within a single frame.

Why it works: Meta-research consistently shows that breadth of knowledge is a precursor to creative output. People who read across disciplines produce more novel work. The combination itself is the creative act.

In CS Research:

• Biological evolution → optimization (genetic algorithms)
• Game theory → networking (mechanism design for routing)
• Statistical physics → machine learning (Boltzmann machines, energy-based models)
• Linguistics → programming (type theory, formal grammars)

Systematic Bisociation Workflow:

1. Select two domains you have at least passing familiarity with
2. List core primitives in each domain (5-10 fundamental concepts per domain)
3. Create a cross-product matrix: row = concepts from Domain A, column = concepts from Domain B
4. For each cell, ask: "What would it mean to apply A's concept to B's problem?"
5. Filter: Which combinations produce a non-trivial, testable research question?
6. Validate structural depth: Is the connection mechanistic or merely metaphorical?

Cross-Product Example:

| | Caching | Load Balancing | Fault Tolerance | |---|---------|---------------|-----------------| | Natural Selection | Evict least-fit entries | Adaptive allocation via fitness | Population-level redundancy | | Immune Memory | Learned threat signatures | Distributed detection | Self/non-self discrimination | | Symbiosis | Cooperative prefetching | Mutualistic resource sharing | Co-dependent resilience |

Quality Test: A strong bisociation is not a surface metaphor ("the network is like a brain") but a structural mapping where the mechanism transfers ("attention mechanisms implement a form of selective gating analogous to cognitive attention filtering").

Self-Check:

• [ ] Is the connection structural (mechanisms map) or merely verbal (labels map)?
• [ ] Does the combination generate testable predictions?
• [ ] Would an expert in both fields find the connection non-obvious but sound?

Framework 2: Problem Reformulation (Representational Change)

Gestalt psychologists identified that breakthroughs often come not from solving the problem as stated, but from re-representing the problem itself. Kaplan and Simon's work on insight shows that changing the problem space — the constraints, the abstraction level, the formalism — is often where creativity lives.

The Key Shift: From "How do I solve this problem?" to "Am I even thinking about this problem correctly?"

Reformulation Strategies:

| Strategy | Example | |----------|---------| | Change the objective | "Make the algorithm faster" → "Eliminate the need for this computation" | | Change the formalism | Graph problem → linear algebra problem (spectral methods) | | Change the granularity | Per-token prediction → per-span prediction | | Change the agent | "How should the model learn?" → "How should the data teach?" (curriculum learning) | | Change the timescale | Real-time optimization → amortized inference | | Invert the direction | Forward simulation → inverse problem (learning from observations) |

Workflow:

1. State your current problem in one sentence
2. Identify the hidden assumptions in that statement:
3. What formalism are you using? (Could you use a different one?)
4. What is the objective? (Is it the right objective?)
5. What level of granularity? (Could you go coarser or finer?)
6. Who is the agent? (Could you shift perspective?)
7. For each assumption, generate the alternative: "What if [opposite assumption]?"
8. For each alternative, ask: "Does this reformulation make the problem easier, harder, or different in a useful way?"
9. A reformulation that makes a hard problem easy is often a publishable insight on its own

Classic CS Examples:

• PageRank: Reformulated "find important web pages" from content analysis to graph eigenvalue problem
• Dropout: Reformulated "prevent overfitting" from regularization to approximate ensemble
• Attention: Reformulated "handle long sequences" from remembering everything to selectively querying

Framework 3: Analogical Reasoning (Structure-Mapping)

Dedre Gentner's structure-mapping theory and Kevin Dunbar's studies of real scientists show that analogy is the core engine of scientific creativity. The critical finding: surface-level analogies are common but weak; structural or relational analogies — where the deep causal/relational structure maps across domains — produce the most powerful insights.

Dunbar's Finding: In the most successful labs, analogies from distant domains drove the most important discoveries. Nearby analogies refined ideas; distant analogies generated them.

Levels of Analogical Depth:

| Level | Description | Value | Example | |-------|-------------|-------|---------| | Surface | Things look similar | Low | "A neural network is like a brain" | | Relational | Relationships between entities match | Medium | "Attention allocation in models parallels resource allocation in economics" | | Structural | Deep causal mechanisms map | High | "Diffusion models reverse a thermodynamic process; the math of non-equilibrium stat-mech directly applies" |

Structure-Mapping Workflow:

1. Describe your problem using only relational/causal language (strip domain-specific nouns)
2. Bad: "We need to improve transformer attention efficiency"
3. Good: "We have a system that must selectively aggregate information from a large set, where relevance is context-dependent and the cost scales quadratically with set size"
4. Search for structural matches: What other systems selectively aggregate from large sets?
5. Database query optimization, visual attention in neuroscience, information retrieval, resource allocation
6. Pick the most distant match with genuine structural fidelity
7. Map the solution mechanism: How does the source domain solve this?
8. Transfer and adapt: What changes when you bring that mechanism into your domain?
9. Generate predictions: The analogy should tell you something you didn't already know

Validation Checklist:

• [ ] Does the mapping preserve causal/relatio