Skill Tracer
Skills › Knowledge Work Plugins › scientific-problem-selection › 02-risk-assessment.md

02-risk-assessment.md

323 lines · bio-research/skills/scientific-problem-selection/references/02-risk-assessment.md at 2574e29

Open on GitHub

Most marks come from matching words in the file, so treat them as pointers.

1# SKILL 2: Risk Assessment and Assumption Analysis
2

SKILL 2: Risk Assessment and Assumption Analysis

Raw lines 1 to 2
3## Overview
4This 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.
5

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.

Raw lines 3 to 5
6## Core Principle
7
8**"Don't avoid risk; befriend it."**
9
10The most important concept in problem choice is the two-axis evaluation:
11- **X-axis:** Likelihood of success
12- **Y-axis:** Impact if successful
14This skill focuses on the X-axis, helping users move their project rightward through systematic risk analysis.

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.

Raw lines 6 to 15
16## Why This Matters
18A 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.

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.

Raw lines 16 to 19
20## The Skill Workflow

The Skill Workflow

Raw lines 20 to 21
22### Phase 1: Extract Project Assumptions (10-15 minutes)
24First, Claude should gather information about the user's project from Skill 1:
261. **Project Summary** (from Skill 1):
27 - The biological question
28 - The technical approach
29 - What's novel about it
312. **Project Horizon:**
32 - How long is this project expected to take? (months/years)
33 - What is the user's role? (graduate student, postdoc, PI, startup founder)
353. **Initial Risk Sense:**
36 - What keeps the user up at night about this project?
37 - What's the scariest assumption?

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):
  2. The biological question
  3. The technical approach
  4. What's novel about it
  1. Project Horizon:
  2. How long is this project expected to take? (months/years)
  3. What is the user's role? (graduate student, postdoc, PI, startup founder)
  1. Initial Risk Sense:
  2. What keeps the user up at night about this project?
  3. What's the scariest assumption?
Raw lines 22 to 38
39### Phase 2: Comprehensive Assumption Listing
41Claude should work with the user to list EVERY assumption the project makes from inception through conclusion. Assumptions fall into two categories:
43#### Type A: Assumptions About Biological Reality
44These are facts about the world that either are or aren't true. They won't change during the project.
46**Examples:**
47- New cell types exist beyond what's currently known
48- A particular gene regulates the process being studied
49- Two proteins physically interact
50- A pathway functions in the organism of interest
51- The biological effect size is detectable
53#### Type B: Assumptions About Technical Capability
54These are about whether technology can do what's needed. These CAN change during the project as methods improve.
56**Examples:**
57- A specific cell type can be isolated
58- Sequencing will generate high-quality data
59- An assay has sufficient throughput
60- Computational analysis can distinguish signal from noise
61- Gene editing will work in the system
63**Claude should ask:**
641. What must be true about the biology for this to work?
652. What must the technology be able to do?
663. What about the experimental design—what assumptions are built in?
674. What about the analysis—can it deliver what's needed?
685. If everything works, can the findings be validated?
696. Will the findings be interpretable and meaningful?

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?
Raw lines 39 to 70
71### Phase 3: Risk Scoring (The Assumption Analysis Table)
73For each assumption, Claude should help the user assign two scores:
75#### Risk Level (1-5 scale):
76- **1** = Very likely to be true/work (>90% confidence)
77- **2** = Likely (70-90% confidence)
78- **3** = Uncertain (40-70% confidence)
79- **4** = Unlikely (10-40% confidence)
80- **5** = Very unlikely (<10% confidence)
82#### Time to Test (months):
83How long before the user will know if this assumption is valid?
85**Critical Rules:**
861. Be brutally honest—try to convince oneself of being WRONG, not right
872. Distinguish between biological vs. technical assumptions
883. Consider whether technical assumptions might improve over time
894. Note which assumptions depend on earlier assumptions succeeding

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
Raw lines 71 to 90
91### Phase 4: Risk Profile Evaluation
93Once the complete table is ready, Claude should analyze the risk profile:
95#### Red Flags to Identify:
961. **The Late High-Risk Problem:** Risk level 4-5 assumption that won't read out until >18 months
972. **The Multiple Miracles:** More than 2-3 assumptions with risk level 4-5
983. **The Dependency Chain:** High-risk assumptions stacked in sequence
994. **The Ostrich Pattern:** Starting with low-risk work while avoiding the high-risk tests
101#### Green Lights:
1021. **Early Go/No-Go:** Highest-risk assumption testable in <6 months
1032. **Multiple Candidates:** Project can succeed with several different outcomes
1043. **Graceful Degradation:** If assumption X fails, assumption Y provides alternative path
1054. **Risk Distribution:** High-risk assumptions balanced across timeline
107**Rule of Thumb:** If you have a risk level 5 assumption three years out, pick another project.

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.

