+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.