
second-order-thinking
Think beyond immediate consequences to understand the chain reactions of decisions. Master Howard Marks' investment framework for seeing what others miss. Use when: Strategic decisions where long-term consequences matter; Policy/rule changes that will trigger behavioral responses; Competitive moves to anticipate market reactions; Product decisions where user behavior may shift; Investment analysis to see past obvious conclusions
- Installs
- 249
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/guia-matthieu/clawfu-skills --skill second-order-thinking- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads second-order-thinking automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Second-Order Thinking
Think beyond immediate consequences to understand the chain reactions of decisions. Master Howard Marks' investment framework for seeing what others miss.
When to Use This Skill
- Strategic decisions where long-term consequences matter
- Policy/rule changes that will trigger behavioral responses
- Competitive moves to anticipate market reactions
- Product decisions where user behavior may shift
- Investment analysis to see past obvious conclusions
- Avoiding unintended consequences in any decision
Methodology Foundation
| Aspect | Details |
|---|---|
| Source | Howard Marks - "The Most Important Thing" (2011), Charlie Munger |
| Core Principle | "First-level thinking says, 'This is a good company, let's buy.' Second-level thinking says, 'This is a good company, but everyone thinks it's great so it's overpriced. Sell.'" |
| Why This Matters | Most people only consider immediate effects. Second-order thinkers anticipate the cascading consequences—and see opportunities and risks others miss. |
What Claude Does vs What You Decide
| Claude Does | You Decide |
|---|---|
| Structures content frameworks | Final messaging |
| Suggests persuasion techniques | Brand voice |
| Creates draft variations | Version selection |
| Identifies optimization opportunities | Publication timing |
| Analyzes competitor approaches | Strategic direction |
What This Skill Does
- Maps consequence chains - Identifies 2nd, 3rd, nth order effects
- Reveals hidden risks - Finds dangers not obvious from first look
- Surfaces opportunities - Discovers advantages in counterintuitive moves
- Anticipates competitor responses - Predicts how others will react
- Avoids common traps - Stops decisions that seem good but backfire
- Improves long-term outcomes - Optimizes for total consequence, not just immediate
How to Use
Analyze a Decision with Second-Order Thinking
Apply second-order thinking to this decision: [decision]
What are the first, second, and third-order consequences?
What might we be missing?
Anticipate Competitive Response
If we [action], what will competitors/market do in response?
Map the chain reaction and help me see if this is still smart.
Evaluate a Policy Change
We're considering [policy/rule change].
Apply second-order thinking to identify unintended consequences.
Instructions
Step 1: Understand the Levels
## First vs. Second-Order Thinking
### First-Order Thinking (What Most People Do)
- Considers only immediate, obvious effects
- Answers: "What happens next?"
- Linear and direct
- Often leads to crowded positions
**Example:** "Raising prices will increase revenue."
### Second-Order Thinking (What Few Do)
- Considers consequences of consequences
- Answers: "And then what?"
- Nonlinear and systemic
- Often reveals counterintuitive truths
**Example:** "Raising prices will increase revenue... but then
some customers will churn, competitors will undercut, and
remaining customers will seek alternatives. Net effect unclear."
### The Marks Formula
"For every action, ask: And then what?
And then what after that?
And then what after that?"
Continue until you've mapped the plausible chain.
Step 2: Map Consequence Chains
## Consequence Chain Framework
### Step-by-Step Process
**1. State the Decision/Action**
"We decide to [X]."
**2. First-Order Effects (Immediate)**
"Directly and immediately, this causes [A, B, C]."
**3. Second-Order Effects (Responses)**
"In response to [A, B, C], people/markets will [D, E, F]."
**4. Third-Order Effects (Adaptations)**
"As [D, E, F] play out, we'll see [G, H, I]."
**5. Net Assessment**
"Considering all levels, is this decision still optimal?"
### Template
Second-Order Analysis: [Decision]
The Decision
[What we're considering]
First-Order Effects (Immediate)
| Effect | Who/What Affected | Probability |
|---|---|---|
| High/Med/Low | ||
| High/Med/Low |
Second-Order Effects (Responses)
| First Effect | Likely Response | Probability |
|---|---|---|
| High/Med/Low | ||
| High/Med/Low |
Third-Order Effects (Cascades)
| Second Effect | Further Consequence | Probability |
|---|---|---|
| High/Med/Low | ||
| High/Med/Low |
Key Players & Their Responses
| Player | First-Order | They Will... | Because... |
|---|---|---|---|
| Customers | |||
| Competitors | |||
| Employees | |||
| Regulators | |||
| Market |
Net Assessment
- Positive cascade: [list]
- Negative cascade: [list]
- Verdict: [Proceed / Reconsider / Modify]
Step 3: Apply Key Mental Models
## Second-Order Thinking Patterns
### 1. The Adaptation Response
**Pattern:** When you change something, people adapt.
Example: Company offers unlimited PTO.
- First-order: Employees take more vacation, happier
- Second-order: Employees feel guilty, take LESS vacation
- Third-order: Burnout increases, opposite of intended effect
**Lesson:** Anticipate how people will adapt to incentives.
### 2. The Competitive Response
**Pattern:** Your move triggers counter-moves.
Example: You cut prices 20%.
- First-order: More customers, higher volume
- Second-order: Competitors match price, your advantage disappears
- Third-order: Price war erodes margins industry-wide
- Fourth-order: Weaker players exit, consolidation
**Lesson:** Think about the game, not just your turn.
### 3. The Capacity Constraint
**Pattern:** Good things attract crowding.
Example: You discover underserved market.
- First-order: High margins, rapid growth
- Second-order: Competitors notice, enter market
- Third-order: Market becomes competitive, margins compress
- Fourth-order: Shakeout, only strong players survive
**Lesson:** Sustainable advantage requires defensibility.
### 4. The Unintended Consequence
**Pattern:** Rules/policies create new behaviors.
Example: School pays teachers based on test scores.
- First-order: Teachers focus on test prep, scores rise
- Second-order: Teaching narrows to tested material only
- Third-order: Student learning actually decreases in unmeasured areas
- Fourth-order: Best teachers leave, game-players stay
**Lesson:** Incentives shape behavior in unexpected ways.
### 5. The Reversion Tendency
**Pattern:** Extremes don't persist.
Example: Stock price triples on hype.
- First-order: Holders feel rich, buy more
- Second-order: Valuation attracts skeptics, shorts
- Third-order: Narrative shifts, selling pressure
- Fourth-order: Price reverts toward fair value
**Lesson:** Ask what happens when things normalize.
Step 4: Common Second-Order Traps
## Traps to Avoid
### Trap 1: "It Worked Before"
**First-order:** Strategy X worked for Company Y.
**Second-order:** But now everyone knows about X. It's priced in. The conditions that made it work have changed. Copycats dilute the advantage.
### Trap 2: "More is Better"
**First-order:** Adding feature Y will attract more users.
**Second-order:** But Y adds complexity, slowing onboarding. It confuses positioning. Support costs rise. Power users love it, new users bounce.
### Trap 3: "Cut Costs"
**First-order:** Reducing spending improves margins.
**Second-order:** But cutting R&D slows product. Cutting sales delays growth. Cutting quality increases churn. Best employees leave for competitors.
### Trap 4: "Lower Prices"
**First-order:** Lower prices attract more customers.
**Second-order:** But it signals low quality. Attracts price-sensitive customers who churn. Competitors match, nullifying advantage. Margins squeeze, can't invest in product.
### Trap 5: "Growth at All Costs"
**First-order:** Aggressive growth captures market.
**Second-order:** But unsustainable spending creates fragility. Unit economics don't work. When funding dries up, company collapses.
### The Antidote
For every "obvious" good idea, force yourself to ask:
"What could go wrong?"
"How might this backfire?"
"What will others do in response?"
Step 5: Decision Framework
## Second-Order Decision Framework
### Pre-Decision Checklist
□ Have I mapped at least 2 levels of consequences?
□ Have I considered how each key player will respond?
□ Have I identified potential unintended effects?
□ Have I considered reversion to mean/normalization?
□ Have I thought about what happens when competitors react?
□ Have I considered what happens if this "works" (success brings its own problems)?
### Decision Matrix
| Factor | First-Order | Second-Order | Net |
|--------|-------------|--------------|-----|
| Revenue | +/- | +/- | ? |
| Costs | +/- | +/- | ? |
| Competitive position | +/- | +/- | ? |
| Team/culture | +/- | +/- | ? |
| Optionality | +/- | +/- | ? |
### Final Assessment Questions
1. "If everyone did this, would it still work?"
2. "What do I believe that the market doesn't?"
3. "What would have to be true for this to backfire?"
4. "Am I thinking about this decision the same way everyone else is?"
### Marks' Test
"First-level thinking says: 'This looks good. Let's do it.'
Second-level thinking says: 'This looks good, but so does everyone think that?
What am I seeing that others don't? What are they seeing that I'm missing?'"
Examples
Example 1: Startup Strategy
Input:
"We're considering launching a freemium tier to grow faster. Apply second-order thinking."
Output:
Second-Order Analysis: Freemium Tier
The Decision
Launch a free tier of our SaaS product to accelerate user acquisition.
First-Order Effects (Immediate)
| Effect | Impact | Probability |
|---|---|---|
| More signups | Significantly increased | High |
| Marketing costs decrease | Reduced CAC | High |
| Server costs increase | More users, more infra | High |
| Team focuses on conversion funnel | Shift from direct sales | Medium |
First-order conclusion: This looks great! More users, lower CAC.
Second-Order Effects (Responses)
| First Effect | Likely Response | Probability |
|---|---|---|
| More signups | Free users demand support | High |
| More signups | Free users request features | High |
| Lower CAC | Competitors copy freemium | Medium |
| Team shift | Sales team resists/leaves | Medium |
| More users | Product positioned as "cheap" | Medium |
Third-Order Effects (Cascades)
| Second Effect | Further Consequence | Probability |
|---|---|---|
| Free users demand support | Support overwhelmed, paid users suffer | Medium |
| Free users request features | Product roadmap shifts to free user needs | Medium |
| Competitors copy freemium | Price pressure on paid tiers | Medium |
| "Cheap" positioning | Enterprise reluctant to buy | High |
| Sales team leaves | Lose relationships, deals slow | Medium |
Deep Analysis
Positive Cascade: ✅ Viral growth if product is shareable ✅ Large user base creates network effects ✅ Free tier = marketing channel ✅ Data/learnings from more users
Negative Cascade: ⚠️ Free users != target customers ⚠️ Conversion rate likely low (2-5% typical) ⚠️ Resources shift from paying customers ⚠️ Harder to raise prices later ⚠️ Enterprise sales become harder ("Why pay when there's free?")
Key Question
"What does freemium optimize for?"
- First-order: Volume
- Second-order: Conversion rate becomes the constraint
The math:
- Current: 1,000 paid users × $100 = $100K MRR
- Freemium: 50,000 free + 2,500 paid × $50 = $125K MRR
- But: Support costs up, team larger, margins down
Is 25% more revenue worth 50x more users and compressed pricing?
Recommendation
Before launching freemium, validate:
- What's realistic conversion rate for your market?
- Can you segment features so free doesn't cannibalize paid?
- Do you have infrastructure to support 10-50x users?
- Will free users actually convert, or just use free forever?
- How will competitors respond?
Alternative second-order moves:
- Free trial (not free forever) → tests without commitment risk
- Freemium for specific segment (students, side projects)
- Community tier with limited features, not hobbled product
Example 2: Competitive Response
Input:
"Our main competitor just cut prices 30%. Should we match?"
Output:
Second-Order Analysis: Competitor Price Cut
The Situation
Competitor cut prices 30%. Immediate pressure to respond.
First-Order Thinking (Obvious)
"They cut prices. We must match or lose customers."
Second-Order Analysis
Why did they cut prices?
- Possibility A: Gaining market share aggressively (funded)
- Possibility B: Desperate (losing customers, need volume)
- Possibility C: Segment focus (lowering to win a specific tier)
What happens if we match?
| If We Match | First-Order | Second-Order | Third-Order |
|---|---|---|---|
| Our prices drop 30% | Revenue drops ~30% short-term | Margins compress, layoffs? | Innovation slows, service degrades |
| Customers stay | Retention maintained | But at lower value | Customers now expect low prices |
| Competitor response | They match again? | Price war escalates | Someone goes out of business |
What happens if we DON'T match?
| If We Don't Match | First-Order | Second-Order | Third-Order |
|---|---|---|---|
| Some customers leave | Lost revenue | Remaining customers are less price-sensitive | Higher quality customer base |
| We look premium | Perceived as expensive | Forced to differentiate | Opportunity to add value, justify |
| Competitor gains share | They grow | But at lower margins | Their growth may be unprofitable |
The Non-Obvious Insight
"Matching their price assumes their strategy is correct."
What if their price cut is a sign of weakness, not strength? What if the customers who leave for 30% savings are your worst customers? What if this forces you to differentiate in ways that ultimately strengthen you?
Strategic Options
| Option | Second-Order Consequences |
|---|---|
| Match the price | Price war, margin compression, race to bottom |
| Don't match, differentiate | Lose some customers, force value innovation |
| Don't match, segment | Keep enterprise pricing, let them have SMB |
| Don't match, add value | Bundle services, increase perceived value |
| Temporary match | Signal willingness to fight, then raise |
Recommendation
Don't immediately match. Instead:
- Analyze who's churning - If it's your least profitable customers, let them go
- Double down on differentiation - What do you do better? Emphasize it
- Segment your response - Maybe match for one tier, not all
- Consider value-add - Instead of cutting price, add something worth 30%
- Wait and see - They may not sustain this; watch for 2 quarters
The second-order winner: The company that doesn't match and instead uses this pressure to get better often wins long-term.
Example 3: Policy Change
Input:
"We're considering implementing a 4-day work week. Apply second-order thinking."
Output:
Second-Order Analysis: 4-Day Work Week
The Decision
Implement 4-day work week (32 hours) at full pay.
First-Order Effects (Obvious)
| Effect | Expected | Probability |
|---|---|---|
| Employee satisfaction increases | Happier team | High |
| Recruiting advantage | More applicants | High |
| Productivity per hour increases | Focused work | Medium |
| Costs same, days worked fewer | Seems efficient | High |
First-order conclusion: Seems like a clear win!
Second-Order Effects
| First Effect | Response/Consequence | Probability |
|---|---|---|
| Happier team | Expectations reset—5 days now feels punishing | High |
| More applicants | Attracted to perk, not mission | Medium |
| Productivity up | Some roles can't compress (support, sales) | High |
| Costs same | Customer coverage issues M-F | Medium |
Third-Order Effects
| Second Effect | Further Cascade | Probability |
|---|---|---|
| 5 days feels punishing | If you need surge capacity, resentment | High |
| Wrong applicants | Culture dilution, mission disconnect | Medium |
| Some roles don't fit | Two-tier system, internal conflict | High |
| Coverage gaps | Customer complaints, competitive disadvantage | Medium |
Deep Analysis
Who benefits?
- Roles where output > hours (engineering, creative)
- People with outside responsibilities (parents, caregivers)
Who doesn't benefit?
- Customer-facing roles that need 5-day coverage
- Time-sensitive functions (sales, support)
- Leaders who work across time zones
Hidden consequences:
- Two-tier culture: If some teams work 4 days and others can't, resentment builds
- Expectation reset: Once given, very hard to take back
- Hiring bar drops: People come for the perk, not the mission
- Surge capacity lost: When crunch time comes, you've lost a norm
- Communication friction: If everyone's off Friday, what about Thursday EOD issues?
The "And Then What" Chain
- You implement 4-day week →
- Team loves it, productivity steady →
- Competitors don't match, you attract their talent →
- But: competitors now work 25% more hours →
- Over time, competitive edge erodes →
- You need to work more, but can't take back the perk →
- You hire more people to cover, costs rise →
- Or you lose ground to more intense competitors
Questions to Answer
- Is your business one where hours correlate with output? (If no, 4-day makes sense)
- Can ALL roles work 4 days, or will you create classes?
- What happens during crunch times?
- How will customers respond to Friday absence?
- What signal does this send about intensity/ambition?
Recommendation
Instead of blanket 4-day week:
- Offer flexible time - Let people choose when to work 32-40 hours
- Pilot first - Try with one team for 3 months, measure
- Measure carefully - Output per person, customer sat, not just hours
- Set expectations - Crunch periods still happen
- Communicate why - It's about productivity, not laziness
The second-order winning move: Find the specific benefit you want (reduced burnout, better talent) and solve it more directly without the blanket policy.
Checklists & Templates
Second-Order Thinking Checklist
## Before Any Major Decision
□ Have I stated the first-order effects?
□ Have I asked "And then what?" at least twice?
□ Have I considered how each stakeholder will respond?
□ Have I identified potential unintended consequences?
□ Have I thought about competitive response?
□ Have I considered what happens if this succeeds? (success problems)
□ Have I considered reversion to mean?
□ Am I thinking differently than the average person?
Consequence Chain Template
## Second-Order Analysis: [Decision]
### The Decision
[What we're considering]
### Stakeholder Responses
| Stakeholder | First Reaction | Second Response |
|-------------|----------------|-----------------|
| Customers | | |
| Competitors | | |
| Employees | | |
| Investors | | |
| Regulators | | |
### Consequence Chain
| Level | Effect | Probability | Severity |
|-------|--------|-------------|----------|
| First | | | |
| Second | | | |
| Third | | | |
### Success Scenario Cascade
If this works perfectly, what problems does success create?
### Failure Scenario Cascade
If this fails, what cascades from that?
### Net Assessment
Given all levels, should we proceed?
Skill Boundaries
What This Skill Does Well
- Structuring persuasive content
- Applying copywriting frameworks
- Creating draft variations
- Analyzing competitor approaches
What This Skill Cannot Do
- Guarantee conversion rates
- Replace brand voice development
- Know your specific audience
- Make final approval decisions
References
- Marks, Howard. "The Most Important Thing" (2011) - Second-level thinking
- Munger, Charlie. "Poor Charlie's Almanack" - Mental models
- Taleb, Nassim. "Antifragile" (2012) - Unintended consequences
- Kahneman, Daniel. "Thinking, Fast and Slow" - Cognitive biases
- Meadows, Donella. "Thinking in Systems" - Systems dynamics
Related Skills
- first-principles - Complementary: challenge assumptions
- inversion - Think backward from failure
- pre-mortem - Anticipate what goes wrong
- regret-minimization - Long-term decision framework
- reversible-decisions - Type 1 vs. Type 2 decisions
Skill Metadata
- Mode: cyborg
name: second-order-thinking
category: thinking
subcategory: decision-making
version: 1.0
author: MKTG Skills
source_expert: Howard Marks, Charlie Munger
source_work: The Most Important Thing
difficulty: intermediate
estimated_value: $3,000 strategic consulting session
tags: [thinking, decisions, strategy, consequences, Howard-Marks, mental-models]
created: 2026-01-25
updated: 2026-01-25
FAQ
What does the second-order-thinking skill do?
Think beyond immediate consequences to understand the chain reactions of decisions. Master Howard Marks' investment framework for seeing what others miss. Use when: Strategic decisions where long-term consequences matter; Policy/rule changes that will trigger behavioral responses; Competitive moves to anticipate market reactions; Product decisions where user behavior may shift; Investment analysis to see past obvious conclusions
How do I install second-order-thinking?
Run npx skills add https://github.com/guia-matthieu/clawfu-skills --skill second-order-thinking in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/second-order-thinking/ (personal) or .claude/skills/second-order-thinking/ (project).
Which AI agents can use second-order-thinking?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is second-order-thinking safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains second-order-thinking?
It is published by guia-matthieu in guia-matthieu/clawfu-skills. It has 249 recorded installs.
More from guia-matthieu/clawfu-skills
whisper-transcription
guia-matthieu/clawfu-skills
Transcribe audio and video files to text using OpenAI Whisper. Use when: converting podcasts to blog posts; creating video subtitles; extracting quotes from interviews; repurposing video content to text; building searchable audio archives
yc-pitch-deck
guia-matthieu/clawfu-skills
Create a compelling startup pitch deck that follows the structure proven to raise billions from top investors. Master the YC and Sequoia formats that get founders funded. Use when: Fundraising to create investor pitch decks; YC application to structure your narrative; Demo Day prep to craft your 2-minute pitch; Angel investors to communicate your opportunity; Partnership pitches to structure compelling asks
conversion-copywriting
guia-matthieu/clawfu-skills
Write copy that gets a "yes" using Joanna Wiebe's research-first, Voice of Customer methodology Use when: Writing landing pages, emails, or sales pages that need measurable conversion results; Starting a new copy project and need a systematic process to follow; Struggling with what to write and staring at a blank page; Wanting to prove ROI to clients with data-backed decisions; Improving existing copy through validation and testing
web-scraper
guia-matthieu/clawfu-skills
Extract structured data from websites. Use when: collecting competitor pricing; scraping product listings; extracting contact information; gathering research data; monitoring website changes
sound-design-film
guia-matthieu/clawfu-skills
Apply Walter Murch's legendary film sound principles to marketing video, creating emotionally resonant audio that audiences feel without consciously noticing. Use when: Designing sound for brand films and documentaries; Creating emotional impact in video ads; Layering music, effects, and voice effectively; Building immersive soundscapes for content; Elevating production value through audio
report-generator
guia-matthieu/clawfu-skills
Generate PDF/HTML reports from templates and data. Use when: creating client reports; generating weekly summaries; producing marketing performance reports; automating recurring reports
Popular other skills
hyperframes-cli
heygen-com/hyperframes
The HyperFrames CLI by job - scaffold, check, look at frames, edit the timeline, preview, render locally or in the cloud, publish, project history - plus reading its JSON and recovering from build or render failures.
triage
mattpocock/skills
Move issues and external PRs through a state machine of triage roles, categorise, verify, grill if needed, and write agent-ready briefs.
ask-matt
mattpocock/skills
Ask which skill or flow fits your situation. A router over the skills in this repo.
to-questionnaire
mattpocock/skills
Turn a decision you can't fully answer into a questionnaire for someone else to fill in.
loop-me
mattpocock/skills
Grill me about specs for the workflows I want to build, within this workspace.