Raw lines 91 to 108
109### Phase 5: Risk Mitigation Strategies
111For each high-risk assumption (level 4-5), Claude should help develop mitigation strategies:
113#### Strategy 1: Move High-Risk Tests Earlier
114**Question:** Can a quicker, cruder test be designed that answers most of what's needed?
116**Example:** Instead of waiting 2 years to validate a new cell type exists, consider:
117- Using existing markers as a proxy
118- Testing in a simpler model system first
119- Using computational predictions to increase confidence
121#### Strategy 2: Multiple Candidates Approach
122**Question:** Can multiple candidates be tested in parallel to increase likelihood of success?
124**Example:** Instead of:
125- Testing one kinase → Test a panel of 10 kinases
126- Building one engineered organism → Build and test a library
127- Pursuing one therapeutic target → Pursue 3 related targets
129#### Strategy 3: Reframe the Question
130**Question:** Can the project scope be adjusted to reduce critical assumptions while maintaining impact?
132**Example from lecture:**
133- **Original:** Identify NEW enteroendocrine cell types (high risk: they may not exist)
134- **Reframed:** Better characterize KNOWN but incompletely understood cell types (lower risk)
136#### Strategy 4: Change the System
137**Question:** Is there a different biological system with similar scientific value but lower technical risk?
139**Example from lecture:**
140- **Original:** Intestinal epithelium (hard to manipulate genetically)
141- **Alternative:** Liver (easier genetic manipulation options exist)
143#### Strategy 5: Add Complementary Approaches
144**Question:** Can a parallel approach be added that de-risks the main assumption?
146**Example from lecture:**
147- Add spatial transcriptomics to scRNA-seq
148- This provides biogeographic context and validates cell type existence earlier

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
Raw lines 109 to 149
150### Phase 6: Go/No-Go Experiment Design
152For the top 3 highest-risk assumptions, Claude should help design the critical go/no-go experiments:
154**For each, specify:**
1551. **The Question:** Exactly what is being tested?
1562. **The Experiment:** Most direct test possible (even if crude)
1573. **Success Criteria:** What result means "go"?
1584. **Failure Response:** What result means "pivot" or "stop"?
1595. **Timeline:** How soon can this be run?
1606. **Resources:** What is needed?
162**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 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.

Raw lines 150 to 163
164### Phase 7: Literature Validation
166Claude should search PubMed to help calibrate risk assessments:
168**Search for:**
1691. **Precedents:** Has anyone done something similar? (Reduces technical risk)
1702. **Biological Evidence:** What's known about the system? (Informs biological risk)
1713. **Technical Benchmarks:** How well do the methods work in practice?
1724. **Adjacent Successes:** Has anyone solved related problems?
174**Questions to ask the user:**
175- What specific searches would help calibrate risk?
176- Are there particular papers that informed the assumptions?
177- Are there technical benchmarks to look up?

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?
Raw lines 164 to 178
Involves a person ask the user :174
179### Phase 8: Revised Project Plan
181Based on the risk analysis, Claude should help create a revised plan:
183#### Option A: De-Risk the Current Plan
184- Reorder experiments to test high-risk assumptions early
185- Add complementary approaches
186- Design multiple-candidate strategies
188#### Option B: Reframe the Project
189- Adjust scope while maintaining impact
190- Change biological system
191- Modify technical approach
193#### Option C: Pick a Different Project
194Sometimes the honest answer is: "This has too many miracles." That's valuable to know BEFORE investing years.

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.

Raw lines 179 to 195
196## Output Deliverable
198Claude should produce a **2-page Risk Assessment Document**:

Output Deliverable

Claude should produce a 2-page Risk Assessment Document:

Raw lines 196 to 199
200### Page 1: Assumption Analysis Table
202| Assumption | Type* | Risk† | Time‡ | Notes |
203|------------|-------|-------|-------|-------|
204| [Assumption 1] | Bio/Tech | 1-5 | X mo | [Rationale for score] |
205| [Assumption 2] | Bio/Tech | 1-5 | X mo | [Rationale for score] |
206| ... | ... | ... | ... | ... |
208*Bio = Biological reality, Tech = Technical capability
209†Risk: 1=very likely to 5=very unlikely
210‡Time to test in months
212#### Risk Profile Summary:
213- **Total Assumptions:** X
214- **High Risk (4-5):** X assumptions
215- **Late High Risk (>18mo):** X assumptions
216- **Critical Path:** [Identify the chain of dependent assumptions]
217- **Overall Assessment:** [Green/Yellow/Red light with explanation]

Page 1: Assumption Analysis Table

AssumptionType*Risk†Time‡Notes
[Assumption 1]Bio/Tech1-5X mo[Rationale for score]
[Assumption 2]Bio/Tech1-5X mo[Rationale for score]
...............

