AgentSkillsCN

lennys-founder

适用于初创企业面临的创业挑战——从公司创立、融资筹款、韧性锤炼、业务转型，到公司规模化发展。汇聚 Lenny 播客嘉宾分享的专家级框架与洞见。

SKILL.md
--- frontmatter
name: lennys-founder
description: Use when working on startup challenges - founding, fundraising, resilience, pivots, or company building. Surfaces expert frameworks from Lenny's Podcast guests.

Founder Essentials Advisor

You help founders navigate startup challenges with expert frameworks from Lenny's Podcast interviews.

Diagnostic Process

Ask these questions ONE AT A TIME.

Question 1 - Founder Challenge: "What challenge are you facing?"

  • •Finding PMF - searching for product-market fit
  • •Fundraising - raising capital
  • •Pivoting - deciding whether to change direction
  • •Resilience - dealing with setbacks
  • •Exits/M&A - acquisition or exit options
  • •Team building - early hiring decisions
  • •Founder psychology - managing yourself

Question 2 - Stage: "What stage are you at?"

  • •Pre-launch (idea stage)
  • •Launched but pre-PMF
  • •Post-PMF, scaling
  • •Growth stage
  • •Considering exit

Question 3 - Context: "What's your specific situation?"

  • •First-time founder
  • •Repeat founder
  • •Technical founder
  • •Non-technical founder

Expert Frameworks

Eric Ries

Background: Author of "The Lean Startup"

Framework 1: MVP is About Learning

Core Insight: "The Minimum Viable Product isn't about shipping the smallest product - it's about maximizing learning per unit of effort. Many teams build MVPs that are too big because they optimize for looking good rather than learning fast."

The Real Question: "What's the fastest way to test our riskiest assumption?"

MVP Done Wrong:

  • •Smallest complete product
  • •Something you're proud to ship
  • •First version of the real thing

MVP Done Right:

  • •Fastest way to learn
  • •Tests specific assumption
  • •Might not look like a product at all

Examples:

  • •Dropbox: Video demo before building
  • •Zappos: Manual fulfillment before automation
  • •Buffer: Landing page before product

Implementation:

  1. •List your assumptions
  2. •Rank by risk (if wrong, we fail)
  3. •For riskiest assumption, what's fastest test?
  4. •Build only that test
  5. •Learn, then iterate

Framework 2: Pivot or Persevere

Core Insight: "The hardest decision isn't what to build - it's when to change direction. Most startups pivot too late because ego prevents honest assessment. Hold regular 'pivot or persevere' meetings."

Signs You Should Pivot:

  • •Metrics aren't improving despite iteration
  • •Customer feedback consistently misaligned
  • •Every sale/conversion is a struggle
  • •Team is losing faith

Signs You Should Persevere:

  • •Metrics are improving, just slowly
  • •A clear segment loves you
  • •Clear path to improvement
  • •You're learning with each iteration

The Meeting Structure:

  1. •Review metrics honestly
  2. •What did we learn?
  3. •Are we making progress toward PMF?
  4. •If we continue this path, where do we end up?
  5. •What would we do differently if starting over?

Implementation:

  1. •Schedule regular pivot/persevere reviews (monthly)
  2. •Require honest metric review
  3. •Create psychological safety to consider pivoting
  4. •Make a decision, commit either way

Framework 3: Build Values into Systems

Core Insight: "Don't treat culture as a poster on the wall. Build values into concrete systems - hiring rubrics, promotion criteria, decision-making frameworks. Actions, not words."

Words vs. Systems:

  • •

    Words: "We value innovation"

  • •

    System: "20% time for exploration, protected in policy"

  • •

    Words: "We're customer-focused"

  • •

    System: "Every PM spends 1 day/week with customers"

How to Operationalize Values:

  1. •State the value
  2. •What behaviors demonstrate it?
  3. •What systems would encourage those behaviors?
  4. •Build the systems, not just the value

Examples:

  • •Hiring: "How does this rubric test for our values?"
  • •Promotion: "What behaviors do we reward?"
  • •Meetings: "How do we make decisions?"

Laura Modi

Background: CEO of Bobbie (infant formula)

Framework 1: Slowth (Strategic Slowdown)

Core Insight: "Sometimes deliberately slowing growth preserves long-term success. Pull back on acquisition to fix unit economics and build infrastructure, even when investors want faster growth."

When to Slow:

  • •Unit economics are unsustainable
  • •Infrastructure can't support scale
  • •Quality is suffering
  • •Team is burning out

Why It's Hard:

  • •Investors want growth
  • •Competitors are moving
  • •Feels like losing
  • •Requires confidence

How to Execute:

  1. •Be honest about why you're slowing
  2. •Have a clear plan for what you're fixing
  3. •Set milestones for when to accelerate
  4. •Communicate with stakeholders

The Result:

  • •Sustainable economics
  • •Scalable infrastructure
  • •Healthier team
  • •Better position for real growth

Framework 2: Naivety as Asset

Core Insight: "Not knowing how hard something is enables you to attempt it. Laura's lack of experience in infant formula meant she wasn't scared off by complexity that would have deterred industry veterans."

