home / skills / refoundai / lenny-skills / running-decision-processes

running-decision-processes skill

/skills/running-decision-processes

This skill helps you run effective decision-making using frameworks like DACI to move from analysis to action with clarity.

npx playbooks add skill refoundai/lenny-skills --skill running-decision-processes

Review the files below or copy the command above to add this skill to your agents.

Files (2)
SKILL.md
4.3 KB
---
name: running-decision-processes
description: Help users run effective decision-making processes. Use when someone is facing a high-stakes decision, dealing with analysis paralysis, needs to align stakeholders on a choice, or wants to establish decision frameworks like DACI or RAPID.
---

# Running Decision Processes

Help the user run effective decision-making processes using frameworks from 65 product leaders.

## How to Help

When the user asks for help with decision processes:

1. **Understand the decision type** - Ask if this is reversible or irreversible, high-stakes or routine
2. **Identify the blockers** - Determine what's preventing the decision from being made
3. **Structure the process** - Recommend an appropriate framework for the decision at hand
4. **Enable commitment** - Help them move from deliberation to action

## Core Principles

### Hesitation is destructive
Ben Horowitz: "The worst thing that you do as a leader is you hesitate on the next decision. The thing that causes you to hesitate is both decisions are horrible." Failing to make an explicit decision causes organizational anxiety. Recognize when you're avoiding a decision because all options are bad.

### Make implicit explicit
Annie Duke: "It's so incredibly necessary in improving decision quality to take what's implicit and make it explicit. It's not that intuition is crap... If you don't make it explicit, then you don't get to find out when it's wrong." Document the assumptions behind gut feelings so you can review them later and learn when intuition is right or wrong.

### Use curiosity loops for advice
Ada Chen Rekhi: "A curiosity loop is essentially going to a whole bunch of people... asking them, 'Hey, here are nine topics... What are two or three of the topics that resonate with you and why?'" Gather contextual advice by asking specific questions that solicit rationale, not biased yes/no answers.

### Act as a historian
Anneka Gupta: "I try to construct this past knowledge of what had happened and what were the decisions that were made and why were those decisions made, whether they were good or bad." Research past failed projects to understand the context of previous decisions and navigate current resistance.

### High-conviction decisions require leaps of faith
Brandon Chu: "Know how to make really, really hard high conviction decisions that actually can't be solved. You got to take a leap of faith and how to do that and bring teams through that type of ambiguity." Some decisions cannot be solved with data - take the leap and maintain high accountability for the choice.

### Distinguish decision types
Jeff Bezos: "Type 1 decisions are consequential and irreversible... Type 2 decisions are changeable, reversible." Spend more time on one-way doors. Move fast on reversible decisions.

### Disagree and commit
Once a decision is made, the team must commit fully even if individuals disagreed during deliberation. Without commitment, decisions get relitigated endlessly.

### Assign a clear decision-maker
Every decision needs a single accountable owner. Frameworks like DACI (Driver, Approver, Contributor, Informed) clarify who makes the call.

## Questions to Help Users

- "Is this a one-way door or a two-way door? How hard would it be to reverse this decision?"
- "What's the cost of waiting another week to decide? What's the cost of being wrong?"
- "Who is the single decision-maker here? Does everyone know who that is?"
- "What information would change your mind? Can you get that information quickly?"
- "What happened last time the team faced a similar decision?"
- "If you had to decide right now with the information you have, what would you choose?"

## Common Mistakes to Flag

- **Analysis paralysis** - Gathering more data when enough information already exists to decide
- **Decision by committee** - No clear owner leading to diffused accountability
- **Treating all decisions equally** - Applying the same rigor to reversible and irreversible decisions
- **Relitigating decisions** - Reopening settled decisions without new information
- **Implicit assumptions** - Making gut decisions without documenting the reasoning for later learning

## Deep Dive

For all 82 insights from 65 guests, see `references/guest-insights.md`

## Related Skills

- running-effective-meetings
- planning-under-uncertainty
- prioritizing-roadmap

Overview

This skill helps you run effective decision-making processes for high-stakes, ambiguous, or stalled choices. It guides you to pick the right framework, clarify ownership, expose hidden assumptions, and move from deliberation to committed action. Use it to cut through analysis paralysis and align stakeholders quickly.

How this skill works

I start by categorizing the decision (reversible vs irreversible, high-stakes vs routine) and identifying the blockers preventing progress. Then I recommend a structured process (e.g., DACI, RAPID, one-way/two-way decision flows), surface assumptions, and design short experiments or information-gathering steps when needed. Finally, I help set a clear owner, timeline, and commitment mechanism so the team can execute without relitigating.

When to use it

  • Facing a high-stakes, irreversible decision that needs deliberate alignment
  • Experiencing analysis paralysis or endless debate with no resolution
  • Needing to align cross-functional stakeholders and clarify who decides
  • Creating repeatable decision frameworks for product or organizational choices
  • Deciding whether to run an experiment vs commit to a large investment

Best practices

  • Classify decisions as one-way (Type 1) or reversible (Type 2) and allocate time accordingly
  • Assign a single accountable decision-maker and publish the decision owner publicly
  • Make implicit assumptions explicit—document beliefs, evidence, and what would change your mind
  • Use short curiosity loops: solicit specific rationale from many people, not yes/no feedback
  • Commit once decided: agree to disagree and execute to avoid relitigation

Example use cases

  • Choosing whether to sunset a major feature that impacts many teams
  • Aligning execs and engineering on a multi-quarter platform investment
  • Deciding between two acquisition targets where limited data exists
  • Breaking a tie on product strategy when stakeholders are polarized
  • Designing a rapid experiment to de-risk a product hypothesis before committing capital

FAQ

How do I know when to use a formal framework like DACI?

Use DACI when decisions involve multiple contributors and unclear accountability. If the outcome affects many teams or requires trade-offs, DACI clarifies who drives, approves, contributes, and needs to be informed.

What if the team keeps reopening decisions after they were made?

Ensure the decision type and evidence threshold were documented, confirm the decision-maker, and require new information to be presented before reopening. Reinforce 'disagree and commit' norms and set review points only when meaningful new data exists.