Suggest edit — over-planning-trap

Title

Name

Note

---
visibility: public-edit
---

# the over-planning trap

## what happened

full PRD, competitive analysis, design spec, technical doc, launch plan, pitch video... never shipped. four name changes. the project went through Nosce -> OnCue -> Axon -> Tellwell, each rename accompanied by another round of planning documents. all the planning in the world, zero users.

## why it's a gotcha

planning feels like progress. writing a PRD feels productive. doing competitive analysis feels like due diligence. but it's all pre-work for the real work, and the real work never starts because there's always one more thing to plan. each rename is a reset that restarts the planning cycle. you end up with a beautiful Google Drive folder and no product.

## the fix

ship something small first, then plan. build the core feature in a weekend. put it in front of one person. get a reaction. then decide if it's worth planning around. the plan should follow the prototype, not precede it. if you've renamed your project more than once before launching, that's a red flag. this is the planning-stage version of [[perfectionism-over-hackathon-fit|perfectionism]] and the mirror of [[building-before-validating|building before validating]] — planning without validation is just daydreaming. at execution level, it becomes the [[just-one-more-feature-loop]], and at team level, it becomes the [[relay-build-fallacy|relay-build fallacy]] — over-coordinating instead of building. don't [[optimizing-for-scale-too-early|build infrastructure]] before building product.