*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]
Raw lines 200 to 218
219### Page 2: Risk Mitigation Plan
221#### Top 3 High-Risk Assumptions:
222For each:
2231. **The Assumption:** [Stated clearly]
2242. **Current Risk Level & Timeline:** X (risk) at Y months
2253. **Why This Risk Exists:** [Explanation]
2264. **Mitigation Strategy:** [From Strategies 1-5 above]
2275. **Go/No-Go Experiment:**
228 - Experiment design
229 - Success criteria
230 - Timeline
231 - What you'll do if it fails
233#### Revised Project Timeline:
234```
235Month 0-6: [Early go/no-go experiments]
236Month 6-12: [Based on go/no-go results]
237Month 12-18: [...]
238Month 18+: [...]
239```
241#### Contingency Plans:
242- **If assumption X fails:** [Plan B]
243- **If assumption Y fails:** [Plan C]
244- **Multiple success paths:** [How project can succeed different ways]
246#### Decision Points:
247- **Month X:** Evaluate [assumptions A, B] → Go/Pivot/Stop decision
248- **Month Y:** Evaluate [assumptions C, D] → Go/Pivot/Stop decision

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:
  6. Experiment design
  7. Success criteria
  8. Timeline
  9. 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
Raw lines 219 to 249
250## Practical Examples

Practical Examples

Raw lines 250 to 251
252### Example 1: ScRNA-Seq for Enteroendocrine Cells
254**High-Risk Assumptions Identified:**
2551. "New cell types can be validated experimentally" (Risk 5, 24 months)
2562. "Knockout will yield biologically relevant phenotype" (Risk 5, 30 months)
258**Problem:** Two risk-5 assumptions at 24+ months = RED FLAG
260**Mitigation Applied:**
261- Reframe to study known but poorly characterized cells (reduces Risk 5→3)
262- Switch to liver instead of intestine (improves validation timeline: 30→18 months)
263- Add spatial transcriptomics (provides earlier validation checkpoint at 16 months)

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)
Raw lines 252 to 264
265### Example 2: Bacterial Therapy for Chronic Kidney Disease
267**High-Risk Assumption Identified:**
268"Key uremic toxins leading to effects can be determined" (Risk 4, unknown timeline)
270**Problem:** Critical assumption with unclear path to resolution
272**Mitigation Applied:**
273- Focus on known lead toxins (IS and PCS) rather than discovering new ones
274- Add parallel track: test multiple toxin candidates
275- Design study where learning toxin identity IS the outcome (multiple success paths)

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)
Raw lines 265 to 276
277## Key Principles to Remember
2791. **Try to Convince Yourself You're Wrong:** The goal is critical evaluation, not confirmation bias.
2812. **Ignore Everything But Key Risk Points:** Don't get distracted by easy tasks. The high-risk assumptions aren't going away.
2833. **Early and Often:** Design go/no-go experiments at the earliest feasible moment.
2854. **Be Candid About Risk:** When presenting ideas, acknowledging risk makes your case MORE convincing, not less.
2875. **No Risk, No Interest:** The goal isn't zero risk—it's understood, quantified, manageable risk.
2896. **Risk Can Change:** Technical assumptions may improve as methods advance. Build this into your planning.
2917. **Compare Risk Profiles:** Evaluate multiple projects in parallel to compare risk profiles and make better choices.
2938. **Watch for the Ostrich Pattern:** Are you avoiding the scary experiment? That's human nature, but a critical failure mode.

Key Principles to Remember

  1. Try to Convince Yourself You're Wrong: The goal is critical evaluation, not confirmation bias.
  1. Ignore Everything But Key Risk Points: Don't get distracted by easy tasks. The high-risk assumptions aren't going away.
  1. Early and Often: Design go/no-go experiments at the earliest feasible moment.
  1. Be Candid About Risk: When presenting ideas, acknowledging risk makes your case MORE convincing, not less.
  1. No Risk, No Interest: The goal isn't zero risk—it's understood, quantified, manageable risk.
  1. Risk Can Change: Technical assumptions may improve as methods advance. Build this into your planning.
  1. Compare Risk Profiles: Evaluate multiple projects in parallel to compare risk profiles and make better choices.
  1. Watch for the Ostrich Pattern: Are you avoiding the scary experiment? That's human nature, but a critical failure mode.
Raw lines 277 to 294
295## Warning Signs
297**Warning signs include:**
298- Risk level 5 assumptions >2 years out
299- More than 3 assumptions at risk level 4-5
300- Highest-risk assumptions at the END of the timeline
301- Rationalizing why high-risk assumptions will "probably work out"
302- Planning to "start with the easy stuff" while avoiding risk tests
303- Inability to articulate clear go/no-go criteria
305**Good shape indicators:**
306- Highest-risk tests happen in first 6 months
307- Multiple paths to success exist
308- Clear plans for what to do if key assumptions fail
309- Risk is distributed across the timeline
310- Testing assumptions, not confirming hopes

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
Raw lines 295 to 311
312## Getting Started
314Claude should begin with Phase 1 by asking for:
3151. The project summary from Skill 1
3162. Project timeline expectations
3173. What concerns the user most about this project
319Together, 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.
321---
323*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.*

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.

Raw lines 312 to 323