PluginBench
Skill
Review
Audit score 70

planning-under-uncertainty

refoundai/lenny-skills

Navigate product planning when outcomes are unpredictable using adaptive frameworks from 44 product leaders.

What is planning-under-uncertainty?

This skill helps you plan products and strategy in uncertain environments—fast-moving markets, AI/ML projects, ambiguous timelines, or when you can't predict what will happen. It provides frameworks for embracing optionality, building buffers, and creating decision triggers instead of rigid plans.

  • Diagnose uncertainty types (technical, market, organizational) driving your planning challenges
  • Match adaptive planning frameworks to your specific uncertainty profile and planning horizon
  • Build checkpoints and decision criteria for pivoting rather than committing to fixed roadmaps
  • Distinguish reversible from irreversible decisions to allocate planning effort efficiently
  • Develop reproducible testing processes to increase success probability in uncertain markets
  • Create buffers and contingency plans for chaos instead of assuming predictable execution

How to install planning-under-uncertainty

npx skills add https://github.com/refoundai/lenny-skills --skill planning-under-uncertainty
Claude Code
Cursor
Windsurf
Cline

How to use planning-under-uncertainty

  1. 1.Identify what's driving your uncertainty: technical unknowns, market volatility, AI/ML unpredictability, or organizational change
  2. 2.Determine your planning horizon—do you need short-term execution tactics or long-term strategic flexibility?
  3. 3.Assess your key assumptions: what would need to be true for your plan to work, and which assumptions are you least confident about?
  4. 4.Choose a planning approach: embrace optionality over prediction, build buffers for chaos, use data as a compass not GPS, or create decision triggers
  5. 5.Define decision criteria and checkpoints where you'll reassess based on learning, not just calendar dates
  6. 6.Test your core hypothesis with the smallest viable experiment before committing major resources

Use cases

Good for
  • Planning an AI/ML product when capabilities and timelines are unpredictable
  • Building in a fast-moving market where competitors and user needs shift rapidly
  • Committing to quarterly roadmaps when you're uncertain about technical feasibility
  • Deciding whether to pivot an initiative based on early signals rather than waiting for full validation
  • Running experiments to test core hypotheses before investing in full execution
Who it's for
  • Product managers planning in volatile or emerging markets
  • AI/ML product leaders dealing with technical uncertainty
  • Startup founders building with incomplete information
  • Engineering leaders balancing exploration with execution
  • Strategy teams making long-term bets in fast-changing industries

planning-under-uncertainty FAQ

When should I use this skill instead of just following a detailed roadmap?

Use this when facing technical unknowns, market volatility, AI/ML unpredictability, or organizational change. If your environment is stable and predictable, a detailed roadmap works fine. If assumptions are likely to change, adaptive planning prevents wasted effort on plans that won't survive contact with reality.

How much buffer should I build into my plans?

Buffer size depends on your chaos level. In chaotic environments, plan for explicit contingencies ranging from days to months depending on scope. The key is making buffers explicit rather than hoping things go smoothly. Ask: if this takes twice as long, what would I do differently?

How do I know if I'm spending too much time planning?

Watch for planning theater—excessive time on documents and processes that don't actually reduce uncertainty. If you're creating detailed long-term roadmaps that resist necessary pivots, or waiting for perfect information instead of deciding with 70% confidence, you're over-planning. Move faster on reversible decisions.

What's the difference between a one-way door and two-way door decision?

One-way door decisions are high-impact and irreversible (hiring a VP, major architecture choice, market entry). Two-way doors are reversible and can be adjusted later (feature experiments, process changes). Spend more planning time on one-way doors; move quickly on two-way doors.

How do I know if an experiment failed or just taught me something valuable?

Shift from judging experiments by outcomes alone to valuing the learning. A 'failed' experiment that invalidates an important hypothesis is valuable. Ask: what did we learn about our core assumption? Did we get useful signals about whether to pivot or continue?

Full instructions (SKILL.md)

