
Running Decision Processes
Run structured decision rituals—curiosity loops and values scorecards—before committing to product, career, or roadmap choices.
Overview
running-decision-processes is a journey-wide agent skill that applies curated Lenny Podcast decision frameworks—curiosity loops and values scorecards—whenever a solo builder needs structured input before committing.
Install
npx skills add https://github.com/refoundai/lenny-skills --skill running-decision-processesWhat is this skill?
- Synthesizes 65 Lenny’s Podcast guests with 82 decision-process mentions into tactical patterns
- Curiosity Loop: lightweight asks (e.g. pick 2 of 9 topics) from curated experts plus people who know you
- Personal values stack-rank as an internal scorecard to stress-test a decision’s future plot line
- Emphasis on rationale-heavy questions over biased yes/no polling
- Close-the-loop etiquette: process feedback and thank participants after the decision
- 65 guests
- 82 mentions
- Curiosity Loop example uses 9 topics with pick 2–3
Adoption & trust: 1.3k installs on skills.sh; 1k GitHub stars; 3/3 security scanners passed (skills.sh audits); trending (+100% hot-view momentum).
What problem does it solve?
You face a big fork and only get shallow yes/no takes or advice that ignores your context and values.
Who is it for?
Founders deciding positioning, roadmap cuts, content series topics, or career moves who want repeatable process instead of gut-only calls.
Skip if: Purely technical implementation tasks, automated CI decisions, or situations where a signed spec and contract are already frozen.
When should I use this skill?
You need structured human input, values alignment, or podcast-backed tactics before committing to a product, content, or career decision.
What do I get? / Deliverables
You run a documented decision process with ranked values, lightweight expert input, and explicit rationale you can hand to planning or implementation skills next.
- Curiosity-loop outreach draft
- Values-aligned decision memo
- Documented rationale for the chosen path
Recommended Skills
Journey fit
Useful at every journey phase - explore requirements and options before committing to a direction.
Where it fits
Poll ten advisors with a pick-two-of-nine topic list to see which problem space resonates before you prototype.
Stack-rank personal values against two MVP scopes to see which path optimizes your stated identity over five years.
Run a lightweight curiosity loop on feature priority before writing an implementation plan for the agent.
Ask channel experts to rank launch tactics with rationale instead of chasing generic growth hacks.
Use values and advisor loops to decide whether to double down on retention work versus new acquisition bets.
How it compares
Use for human judgment workflows with structured outreach—not for Jira automations or statistical A/B design skills.
Common Questions / FAQ
Who is running-decision-processes for?
Solo and indie builders who make frequent strategic calls and want podcast-grade decision hygiene without hiring a coach.
When should I use running-decision-processes?
At Idea when researching direction, at Validate when scoping what to build, at Launch when picking distribution bets, at Grow when choosing lifecycle bets, and anytime you need a Curiosity Loop before locking a plan.
Is running-decision-processes safe to install?
It is reference content only; review the Security Audits panel on this page and avoid pasting secrets into prompts when drafting outreach emails.
SKILL.md
READMESKILL.md - Running Decision Processes
# Running Decision Processes - All Guest Insights *65 guests, 82 mentions* --- ## Ada Chen Rekhi *Ada Chen Rekhi* > "A curiosity loop is essentially going to a whole bunch of people. In this case, I sent out an email very quickly to about 10 or 11 people and asking them, 'Hey, here are nine topics for Lenny's Podcast. What are two or three of the topics that resonate with you and why?'" **Insight:** Use a structured 'Curiosity Loop' to gather contextual advice from a curated group to fight the bias of generic, non-contextual advice. **Tactical advice:** - Ask specific questions that solicit rationale rather than biased 'yes/no' answers. - Curate a mix of subject matter experts and people who know you personally. - Make the ask lightweight (e.g., 'pick top 2 of 9') to ensure a high response rate from busy people. - Close the loop by processing the info and thanking participants for their impact on your decision. *Timestamp: 00:04:08* --- > "I looked at those values and I said, 'Well, if I draw a straight line from where I am right now and just extend it forward and play the rest of the movie as it plays out, given the current plot line, how well does that optimize for those values?'" **Insight:** Use a personal values stack-rank as an 'internal scorecard' to evaluate if major life and career decisions align with your core identity. **Tactical advice:** - Filter a broad list of value words down to a top 3-5 list. - Apply these values to specific opportunities to see if they pass or fail your internal criteria. - Prioritize the 'inner scorecard' (personal fulfillment) over the 'outer scorecard' (status, wealth, titles). *Timestamp: 00:37:12* ## Alisa Cohn *Alisa Cohn* > "How do we decide when we disagree? And that is a very good thing to explore because there's actually a lot of different ways to decide when you disagree... let's assume that the person who cares the most can win that argument. It might be, the person who's got the best perspective and the most expertise can win that argument." **Insight:** Establishing a 'tie-breaking' protocol in advance prevents stalemates and resentment during disagreements. **Tactical advice:** - Decide if the 'most passionate' person wins or the 'most expert' person wins - Consider a 'back and forth' system where partners take turns making the final call *Timestamp: 01:05:57* ## Ami Vora *Ami Vora* > "As you get senior, the only problems you'll see are ones that are fundamentally unsolvable because otherwise, someone would've solved it before they got to you. And so all you're doing is choosing which branch of suboptimal you're going to put your name on and describing the principles you're using." **Insight:** Senior leadership decisions are often about choosing the best possible 'suboptimal' path among difficult trade-offs. **Tactical advice:** - Acknowledge when a decision is suboptimal but necessary. - Clearly communicate the principles and context used to arrive at a difficult choice. *Timestamp: 01:01:59* ## Annie Duke *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, your intuition is sometimes right. If you don't make it explicit, then you don't get to find out when it's wrong." **Insight:** High-quality decision-making requires moving from 'gut feel' to explicit models that can be tested and refined. **Tactical advice:** - Document the implicit assumptions behind a 'gut' feeling. - Review these explicit assumptions later to see where your intuition was right or wrong. *Timestamp: 00:00:00* --- > "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?" **Insight:** You can shorten any feedback loop by identifying and tracking leading indicators that are necessary for the final desired outcome. **Tactical advice:*