SKILL: Intuition Pumps for Scientific Problem Ideation

Overview

This skill helps scientists generate high-quality research ideas by providing systematic prompts ("intuition pumps") and identifying common ideation traps. Based on the framework that most biological and chemical science projects involve perturbing a system, measuring it, and analyzing the data, this skill guides users through structured ideation that can significantly impact how they spend years of their career.

Core Framework

The Three Pillars of Scientific Work

Research advances generally fall into one of these categories, each with two dimensions:

PERTURBATION

• Logic: Novel ways to manipulate biological systems (e.g., using CRISPR for deep mutational scanning)
• Technology: New tools for manipulation (e.g., developing base editors, creating whole-genome CRISPR libraries)

MEASUREMENT

• Logic: Novel applications of existing measurement tools (e.g., using tissue clearing to study liver fibrosis)
• Technology: New measurement capabilities (e.g., developing tissue-clearing techniques, super-resolution microscopy)

THEORY/COMPUTATION

• Logic: Using computational tools to make discoveries (e.g., applying AlphaFold to identify protein functions)
• Technology: Building new algorithms or models (e.g., developing machine learning architectures for biological data)

Understanding which quadrant resonates with the user can help identify their niche and guide ideation.

The Skill Workflow

Phase 1: Initial Discovery Questions (5-10 minutes)

Before diving into intuition pumps, Claude should gather context by asking the user:

1. What is the user's general research area or field? (e.g., immunology, synthetic biology, neuroscience, protein engineering)

2. What excites the user most about science?

   • Building new tools/technologies?
   • Discovering fundamental principles?
   • Solving practical problems?
   • Understanding dynamic processes?

3. What are the user's existing strengths? (Select all that apply)

   • Specific techniques (please list)
   • Computational skills
   • Access to unique systems/models
   • Domain expertise in a particular area

4. Current constraints:

   • Time horizon for this project? (months/years)
   • Resources available?
   • Must it connect to existing work, or can the user start fresh?

5. On a scale of 1-5, how would the user rate their current idea?

   • Likelihood of success: 1 (very risky) to 5 (highly feasible)
   • Potential impact: 1 (incremental) to 5 (transformative)

Phase 2: Applying Intuition Pumps

Based on the user's responses, Claude should guide them through relevant intuition pumps from this list:

Intuition Pump #1: Make It Systematic

Prompt: Take any one-off perturbation or measurement and make it systematic.

Examples:

• Instead of mutating one enzyme, measure kinetic parameters across an entire enzyme family
• Instead of one CRISPR mutant → genome-wide screen with transcriptomic readout
• Instead of imaging one condition → high-throughput imaging across thousands of conditions

Prompt for User: What one-off experiment in your field could become a systematic survey?

Intuition Pump #2: Identify Technology Limitations

Prompt: What are the fundamental limitations of technologies you use? These limitations are opportunities.

Examples:

• Microscopy can't resolve beyond diffraction limit → super-resolution microscopy
• DNA synthesis can't make complete genomes → develop assembly methods
• Genetic screens have precise input but imprecise output → develop high-dimensional readouts
• We do single gene KOs but networks are complex → develop combinatorial perturbation methods

Prompt for User: What technology limitation frustrates you most? How might you turn that limitation into an opportunity?

Intuition Pump #3: The "I Can't Imagine" Test

Prompt: I can't imagine a future in which we don't have ____, but it doesn't exist yet.

Examples:

• The ability to design highly efficient enzymes like we design other proteins
• The ability to deliver genome editing payloads to any cell type in vivo
• 3D tomographic imaging of live cells at molecular resolution
• Proteome-scale sequencing with the throughput of RNA-seq

Prompt for User: What capability seems inevitable but doesn't exist yet in your field?

Intuition Pump #4: Static vs. Dynamic Understanding

Prompt: We understand biological "parts lists" but rarely understand dynamic processes.

Key Insight: Most observations are single-timepoint, single-perturbation format. But biological systems are dynamic—like humans flowing through Grand Central Station or money through financial systems.

Examples:

• Understanding growth factor signaling like we understand turning a key in a car engine
• Time-resolved cell atlases with lineage tracing through entire development
• Following metabolite flux through pathways in real-time

Prompt for User: What dynamic process in your field do we observe as static snapshots? How might you capture the full temporal or spatial dynamics?

Intuition Pump #5: Pick a New Axis

Prompt: We almost always use time as the x-axis for dynamic processes. What other coordinate could you use?

Example: Instead of time, use "infection progression" markers to enable monitoring asynchronous cells

Prompt for User: What non-temporal coordinate could reveal new biology in your system?

Intuition Pump #6: Create a Technology Platform

Prompt: Instead of answering one question, could you build a platform that enables many questions?

Examples:

• Antibodies for intracellular targets (not just extracellular)
• AI that predicts perturbations needed to reach desired cell states
• Universal genome delivery vehicles

Prompt for User: What platform would transform how your field asks questions?

Intuition Pump #7: Dogs That Don't Bark

Prompt: Why doesn't something exist or occur? Absence can be as informative as presence.

Examples:

• Why are there no Gram-negative bacteria on human skin?
• Why do some catalytically inactive enzymes persist through evolution?
• Why don't certain cell types exist in certain tissues?

Prompt for User: What absence puzzles you in your field?

Phase 3: Avoiding Common Traps

After generating ideas, we must evaluate them critically. Here are the most common traps:

Trap #1: The Truffle Hound

Warning: Don't become so good at one system or technique that you fail to ask questions of biological import.

Bad: "What is the role of p190 RhoGAP in wing development?"
Better: "How do signaling pathways and cytoskeleton coordinate to control wing development?"

Self-Check: Is the question driven by biological curiosity or by what the user is technically capable of?

Trap #2: Applying Existing Tool to New System

Warning: "Let's use CRISPR in my organism" can be valuable but risks crowding and incrementalism.

When It Works: The user is enabling a field that truly needs this capability When It Fails: The tool is already widely applied; the contribution will be incremental

Self-Check: Will this tool application open new biological questions, or just extend existing observations? Claude should help the user evaluate this honestly.

Trap #3: Jumping on the First Idea

Warning: Treating ideas with reverence instead of skepticism. Confirmation bias sets in quickly.

Better Approach: Users should treat new ideas like leeches trying to steal their time. Look for the warts. Develop several ideas in parallel and comparison shop.

Self-Check: Has the user critically evaluated at least 3-5 alternative approaches?

Trap #4: Too Many Fixed Parameters

Warning: Fixing too many parameters at the outset creates a poor technique-application match.

Example of Over-Constraining: "I will use spatial transcriptomics to study antigen-presenting cell and T cell interactions in the tumor microenvironment."

• This fixes: technique (spatial transcriptomics), cell types, and context
• If any assumption fails, the project fails

Self-Check: Has the user fixed more than 2 parameters before starting?

Trap #5: Too Few Fixed Parameters

Warning: "I want to do impactful work in cell engineering" → paralysis

Resolution: Constraints engender creativity. Fix ONE parameter at a time and let creativity flow.

Self-Check: Does the user have at least one concrete constraint to work with?

Phase 4: Literature Integration

To ensure the idea has appropriate scope and hasn't been thoroughly explored, Claude should ask:

1. What are 2-3 key questions or gaps the idea addresses?

2. What should be searched in PubMed to:

   • Understand the current state of the field?
   • Identify related approaches?
   • Find empirical knowledge from adjacent domains that could inform the approach?

Claude should use PubMed to:

• Assess how general/specific the problem is
• Identify relevant methodological advances
• Find analogous systems or approaches in other fields
• Determine the degree of competition

Phase 5: Idea Refinement and Output

After working through intuition pumps, avoiding traps, and reviewing literature, Claude should help the user:

1. Crystallize the Idea:

   • Biological question
   • Technical approach (perturbation/measurement/theory: logic vs. technology)
   • What's novel about this angle?

2. Articulate Fixed vs. Floating Parameters:

   • What MUST remain constant in the approach?
   • What can be flexible if obstacles arise?

3. Identify Key Assumptions:

   • What must be true for this to work?
   • Which assumptions are about biology vs. technology capabilities?

4. Sketch Alternative Paths:

   • If the primary approach fails, what's Plan B?
   • Can the project be designed to succeed regardless of outcome?

Output Deliverable

At the end of this skill, Claude should produce a 2-page Problem Ideation Document containing:

Page 1: Core Idea

• Title: Concise project name
• The Question: What biological question is being asked?
• The Approach: How will it be answered? (Specify perturbation/measurement/computation: logic vs. technology)
• What's Novel: The unique angle
• Why It Matters: Potential impact (generality × learning, or technology development)
• Intuition Pump(s) Used: Which prompted this idea

Page 2: Critical Analysis

• Fixed vs. Floating Parameters:

  • Fixed: What must stay constant
  • Floating: What can adapt

• Key Assumptions & Risk Assessment:

  • Biological assumptions (risk level 1-5)
  • Technical assumptions (risk level 1-5)

• Traps Avoided: Which pitfalls were navigated around?

• Alternative Approaches: Plan B and Plan C

• Literature Context:

  • 3-5 key papers that inform or relate to this work
  • Degree of competition (low/medium/high)
  • The user's edge/advantage

• Next Steps: First 3 concrete experiments or analyses

Key Principles to Remember

1. Reversal of Polarity: Treat ideas with skepticism, not reverence. Look for flaws before falling in love.

2. Comparison Shopping: Develop multiple ideas in parallel. The act of comparison improves decision-making.

3. Fix One Parameter at a Time: Constraints engender creativity, but too many constraints prevent it.

4. Think in Ensembles: The user is picking a family of possible projects, not a singular path. Flexibility is essential.

5. Balance Logic and Technology: Novel biology can come from new tools OR clever application of existing tools.

6. Systematic Over One-Off: High-throughput and systematic approaches often reveal more than single observations.

7. Dynamic Over Static: Biological systems are dynamic. How can process be captured rather than snapshot?

Getting Started

When the user is ready, Claude should guide them through the Phase 1 questions to begin the systematic ideation process. The key message: spending extra time on problem choice is the highest-leverage activity in science. A well-chosen problem executed reasonably well will have more impact than a mediocre problem executed brilliantly.

