
Planning Under Uncertainty
Ground product decisions in curated Lenny Podcast guest tactics when roadmap, metrics, and playbooks are unclear.
Install
npx skills add https://github.com/refoundai/lenny-skills --skill planning-under-uncertaintyWhat is this skill?
- Aggregates planning-under-uncertainty insights from 44 Lenny Podcast guests with 52 tagged mentions
- Surfaces tactical quotes on crisis diagnosis, wartime PM, and building arks instead of predicting failure
- Emphasizes playbook-free problem solving and leadership under unprecedented conditions
- Organized by guest with timestamps for traceability back to source episodes
- Product-management mindset reference rather than implementation automation
Adoption & trust: 1.3k installs on skills.sh; 1k GitHub stars; 3/3 security scanners passed (skills.sh audits); trending (+100% hot-view momentum).
Recommended Skills
Journey fit
Canonical shelf is validate/scope because uncertainty framing matters most before committing build scope, but insights apply across the journey. The skill is a synthesis of PM judgment for scoping under ambiguity—diagnosis, grit, and wartime humility—not a technical integration.
Common Questions / FAQ
Is Planning Under Uncertainty safe to install?
skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.
SKILL.md
READMESKILL.md - Planning Under Uncertainty
# Planning Under Uncertainty - All Guest Insights *44 guests, 52 mentions* --- ## Alex Hardimen *Alex Hardimen* > "I think about wartime product management, right? You're coming in, and I think there was... this incredible humility that was needed to really understand and first diagnose what was actually happening on the platform." **Insight:** Managing through a crisis requires 'wartime' humility to accurately diagnose problems before attempting solutions. **Tactical advice:** - Prioritize diagnosis over immediate action in a crisis - Approach unknown platform issues with humility *Timestamp: 00:09:28* --- > "These are core product skills that we look for in terms of leadership and grit, and the ability to drive through really, really tough problems that there's no playbook for, nobody has ever really done before." **Insight:** The most valuable PMs are those who can navigate problems that lack a pre-existing playbook. **Tactical advice:** - Focus on grit and leadership when there is no playbook - Develop the ability to drive through unprecedented problems *Timestamp: 00:11:21* ## Ben Horowitz *Ben Horowitz* > "no credit will be given for predicting rain, only credit for building an ark... You have to build the ark. It doesn't matter if you predict you're going to fail, you've still failed. It gets you nothing. So what you have to do is figure your way out of it and spend all your time on that." **Insight:** In uncertain or failing conditions, the only valuable action is building a solution (the 'ark') rather than accurately forecasting the disaster. **Tactical advice:** - Shift focus from 'predicting failure' to 'figuring a way out' - Spend 100% of energy on the solution path once a threat is identified *Timestamp: 01:24:05* ## Brian Balfour *Brian Balfour* > "If you're a late-stage startup... you can afford the luxury to place multiple bets and spread your chips and wait it out a little bit to see who the winner is... The key question for startups is totally different. You don't have the luxury to spread your chips. You have to go all in. You have to choose one and go all in." **Insight:** Strategic betting depends on company stage: late-stage companies should diversify bets, while early-stage startups must commit to a single, focused bet. **Tactical advice:** - Assess your resource constraints before deciding on a multi-platform vs. single-platform strategy. - For early-stage startups, pick the platform with the best retention and commit fully to avoid resource dilution. *Timestamp: 00:48:37* ## Brian Tolkin *Brian Tolkin* > "If you're not going to get significance, if there's no other techniques at your disposal, then sometimes you just got to trust your intuition and ship it. And if that's what you believe, then that's what you believed and you shouldn't spend time trying to get false precision." **Insight:** When data volume is too low for statistical significance, rely on intuition and judgment rather than seeking 'false precision' through flawed tests. **Tactical advice:** - Use power analysis to determine if an A/B test is even viable before starting - When data is lacking, increase conviction by talking to customers or using observational data (diff-in-diff) *Timestamp: 00:40:29* ## Camille Hearst *Camille Hearst* > "One of my favorite takeaways from that is that from this way of working around this dual track agile de-risking your riskiest ideas first approach is a concept of taking the things in the top, the biggest swing and actually prioritizing those first in terms of product discovery and figuring out what can you do to start de-risking because if you constantly put those off in favor of the lower risk or more predictable smaller swings, how are you ever going to truly innovate and get to the next level." **Insight:** To innovate, teams must prioritize the discovery and de-risking of high-risk 'big swings' rather than defaulting to safe, incremental tasks. **Tactical advice:*