---
title: Fishing Pond Effect
synced_from_vault: true
vault_source: 03-living-docs/patterns/Fishing-Pond-Effect.md
public: true
type: pattern
tags:
  - pattern
  - validation
  - startup
  - user-research
origin: Show Notes CEO sessions (Feb 2026)
---

## Core Concept

Where you test matters as much as what you test. The same hypothesis can be invalidated in one community and confirmed in another. Don't treat invalidation as universal — always try 2-3 different community types before declaring a thesis dead.

## The Pattern

You ask the right questions to the wrong people and conclude the problem doesn't exist. The hypothesis isn't wrong — the fishing pond is. Your target user self-selects into specific communities that match their behavior and identity. General friend groups, family, and broad social circles are almost never the right place to validate a niche product thesis.

## Where I've Seen It

- **Show Notes (Feb 2026):** 0-for-12 on "podcast overwhelm" across friends, family, and Mega Maker Slack. But Rands Leadership Slack (~25k engineering leaders) produced 8+ organic overwhelm signals, multiple manual workarounds, and one person who literally built a manual version of the product. Same thesis, different pond, opposite result.
- **The key variable:** Mega Maker members are indie creators who *build* podcasts. Rands members are engineering leaders who *consume* them for professional development. The behavior pattern (subscribing to more than you can consume) existed in both — but the *pain* only existed where consumption was professional, not recreational.

## The Countermeasure

1. **Set a fishing-pond hypothesis BEFORE starting.** "Where do people who [behavior] hang out online?"
2. **Start with targeted communities immediately.** Skip friends/family for problem validation.
3. **Try at least 2-3 community types** before declaring a hypothesis dead.
4. **Search before asking.** In any new community, search its history for existing pain signals before starting outreach.

## Related Patterns

- [Validate-Before-Building](/patterns/validate-before-building) — Don't build until you've validated
- Manual-Workaround-Signal — When you find the right pond, look for workarounds
- Community-Engagement-Earned — Different ponds have different engagement rules

---

## Cross-References