{"kind":"Skill","metadata":{"namespace":"community","name":"thinking-effectuation","version":"0.1.0"},"spec":{"description":"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.","files":{"SKILL.md":"---\nname: thinking-effectuation\ndescription: 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.\n---\n\n# Effectuation\n\n## Overview\n\nEffectuation, 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.\n\n**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.\n\n## When to Use\n\n- Startup and new product development\n- Innovation in uncertain domains\n- When prediction is unreliable\n- Entering new markets\n- When resources are constrained\n- Side projects and experiments\n- Career pivots\n\nDecision flow:\n\n```\nFacing uncertainty about outcomes?\n  → Can you predict the future reliably? → no → USE EFFECTUATION\n  → Do you have fixed goals but uncertain resources? → yes → Traditional planning\n  → Do you have available means but uncertain goals? → yes → USE EFFECTUATION\n```\n\n## Causal vs Effectual Reasoning\n\n### Causal (Traditional)\n\n```\n1. Set a goal\n2. Plan to achieve the goal\n3. Gather necessary resources\n4. Execute the plan\n5. Measure against the goal\n\nExample:\nGoal: Build a $10M company\nPlan: Build product X for market Y\nResources: Raise $2M, hire 10 people\nExecute: 18-month development plan\nMeasure: Revenue against projections\n```\n\n### Effectual (Entrepreneurial)\n\n```\n1. Start with your means\n2. Take action with acceptable loss\n3. Build partnerships\n4. Leverage contingencies\n5. Goals emerge from action\n\nExample:\nMeans: I know databases, have some savings, know other engineers\nAction: Build a small tool, see who's interested\nPartners: Three early users want to co-create\nContingency: One user has a different problem that's bigger\nEmerging goal: Pivot to new problem, user becomes co-founder\n```\n\n## The Five Principles of Effectuation\n\n### 1. Bird in Hand (Start with Means)\n\nBegin with what you have:\n\n```markdown\n## My Means Inventory\n\nWho I am:\n- Skills: [List skills]\n- Preferences: [What I enjoy]\n- Values: [What matters to me]\n\nWhat I know:\n- Domain expertise: [Areas of knowledge]\n- Unique insights: [What I see that others don't]\n- Technical skills: [What I can build]\n\nWho I know:\n- Potential partners: [People who might join]\n- Potential customers: [People who might buy]\n- Resources: [People who can help]\n\nWhat can I do with THESE means?\n(Don't start with \"what's needed\"—start with \"what I have\")\n```\n\n### 2. Affordable Loss (Acceptable Downside)\n\nFocus on what you can afford to lose, not expected return:\n\n```markdown\n## Affordable Loss Analysis\n\nI can afford to lose:\n- Time: 6 months of evenings/weekends\n- Money: $5K of savings\n- Opportunity: Delay of other projects\n- Reputation: Minor if it fails quietly\n\nI cannot afford to lose:\n- Day job income\n- Family time beyond X hours\n- More than $5K\n\nAction: Design the experiment to fit within affordable loss\n        Don't calculate expected return—calculate maximum loss\n        Can I live with maximum loss? If yes, proceed.\n```\n\n### 3. Crazy Quilt (Partnerships)\n\nCo-create with anyone who commits:\n\n```markdown\n## Partnership Building\n\nInstead of: Finding resources for my predetermined plan\nDo: Let partners shape the venture\n\nApproach:\n1. Share what I'm working on\n2. Anyone who commits becomes a partner\n3. They bring their means and constraints\n4. The venture adapts to include them\n\nExample:\n- I start with: Database tool idea\n- Partner 1 commits: Brings sales experience, shifts to B2B\n- Partner 2 commits: Brings design, shifts to user-facing product\n- Customer 1 commits: Brings specific use case, shapes roadmap\n\nThe venture becomes what committed partners make it.\n```\n\n### 4. Lemonade (Leverage Contingencies)\n\nTreat surprises as opportunities:\n\n```markdown\n## Contingency Response\n\nCausal mindset: \"That wasn't in the plan—it's a problem\"\nEffectual mindset: \"That's unexpected—how can we use it?\"\n\nExamples:\n- Competitor launches similar product\n  Causal: \"Our plan is threatened\"\n  Effectual: \"They validated market, potential acquirer, potential partner\"\n\n- Key hire falls through\n  Causal: \"We're behind plan\"\n  Effectual: \"Maybe we don't need that role; what can we do with who we have?\"\n\n- Customer wants something different\n  Causal: \"That's not our product\"\n  Effectual: \"Maybe that IS our product\"\n```\n\n### 5. Pilot in the Plane (Control, Don't Predict)\n\nFocus on what you can control:\n\n```markdown\n## Control vs Predict\n\nCan't control/predict:\n- Market movements\n- Competitor actions\n- Customer adoption rate\n- Economic conditions\n- Technology shifts\n\nCan control:\n- Who I work with\n- What I build this week\n- How I respond to feedback\n- What partnerships I form\n- How much I risk\n\nStrategy: Maximize actions on controllable factors\n          Don't waste energy predicting uncontrollable factors\n          Create the future through action, not prediction\n```\n\n## Effectuation Process\n\n### Step 1: Inventory Your Means\n\n```markdown\n## Means Inventory\n\n### Who I Am\n- Background: [Experience, skills, identity]\n- Passions: [What energizes me]\n- Values: [What I won't compromise]\n\n### What I Know\n- Professional knowledge: [Domains]\n- Technical skills: [Abilities]\n- Market insights: [What I understand that others might not]\n\n### Who I Know\n- Close network: [People who would take my call]\n- Extended network: [People who know people]\n- Communities: [Groups I'm part of]\n```\n\n### Step 2: Define Affordable Loss\n\n```markdown\n## Affordable Loss\n\nTime I can invest: [Hours/week, months]\nMoney I can lose: [$X]\nReputation at stake: [What's the downside?]\nOpportunity cost: [What else am I not doing?]\n\nMaximum I'm willing to lose: [Clear boundary]\n```\n\n### Step 3: Take Action\n\n```markdown\n## Next Action\n\nGiven my means and affordable loss:\nWhat's the smallest action that could create information?\n\nOptions:\n1. [Action] - Teaches me [what]\n2. [Action] - Teaches me [what]\n3. [Action] - Teaches me [what]\n\nSelected action: [Action with best learning/risk ratio]\n```\n\n### Step 4: Seek Commitments\n\n```markdown\n## Partnership Outreach\n\nWho might be interested in co-creating?\n\n| Person | Their Means | Ask | Commitment |\n|--------|-------------|-----|------------|\n| [Name] | [Skills/resources] | [What to ask] | [What they commit] |\n\nEach commitment expands my means and shapes the direction.\n```\n\n### Step 5: Adapt and Iterate\n\n```markdown\n## Iteration Log\n\n| Action | Outcome | Surprise | How to leverage |\n|--------|---------|----------|-----------------|\n| | | | |\n\nAfter each action:\n- What did I learn?\n- What commitments emerged?\n- What contingencies can I leverage?\n- What's the next action?\n```\n\n## Effectuation Template\n\n```markdown\n# Effectuation Analysis: [Venture/Project]\n\n## Means Inventory\nWho I am: [Identity, skills, values]\nWhat I know: [Knowledge, expertise]\nWho I know: [Network, relationships]\n\n## Affordable Loss\nCan afford: [Time, money, reputation]\nCannot afford: [Boundaries]\nMaximum loss I'm willing to accept: [Clear number]\n\n## Current Commitments\n| Partner | Their Means | Commitment |\n|---------|-------------|------------|\n| | | |\n\n## Contingencies Available\n| Surprise | Potential Leverage |\n|----------|-------------------|\n| | |\n\n## Next Action\nAction: [Specific, small action]\nAffordable loss: [What's at stake]\nLearning goal: [What I'll know after]\n\n## Emerging Direction\nWhere seems to be going: [Current trajectory]\nHow it differs from start: [Evolution]\n```\n\n## When to Use Causal vs Effectual\n\n| Context | Approach | Why |\n|---------|----------|-----|\n| Existing market, proven model | Causal | Prediction is reliable |\n| New market, unproven model | Effectual | Prediction is unreliable |\n| Abundant resources | Causal | Can afford to plan extensively |\n| Constrained resources | Effectual | Must work with what you have |\n| Clear goal | Causal | Plan toward the goal |\n| Exploring opportunities | Effectual | Goals emerge from action |\n| Risk can be calculated | Causal | Expected return is meaningful |\n| Risk is uncertain | Effectual | Affordable loss is meaningful |\n\n## Verification Checklist\n\n- [ ] Inventoried available means\n- [ ] Defined affordable loss (not expected return)\n- [ ] Sought commitments, not just resources\n- [ ] Treating surprises as opportunities\n- [ ] Focusing on what I can control\n- [ ] Taking action to learn, not to execute plan\n- [ ] Letting goals emerge from action\n\n## Key Questions\n\n- \"What can I do with what I have?\"\n- \"What am I willing to lose?\"\n- \"Who might want to co-create this?\"\n- \"How can I leverage this surprise?\"\n- \"What can I control right now?\"\n- \"What's the smallest action that teaches me something?\"\n\n## Sarasvathy's Wisdom\n\n\"Effectual reasoning does not begin with a specific goal. Instead, it begins with a given set of means and allows goals to emerge contingently over time from the varied imaginations and diverse aspirations of the founders and the people they interact with.\"\n\n\"In the face of an uncertain future, entrepreneurs use effectual logic to fabricate—make—the future, rather than try to find or predict it.\"\n\nYou can't predict the future. But you can create it through action. Start with your means, take affordable risks, build with partners, leverage surprises, and control what you can. The goal will find you.\n"},"import":{"commit_sha":"a31e22d4445ad8fef7cd771d32af537aebb68c49","imported_at":"2026-05-22T21:14:39Z","license_text":"MIT License\n\nCopyright (c) 2025 TJ Boudreaux\n\nPermission is hereby granted, free of charge, to any person obtaining a copy\nof this software and associated documentation files (the \"Software\"), to deal\nin the Software without restriction, including without limitation the rights\nto use, copy, modify, merge, publish, distribute, sublicense, and/or sell\ncopies of the Software, and to permit persons to whom the Software is\nfurnished to do so, subject to the following conditions:\n\nThe above copyright notice and this permission notice shall be included in all\ncopies or substantial portions of the Software.\n\nTHE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\nIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,\nFITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE\nAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER\nLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,\nOUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE\nSOFTWARE.\n","owner":"tjboudreaux","repo":"tjboudreaux/cc-thinking-skills","source_url":"https://github.com/tjboudreaux/cc-thinking-skills/tree/a31e22d4445ad8fef7cd771d32af537aebb68c49/skills/thinking-effectuation"}},"content_hash":[215,41,67,7,145,104,50,96,72,27,153,135,47,35,173,35,108,131,47,162,160,86,74,120,214,80,174,157,15,22,20,255],"trust_level":"unsigned","yanked":false}