High Stakes Decision Making
Navigate irreversible choices and extreme uncertainty with speed and structural clarity.
The Guide
5 key steps synthesized from 11 experts.
Categorize and Filter the Decision
Use the Kombucha Scale or the Type-1 and Type-2 framework to determine if the choice warrants a formal process. Separate one-way door decisions from two-way door decisions to ensure you do not over-process reversible actions. Reserve high-rigor structured frameworks exclusively for choices with long-term, irreversible consequences.
Featured guest perspectives
"Important truths can be uncomfortable and make people defensive. Any high-functioning organization has to have mechanisms and a culture that supports truth-telling. You have to talk about that and how it takes energy."— Lenny Rachitsky
"A decision-making framework is only needed when there is lack of clarity about a decision that is higher-risk. Higher risk can mean that the decision has long-term implications or that it can be costly to unwind if the wrong decision is made."— Lenny Rachitsky
Frame the Eigenquestion
Identify the single most important question that, when answered, will make all subsequent choices clear. Avoid relying on a laundry list of mediocre arguments and instead seek a Single Decisive Reason (SDR) that justifies the path. This simplifies complex problems by focusing the team's energy on the root logic rather than surface-level symptoms.
Socialize and Align Individually
High-stakes meetings should never be the first time stakeholders see a controversial proposal. Meet with detractors early to deeply understand their concerns and enlist champions to support your case in the group setting. This pre-alignment prevents public friction and ensures the formal meeting is a culmination of alignment rather than a debate.
Featured guest perspectives
"If your plan is to just show up and hope the meeting goes well in full view of key decision makers, then you have a high risk of not getting the outcome you want. Instead, I prepare key attendees before the meeting, because my goal is to walk into the room with a coalition of supporters. I do this with both detractors and champions."— Lenny Rachitsky
Establish Kill Criteria and Pre-mortems
Conduct a pre-mortem by imagining the project has already failed and identifying the specific causes, such as tigers or paper tigers. Define explicit kill criteria at the start of the investment to make the decision to stop objective and emotion-free later. This prevents the bias to persist in failing projects due to sunk costs or organizational identity.
Featured guest perspectives
"So a pre-mortem, it's great only if you set up kill criteria. Commit to actions that you're going to take if you see those signals."— Annie Duke
Commit and Communicate Unified Direction
Commit to a decision once you have roughly 70 percent of the information required to move forward. Transition from seeking consensus to ensuring everyone is heard before a single accountable owner makes the final call using a framework like S.P.A.D.E. or RAPID. Once a call is made, communicate it clearly as the unified company direction to maintain execution speed.
Featured guest perspectives
"What is important isn’t that everyone agrees, it’s that everyone is listened to. And then the right person makes a decision, communicates it clearly, and rallies everyone around it."— Lenny Rachitsky
"The biggest challenge was that in crypto there's just so much uncertainty in general, simple questions like, is Ethereum going to be a thing, are the subject of debate. And no one actually at the time had an answer to that question. Lots of really strong opinions and so you have to be able to have those debates because lots is going on, but then you have to be able to come out of those conversations with a clear kind of company point of view that you're all shooting toward."— Jeremy Henrickson
"Try this next time you’re stuck on a decision: Ask your team if they’d rather keep hashing it out or for you to just make a call. I bet you they’d rather just move on."— Lenny Rachitsky
Get this guide as an AI skill for Claude Code
Install This Skill
Add this skill to Claude Code, Cursor, or any AI coding assistant that supports Agent Skills.
Quick Install (Recommended)
Install this skill directly using npx:
npx skills add RefoundAI/lenny-skills --skill high-stakes-decisions Or install all 76 skills:
npx skills add RefoundAI/lenny-skills Manual Installation
Download the skill
Download Skill (.zip)Add to your project
Create a folder in your project root and add the skill file:
.claude/skills/high-stakes-decisions/SKILL.md Start using it
Claude will automatically detect and use the skill when relevant. You can also invoke it directly:
Help me with high stakes decision making Or receive these install instructions in your inbox:
Guest Perspectives
Deep dive into what 10 podcast guests shared about high stakes decision making.
Annie Duke
"There is no such thing as a long feedback loop. And the way you choose to shorten the feedback loop is to say, what are the things that are correlated with the outcome that I eventually desire?"
- Identify leading indicators that correlate with your desired long-term outcome.
- Deconstruct long-term goals into smaller, measurable segments to create faster feedback loops.
- Adjust project strategy based on early signals rather than waiting for the final result.
"So a pre-mortem, it's great only if you set up kill criteria. Commit to actions that you're going to take if you see those signals."
- Set explicit 'kill criteria' before a project or investment begins.
- Identify the specific negative signals that would trigger a project shutdown.
- Pre-commit to the specific actions the team must take if those shutdown signals are observed.
Ben Horowitz
"The biggest mistake that you make, the worst thing that you do as a leader, there's things in your control and there's things out of your control and hesitation, that's generally the most destructive. And I go through all the ways that it's destructive, but it's extremely bad. And the thing that causes you to hesitate is both decisions are horrible."
- Identify when you are avoiding a subject because all possible alternatives are painful.
- Trust your perception of the situation and run toward the necessary decision immediately.
- Acknowledge that any decision is better than the destructive paralysis of hesitation.
Claire Hughes Johnson
"If you're not sure who the decision maker is, one, it's probably you. And I'd rather you act that way than not because you're going to like slow the whole company down. Follow a process and get it done, and don't forget to actually make a decision."
- Assume ownership of a decision if the designated owner is unclear to prevent organizational paralysis.
- Follow established processes to reach a conclusion, but ensure a final, definitive decision is actually made.
- Ask for clarification immediately if you are truly unsure of your authority, rather than staying stuck.
Daniel Lereya
"A, we understood that you need to constantly think, especially at these phases, how would you transform completely the product in the next three months? And if you can't answer that and you say, 'Listen, I'm doing so much.' But you can't point this exact thing, you have a focus problem in my eyes."
- Audit your roadmap to ensure you can point to one specific initiative that will fundamentally transform the product this quarter.
- Pivot away from 'fake speed'—doing many small things—if they do not lead to a significant product transformation.
- View competitive pressure as a 'gift' that provides permission to rethink your entire platform architecture.
Jeremy Henrickson
"The biggest challenge was that in crypto there's just so much uncertainty in general, simple questions like, is Ethereum going to be a thing, are the subject of debate. And no one actually at the time had an answer to that question. Lots of really strong opinions and so you have to be able to have those debates because lots is going on, but then you have to be able to come out of those conversations with a clear kind of company point of view that you're all shooting toward."
- Define a clear company point of view even when perfect answers are unavailable.
- Execute at full speed toward a chosen direction until the leadership team explicitly decides to pivot.
- Communicate progress and security in a technical context rather than focusing on external market hype.
Kevin Weil
"Our general mindset is in two months, there's going to be a better model and it's going to blow away whatever the current set of limitations are. And we say this to developers too. If you're building and the product that you're building is kind of right on the edge of the capabilities of the models, keep going because you're doing something right. Give it another couple months and the models are going to be great, and suddenly the product that you have that just barely worked is really going to sing."
- Build products that sit on the edge of current model capabilities.
- Maintain development conviction when performance is subpar, anticipating rapid model upgrades.
- Re-evaluate product goals and limitations every two months to align with technological leaps.
Laura Modi
"We are going to run out of product for the babies that are on Bobbie today. We have about six days before we get to a place where we won't be able to serve those who've already made a commitment to Bobbie. She's like, 'So we need to turn off our site and stop growing the business.'"
- Monitor inventory depletion rates relative to replenishment capacity daily.
- Be prepared to halt all customer acquisition immediately if supply stability is at risk.
- View aggressive growth as a potential liability rather than a purely positive metric.
Matt Mochary
"It's not because I'm magician or a genius, it's because when someone's in fear, they're gripped. They can't see reality, their brain is making very exaggerated predictions. Whereas when someone is not in fear, and I'm not because it's not my situation, I am not gripped and therefore, my brain isn't making exaggerated predictions. And so, we make this bet once I win, then all of a sudden the CEO realizes, oh my God, there's something to this, fear gives bad advice."
- Identify when fear has 'gripped' your mind, causing you to make exaggerated negative predictions.
- Seek input from a neutral third party who is not emotionally involved in the situation to clarify reality.
- Use low-stakes 'bets' to prove that fear-based intuition often provides incorrect advice.
Sahil Mansuri
"So the way I think about setting up a plan when you have limited visibility and some major headwinds is setting up a really conservative plan and then having milestones, short term milestones that unlock the ability to lean into growth and spend based on hitting those targets."
- Draft a highly conservative annual base plan to manage burn risk and ensure financial stability.
- Identify specific short-term performance milestones to serve as triggers for future growth spending.
- Unlock budget for expansion or hiring only after predetermined targets have been successfully achieved.
Tim Holley
"Another example of a principle is minimizing waste. It aligns with how we think about product development, which is, we want to know, is the work we're doing adding value to the customer and the business? And so something that isn't working out a lot of times in product development we're wrong. And so being able to say, 'No, this is no longer valuable, we need to move on to the next thing,' has been something that's served us really well."
- Regularly audit ongoing initiatives to ensure they are driving the North Star metric.
- Foster a culture where being 'wrong' in product development is accepted and used as a trigger to stop low-value work.
- Prioritize moving resources to the next valuable project over sustaining a failing initiative.
Make your product team AI-native
These skills work best as a system. Get a free 8-email course: map how your team works today, wire agents into real workflows, and make it stick. From the team that does this for a living.
Related Skills
Other Planning & Prioritization skills you might find useful.
Roadmap Prioritization
Prioritizing 'lovability' over mere viability ensures that early product versions generate the organ...
View Skill → →Goal Setting and OKRs
Measuring success through absolute volume rather than conversion percentages prevents teams from art...
View Skill → →Planning Cadence Optimization
Maintaining momentum requires shifting focus from distant deadlines to the immediate actions require...
View Skill → →Evaluating Trade-Offs
High-velocity teams avoid the binary choice of building or buying by using SaaS for core functionali...
View Skill → →