Source of truth, from refoundai/lenny-skills.


name: planning-under-uncertainty description: Help users plan products and strategy when outcomes are unpredictable. Use when someone is dealing with ambiguous timelines, building in fast-moving markets, planning AI/ML projects, or asking how to make commitments when they don't know what will happen.

Planning Under Uncertainty

Help the user navigate product planning when the future is unclear using adaptive planning frameworks from 44 product leaders.

How to Help

When the user asks for help with planning under uncertainty:

  1. Understand the uncertainty type - Ask what's driving the ambiguity: technical unknowns, market volatility, AI/ML unpredictability, or organizational change
  2. Assess planning horizon - Determine if they need short-term execution tactics or long-term strategic flexibility
  3. Match framework to context - Recommend appropriate planning approaches based on their uncertainty profile
  4. Build in adaptation mechanisms - Help them create checkpoints and decision criteria for pivoting

Core Principles

Embrace optionality over prediction

Amjad Masad: "Being agile, not being stuck with roadmaps, being able to just say, oh, we're just going to switch priorities right away, is going to be super important." In rapidly changing environments like AI, maintain flexibility to pivot when new capabilities emerge rather than committing to rigid long-term plans.

Build buffers for chaos

Upasna Gautam: "Any time we're planning we build in buffers for all of that chaos that's happening on a daily basis." In chaotic environments, planning must include explicit time buffers and contingency plans ranging from days to months depending on scope.

Use data as compass, not GPS

Shaun Clowes: "Data is more like a compass than a GPS. If you look at data as a way of giving you the answer, you're always wrong." Use data to validate or invalidate intuition rather than waiting for it to tell you exactly what to do.

Value learning over winning

Ramesh Johari: "Experimentation was never historically in science about winners and losers... Experimentation is always very hypothesis driven. It's about, what are you learning?" A healthy experimentation culture values learning from "failed" risky bets more than safe, incremental "wins."

Develop reproducible testing processes

Nikita Bier: "Develop a reproducible testing process, and that will actually influence the probability of your success more than anything." Success in uncertain markets is driven by the quality and speed of the testing process rather than the initial idea.

Diagnose before acting in crisis

Alex Hardimen: "There's this incredible humility that was needed to really understand and first diagnose what was actually happening on the platform." Managing through a crisis requires "wartime" humility to accurately diagnose problems before attempting solutions.

Create decision triggers, not fixed plans

Eric Ries: "Give yourself a fixed period of time to take some decisive action and see if it feels better." Build checkpoints into plans where you'll reassess based on what you've learned, not just calendar dates.

Distinguish reversible from irreversible decisions

Claire Hughes Johnson: "Type one, type two decisions. Is it high impact? Is it irreversible? Is it not?" Spend more time on one-way doors and move quickly on reversible decisions that can be adjusted later.

Questions to Help Users

  • "What would need to be true for your current plan to work? Which of those assumptions are you least confident about?"
  • "If this takes twice as long as expected, what would you do differently? What if it takes half as long?"
  • "What's the smallest thing you could ship to learn whether your core hypothesis is correct?"
  • "Is this a one-way door or a two-way door decision?"
  • "What signals would tell you to pivot or kill this initiative?"
  • "How much buffer have you built in for unexpected chaos?"

Common Mistakes to Flag

  • Over-planning - Creating detailed long-term roadmaps that create false confidence and resist necessary pivots
  • Analysis paralysis - Waiting for perfect information instead of making decisions with 70% confidence
  • Ignoring leading indicators - Not tracking intermediate signals that could tell you earlier if you're on track
  • Judging experiments by outcomes alone - Not valuing the learning from "failed" experiments that tested important hypotheses
  • Planning theater - Spending excessive time on documents and processes that don't reduce actual uncertainty

Deep Dive

For all 52 insights from 44 guests, see references/guest-insights.md

Related Skills

  • prioritizing-roadmap
  • running-decision-processes
  • scoping-cutting
  • problem-definition