thinking-second-order

Analyze decision outcomes by mapping second- and third-order effects.

941|129|Updated Jan 28, 2026
One-click install
npx skills add https://github.com/tjboudreaux/cc-thinking-skills --skill thinking-second-order
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: thinking-second-order
Source: https://github.com/tjboudreaux/cc-thinking-skills/tree/main/skills/thinking-second-order
Command: npx skills add https://github.com/tjboudreaux/cc-thinking-skills --skill thinking-second-order

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Second-order thinking helps decision-makers avoid simple, short-term fixes by systematically considering longer-term and indirect effects of actions. It challenges the default "what works now" mindset and provides a disciplined way to anticipate unintended consequences, dependencies, and feedback loops that shape outcomes over time.

Core Features & Use Cases

  • Identifies first-order vs second- and third-order effects to prevent tunnel vision.
  • Provides a pragmatic framework (including the 10/10/10 horizon, consequence mapping, and systemic thinking) for strategic decisions, policy design, and product planning.
  • Includes an actionable workflow, prompts, and a verification checklist to support robust analysis in real projects.

Quick Start

Apply the Second-Order Analysis workflow to a current decision by outlining its immediate effects, then iteratively map downstream consequences.

The Process

  1. Identify the Decision and First-Order Effect
  2. Ask "And Then What?" and chain downstream consequences
  3. Apply the 10/10/10 framework to time-bound impacts
  4. Consider systemic effects and feedback loops
  5. Map the consequence chain and revise the decision accordingly

Questions to Surface Second-Order Effects

  • "And then what?"
  • "Who else is affected, and how will they respond?"
  • "What incentives does this create?"
  • "What behavior does this encourage/discourage?"
  • "If this works, what problems does success create?"
  • "What will we wish we had done differently in a year?"
  • "What does this look like if everyone does it?"

Verification Checklist

  • [ ] Identified first-order effect clearly
  • [ ] Asked "and then what?" at least 3 times
  • [ ] Applied 10/10/10 framework
  • [ ] Considered systemic/scaled effects
  • [ ] Identified potential feedback loops
  • [ ] Revised decision based on full consequence chain
  • [ ] Documented reasoning for future reference

Marks' Warning

"First-level thinking is simplistic and superficial, and just about everyone can do it. Second-level thinking is deep, complex, and convoluted."

Frequently Asked Questions about thinking-second-order

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is second-order thinking in decision making?

Second-order thinking is a decision-making process that evaluates the long-term, indirect effects of actions. It moves past superficial first-order outcomes to map downstream consequences, feedback loops, and unintended systemic impacts.

How do I apply second-order thinking to strategic planning?

Apply second-order thinking by identifying an immediate first-order effect, repeatedly asking "and then what?" to chain consequences, and applying the 10/10/10 horizon framework to time-bound the resulting impacts for strategic planning.

When do I need to analyze third-order effects in product roadmapping?

Analyze third-order effects in product roadmapping when immediate fixes risk creating long-term behavioral changes or systemic feedback loops. It prevents tunnel vision by mapping how success or scaled adoption alters future incentives.

How do I evaluate unintended consequences in policy design?

Evaluate unintended consequences in policy design by mapping the consequence chain and asking what new incentives the policy creates. Consider how affected parties will respond and what problems success might generate to revise decisions accordingly.

What is the 10/10/10 framework for consequence mapping?

The 10/10/10 framework is a consequence mapping technique used to time-bound decision impacts across 10 minutes, 10 months, and 10 years. It structures systemic thinking to surface delayed feedback loops and strategic risks.

Best way to avoid tunnel vision in risk management decisions?

The best way to avoid tunnel vision in risk management is to use a verification checklist that ensures you ask "and then what?" multiple times. This confirms systemic effects and feedback loops are documented before finalizing decisions.