This skill is based on the problem choice framework developed by Michael A. Fischbach and Christopher T. Walsh, as described in "Problem choice and decision trees in science and engineering" (Cell, 2024).

SKILL 2: Risk Assessment and Assumption Analysis

Overview

This skill helps scientists systematically identify, quantify, and manage project risk through rigorous assumption analysis. The goal is not to eliminate risk—risk-free projects tend to be incremental—but to name it, quantify it, and work steadily to chip away at it. This skill builds directly on the Problem Ideation Document from Skill 1.

Core Principle

"Don't avoid risk; befriend it."

The most important concept in problem choice is the two-axis evaluation:

• X-axis: Likelihood of success
• Y-axis: Impact if successful

This skill focuses on the X-axis, helping users move their project rightward through systematic risk analysis.

Why This Matters

A project with a high-risk assumption that won't read out for >2 years is problematic. One that requires multiple miracles to succeed should be avoided or refined. The human tendency is to stay in a safe local space, work laterally, and put off facing existential risks—like an ostrich burying its head in the sand. This skill helps users face risk head-on.

The Skill Workflow

Phase 1: Extract Project Assumptions (10-15 minutes)

First, Claude should gather information about the user's project from Skill 1:

1. Project Summary (from Skill 1):

   • The biological question
   • The technical approach
   • What's novel about it

2. Project Horizon:

   • How long is this project expected to take? (months/years)
   • What is the user's role? (graduate student, postdoc, PI, startup founder)

3. Initial Risk Sense:

   • What keeps the user up at night about this project?
   • What's the scariest assumption?

Phase 2: Comprehensive Assumption Listing

Claude should work with the user to list EVERY assumption the project makes from inception through conclusion. Assumptions fall into two categories:

Type A: Assumptions About Biological Reality

These are facts about the world that either are or aren't true. They won't change during the project.

Examples:

• New cell types exist beyond what's currently known
• A particular gene regulates the process being studied
• Two proteins physically interact
• A pathway functions in the organism of interest
• The biological effect size is detectable

Type B: Assumptions About Technical Capability

These are about whether technology can do what's needed. These CAN change during the project as methods improve.

Examples:

• A specific cell type can be isolated
• Sequencing will generate high-quality data
• An assay has sufficient throughput
• Computational analysis can distinguish signal from noise
• Gene editing will work in the system

Claude should ask:

1. What must be true about the biology for this to work?
2. What must the technology be able to do?
3. What about the experimental design—what assumptions are built in?
4. What about the analysis—can it deliver what's needed?
5. If everything works, can the findings be validated?
6. Will the findings be interpretable and meaningful?

Phase 3: Risk Scoring (The Assumption Analysis Table)

For each assumption, Claude should help the user assign two scores:

Risk Level (1-5 scale):

• 1 = Very likely to be true/work (>90% confidence)
• 2 = Likely (70-90% confidence)
• 3 = Uncertain (40-70% confidence)
• 4 = Unlikely (10-40% confidence)
• 5 = Very unlikely (<10% confidence)

Time to Test (months):

How long before the user will know if this assumption is valid?

Critical Rules:

1. Be brutally honest—try to convince oneself of being WRONG, not right
2. Distinguish between biological vs. technical assumptions
3. Consider whether technical assumptions might improve over time
4. Note which assumptions depend on earlier assumptions succeeding

Phase 4: Risk Profile Evaluation

Once the complete table is ready, Claude should analyze the risk profile:

Red Flags to Identify:

1. The Late High-Risk Problem: Risk level 4-5 assumption that won't read out until >18 months
2. The Multiple Miracles: More than 2-3 assumptions with risk level 4-5
3. The Dependency Chain: High-risk assumptions stacked in sequence
4. The Ostrich Pattern: Starting with low-risk work while avoiding the high-risk tests

Green Lights:

1. Early Go/No-Go: Highest-risk assumption testable in <6 months
2. Multiple Candidates: Project can succeed with several different outcomes
3. Graceful Degradation: If assumption X fails, assumption Y provides alternative path
4. Risk Distribution: High-risk assumptions balanced across timeline

Rule of Thumb: If you have a risk level 5 assumption three years out, pick another project.

Phase 5: Risk Mitigation Strategies

For each high-risk assumption (level 4-5), Claude should help develop mitigation strategies:

Strategy 1: Move High-Risk Tests Earlier

Question: Can a quicker, cruder test be designed that answers most of what's needed?

Example: Instead of waiting 2 years to validate a new cell type exists, consider:

• Using existing markers as a proxy
• Testing in a simpler model system first
• Using computational predictions to increase confidence

Strategy 2: Multiple Candidates Approach

Question: Can multiple candidates be tested in parallel to increase likelihood of success?

Example: Instead of:

• Testing one kinase → Test a panel of 10 kinases
• Building one engineered organism → Build and test a library
• Pursuing one therapeutic target → Pursue 3 related targets

Strategy 3: Reframe the Question

Question: Can the project scope be adjusted to reduce critical assumptions while maintaining impact?

Example from lecture:

• Original: Identify NEW enteroendocrine cell types (high risk: they may not exist)
• Reframed: Better characterize KNOWN but incompletely understood cell types (lower risk)

Strategy 4: Change the System

Question: Is there a different biological system with similar scientific value but lower technical risk?

Example from lecture:

• Original: Intestinal epithelium (hard to manipulate genetically)
• Alternative: Liver (easier genetic manipulation options exist)

Strategy 5: Add Complementary Approaches

Question: Can a parallel approach be added that de-risks the main assumption?

Example from lecture:

• Add spatial transcriptomics to scRNA-seq
• This provides biogeographic context and validates cell type existence earlier

Phase 6: Go/No-Go Experiment Design

For the top 3 highest-risk assumptions, Claude should help design the critical go/no-go experiments:

For each, specify:

1. The Question: Exactly what is being tested?
2. The Experiment: Most direct test possible (even if crude)
3. Success Criteria: What result means "go"?
4. Failure Response: What result means "pivot" or "stop"?
5. Timeline: How soon can this be run?
6. Resources: What is needed?

Key Principle: Cut right to the critical go/no-go experiment. Don't just start with easy stuff—the risk points aren't going away.

Phase 7: Literature Validation

Claude should search PubMed to help calibrate risk assessments:

Search for:

1. Precedents: Has anyone done something similar? (Reduces technical risk)
2. Biological Evidence: What's known about the system? (Informs biological risk)
3. Technical Benchmarks: How well do the methods work in practice?
4. Adjacent Successes: Has anyone solved related problems?

Questions to ask the user:

• What specific searches would help calibrate risk?
• Are there particular papers that informed the assumptions?
• Are there technical benchmarks to look up?

Phase 8: Revised Project Plan

Based on the risk analysis, Claude should help create a revised plan:

Option A: De-Risk the Current Plan

• Reorder experiments to test high-risk assumptions early
• Add complementary approaches
• Design multiple-candidate strategies

Option B: Reframe the Project

• Adjust scope while maintaining impact
• Change biological system
• Modify technical approach

Option C: Pick a Different Project

Sometimes the honest answer is: "This has too many miracles." That's valuable to know BEFORE investing years.

Output Deliverable

Claude should produce a 2-page Risk Assessment Document:

Page 1: Assumption Analysis Table

*Bio = Biological reality, Tech = Technical capability
†Risk: 1=very likely to 5=very unlikely
‡Time to test in months

Risk Profile Summary:

• Total Assumptions: X
• High Risk (4-5): X assumptions
• Late High Risk (>18mo): X assumptions
• Critical Path: [Identify the chain of dependent assumptions]
• Overall Assessment: [Green/Yellow/Red light with explanation]

Page 2: Risk Mitigation Plan

Top 3 High-Risk Assumptions:

For each:

1. The Assumption: [Stated clearly]
2. Current Risk Level & Timeline: X (risk) at Y months
3. Why This Risk Exists: [Explanation]
4. Mitigation Strategy: [From Strategies 1-5 above]
5. Go/No-Go Experiment:
   • Experiment design
   • Success criteria
   • Timeline
   • What you'll do if it fails

Revised Project Timeline:

Month 0-6:   [Early go/no-go experiments]
Month 6-12:  [Based on go/no-go results]
Month 12-18: [...]
Month 18+:   [...]

Contingency Plans:

• If assumption X fails: [Plan B]
• If assumption Y fails: [Plan C]
• Multiple success paths: [How project can succeed different ways]

Decision Points:

• Month X: Evaluate [assumptions A, B] → Go/Pivot/Stop decision
• Month Y: Evaluate [assumptions C, D] → Go/Pivot/Stop decision

Practical Examples

Example 1: ScRNA-Seq for Enteroendocrine Cells

High-Risk Assumptions Identified:

1. "New cell types can be validated experimentally" (Risk 5, 24 months)
2. "Knockout will yield biologically relevant phenotype" (Risk 5, 30 months)

Problem: Two risk-5 assumptions at 24+ months = RED FLAG

Mitigation Applied:

• Reframe to study known but poorly characterized cells (reduces Risk 5→3)
• Switch to liver instead of intestine (improves validation timeline: 30→18 months)
• Add spatial transcriptomics (provides earlier validation checkpoint at 16 months)

Example 2: Bacterial Therapy for Chronic Kidney Disease

High-Risk Assumption Identified: "Key uremic toxins leading to effects can be determined" (Risk 4, unknown timeline)

Problem: Critical assumption with unclear path to resolution

Mitigation Applied:

• Focus on known lead toxins (IS and PCS) rather than discovering new ones
• Add parallel track: test multiple toxin candidates
• Design study where learning toxin identity IS the outcome (multiple success paths)

Key Principles to Remember

1. Try to Convince Yourself You're Wrong: The goal is critical evaluation, not confirmation bias.

2. Ignore Everything But Key Risk Points: Don't get distracted by easy tasks. The high-risk assumptions aren't going away.

3. Early and Often: Design go/no-go experiments at the earliest feasible moment.

4. Be Candid About Risk: When presenting ideas, acknowledging risk makes your case MORE convincing, not less.

