effectuation
Skill1 starsChanged 8 months agoMITView on GitHub
Sarasvathy's effectuation framework for pre-PMF exploration, post-pivot situations, and Knightian uncertainty. Use when goals are unclear, markets are illegible, or historical data is absent. Replaces standard causation planning.
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 13
No historical data to estimate probabilities (Knightian uncertainty)
- Distinctive: line 14
Every direction looks equally plausible
- Distinctive: line 27
All 3 YES: Causation mode (Strategy Kernel, KPI Tree, Critical Chain)
- Distinctive: line 45
Every experiment is checked against ALL four dimensions:
- Distinctive: line 85
All 3 conditions flip to NO
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Effectuation (Exploration Mode)
When to Apply
- Pre-PMF stage with unclear product direction
- Post-pivot with new market entry
- Goals are ambiguous or evolving
- No historical data to estimate probabilities (Knightian uncertainty)
- Every direction looks equally plausible
Core Framework
Three-Condition Test (Auto-Evaluate)
| Condition | Causation (YES) | Effectuation (NO) |
| Goal clarity | Founder can state clear, measurable goal | Goal is ambiguous or evolving |
| Environmental legibility | Clear which market signals matter | Every direction looks equally plausible |
| Historical data | Data exists to estimate probabilities | No precedent, Knightian uncertainty |
Mode selection:
- All 3 YES: Causation mode (Strategy Kernel, KPI Tree, Critical Chain)
- Any 1+ NO: Effectuation mode (this framework)
- Mixed: Hybrid mode (Causation structure with Effectuation flexibility)
Effectuation Cycle
In effectuation mode, DISABLE: KPI tree decomposition, buffer management, Critical Chain. Run this repeating expansion cycle instead:
1. Bird-in-Hand Audit "What resources do you have RIGHT NOW?"
- Skills (founder + team)
- Network (who do you know?)
- Capital (how much can you invest?)
- Technology (what have you already built?)
- Domain knowledge (what do you uniquely understand?)
2. Affordable Loss Ceiling (4 Dimensions)
Every experiment is checked against ALL four dimensions:
| Dimension | Question | Threshold |
| Financial | "How much capital can you invest and survive if it goes to zero?" | Set dollar amount |
| Time | "How many months can you devote before you need income?" | Set month limit |
| Reputation | "Would failure here damage your ability to raise funds or get hired?" | low/medium/high |
| Psychological | "Can you handle this failing and try again?" | yes/no |
Track CUMULATIVE commitments across all active experiments. Individual experiments may each be small, but together they can exceed limits.
3. Execute Small Experiment -> Measure
Design the cheapest experiment to learn something. Not the best experiment — the cheapest one that still generates a useful signal.
4. Lemonade Principle "What surprised you this week? Can it be used?"
Unexpected outcomes are not failures — they are data. A surprising customer segment, an unexpected use case, an unplanned partnership opportunity. Capture and evaluate.
5. Crazy Quilt "Who showed interest? Who self-selected in?"
Early stakeholders who voluntarily engage (customers, partners, advisors) define the venture's direction. Don't chase — follow the self-selected.
6. Resources expand -> New Bird-in-Hand -> Repeat
Goal may mutate each cycle. This is NOT scope creep — it is effectuation working correctly.
Mode Switching Triggers
Effectuation -> Causation:
- PMF confirmed (retention curve flattening)
- Founder can state clear measurable goal
- Sufficient data exists to estimate probabilities
- Announce: "Your situation has changed. Switching from exploration mode to scaling mode."
Causation -> Effectuation:
- Major pivot
- New market entry
- All 3 conditions flip to NO
- Announce: "The conditions for structured planning are no longer met. Switching to exploration mode."
Decision Rules
- Never apply KPI trees in effectuation mode — goals are undefined, so decomposition is premature
- Affordable loss, not expected return — ask "what can I afford to lose?" not "what's the ROI?"
- Goal mutation is expected — don't resist it, track it
- Follow self-selectors — Crazy Quilt participants define direction
- Surprises are the product — Lemonade principle is the core engine of discovery
- Cumulative exposure tracking — individual experiments are small, totals can be large
Anti-Patterns to Detect
| Anti-Pattern | Signal | Response |
| Premature causation | Building KPI trees with no data | "You don't have enough data to decompose this goal. Let's run experiments first." |
| Ignoring surprises | Sticking to original plan despite new signals | "The lemonade principle says unexpected results are your best data. What surprised you?" |
| Over-investing in exploration | Experiments getting expensive | "Check affordable loss: cumulative exposure is [X]% of your financial ceiling." |
| Analysis paralysis in uncertainty | Trying to predict the unpredictable | "In effectuation mode, the cheapest experiment beats the best analysis." |
| Resisting goal mutation | Treating changed goals as failure | "Goal evolution is how effectuation works. Track the mutation — is it converging?" |
In this repository24 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- anticipatory-sellingSkill
- choice-architectureSkill
- confidenceSkill
- content-rulesSkill
- critical-chainSkill
- culture-mapSkill
- disruptionSkill
- failure-essenceSkill
- growth-metricsSkill
- kpi-treeSkill
- network-effectsSkill
- pipelineSkill
- plan-bSkill
- pre-mortemSkill
- qualificationSkill
- quest-interviewSkill
- retention-cohortsSkill
- review-engineSkill
- root-causeSkill
- strategy-kernelSkill
- stupid-gamesSkill
- unit-economicsSkill
- value-stickSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

