…oo much criticism from too many people (which, according to #2, means your design is not yet good). This is either because a) you’re working under too many constraints b) you’re not exploring solutions broadly enough, or c) the problem is beyond your current skill level.
…A artifacts. I won’t go as far as to call it bullshit, but it’s not the way to succeed in software. Understand the vision, find a problem worth solving to achieve it, build a hypothesis to solve it, and then validate it as quickly as you can with real customers. Rinse and repeat.