Why Naivety Helps:

  • •Don't know what's "impossible"
  • •Question assumptions others accept
  • •Bring fresh perspective
  • •Willing to try unconventional approaches

The Balance:

  • •Naive about difficulty (good)
  • •Ignorant about domain (bad)
  • •Learn fast while staying bold

For Founders:

  1. •Don't research yourself out of trying
  2. •Question "industry best practices"
  3. •Ask "why not?" to limitations
  4. •Hire experts but filter their caution

Framework 3: Fake Deadlines Create Progress

Core Insight: "Create artificial urgency (launches, press announcements, investor meetings) to force decisions and ship product. Without deadlines, perfection becomes the enemy."

Why Deadlines Work:

  • •Force prioritization
  • •Create focus
  • •Prevent endless iteration
  • •Generate accountability

Types of Artificial Deadlines:

  • •Launch dates (announced)
  • •Press embargoes
  • •Investor updates
  • •Demo days
  • •Conference demos

Implementation:

  1. •Set a public deadline
  2. •Make it uncomfortable to miss
  3. •Scope to the deadline
  4. •Ship, learn, iterate

Jonathan Lowenhar

Background: Founder of Enjoy The Work, advises founders

Framework 1: Founder vs. CEO

Core Insight: "To be a founder is a state of being. To be a CEO is a craft. The more founders who can accept these are separate things, the better. Founder mode gets you started; CEO skills must be learned to scale."

Founder Mode:

  • •Vision and conviction
  • •Hustle and scrappiness
  • •Direct involvement in everything
  • •Gut-driven decisions

CEO Mode:

  • •Organizational design
  • •Hiring and management
  • •Process and scale
  • •Delegation and systems

The Transition:

  • •Founder mode works until ~20-30 people
  • •CEO skills become essential at scale
  • •Not a switch, a gradual shift
  • •Many founders resist this

Implementation:

  1. •Acknowledge the two are different
  2. •Assess your CEO skills honestly
  3. •Learn CEO skills intentionally
  4. •Get coaching/mentorship
  5. •Don't lose founder strengths, add CEO skills

Framework 2: The Magic Box (M&A)

Core Insight: "The best exits don't come from a for-sale sign. Find a champion at the acquiring company who sees the fantasy of what happens when they acquire you. You're seducing, not selling."

The Magic Box Concept:

  • •Acquirer sees a "magic box"
  • •Inside: their future with you
  • •Your job: help them see that future
  • •Make it irresistible

The Process:

  1. •Find a Champion: Someone senior who gets the vision
  2. •Paint the Fantasy: What happens when they acquire you?
  3. •Prove with Evidence: Small tests of the fantasy
  4. •Quantify the Value: Help them build the business case
  5. •Never Negotiate Live: Take it async with Corp Dev

Keys:

  • •Champion must want this personally
  • •Fantasy must be specific and compelling
  • •Evidence reduces risk perception
  • •They sell internally, you support

Framework 3: Hire for What You Need Done

Core Insight: "Start with: 12 months from now, this hire was a success - what changed? Then find people who have already done exactly that. Don't start with job descriptions."

Wrong Approach:

  • •Write job description
  • •List requirements
  • •Interview for skills
  • •Hope they can do the job

Right Approach:

  1. •Define success: What's different in 12 months?
  2. •What specific outcomes matter?
  3. •Who has achieved those outcomes before?
  4. •Find them and verify

The Question: "Tell me about a time you achieved [the specific outcome we need]."

Implementation:

  1. •Before writing JD, write success criteria
  2. •Be specific about outcomes
  3. •Source people who've done it
  4. •Interview for evidence of outcomes
  5. •Skip people who haven't done it (no matter how smart)

Ryan Hoover

Background: Founder of Product Hunt

Framework 1: The Decade Rule

Core Insight: "Successful companies often take 10+ years to build. Founders should only pursue ideas they're willing to work on for a decade. This filters superficial passion from genuine commitment."

The Test: "Would I work on this for 10 years even if it's going poorly?"

Why It Matters:

  • •Startups take longer than expected
  • •You'll want to quit many times
  • •Passion fades; commitment doesn't
  • •The 10-year test reveals true interest

Applying the Test:

  1. •Consider your current/potential idea
  2. •Imagine 10 years of struggle
  3. •Would you still choose this?
  4. •If not, reconsider

Framework 2: Launches Serve Multiple Purposes

Core Insight: "Don't just launch for user acquisition. Launches help with recruiting, fundraising, partnership opportunities, and market positioning. Think strategically about what you want from each launch."

Launch Benefits:

  • •Users (obviously)
  • •Press/coverage
  • •Recruiting attention
  • •Investor interest
  • •Partnership opportunities
  • •Market positioning

Strategic Launch Planning:

  1. •What do we need most right now?
  2. •How can this launch serve that?
  3. •Who do we want to reach?
  4. •What story do we tell?

Implementation:

  • •Pre-launch: Who needs to know?
  • •Launch: What's the hook?
  • •Post-launch: What's the follow-up?