5. No Risk, No Interest: The goal isn't zero risk—it's understood, quantified, manageable risk.

6. Risk Can Change: Technical assumptions may improve as methods advance. Build this into your planning.

7. Compare Risk Profiles: Evaluate multiple projects in parallel to compare risk profiles and make better choices.

8. Watch for the Ostrich Pattern: Are you avoiding the scary experiment? That's human nature, but a critical failure mode.

Warning Signs

Warning signs include:

• Risk level 5 assumptions >2 years out
• More than 3 assumptions at risk level 4-5
• Highest-risk assumptions at the END of the timeline
• Rationalizing why high-risk assumptions will "probably work out"
• Planning to "start with the easy stuff" while avoiding risk tests
• Inability to articulate clear go/no-go criteria

Good shape indicators:

• Highest-risk tests happen in first 6 months
• Multiple paths to success exist
• Clear plans for what to do if key assumptions fail
• Risk is distributed across the timeline
• Testing assumptions, not confirming hopes

Getting Started

Claude should begin with Phase 1 by asking for:

1. The project summary from Skill 1
2. Project timeline expectations
3. What concerns the user most about this project

Together, Claude and the user will build a rigorous risk assessment that dramatically improves the likelihood of success by helping avoid years of work on projects with insurmountable obstacles.

Remember: Spending time on risk analysis is the most valuable investment a scientist can make. A well-understood risk profile enables moving forward with confidence or pivoting with clarity—both are valuable outcomes.

SKILL 3: Optimization Function Selection

Overview

This skill helps scientists articulate HOW their project should be evaluated and define what success means. While Skill 2 focused on likelihood of success (the X-axis), this skill focuses on impact if successful (the Y-axis). The key insight: value is in the eye of a belief system—the value creation framework must be explicitly stated and led with.

Core Principle

"Pick the right optimization function."

Different types of projects should be evaluated by different metrics. A common source of conflict between trainees and PIs, or authors and referees, is a misunderstanding about which category a project falls under. The root cause is often failure to articulate evaluation criteria clearly.

The Fundamental Truth

The default state of:

1. Every new discovery is irrelevance
2. Every new technology is non-use
3. Every company is death

Scientists must actively work against these defaults by choosing the right metrics and scoring well on at least one axis.

The Skill Workflow

Phase 1: Project Categorization (5 minutes)

First, Claude should determine what type of project the user is pursuing:

Question 1: What is the primary goal? A. Understand how biology works (fundamental knowledge) B. Enable new experiments or capabilities (tool/technology) C. Solve a practical problem (invention/application) D. Something else (please describe)

Question 2: What would "success" look like in 3-5 years?

• 1-2 sentences describing the ideal outcome

Question 3: Who cares if this succeeds?

• Academic researchers in the subfield?
• Broader scientific community across fields?
• Clinicians or practitioners?
• Industry partners or companies?
• General public or specific communities?
• All of the above?

Based on the answers, Claude should help identify the right optimization function.

Phase 2: Understanding the Three Main Frameworks

Framework 1: Basic Science

Axes: How much did we learn? × How general/fundamental is the object of study?

Philosophy: A high score on EITHER axis yields substantial impact. You don't need both.

Examples:

• High Generality, Medium Learning: Ribosome stalling complex

  • Updates understanding of translation (fundamental process)
  • Scores well because translation is universal

• Medium Generality, High Learning: Oxytricha germ-line nucleus

  • Genomic acrobatics may not be common to other organisms
  • BUT elegant mapping scores highly on how much we learned
  • May yield tools for genome editing (bonus)

• High on Both Axes (Landmark): RNA interference, biomolecular condensates

  • These are rare—don't expect every project to be here
  • But aim to score well on at least one axis

Key Questions:

• How many systems/organisms does this apply to?
• Does it update understanding of a fundamental process?
• Will textbooks need to be rewritten?
• What new questions does this open?

Framework 2: Technology Development

Axes: How widely will it be used? × How critical is it for the application?

Philosophy: Again, high score on EITHER axis is sufficient.

Examples:

• Widely Used, Not Critical: BLAST

  • Used in countless projects
  • Rarely THE critical tool, but enormous cumulative impact

• Not Widely Used, Highly Critical: Cryo-electron tomography

  • Too complicated for broad adoption
  • But generates stunning data that's impossible to get otherwise
  • When you need it, nothing else works

• High on Both Axes (Game-Changing):

  • GFP, CRISPR, AlphaFold (the famous ones)
  • But also: lentiviral delivery, cell sorting, massively parallel sequencing
  • Technologies we cannot imagine living without

Key Questions:

• How many labs would adopt this?
• For what fraction of experiments is this THE enabling technology?
• What becomes possible that wasn't before?
• How hard is it to implement?

Critical Rule: A tool that won't be widely used AND isn't critical for an application probably isn't worth building.

Framework 3: Typical Invention/Application

Axes: How much good? × For how many people?

Philosophy: Useful for translational work, frugal science, global health.

Examples:

• Foldscope: Paper microscope accessible to millions of students globally
• Neglected tropical disease intervention: Quality-adjusted life years per $100
• Medical device: Number of patients who can access treatment

Key Questions:

• What problem does this solve?
• How many people have this problem?
• How much better is their life if you solve it?
• What's the cost per person helped?

Phase 3: Selecting and Articulating Your Framework

Based on your Phase 1 responses, let me help you choose:

If you selected A (fundamental knowledge): → Basic Science Framework If you selected B (enable experiments): → Technology Development Framework
If you selected C (solve practical problem): → Invention Framework

Now, let's be explicit:

1. State Your Framework: "This project should be evaluated as [basic science/technology development/invention]."

2. Define Your Axes:

   • X-axis measures: [specific metric]
   • Y-axis measures: [specific metric]

3. Make Your Case:

   • X-axis score (Low/Medium/High): [Your assessment + reasoning]
   • Y-axis score (Low/Medium/High): [Your assessment + reasoning]

4. Threshold Check:

   • Do you score at least MEDIUM-HIGH on one axis?
   • If both are LOW-MEDIUM, you have a problem

Phase 4: Alternative or Custom Metrics

Sometimes standard frameworks don't fit. Examples where custom metrics work:

Alternative Metric Examples:

• Frugal Science: How many children in low/middle-income countries gain access to microscopy?
• Neglected Disease: Quality-adjusted life years saved per $100 invested
• Sustainability: Tons of CO₂ equivalent prevented × cost-effectiveness
• Equity: Reduction in disparity metric × number of people affected

When to propose alternative metrics:

• Your work addresses a specific underserved need
• Standard metrics miss your core value proposition
• You're working in an emerging area without established norms
• Your work crosses traditional boundaries

How to propose alternative metrics:

1. Explain why standard metrics are insufficient
2. Define your proposed metric clearly
3. Provide a value creation index (two axes)
4. Show how your project scores on these axes

Phase 5: Comparative Assessment

Even if absolute impact is hard to estimate, comparative assessment is valuable:

Exercise: Compare 3 Related Projects

For your project and two alternatives (either from literature or hypothetical):

Comparative Questions:

• Which would be most impactful if they all work?
• Which has the best risk-adjusted impact?
• Are you pursuing the best option?
• If not, why? (Sometimes there are good reasons: resources, expertise, timing)

Phase 6: Avoiding Metric Mismatch

Common Mismatches:

Mismatch 1: Basic Science vs. Technology Evaluation

Scenario: You're doing fundamental biology, but reviewers ask "How widely will this be used?"

Problem: They're evaluating basic science with technology metrics

Solution: Explicitly frame as basic science. Lead with: "This updates our understanding of [fundamental process], which is conserved across [many systems]."

Mismatch 2: Technology vs. Basic Science Evaluation

Scenario: You're building a tool, but reviewers ask "How much did we learn about biology?"

Problem: They're evaluating technology with basic science metrics

Solution: Explicitly frame as technology development. Lead with: "This enables experiments that are currently impossible, which [X] labs need for [Y] applications."

Mismatch 3: Within-Category Confusion

Scenario: Your basic science is specific but deep, but reviewers want broad generality

Problem: They think both axes are required, rather than either/or

Solution: Explicitly acknowledge: "While this may not be universal, the depth of mechanistic insight scores highly on the learning axis."

Mismatch 4: Time Horizon Mismatch

Scenario: You're working on long-term fundamental research, but reviewers want immediate impact

Problem: Different value systems about when impact should materialize

Solution: Articulate your time horizon explicitly and provide historical examples of similar timelines

Phase 7: Value System Discussion

This is where Claude explicitly discusses the user's belief system about what matters:

Questions for Reflection:

1. What drives the user?

   • Discovery and understanding?
   • Enabling others?
   • Solving problems?
   • Building things?

2. What would make the user proud?

   • Paper in Cell/Nature/Science?
   • Tool used by hundreds of labs?
   • Treatment reaching patients?
   • Opening a new field?

3. How does the user want to be remembered?

   • "Discovered X"
   • "Built Y that enabled Z"
   • "Solved problem W"
   • "Trained students who went on to..."

4. Whose approval matters?

   • Specific senior scientists in the field?
   • Broader community across fields?
   • Practitioners who use tools?
   • People whose lives are improved?

There are no wrong answers—but alignment matters:

• The project should match the user's value system
• The evaluation framework should match the project type
• Communication should lead with the framework

Phase 8: Literature Benchmarking

Claude should use PubMed to benchmark impact in the user's area:

Searches should include:

1. Impact Exemplars: Papers the user considers high-impact in the field

   • What framework did they use (implicitly or explicitly)?
   • How did they score on the axes?
   • What made them successful?

2. Analogous Projects: Similar approaches or systems

   • How were they evaluated?
   • What impact did they achieve?
   • What can be learned from their framing?

3. Field Expectations: What's typical for the area?

   • Are basic science papers common?
   • Is technology development valued?
   • What level of impact is "good enough"?

Questions to ask the user:

• What papers should be analyzed as benchmarks?
• What search terms capture the field's impact exemplars?
• Are there specific journals or authors whose framing to emulate?

Phase 9: Communication Strategy

