samuelcastro/startup-skills / idea-validation
idea-validation
VerifiedGuide founders through validating startup ideas before building. Use when a founder says "I have an idea", "help me validate", "is this a good idea", "should I build this", "customer discovery", or asks about product-market fit, market sizing, or customer interviews. Covers problem discovery, customer interviews, market validation, and go/no-go decisions.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 5.3 KB |
| references/case-studies.md | markdown | 10.6 KB |
| references/frameworks.md | markdown | 4.9 KB |
| references/interview-guide.md | markdown | 5.7 KB |
| references/traps.md | markdown | 6.4 KB |
references/traps.md
View on GitHub# Seven Deadly Traps in Idea Validation
Common mistakes that kill startups before they start. From Todd Jackson's research.
## Trap 1: Asking the Wrong Questions
### The Problem
Humans don't see themselves clearly and are bad at predicting future behavior. Asking hypothetical questions gets you hypothetical answers.
### Detection
You're falling into this trap if you're asking:
- "Would you use this?"
- "Would you pay for this?"
- "Is this a good idea?"
- "What features would you want?"
### Solution
Ask about **past and current behavior**, not future predictions:
- "How have you tried to solve this before?"
- "What did you do the last time this happened?"
- "What are you using now?"
- "How much did you pay?"
**Key insight**: If someone tells you they've never looked for a solution, chances are you won't be selling them one.
**Resource**: Read "The Mom Test" by Rob Fitzpatrick
---
## Trap 2: Settling for "Meh"
### The Problem
People are generally nice. If you ask them about your product, they'll say "Sure, yeah, I'd check it out." This is not validation.
### Detection
You're falling into this trap if you hear:
- "That's interesting"
- "I could see how that might be useful"
- "Yeah, that's kind of annoying I guess"
- "Cool idea!"
### Solution
Don't settle for lukewarm. Look for:
- Product being "pulled out of your hands"
- People asking when they can use it
- Emotional reactions (sighing, frustration, relief)
- Unsolicited referrals
**Cocoon example**: When exploring financial planning, reactions were lukewarm. When they hit parental leave, people pounced on the topic.
**Rule**: Anything short of "I want this!" is really "No thanks."
---
## Trap 3: Not Enough Conversations
### The Problem
You can't find patterns in 3-5 conversations. You need volume to separate signal from noise.
### Detection
You're falling into this trap if:
- You've talked to fewer than 20 people
- You're drawing conclusions from 5 interviews
- Everyone you've talked to is a friend
- You stopped when you heard what you wanted
### Solution
| Type | Minimum Conversations |
|------|----------------------|
| B2C with uniform behavior | ~20 interviews |
| B2B with varied buying patterns | 50+ interviews |
| Marketplaces | 20+ on EACH side |
**Rule**: Keep starting new conversations until clear patterns emerge. Don't stop when you get good feedback—stop when you stop learning new things.
**Good Dog example**: 20+ dog owner interviews before they were confident.
**Cocoon example**: Talked to well over 50 people in early research phase.
---
## Trap 4: Selling a Vitamin, Not a Painkiller
### The Problem
Vitamins are "nice to have"—you'll take them if convenient. Painkillers are "need to have"—you'll go out of your way to get aspirin for a headache.
### Detection
Your idea is a vitamin if:
- People say "that would be nice" but take no action
- No one has an elaborate workaround for the problem
- The problem is mild inconvenience, not burning pain
- People aren't actively searching for solutions
### Solution
Look for "hair on fire" problems:
- People have tried multiple solutions
- They've spent significant time/money
- They complain about it unprompted
- They'll try almost anything to solve it
**Examples**:
- Painkillers: UberX, Google search, Mailchimp
- Vitamins: Google Glass, Crystal Pepsi, CNN+
---
## Trap 5: Ignoring Distribution (Myopia in Focus)
### The Problem
Focusing only on the product and ignoring how you'll reach customers.
### Detection
You're falling into this trap if:
- You've never thought about customer acquisition
- Your answer to "how will you get customers?" is "it'll spread virally"
- You have no hypotheses for go-to-market
- You're only thinking about features
### Solution
You don't need a full GTM strategy on day 1, but you need **smart hypotheses** for how you'll find and win customers:
- What communities will love this?
- How would a user describe it to a friend?
- What's your unfair distribution advantage?
- Can you leverage content/SEO? (LaunchDarkly did this)
- Do you have a built-in network? (Edith used engineering buddies)
---
## Trap 6: Pivoting Too Early
### The Problem
Giving up on an idea before you've really tested it. Getting discouraged by early friction.
### Detection
You're falling into this trap if:
- You've explored the idea for less than 1-2 months
- You've had fewer than 20 meaningful conversations
- You changed direction after one or two rejections
- You're chasing a "new shiny" idea
### Solution
Give ideas proper time and effort:
- Minimum 1-2 months of deep exploration
- Up to a year to bring to market
- Multiple angles and approaches
- Different customer segments
**LaunchDarkly example**: First 8 months, only 1 paying customer per month. "Those days were pretty depressing." They kept going and became a $3B company.
---
## Trap 7: Pivoting Too Late
### The Problem
Spending too long on an idea that's clearly not working. Sunk cost fallacy.
### Detection
You're falling into this trap if:
- Lukewarm reactions after 20+ interviews
- You have to "convince" people the problem exists
- Multiple pivots with same core idea, none gaining traction
- You're out of money or sanity
- No one seems to want what you're building
### Solution
Be willing to kill ideas:
- Set clear validation criteria upfront (Failory framework)
- Define what "success" looks like before you start
- Have a deadline for key milestones
- Trust the data over your emotions
---
## The Gray Zone
**How do you know if it's too early or too late to pivot?**
Unfortunately, no magic formula.
**Too early** if:
- You truly believe you've found a real pain point
- You just can't nail product execution or GTM yet
- You haven't exhausted different angles
**Too late** if:
- You're out of money or sanity
- No one seems to want what you're building after multiple tries
- You can't articulate why THIS approach will be different
**Everything in between is a gray area.**
---
## Trap Detection Checklist
Run through this after validation work:
| Trap | Check |
|------|-------|
| Wrong questions | Am I asking about past behavior, not hypotheticals? |
| Settling for meh | Am I seeing genuine pull, not just politeness? |
| Not enough conversations | Have I talked to 20+ people (50+ for B2B)? |
| Vitamin not painkiller | Are people actively trying to solve this? |
| Ignoring distribution | Do I have a hypothesis for reaching customers? |
| Pivoting too early | Have I spent 1-2+ months and 20+ conversations? |
| Pivoting too late | Am I ignoring clear negative signals? |
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |