... this point And that's the thing most people miss: the roast is the value. A good designer doesn't just tell you what looks bad, they surface assumptions you didn't even know you were making. Half the time it's not "your button color is wrong" it's "why does this step even exist?" Those questions are worth gold. Comment from Burak Urhan(@burakurhan): I shipped my first product with zero design thinking and paid the price ... ... some extent, affordable, but you still don't know what you don't know. Comment from Borja DR(@borja_diazroig): I m somewhere in the middle. While building Uxia, I ve changed my mind on this a few times

... idea of using impact instead of reversibility as the approval trigger. That feels much closer to how people actually think about risk. Comment from Aria(@ariajinling): I agree: degradation has to be an explicit, author-authored alternative, not a timeout-time

... then iterate over Comment from Neil Shah(@xshahneil): I always prefer the default time on Product Hunt to schedule, because it is so random and i never understand how planning an appropriate time

... with your point on pitching too, once the problem is named clearly, everything after that (to buyers, other makers, whoever) gets so much easier to explain. Comment from Tom Brothers(@tom_brothers): I have to use terminals from time to time

... hypothesis by the time we started building, it was already established. The app is really just the natural next step, taking what we'd already validated in one salon and making it available to anyone, anywhere. Appreciate you taking the time

... only that agent writes to. sounds basic but the key part was making the notification say WHY it's waiting (needs approval vs finished vs