thinking-effectuation
Start with means, not goals; co-create with partners; leverage contingencies. Use for startup strategy, innovation projects, and uncertain/novel domains where planning is unreliable.
What this skill does
# Effectuation
## Overview
Effectuation, developed by Saras Sarasvathy from studying expert entrepreneurs, inverts traditional causal reasoning. Instead of starting with a goal and finding resources, effectuators start with available means and discover goals through action. This approach is more robust in highly uncertain environments where prediction is unreliable.
**Core Principle:** When you can't predict the future, don't try. Instead, focus on what you can control and let the future emerge from your actions.
## When to Use
- Startup and new product development
- Innovation in uncertain domains
- When prediction is unreliable
- Entering new markets
- When resources are constrained
- Side projects and experiments
- Career pivots
Decision flow:
```
Facing uncertainty about outcomes?
→ Can you predict the future reliably? → no → USE EFFECTUATION
→ Do you have fixed goals but uncertain resources? → yes → Traditional planning
→ Do you have available means but uncertain goals? → yes → USE EFFECTUATION
```
## When NOT to Use
- **Use effectuation only under genuine (Knightian) uncertainty** — where outcomes can't be assigned meaningful probabilities because the market/technology/problem is novel. That's where "create the future through action" beats prediction.
- **For predictable markets with a known model, use causal planning instead.** If the market exists, the unit economics are knowable, and the path is a known sequence of steps, set the goal and plan to it — effectuation's "let goals emerge" wastes time you don't need to spend exploring.
- **Not when the cost of a wrong action exceeds affordable loss.** Effectuation assumes you can afford to act-and-learn; if a single misstep is ruinous, plan and de-risk first.
## Trigger Card
When starting a new initiative in an uncertain domain where planning is unreliable:
1. **Inventory your means** — who you are, what you know, who you know. Start from what's available, not from a distant goal.
2. **Take an affordable-loss step** — what can you act on now where the downside is survivable if it fails? Act; don't plan.
3. **Co-create with committed partners** — find stakeholders willing to make real commitments, then let the direction emerge from their input.
If the market and path are predictable, use causal planning instead. If a single misstep is ruinous, de-risk before acting.
## Causal vs Effectual Reasoning
### Causal (Traditional)
```
1. Set a goal
2. Plan to achieve the goal
3. Gather necessary resources
4. Execute the plan
5. Measure against the goal
Example:
Goal: Build a $10M company
Plan: Build product X for market Y
Resources: Raise $2M, hire 10 people
Execute: 18-month development plan
Measure: Revenue against projections
```
### Effectual (Entrepreneurial)
```
1. Start with your means
2. Take action with acceptable loss
3. Build partnerships
4. Leverage contingencies
5. Goals emerge from action
Example:
Means: I know databases, have some savings, know other engineers
Action: Build a small tool, see who's interested
Partners: Three early users want to co-create
Contingency: One user has a different problem that's bigger
Emerging goal: Pivot to new problem, user becomes co-founder
```
## The Five Principles of Effectuation
### 1. Bird in Hand (Start with Means)
Begin with what you have:
```markdown
## My Means Inventory
Who I am:
- Skills: [List skills]
- Preferences: [What I enjoy]
- Values: [What matters to me]
What I know:
- Domain expertise: [Areas of knowledge]
- Unique insights: [What I see that others don't]
- Technical skills: [What I can build]
Who I know:
- Potential partners: [People who might join]
- Potential customers: [People who might buy]
- Resources: [People who can help]
What can I do with THESE means?
(Don't start with "what's needed"—start with "what I have")
```
### 2. Affordable Loss (Acceptable Downside)
Focus on what you can afford to lose, not expected return:
```markdown
## Affordable Loss Analysis
I can afford to lose:
- Time: 6 months of evenings/weekends
- Money: $5K of savings
- Opportunity: Delay of other projects
- Reputation: Minor if it fails quietly
I cannot afford to lose:
- Day job income
- Family time beyond X hours
- More than $5K
Action: Design the experiment to fit within affordable loss
Don't calculate expected return—calculate maximum loss
Can I live with maximum loss? If yes, proceed.
```
### 3. Crazy Quilt (Partnerships)
Co-create with anyone who commits:
```markdown
## Partnership Building
Instead of: Finding resources for my predetermined plan
Do: Let partners shape the venture
Approach:
1. Share what I'm working on
2. Anyone who commits becomes a partner
3. They bring their means and constraints
4. The venture adapts to include them
Example:
- I start with: Database tool idea
- Partner 1 commits: Brings sales experience, shifts to B2B
- Partner 2 commits: Brings design, shifts to user-facing product
- Customer 1 commits: Brings specific use case, shapes roadmap
The venture becomes what committed partners make it.
```
### 4. Lemonade (Leverage Contingencies)
Treat surprises as opportunities:
```markdown
## Contingency Response
Causal mindset: "That wasn't in the plan—it's a problem"
Effectual mindset: "That's unexpected—how can we use it?"
Examples:
- Competitor launches similar product
Causal: "Our plan is threatened"
Effectual: "They validated market, potential acquirer, potential partner"
- Key hire falls through
Causal: "We're behind plan"
Effectual: "Maybe we don't need that role; what can we do with who we have?"
- Customer wants something different
Causal: "That's not our product"
Effectual: "Maybe that IS our product"
```
### 5. Pilot in the Plane (Control, Don't Predict)
Focus on what you can control:
```markdown
## Control vs Predict
Can't control/predict:
- Market movements
- Competitor actions
- Customer adoption rate
- Economic conditions
- Technology shifts
Can control:
- Who I work with
- What I build this week
- How I respond to feedback
- What partnerships I form
- How much I risk
Strategy: Maximize actions on controllable factors
Don't waste energy predicting uncontrollable factors
Create the future through action, not prediction
```
## Effectuation Process
### Step 1: Inventory Your Means
```markdown
## Means Inventory
### Who I Am
- Background: [Experience, skills, identity]
- Passions: [What energizes me]
- Values: [What I won't compromise]
### What I Know
- Professional knowledge: [Domains]
- Technical skills: [Abilities]
- Market insights: [What I understand that others might not]
### Who I Know
- Close network: [People who would take my call]
- Extended network: [People who know people]
- Communities: [Groups I'm part of]
```
### Step 2: Define Affordable Loss
```markdown
## Affordable Loss
Time I can invest: [Hours/week, months]
Money I can lose: [$X]
Reputation at stake: [What's the downside?]
Opportunity cost: [What else am I not doing?]
Maximum I'm willing to lose: [Clear boundary]
```
### Step 3: Take Action
```markdown
## Next Action
Given my means and affordable loss:
What's the smallest action that could create information?
Options:
1. [Action] - Teaches me [what]
2. [Action] - Teaches me [what]
3. [Action] - Teaches me [what]
Selected action: [Action with best learning/risk ratio]
```
### Step 4: Seek Commitments
```markdown
## Partnership Outreach
Who might be interested in co-creating?
| Person | Their Means | Ask | Commitment |
|--------|-------------|-----|------------|
| [Name] | [Skills/resources] | [What to ask] | [What they commit] |
Each commitment expands my means and shapes the direction.
```
### Step 5: Adapt and Iterate
```markdown
## Iteration Log
| Action | Outcome | Surprise | How to leverage |
|--------|---------|----------|-----------------|
| | | | |
After each action:
- What did I learn?
- What commitments emerged?
- What contingencies can I leverage?
- What's the nexRelated in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.