Justin Lee

Since sharing Prodshort here on @producthunt , we ve received a lot of early feedback. Ideas, feature requests, small improvements, UX feedback sometimes things we didn t even think about.

How do you decide what to actually build from all that feedback?
Some feedback looks useful at first, but once you test it, you realize it adds complexity without real value. Other times, a small suggestion turns into something essential for the product.
Would love to hear from your experience:
How do you handle early feedback without going in too many directions?

Lately I ve been thinking about how hard it s become to choose well.

Almost every category now feels overcrowded agencies, SaaS tools, AI products, consultants, even simple productivity apps. On the surface, there are more options than ever. But instead of making decisions easier, that abundance often makes everything feel noisier and harder to evaluate.

We analyzed the codebases of 100 startups that hit a scalability wall (*)
The goal was not to find the most exotic bug. The goal was to find the most common, expensive, and preventable patterns of failure.

The results were almost identical across 85% of them. Here is what the data says.

The Timeline to Failure

Months 1 6: Everything worked. Fast releases. Happy customers. No time for architecture.