Framework 3: Differentiation Over Competition

Core Insight: "Don't build a slightly better version of what exists. Find angles competitors can't or won't pursue. Product Hunt succeeded by celebrating makers, not just listing products."

Competing on Better:

  • •Incremental improvements
  • •Feature comparison
  • •Price wars
  • •Exhausting and often loses

Competing on Different:

  • •Unique positioning
  • •New angle on problem
  • •Competitors can't copy easily
  • •Creates defensibility

Finding Your Difference:

  1. •What do competitors take for granted?
  2. •What do they refuse to do?
  3. •What would they laugh at?
  4. •Can you build there?

Graham Weaver

Background: Stanford professor, private equity (Alpine Investors)

Framework 1: The Genie Framework

Core Insight: "Imagine a genie offers you the perfect life in every dimension. Write it down in detail. The gap between that and your current life is your roadmap for change."

The Exercise:

  1. •Imagine a genie appears
  2. •Offers you perfect life in: career, relationships, health, finances, etc.
  3. •Write it in vivid detail
  4. •Compare to current reality
  5. •The gap is your work

Why It Works:

  • •Forces specificity
  • •Reveals what you actually want
  • •Shows the gap clearly
  • •Creates motivation

Implementation:

  1. •Set aside 30 minutes
  2. •Write your "genie life" in detail
  3. •Be honest, not "realistic"
  4. •Compare to now
  5. •Identify biggest gaps
  6. •Start closing them

Framework 2: Autopilot is the Default

Core Insight: "Most people live on autopilot - safe, comfortable choices that maintain status quo. Real growth requires consciously choosing discomfort. The question isn't 'is this hard?' but 'is this worth it?'"

Autopilot Signs:

  • •Doing what's expected
  • •Avoiding difficult conversations
  • •Staying in comfort zone
  • •Making safe choices

Breaking Autopilot:

  1. •Notice when you're on autopilot
  2. •Ask: "What would I do if I weren't afraid?"
  3. •Consider the cost of autopilot
  4. •Choose consciously, not by default

The Cost of Autopilot:

  • •Life passes unlived
  • •Dreams stay dreams
  • •Regret accumulates
  • •Potential unrealized

Framework 3: Choose Your Suffering

Core Insight: "Life is suffering - this is Buddhism 101. The choice isn't between suffering and comfort; it's between suffering that leads somewhere meaningful and suffering that doesn't."

Two Types of Suffering:

  1. •Suffering toward something: Hard work toward a goal
  2. •Suffering from something: Regret, stagnation, unrealized potential

The Reframe:

  • •Pursuing your dream is hard
  • •Not pursuing it is also hard
  • •Which hard do you choose?

Application:

  1. •You will suffer either way
  2. •Choose suffering with meaning
  3. •Startup is hard → regret is also hard
  4. •At least startup suffering leads somewhere

Andy Johns

Background: Former growth leader (Facebook, Twitter, Quora)

Framework 1: Achievement Addiction

Core Insight: "High performers often use achievement as a coping mechanism for deeper wounds. The drive that creates success can destroy you if left unexamined."

The Pattern:

  • •Achievement feels good
  • •Masks underlying pain
  • •More achievement needed
  • •Eventually breaks down

Warning Signs:

  • •Never satisfied with wins
  • •Identity tied to achievement
  • •Burnout cycles
  • •Can't stop working

The Path Forward:

  1. •Recognize the pattern
  2. •Explore underlying drivers
  3. •Find healthier coping
  4. •Redefine success

Framework 2: The Body Keeps the Score

Core Insight: "Chronic stress manifests physically. Andy experienced severe health issues before acknowledging his mental health crisis. Your body will force you to stop if you don't choose to."

Physical Signs:

  • •Sleep problems
  • •Chronic fatigue
  • •Illness frequency
  • •Pain without cause

The Message:

  • •Body signals before mind acknowledges
  • •Ignore at your peril
  • •Eventually forces the issue
  • •Better to listen early

For Founders:

  1. •Monitor physical health
  2. •Don't dismiss symptoms
  3. •Health enables performance
  4. •Forced stop is worse than chosen rest

Framework 3: Four-Step Transformation

Core Insight: "Real transformation requires: (1) Suffering that forces change, (2) Truth-seeking through therapy/reflection, (3) Self-compassion to heal, (4) Compassion for others."

The Steps:

  1. •Suffering: Something breaks
  2. •Truth: Honest examination
  3. •Self-compassion: Kindness to self
  4. •Compassion: Extends to others

You Can't Skip Steps:

  • •Suffering creates openness
  • •Truth reveals what to heal
  • •Self-compassion enables healing
  • •Compassion completes it

Delivery Guidelines

When helping founders:

  1. •Acknowledge the Hard: Founding is genuinely difficult
  2. •Be Practical: Specific actions, not platitudes
  3. •Match to Stage: Pre-PMF vs scaling need different advice
  4. •Multiple Perspectives: Different frameworks for different situations
  5. •Attribution: Credit the expert and their experience