Once the framework is selected, here's how to lead with it:

In Talks:

Opening Frame (within first 2 slides):

• "The goal of this work is to understand [fundamental process X] in [general system Y]" → Basic science
• "We're developing a technology that will enable [critical experiment X] for [community Y]" → Technology
• "This invention addresses [problem X] affecting [N] people" → Application

In Papers:

Abstract Structure:

• State your framework implicitly through word choice
• Basic science: "reveals," "demonstrates," "shows that"
• Technology: "enables," "provides," "makes it possible to"
• Application: "solves," "addresses," "improves"

In Grants:

Broader Impact Section:

• Explicitly name your evaluation framework
• Provide the two-axis assessment
• Score yourself on each axis with evidence

With Your PI/Committee:

Alignment Conversation:

• "I want to make sure we're aligned on how this should be evaluated"
• "I see this as [framework], scoring [X] on [axis 1] and [Y] on [axis 2]"
• "Do you agree, or do you see it differently?"
• "This matters because..." [explain downstream implications]

Output Deliverable

Claude should produce a 2-page Impact Assessment Document:

Page 1: Framework and Scoring

Project Categorization:

• Type: Basic Science / Technology Development / Invention / Custom
• Rationale: [Why this categorization fits]

Optimization Function:

• X-Axis: [Metric name and definition]
• Y-Axis: [Metric name and definition]
• Custom Rationale (if applicable): [Why standard metrics don't fit]

Self-Assessment:

X-Axis Score: [Low/Medium/High]

• Evidence: [Specific reasons for this score]
• Examples: [Comparable projects or benchmarks]
• PubMed Support: [Key papers that inform assessment]

Y-Axis Score: [Low/Medium/High]

• Evidence: [Specific reasons for this score]
• Examples: [Comparable projects or benchmarks]
• PubMed Support: [Key papers that inform assessment]

Overall Assessment:

• Score on at least one axis: ☑ Yes / ☐ No
• Strong justification: ☑ Yes / ☐ No
• Aligned with your values: ☑ Yes / ☐ No

Visual Framework:

         [Your Project Type]
              
Y-Axis    |           ★ Your Project
[Metric]  |         /
          |       /
          |     /
          |   /
          |_________________
              X-Axis [Metric]
              
★ = Your project
Reference projects plotted for context

Page 2: Communication and Alignment

Value System Alignment:

• What Drives You: [Discovery/Enabling/Problem-solving/Building]
• Success Definition: [What would make this worthwhile]
• Approval Sources: [Whose opinion matters and why]
• Framework Fit: [How project aligns with values]

Potential Mismatches to Avoid:

1. [Specific mismatch type]

   • Scenario: [When this might happen]
   • Prevention: [How to frame to avoid it]

2. [Another mismatch]

   • Scenario: [When this might happen]
   • Prevention: [How to frame to avoid it]

Communication Strategy:

For Talks:

• Opening frame: [Exact language to use in first 2 slides]
• Key phrases: [Vocabulary that signals your framework]

For Papers:

• Abstract structure: [Framework-appropriate language]
• Impact statement: [How to articulate in discussion]

For Grants:

• Broader impact: [How to score yourself explicitly]
• Justification: [Evidence for scores]

For Mentors:

• Alignment question: [Exact question to ask]
• Your perspective: [How you see it]
• Discussion points: [What matters for alignment]

Comparative Analysis:

Action Items:

1. [Specific step to strengthen X-axis score or argument]
2. [Specific step to strengthen Y-axis score or argument]
3. [Communication alignment with key stakeholders]

Practical Examples

Example 1: Ribosome Stalling (Basic Science)

• Framework: Basic science
• X-Axis (Generality): HIGH—translation is universal
• Y-Axis (Learning): MEDIUM—mechanism of one quality control system
• Assessment: High on generality alone = substantial impact
• Communication: "Updates our understanding of translation quality control"

Example 2: BLAST (Technology)

• Framework: Technology development
• X-Axis (Widely Used): VERY HIGH—used by virtually all molecular biologists
• Y-Axis (Critical): LOW-MEDIUM—helpful but rarely essential
• Assessment: Extreme breadth of use = enormous cumulative impact
• Communication: "Enables rapid sequence comparison across all biological databases"

Example 3: Cryo-EM Tomography (Technology)

• Framework: Technology development
• X-Axis (Widely Used): LOW—complex, expensive, specialized
• Y-Axis (Critical): VERY HIGH—generates impossible-to-get-otherwise data
• Assessment: Extreme criticality for niche = high impact
• Communication: "Enables 3D visualization of molecular machines in native cellular context"

Example 4: Foldscope (Invention)

• Framework: Invention (custom metric)
• X-Axis (Good): MEDIUM—functional microscopy
• Y-Axis (People): VERY HIGH—millions of students globally
• Assessment: Massive reach × modest utility = transformative for education
• Communication: "Democratizes microscopy for global education"

Key Principles to Remember

1. Value Is in the Eye of a Belief System: Make yours explicit.

2. Lead with Your Metric: Don't assume others share your framework.

3. Either Axis Suffices: You don't need both—just score well on one.

4. Articulate Early: Discuss with mentors before you're 2 years in.

5. Avoid Default State: Work actively against irrelevance/non-use.

6. Compare, Don't Absolute: Even rough comparison beats ignoring impact.

7. Align Communication: Your words should signal your framework.

8. Match Project to Values: Life is too short for misaligned work.

Warning Signs

Warning signs include:

• Inability to articulate which framework applies
• Scoring LOW on both axes
• Project type and evaluation framework don't match
• User and PI have different frameworks but haven't discussed it
• Using basic science metrics for a tool or vice versa
• Never explicitly discussing impact assessment

Good shape indicators:

• Clear statement of optimization function
• MEDIUM-HIGH score on at least one axis
• Framework matches project type
• Alignment with key stakeholders
• Communication signals framework clearly
• Benchmarking against comparable work

Getting Started

Claude should begin Phase 1 by asking:

1. What is the primary goal? (A/B/C/D)
2. What would success look like in 3-5 years?
3. Who cares if this succeeds?

Together, Claude and the user will select the right optimization function and position the work for maximum impact.

Remember: Impact assessment isn't about ego—it's about ensuring work matters in the way the scientist wants it to matter. Explicit framing prevents years of misalignment.

SKILL 4: Parameter Fixation Strategy

Overview

This skill helps scientists strategically decide which parameters to fix and which to keep flexible in their project. The paradox: too many fixed parameters creates brittleness, but too few causes paralysis. The key is fixing ONE parameter thoughtfully and letting others float—constraints engender creativity.

Core Principle

"Fix one parameter; let the others float."

Most failure modes in ideation involve fixing too many parameters at the outset (system + method + application). Conversely, statements like "I want to do impactful work in cell engineering" are so broad they cause paralysis. The sweet spot: fix one meaningful constraint and let creativity flow within that boundary.

What Are Project Parameters?

Parameters are the choices that define your project:

Common Parameters:

• System: Which organism/cell type/tissue/molecule?
• Question: What biological phenomenon to study?
• Tool/Method: Which experimental approach?
• Application: What practical use or goal?
• Output: What form will results take?
• Collaborators: Who will you work with?
• Timeline: How fast must you move?
• Resources: What's available/necessary?

The Skill Workflow

Phase 1: Parameter Inventory (10 minutes)

First, let's identify what's already fixed in your current project idea:

Question 1: List your project parameters

For each category, indicate if it's FIXED (must stay) or FLOATING (could change):

Question 2: Count your fixed parameters

• How many did you mark as FIXED? _____
• If >2, you may have over-constrained the problem

Question 3: Why are they fixed? For each fixed parameter, is it because: A. Your expertise/passion B. Lab resources/capabilities
C. Advisor requirements D. You think it's the "best" solution E. Historical accident (you started this way)

Phase 2: The GLP-1 Example (Case Study)

Let's learn from a concrete example:

Proposed Project: Engineer a T cell to produce GLP-1 (glucagon-like peptide-1) for continuous supply.

Analysis: What's Fixed?

1. Improving GLP-1 receptor agonist delivery characteristics (the problem)
2. Using an engineered T cell (the solution)

Problem: Two parameters fixed = poor technique-application match

Alternative Framings:

If you fix Parameter 1 (GLP-1 delivery):

• Let the solution float
• Better options: peptide engineering for extended half-life, oral peptides, small molecules, B cells (better protein secretion)
• Why T cell is suboptimal: Not designed for protein secretion
• Best for: Trainee in metabolism lab who cares about GLP-1

If you fix Parameter 2 (Engineered T cell):

• Let the application float
• Better options: local-acting peptides (cytokines, chemokines, growth factors) for oncology/autoimmunity/regeneration
• Why GLP-1 is suboptimal: Doesn't leverage T cell's natural capabilities
• Best for: Trainee in immunology/cell engineering lab

Key Insight: Which parameter you fix depends on YOUR interests and your lab's expertise. Both can lead to great projects, but they're DIFFERENT projects.

Phase 3: Diagnostic Questions

The Goldilocks Test:

Too Many Fixed Parameters (>2):

• Are you forcing a technique-application match?
• If one assumption fails, does everything fail?
• Are you more attached to HOW than WHAT?
• Does your project sound like: "Use X to do Y in Z"?

Too Few Fixed Parameters (0-1 very broad):

• Do you feel paralyzed where to start?
• Is your statement super generic? ("Do impactful work in...")
• Are you avoiding commitment?
• Do you have decision fatigue?

Just Right (1-2 well-chosen):

• Do you have creative constraints?
• Can you articulate why THIS constraint matters?
• If one approach fails, do alternatives exist?
• Does the constraint energize you?

Phase 4: The Illumina Example (Constraints Drive Innovation)

Historical Context: Next-generation sequencing wasn't designed; we got Illumina's approach (many short reads).

Initial Constraint: Short reads seemed like a limitation

• Not what we would have "asked for"
• Seemed inferior to long reads

Innovation Unleashed:

• Computational methods (assembly algorithms)
• Novel applications (RNA-seq, ChIP-seq, ATAC-seq)
• Unexpected uses (protein folding via sequencing)
• Biochemical creativity to work within constraints

Lesson: Constraints don't limit creativity—they focus it. If you feel stuck, fix ONE parameter and watch resourcefulness emerge.

Phase 5: Which Parameter Should You Fix?

Strategic Questions to Identify the Right Fixed Parameter:

1. What can you prototype quickly?

   • What test article could you build rapidly?
   • Which experimental conditions enable early go/no-go?
   • What gives you fastest feedback?

2. What are people around you unusually good at?

   • Lab expertise?
   • Core facility capabilities?
   • Collaborator strengths?
   • Your unique skill combination?

3. What do you enjoy so much you don't think of it as work?

   • System you're passionate about?
   • Technique you love?
   • Type of question that excites you?

4. What's your competitive advantage?

   • Unique resource access?
   • Rare skill combination?
   • Proprietary data/reagents?
   • First-mover opportunity?

Common Strategic Choices:

Fix the System (Let question & tool float):

• Good if: You're an expert in the organism/tissue/cell type
• Enables: Asking multiple questions, trying various tools
• Example: "I study Drosophila neural development; I'll let the specific questions and methods emerge"

Fix the Question (Let system & tool float):

• Good if: You care deeply about a biological phenomenon
• Enables: Testing across systems, using best tool for each
• Example: "I want to understand phase separation; I'll study it wherever it's clearest"

Fix the Tool (Let system & question float):

• Good if: You're developing or mastering a technology
• Enables: Finding best applications, comparing across systems
• Example: "I'm building a new microscopy method; I'll find the most impactful uses"

Fix the Application (Let system & tool float):

• Good if: You have a specific translational goal
• Enables: Trying multiple approaches, testing in different models
• Example: "I want to treat disease X; I'm open to any validated approach"

Phase 6: Parameter Flexibility Matrix

For your project, let's create a flexibility assessment:

Analysis:

• Flexibility Score: How many "Yes" or "Maybe"? _____
• Risk Assessment: If <3 can float, you're brittle
• Pivot Potential: Which parameters provide escape routes?

Phase 7: Scenario Planning

For each fixed parameter, let's plan what happens if it becomes untenable:

Fixed Parameter 1: [Name it]

• Why it's fixed: [Your reason]
• Risk if this fails: [What breaks]
• Contingency: [What could you float instead]
• Alternative project: [If you fixed something else]

Fixed Parameter 2: [Name it]

• Why it's fixed: [Your reason]
• Risk if this fails: [What breaks]
• Contingency: [What could you float instead]
• Alternative project: [If you fixed something else]

Phase 8: The Unfixing Exercise

Sometimes you need to unfix parameters to escape a rut:

Current State: [Describe your over-constrained project]

Unfixing Experiment:

Try 1: Unfix the System

• Keep question & tool
• What other systems could you study?
• Which would be easier/faster/more informative?

Try 2: Unfix the Tool

• Keep system & question
• What other methods exist?
• Which are more mature/accessible/powerful?

Try 3: Unfix the Question

• Keep system & tool
• What other questions could you ask?
• Which would be more impactful/feasible?

Evaluation: Does any "unfixed" version seem better than your original? If yes, you over-constrained.

Phase 9: Literature Reality Check

Let's use PubMed to see how others handled parameter fixation:

Search 1: Successful projects in your area

• What did they fix?
• What did they let float?
• Did they pivot from their initial parameter choices?

Search 2: Failed or stalled projects

• (Often in discussion sections or preprints)
• Did they over-constrain?
• What parameters trapped them?

Search 3: Method papers

• How did technology developers choose applications?
• Did they fix the tool and let applications emerge?

Your Searches: What specific papers should we analyze for parameter lessons?

Output Deliverable

2-Page Parameter Strategy Document

Page 1: Current State and Analysis

Parameter Inventory:

Diagnostic Summary:

• Fixed Parameters: [Count and list]
• Assessment: ☐ Too Many (>2) / ☐ Just Right (1-2) / ☐ Too Few (0, too broad)
• Primary Fixed Parameter: [The one that matters most]
• Reason for Fixation: [Expertise/Passion/Resources/Other]

Goldilocks Test Results:

• Over-constrained indicators: [Yes/No to each test]
• Under-constrained indicators: [Yes/No to each test]
• Verdict: [Analysis]

Page 2: Strategy and Contingencies

Recommended Parameter Strategy:

Core Fixed Parameter: [The one to keep]

• Rationale: [Why this one]
• Your advantage: [Expertise/access/passion]
• Enables: [What becomes possible]

Parameters That Should Float: [List]

• [Parameter 1]: [How to explore alternatives]
• [Parameter 2]: [How to explore alternatives]

If Core Assumptions Fail:

Scenario 1: [Specific failure mode]

• Unfix: [Which parameter to let float]
• Alternative 1: [New configuration]
• Alternative 2: [Another option]

Scenario 2: [Another failure mode]

• Unfix: [Which parameter]
• Alternative 1: [New configuration]
• Alternative 2: [Another option]

Project Ensemble:

Core Fixed: [X]

Possible Projects:
1. [X] + [A] + [B1] → [Outcome]
2. [X] + [A] + [B2] → [Outcome]
3. [X] + [C] + [B1] → [Outcome]

All share [X], but float other parameters

Strategic Questions Answered:

1. Quick prototype: [How to test quickly]
2. Team strengths: [Who's good at what]
3. Your passion: [What energizes you]
4. Competitive advantage: [Your edge]

Historical Parallel:

[Example like Illumina where constraints drove innovation in your field]

• The constraint: [What seemed limiting]
• The innovation: [How people worked within it]
• Your application: [How this applies to your project]

Practical Examples

Example 1: GLP-1 T Cell Project (Over-Constrained)

• Fixed: GLP-1 delivery + T cell engineering
• Problem: Poor technique-application match
• Solution: Unfix one parameter
  • Fix delivery, float cell type → Better options emerge
  • Fix T cell, float payload → Better applications emerge

Example 2: Drosophila Neurobiologist (Well-Constrained)

• Fixed: Drosophila nervous system
• Floating: Specific questions, methods
• Works because: Deep system expertise, many tools available
• Enables: Pursuing most impactful questions as field evolves

Example 3: "Impactful Cell Engineering" (Under-Constrained)

• Fixed: Nothing specific
• Problem: Paralysis from too many options
• Solution: Fix one meaningful constraint
  • Option A: Fix CAR-T platform → Find best applications
  • Option B: Fix autoimmune disease → Find best cell engineering approach
  • Option C: Fix specific rare disease → Let methods emerge

Key Principles to Remember

1. Constraints Engender Creativity: Limitations focus resourcefulness

2. One Parameter Rule: Fix one meaningful constraint, let others float

3. Match to Your Strengths: Fix the parameter you have advantage in

4. Technique-Application Match: Don't force tools into wrong problems

5. Flexibility = Resilience: Floating parameters provide pivot options

6. Historical Lesson: Best technologies emerged from working within constraints (Illumina)

7. Not Forever: Parameters can unfix mid-project when stuck

Warning Signs

Over-Constrained (Too Many Fixed):

• Project sounds like: "Use X to study Y in Z"
• When one assumption fails, everything fails
• You're attached to HOW more than WHAT
• Forcing a technique-application match

Under-Constrained (Too Few/Vague):

• Statement is incredibly broad ("impactful work in...")
• Feeling paralyzed about where to start
• Avoiding commitment due to infinite options
• No clear next experimental step

Well-Constrained:

• One clear fixed parameter with good rationale
• Multiple paths within that constraint
• Energized by the focused challenge
• If one approach fails, alternatives exist

Ready to Begin?

Let's start with Phase 1. Please provide:

1. Your current project description
2. List of what you think is fixed vs. floating
3. Your lab's core expertise
4. What aspect excites you most

Together we'll optimize your parameter strategy for maximum creativity and resilience.

Remember: The right constraint is liberating, not limiting. It channels creativity into productive directions while maintaining flexibility for pivots.

SKILL 5: Decision Tree Navigation ("The Altitude Dance")

Overview

This skill teaches you to move fluidly between execution (Level 1: getting stuff done) and strategic evaluation (Level 2: critical thinking). Projects rarely unfold linearly—they require frequent course correction. Most trainees should spend MORE time on their project's decision tree.

Core Principle

"Learn the altitude dance"

Move back and forth frequently between:

• Level 1: Full immersion in experimental details or coding
• Level 2: Step back, clear your head, evaluate as if someone else did the work

These cannot be done simultaneously. The key to navigating a project's decision tree is alternating between these levels deliberately.

Key Concepts

Why Decision Trees Matter: Once you're in a project, the landscape changes:

• You've learned from initial experiments
• New papers have been published
• Technology has advanced
• Your assumptions have been tested

At any decision point, you should rarely follow your plan from 2 years ago—there will be a better alternative.

The Altitude Levels:

• Level 1 (Ground Level): Doing the work, troubleshooting, optimizing
• Level 2 (Strategic Altitude): What did we learn? What should we do next?
• Level 3 (Field Altitude): How does this fit in the broader landscape?
• Level 4 (Career Altitude): Is this the right use of my finite time?

Common Failure Modes:

1. Stuck in Level 1: Troubleshooting endlessly without reassessing the plan
2. Only Level 2: Brilliant strategist but never rolls up sleeves
3. No rhythm: Switching randomly instead of deliberately

Workflow

Phase 1: Map Your Decision Tree

For your project, identify:

1. Initial plan: What was the intended path?
2. Branch points: Where might alternative paths emerge?
3. Decision criteria: What determines which branch to take?
4. New information: What could change the landscape?

Phase 2: Establish Your Rhythm

Recommended Schedule:

• Daily: Level 1 work (experiments, coding, analysis)
• Weekly: Level 2 evaluation (1-2 hours, ideally Friday afternoon)
• Monthly: Level 3 field review (read new papers, attend seminars)
• Quarterly: Level 4 career check-in (with mentor)

Level 2 Weekly Protocol:

1. Clear your head (walk, coffee, change of scene)
2. Review what happened this week
3. Ask: What did we learn?
4. Ask: What should happen next?
5. Update decision tree
6. Plan next week's Level 1 work

Phase 3: Decision Points

At each major branch point:

Example: Genetic Screen Hits Wall

Instead of endless troubleshooting:

• Alternative 1: Redo computational analysis with larger genome dataset
• Alternative 2: Use AlphaFold models to search for similar folds
• Alternative 3: Print and test larger candidate set (DNA synthesis cheaper now)

Framework:

1. Acknowledge the stuck point
2. Step to Level 2: Evaluate with fresh eyes
3. Consider: What's newly possible? (technology, knowledge)
4. Generate 3 alternatives
5. Decide: Troubleshoot more vs. pursue alternative

Output: Decision Tree Map

• Visual map of your project's decision points
• Update frequency schedule
• Criteria for each branch point
• Protocol for getting unstuck

SKILL 6: Adversity Response Planning ("The Adversity Feature")

Overview

This skill helps you prepare for inevitable crises and reframe them as opportunities. The term "adversity feature" (like a "rock garden" on a mountain bike trail) captures the mindset: adversity is not an obstacle—it's an opportunity to develop skill and improve your project.

Core Principle

"Capitalize on the 'adversity feature'"

Adversity in a project is inevitable AND opportune:

• Inevitable: Almost every project suffers existential crisis or sharp turn
• Opportune: Two valuable outcomes possible:
  1. Fix the problem AND upgrade the project simultaneously
  2. Develop reasoning-your-way-out skills (best growth opportunity)

Key Concepts

Why Adversity Is Inevitable:

• Technology doesn't work as advertised
• Biological assumptions prove false
• You get scooped
• Key collaborator leaves
• Funding runs out
• Results don't support hypothesis

Why Adversity Is Opportune:

• Forces you to think deeply about alternatives
• Removes sunk-cost bias (path is blocked anyway)
• Often leads to better projects than original plan
• Develops critical problem-solving skills
• Makes you resourceful

The Crisis Mindset:

• Wrong: "This is a disaster that delays me"
• Right: "This is the crisis I've been waiting for—don't waste it"

Workflow

Phase 1: Anticipate Failure Modes

For your project, list likely adversity scenarios:

1. Technical failures: Method doesn't work, signal too low, etc.
2. Biological surprises: System behaves unexpectedly
3. Competition: Someone scoops you
4. Resource issues: Funding, equipment, access
5. Timeline pressures: Takes longer than expected

For each, rate:

• Likelihood (Low/Medium/High)
• Impact if it happens (Low/Medium/High)
• When it might surface (early/mid/late)

Phase 2: Upgrade Opportunities

For each high-likelihood or high-impact failure mode:

Question 1: How could you fix this AND make the project better? Not just: "Get it working" Instead: "Use this as opportunity to improve the approach"

Example: Your Cell Type Can't Be Isolated

• Fix: Develop new isolation method
• Upgrade: Make method work for whole class of cell types
• Result: Better project (technology paper) + original biology

Question 2: What skill would you develop by solving this?

• Computational: Learn new analysis method
• Technical: Master challenging technique
• Conceptual: Reason through biological complexity

Phase 3: The Ensemble View

Critical Insight: You're not picking ONE project path—you're picking an ENSEMBLE of possible projects that share core elements.

Your Project Ensemble:

Core Theme: [What stays constant]

Path 1: [Original plan]
Path 2: [If assumption A fails]
Path 3: [If technical barrier B encountered]
Path 4: [If scooped on C]

All paths lead to impactful results, just different ones

This reframing is liberating: when adversity strikes, you're not failing—you're discovering which path in the ensemble you're actually on.

Phase 4: Historical Examples

Example 1: PROTAC Discovery

• Original Plan: Create molecules to degrade specific kinase
• Crisis: Didn't work for intended target
• Upgrade: Test across kinome systematically
• Result: Better project (mapped degradable kinome, discovered that target engagement ≠ degradation)
• Impact: More influential than if original plan succeeded

Example 2: Steroid Receptor Study

• Original Plan: Identify THE receptor for a steroid
• Crisis: Binds multiple receptors at different affinities
• Upgrade: Reframe question: How does finite receptor pool sense infinite lipids?
• Result: Combinatorial sensing model (like piano chords)
• Impact: More interesting than "receptor X binds steroid Y"

Output: Adversity Playbook

Page 1: Anticipated Crises

Page 2: Upgrade Strategies For each high-priority crisis:

• The Crisis: [Description]
• Fix Strategy: [How to solve it]
• Upgrade Strategy: [How to make project better while fixing]
• Alternative Path: [New direction if fix doesn't work]
• Ensemble Position: [How this fits in project family]

Page 3: Resilience Rituals

• Weekly check-in: Review what went wrong, what was learned
• Monthly ensemble review: Update the family of possible projects
• Crisis protocol: When major setback hits, take 2 days to think before acting
• Growth tracking: Document skills developed through adversity

SKILL 7: Problem Inversion Strategies ("Turn It On Its Head")

Overview

This skill provides three concrete strategies for navigating around obstacles by reframing problems. When stuck, instead of pushing harder on the current approach, try inverting the problem.

Core Principle

"Turn a problem on its head"

Three powerful strategies:

1. Unfix parameters (covered in Skill 4, applied here in crisis)
2. Don't achieve goal A? Achieve comparable goal B
3. "I have the answer; what is the question?"

Strategy 1: Unfix Parameters (In Crisis Mode)

When to Use: Run-of-the-mill issues in project execution

Approach: Let a "sacred" fixed parameter float

Example from Lecture:

• Stuck: Spatial transcriptomics of APC-T cell interactions in tumor microenvironment
• All fixed: Technique, cell types, context
• Inversion:
  • Unfix technique → What else could measure these interactions?
  • Unfix cell types → What other interactions matter in tumors?
  • Unfix context → Where else do APC-T interactions matter?

Your Application: For each fixed parameter in your project:

• What if this floated?
• What alternatives exist?
• Which would be easier/faster/more informative?

Strategy 2: Comparable Goal Substitution

When to Use: Existential threats to project (can't achieve original goal)

Approach: Achieve a different but equally valuable goal

Mindset Shift:

• Wrong: "I failed to do X"
• Right: "The world needs Y instead, which I CAN do"

Example from Lectures: PROTAC Story

• Goal A (Failed): Degrade specific therapeutic target
• Goal B (Achieved): Map which kinases ARE degradable
• Value: B is more impactful (general principle + method validation)
• Learning: Target engagement ≠ degradation (important discovery)

Framework:

1. Original goal: [What you wanted]
2. Why it failed: [Specific reason]
3. What CAN you do with current data/tools: [Capabilities]
4. Comparable goals:
   • Option 1: [Different but related goal]
   • Option 2: [Another alternative]
   • Option 3: [Yet another]
5. Which is most valuable: [Analysis]
6. How to frame it: [Communication strategy]

Strategy 3: Answer Seeking Question

When to Use: End-of-project challenges (interpretation, framing, application)

Approach: You got an answer, but not to your original question. What question DOES your data answer?

Mindset Shift:

• Wrong: "This doesn't answer my question"
• Right: "What interesting question does this answer?"

Example from Lectures: Steroid Receptor

• Original Question: What is THE receptor for this steroid?
• Answer Obtained: Binds multiple receptors at different affinities
• Problem: Can't answer original question (no single receptor)
• Inversion: "What question does this answer?"
• New Question: How does finite receptor pool sense infinite lipids?
• Answer: Combinatorial sensing (pattern = unique "chord")
• Impact: More interesting than intended finding

Framework:

1. Original question: [What you asked]
2. Data obtained: [What you actually found]
3. Why it doesn't answer: [The mismatch]
4. What DOES the data show clearly: [Solid findings]
5. What questions could these answer:
   • Question 1: [Option]
   • Question 2: [Option]
   • Question 3: [Option]
6. Which is most interesting: [Assessment]
7. How to reframe paper/project: [New framing]

Workflow

Phase 1: Identify Your Obstacle

• Type: Technical / Biological / Competitive / Interpretive
• Severity: Run-of-mill / Existential / End-stage
• Description: [What's blocking you]

Phase 2: Select Strategy

Phase 3: Apply Strategy

Work through the relevant framework above with your specific situation.

Phase 4: Evaluate Alternatives

For each alternative generated:

• Scientific value: How interesting is this?
• Feasibility: How hard to execute?
• Timeline: How long will it take?
• Impact: How does this compare to original plan?
• Your advantage: Do you still have edge here?

Output: Problem Inversion Analysis

Page 1: Current Situation

• Obstacle: [Clear description]
• Why you're stuck: [Root cause]
• Original plan: [What you intended]
• Current capability: [What you CAN do]

Page 2: Strategy Applications

Strategy 1 (Unfix Parameters):

Strategy 2 (Comparable Goals):

Strategy 3 (Answer → Question):

• Data obtained: [What you have]
• Question 1 it could answer: [Option 1]
• Question 2 it could answer: [Option 2]
• Question 3 it could answer: [Option 3]
• Most interesting: [Selection + reasoning]

Page 3: Recommended Path

• Selected strategy: [1, 2, or 3]
• New direction: [Specific plan]
• Why this is better: [Not just "it works" but "it's more interesting"]
• Communication approach: [How to frame this pivot]
• Timeline: [New schedule]

SKILL 8: Integration and Synthesis

Overview

This final individual skill synthesizes all previous skills into a coherent project plan and communication strategy. You'll create a complete package that demonstrates thoughtful problem selection and rigorous planning.

Core Principle

"Tell a compelling story with your choices"

Humans love stories. Your project should have:

• Setting: Background and problem framing
• Problem statement: Clear, general enough to be interesting, specific enough to be distinctive
• New idea/approach: Your angle (perturbation/measurement/theory: logic vs. technology)
• Iteration: Loop of "we wondered X → did Y → found Z → interpreted as W"
• Conclusion: What we learned and/or what's now possible
• Passion: Authentic enthusiasm

Workflow

Phase 1: Gather Your Skill Outputs

Collect your completed documents:

• ☐ Skill 1: Problem Ideation Document
• ☐ Skill 2: Risk Assessment Matrix
• ☐ Skill 3: Impact Assessment Document
• ☐ Skill 4: Parameter Strategy Document
• ☐ Skill 5: Decision Tree Map
• ☐ Skill 6: Adversity Playbook
• ☐ Skill 7: Problem Inversion Analysis (if applicable)

Phase 2: Create Narrative Arc

Story Structure for Your Project:

1. Setting (Background)

• What's known in the field?
• What's the gap or opportunity?
• Why does this matter?

2. Problem Statement

• General enough: connects to broad principle
• Specific enough: distinctive and tractable
• Your framing from Skill 1

3. Your Approach

• Perturbation/Measurement/Theory
• Logic vs. Technology
• What's novel about your angle (from Skill 1)
• How your optimization function shapes approach (from Skill 3)

4. Strategy

• Fixed vs. floating parameters (from Skill 4)
• Decision points mapped out (from Skill 5)
• Risk mitigation built in (from Skill 2)
• Adversity contingencies (from Skill 6)

5. Why You

• Your competitive advantage
• Lab expertise
• Your passion and alignment
• Timeline and resources

Phase 3: Communication Formats

Format 1: 3-Slide, 5-Minute Presentation

Slide 1: The Opportunity

• Setting + Problem statement
• One key figure or schematic
• Why this matters (optimization function)

Slide 2: Your Approach

• New idea/angle
• Key experiments or analyses
• What makes this feasible
• Decision tree highlights

Slide 3: Impact and Timeline

• What you'll learn or enable
• Success metrics
• Timeline with milestones
• Your advantage

Slide Design Tips:

• Minimal text (bullets are fine here)
• Strong visuals
• Tell story, don't catalog facts
• Passion shows through

Format 2: 1-Page Written Summary

Paragraph 1: Setting and problem (2-3 sentences) Paragraph 2: Your approach and novelty (3-4 sentences) Paragraph 3: Why it will work (risk mitigation, your advantage) (2-3 sentences) Paragraph 4: Impact and timeline (2-3 sentences)

Total: ~250-300 words that could be abstract or summary

Format 3: 1-Minute Elevator Pitch

Structure:

• "I'm working on [problem] because [why it matters]"
• "Current approaches are limited by [gap]"
• "My angle is [approach] which is novel because [what's new]"
• "This will [impact] and I have [advantage]"

Practice until: Natural, passionate, memorable

Phase 4: Integration Document

Complete Project Plan Integrating All Skills:

Section 1: Problem Selection Rationale

• How you generated this idea (Skill 1 intuition pumps)
• Why this problem matters (Skill 3 optimization function)
• Your competitive advantage

Section 2: Risk Management

• Assumption analysis table (Skill 2)
• Go/no-go experiments
• Timeline with checkpoints
• Mitigation strategies

Section 3: Execution Strategy

• Fixed vs. floating parameters (Skill 4)
• Decision tree navigation plan (Skill 5)
• Adversity response protocols (Skill 6)
• Project ensemble (alternative paths)

Section 4: Communication Plan

• Presentations (3-slide deck)
• Written summary (1-page)
• Elevator pitch (1-minute)
• Key messages for different audiences

Section 5: Career Alignment

• How this fits your trajectory
• Skills you'll develop
• Network you'll build
• Next steps after this project

Output: Complete Project Package

Document 1: Integrated Project Plan (4-6 pages)

• All sections above
• References to individual skill outputs
• Timeline and milestones
• Resource requirements

Document 2: Communication Materials

• 3-slide presentation
• 1-page summary
• Elevator pitch script
• Talking points for different audiences

Document 3: Living Documents

• Decision tree (to update regularly)
• Risk assessment (to review quarterly)
• Adversity playbook (to consult in crisis)
• Parameter strategy (to revisit if stuck)

Key Principles

1. Integration, Not Duplication: Each skill output serves a purpose in the whole
2. Story Over Catalog: Communicate choices, not just facts
3. Passion Matters: Authentic enthusiasm is persuasive
4. Living Plan: This evolves; revisit quarterly
5. Alignment: Project, values, and career fit together
6. Preparation: You've thought through contingencies
7. Communication: You can pitch this clearly to anyone

Ready to Synthesize

With all skills complete, you now have a comprehensive, thoughtful, rigorous approach to problem selection and project planning. This is the highest-leverage work you can do in science.

SKILL 9: Meta-Framework - Complete Problem Selection Workflow

Overview

This meta-skill orchestrates the complete problem selection process, guiding users through Skills 1-8 in a systematic, iterative way. This skill should be used when comprehensive support is needed from ideation through execution planning, with integrated literature searches and coherent documentation.

When to Use This Skill

Use Skill 9 (Complete Workflow) when:

• Starting a new project from scratch
• Major project pivot or reframe needed
• Grant/fellowship application requiring systematic planning
• Thesis committee meeting preparation
• Startup company planning
• Want comprehensive, documented problem selection process

Use Individual Skills when:

• You're at a specific stage (e.g., just need risk assessment)
• Quick consultation on one aspect
• Updating one component of existing plan
• Teaching/learning one concept

The Complete Workflow

Overview of the Journey

START: Vague idea or area of interest
    ↓
[SKILL 1] → Problem Ideation Document
    ↓
[SKILL 2] → Risk Assessment Matrix
    ↓
[SKILL 3] → Impact Assessment Document
    ↓
[SKILL 4] → Parameter Strategy Document
    ↓
[SKILL 5] → Decision Tree Map
    ↓
[SKILL 6] → Adversity Playbook
    ↓
[SKILL 7] → Problem Inversion Analysis (if needed)
    ↓
[SKILL 8] → Integrated Project Plan + Communication Materials
    ↓
END: Comprehensive, rigorous project ready to execute

Estimated Time:

• Intensive: 1 week of focused work (full-time)
• Distributed: 4-6 weeks with other commitments
• With iterations: Add 50% more time

You'll invest time once to save years of potential missteps.

Phase-by-Phase Workflow

Phase 1: Preparation (Before Starting)

Gather Your Context:

1. Your background:

   • Research area/field
   • Current position (grad student, postdoc, PI, etc.)
   • Lab expertise and resources
   • Timeline constraints

2. Your starting point:

   • Vague area of interest?
   • Specific problem in mind?
   • Must build on existing work?
   • Starting completely fresh?

3. Your goals:

   • Publication target (journal tier, timeline)?
   • Degree requirement (thesis chapter)?
   • Funding application?
   • Startup foundation?
   • Career development?

Set Expectations:

• This process will challenge your assumptions
• You may discover your initial idea needs major revision
• That's the point—better to know now than after 2 years
• Intellectual honesty is required; this only works if you're rigorous

Phase 2: Ideation (Skill 1) - ~1 week

What We'll Do:

1. Understand your context and constraints
2. Work through relevant intuition pumps
3. Avoid common ideation traps
4. Generate 2-3 project ideas
5. Preliminary literature search to calibrate scope
6. Select most promising idea
7. Create Problem Ideation Document (2 pages)

Literature Integration Point 1:

• Search PubMed for precedents and adjacent work
• Assess generality of problem
• Identify methodological advances
• Determine competition level

Deliverable:

• Problem Ideation Document with core idea and initial analysis
• List of 10-15 key papers
• Preliminary assessment of novelty and feasibility

Checkpoint: Do you have a clear, specific idea that excites you? If not, iterate on intuition pumps.

Phase 3: Risk Analysis (Skill 2) - ~3-5 days

What We'll Do:

1. Extract ALL assumptions from your idea
2. Categorize (biological vs. technical)
3. Score each assumption (risk 1-5, time to test)
4. Identify high-risk late-reading assumptions
5. Design go/no-go experiments
6. Develop mitigation strategies
7. Create Risk Assessment Matrix (2 pages)

Literature Integration Point 2:

• Search for technical precedents (has method worked before?)
• Find biological evidence (what's known about your system?)
• Identify benchmarks (success rates, effect sizes)
• Assess timeline realism

Deliverable:

• Complete assumption analysis table
• Top 3 high-risk assumptions with mitigation plans
• Go/no-go experiment designs
• Revised timeline with decision points

Checkpoint: Is your risk profile acceptable? If risk-5 assumptions are >2 years out, return to Skill 1 to reframe.

Phase 4: Impact Assessment (Skill 3) - ~2-3 days

What We'll Do:

1. Categorize your project type
2. Select appropriate optimization function
3. Score yourself on both axes
4. Compare to benchmarks
5. Articulate value system alignment
6. Develop communication strategy
7. Create Impact Assessment Document (2 pages)

Literature Integration Point 3:

• Identify high-impact exemplars in your field
• Analyze their framing and evaluation
• Benchmark your potential impact
• Understand field expectations

Deliverable:

• Clear optimization function selection
• Self-assessment on both axes with justification
• Comparative analysis vs. alternatives
• Communication strategy for different audiences

Checkpoint: Do you score MEDIUM-HIGH on at least one axis? If not, return to Skill 1 to find higher-impact angle.

Phase 5: Parameter Strategy (Skill 4) - ~2-3 days

What We'll Do:

1. Inventory all project parameters
2. Identify which are fixed vs. floating
3. Assess if you're over/under-constrained
4. Select strategic fixed parameter
5. Plan flexibility for contingencies
6. Create Parameter Strategy Document (2 pages)

Literature Integration Point 4:

• How did successful projects handle parameters?
• What parameter choices led to breakthroughs?
• What over-constraints caused failures?

Deliverable:

• Complete parameter inventory
• Strategic rationale for fixed/floating decisions
• Flexibility matrix for contingencies
• Project ensemble (family of related projects)

Checkpoint: Have you fixed 1-2 meaningful parameters while maintaining flexibility? If too rigid, adjust.

Phase 6: Decision Tree Planning (Skill 5) - ~2 days

What We'll Do:

1. Map your project's decision tree
2. Identify major branch points
3. Set criteria for each decision
4. Establish Level 1 / Level 2 rhythm
5. Create protocols for getting unstuck
6. Create Decision Tree Map (1-2 pages)

No major literature search here (unless you identify specific decision points needing technical information)

Deliverable:

• Visual decision tree
• Decision criteria at each branch
• Schedule for Level 2 evaluations
• Protocol for course correction

Checkpoint: Have you planned for regular strategic evaluation, not just execution?

Phase 7: Adversity Preparation (Skill 6) - ~2 days

What We'll Do:

1. Anticipate likely failure modes
2. For each, identify upgrade opportunity
3. Map your project ensemble
4. Create crisis response protocols
5. Create Adversity Playbook (2-3 pages)

Literature Integration Point 5:

• Historical examples of productive pivots
• How did others capitalize on adversity?
• What second-generation projects emerged from failures?

Deliverable:

• Anticipated crisis catalog
• Upgrade strategies for each
• Project ensemble map
• Resilience rituals and protocols

Checkpoint: Are you prepared to see adversity as opportunity? Have you planned how to upgrade, not just fix?

Phase 8: Problem Inversion Toolkit (Skill 7) - ~1 day

What We'll Do:

1. Review three inversion strategies
2. Pre-plan applications for your likely obstacles
3. Create Problem Inversion Analysis (1-2 pages)

This is preparatory - you may not need it now, but when crisis hits, you'll have framework ready.

Deliverable:

• Strategy 1 application planned
• Strategy 2 options identified
• Strategy 3 alternative questions brainstormed
• Quick-reference guide for crisis

Checkpoint: Do you have concrete strategies for inverting problems when stuck?

Phase 9: Integration and Synthesis (Skill 8) - ~3-5 days

What We'll Do:

1. Review all outputs from Skills 1-7
2. Create cohesive narrative
3. Develop communication materials:
   • 3-slide presentation
   • 1-page summary
   • 1-minute elevator pitch
4. Write integrated project plan (4-6 pages)
5. Create living documents for ongoing use

Literature Integration Point 6:

• Final references for integrated plan
• Key papers for each section
• Communication examples from field leaders

Deliverable:

• Complete Integrated Project Plan (4-6 pages)
• 3-slide presentation deck
• 1-page written summary
• Elevator pitch script
• Living documents (decision tree, risk matrix, etc.)

Checkpoint: Can you communicate your project compellingly in 1 minute, 5 minutes, and 1 page? Do all pieces fit together coherently?

Iteration and Refinement

When to Iterate

Red Flags That Require Going Back:

From Skill 2 (Risk):

• Risk-5 assumptions >2 years out → Return to Skill 1 (reframe problem)

• 3 risk-4-5 assumptions → Return to Skill 1 (simplify or change approach)

From Skill 3 (Impact):

• Score LOW on both axes → Return to Skill 1 (find higher-impact angle)
• Optimization function mismatch → Return to Skill 1 (reframe problem)

From Skill 4 (Parameters):

• 2 fixed parameters → Return to Skill 1 (over-constrained)

• Zero fixed parameters → Return to Skill 1 (under-constrained)

From Skills 5-6:

• No clear decision points → Return to Skill 4 (need more flexibility)
• Every failure mode is existential → Return to Skill 2 (too risky)

Iteration Protocol

Major Revision Needed:

1. Pause and acknowledge: The process is working—it caught a problem
2. Return to indicated skill: Usually Skill 1 or 2
3. Bring forward what you learned: Don't start from scratch
4. Revised idea → Run through workflow again: Faster the second time
5. Multiple iterations OK: Better than years on wrong project

Minor Refinement:

1. Update specific document: E.g., adjust parameter strategy
2. Check downstream effects: Does this change anything else?
3. Update integration document: Keep everything coherent

Literature Integration Strategy

Overall PubMed Approach

Throughout the workflow, use PubMed strategically:

1. Skill 1 (Ideation): Assess generality, find precedents, gauge competition
2. Skill 2 (Risk): Technical feasibility, biological evidence, benchmarks
3. Skill 3 (Impact): Field exemplars, evaluation frameworks, benchmarks
4. Skill 4 (Parameters): Successful parameter choices, cautionary tales
5. Skill 6 (Adversity): Productive pivots, upgrade examples
6. Skill 8 (Integration): Communication models, comprehensive references

Search Strategy:

• Start broad (field overview)
• Get specific (your exact approach)
• Look adjacent (related systems/methods)
• Find benchmarks (what's state-of-art?)
• Identify competition (who else is doing this?)

Papers to Track:

• ~10-15 key papers from Skill 1
• ~5-10 technical papers from Skill 2
• ~5-10 impact exemplars from Skill 3
• ~5 parameter lessons from Skill 4
• ~3-5 pivot examples from Skill 6
• Total: ~30-50 papers (your foundation)

Final Deliverable Package

What You'll Have at the End

Core Documents (Organized Folder):

1. 01_Problem_Ideation.pdf (2 pages, Skill 1)
2. 02_Risk_Assessment.pdf (2 pages, Skill 2)
3. 03_Impact_Assessment.pdf (2 pages, Skill 3)
4. 04_Parameter_Strategy.pdf (2 pages, Skill 4)
5. 05_Decision_Tree.pdf (1-2 pages, Skill 5)
6. 06_Adversity_Playbook.pdf (2-3 pages, Skill 6)
7. 07_Problem_Inversion.pdf (1-2 pages, Skill 7)
8. 08_Integrated_Plan.pdf (4-6 pages, Skill 8)

Communication Materials:

• Presentation_3slides.pptx
• Summary_1page.pdf
• Elevator_Pitch.txt

Living Documents (for ongoing use):

• Decision_Tree.pdf (update monthly)
• Risk_Matrix.xlsx (update quarterly)
• Adversity_Playbook.pdf (consult in crisis)
• Parameter_Strategy.pdf (revisit if stuck)

Reference Library:

• Key_Papers.pdf (annotated bibliography, 30-50 papers)
• Organized by: Ideation / Technical / Impact / Pivots

Total: ~20-25 pages of documentation + supporting materials

Using Your Outputs

For Different Purposes

Grant/Fellowship Applications:

• Start with Integrated Plan (Skill 8)
• Include specific aims from Ideation (Skill 1)
• Show risk mitigation from Risk Assessment (Skill 2)
• Demonstrate impact from Impact Assessment (Skill 3)
• Timeline from Decision Tree (Skill 5)

Thesis Committee Meetings:

• Present 3-slide deck (Skill 8)
• Walk through decision tree (Skill 5)
• Discuss risk mitigation (Skill 2)
• Show parameter flexibility (Skill 4)
• Demonstrate thoughtful planning

Lab Meetings:

• Use elevator pitch (Skill 8)
• Show decision tree updates (Skill 5)
• Discuss latest adversity and response (Skill 6)
• Get input on parameter strategy (Skill 4)

Collaborator Conversations:

• Share 1-page summary (Skill 8)
• Highlight where their expertise fits (Skill 4)
• Show risk mitigation plan (Skill 2)
• Discuss impact potential (Skill 3)

Personal Reflection:

• Quarterly: Review Decision Tree (Skill 5), update milestones
• After setbacks: Consult Adversity Playbook (Skill 6)
• When stuck: Use Problem Inversion (Skill 7)
• Annual: Full workflow review, consider new projects

Maintenance and Updates

Living Documents Protocol

Monthly:

• Update Decision Tree (Skill 5)
• Log adversities and responses (Skill 6)
• Note new papers or competition
• Adjust timeline if needed

Quarterly:

• Review Risk Matrix (Skill 2) - mark assumptions tested
• Reassess Impact (Skill 3) - has evaluation changed?
• Check Parameter Strategy (Skill 4) - still optimal?
• Update Integrated Plan (Skill 8) - keep current

Annually:

• Complete workflow review
• Consider new projects with fresh Skill 1 ideation
• Archive old project docs
• Extract lessons learned

Success Metrics

How Do You Know This Worked?

Immediate Indicators:

• Clearer project vision than before
• Honest assessment of risks
• Contingency plans for failures
• Compelling communication materials
• Alignment between project and values
• Confidence in problem choice

6-Month Indicators:

• Major decisions made faster (have framework)
• Adversity handled productively (used playbook)
• No existential crises (risks were mitigated)
• Regular Level 2 evaluation happening
• Project staying on-track or pivoting smartly

2-Year Indicators:

• Published results or strong progress
• Avoided dead-end projects
• Multiple high-quality options at decision points
• Skills developed as planned
• Career trajectory aligned with goals
• Time well-spent (the ultimate measure)

Key Principles of the Meta-Framework

1. Systematic > Ad Hoc: Process ensures nothing forgotten
2. Iterative > Linear: Expect to loop back, that's good
3. Documented > Mental: Writing forces clarity
4. Integrated > Fragmented: All skills connect
5. Living > Static: Update as you learn
6. Thoughtful > Fast: Time invested now saves years later
7. Honest > Optimistic: Rigor protects against wishful thinking
8. Prepared > Surprised: Anticipate adversity
9. Flexible > Rigid: Parameters float when needed
10. Passionate > Obligatory: Alignment matters

Getting Started

First Steps

This Week:

1. Block time in calendar (1-2 hours to start)
2. Gather your context (background, goals, constraints)
3. Begin Skill 1 (Intuition Pumps)
4. Let me know your starting point

This Month:

1. Work through Skills 1-4 (foundation)
2. Share with mentor for alignment check
3. Iterate if major changes needed
4. Complete Skills 5-8 (execution planning)

This Quarter:

1. Begin project execution with living documents
2. Monthly decision tree updates
3. Quarterly risk assessment reviews
4. Log adversities and responses

This Year:

1. Execute planned project
2. Use frameworks when stuck
3. Update living documents
4. Evaluate process and refine

Ready to Begin?

The complete meta-framework is substantial, but each step builds on the last. You'll move through:

• ~2 weeks of intensive planning
• Comprehensive documentation
• Clear decision criteria
• Communication materials
• Living documents for ongoing guidance

Most importantly: You'll KNOW you're working on a well-chosen problem with rigorous planning. That confidence is priceless.

Let's start with Skill 1. Are you ready to begin?

Remember: The highest-leverage work in science is choosing the right problem. This meta-framework ensures you spend your finite time wisely. The investment in systematic planning pays dividends for years.