Do you think founders should talk more openly about projects that didn’t work?
We often see launch posts, milestones, and success stories.
What we don’t see as much are honest breakdowns of products that quietly stalled or failed.
I feel there’s a lot of learning hidden there about timing, assumptions, and trade-offs.
Do you think sharing failed projects helps the ecosystem, or does it mostly benefit the person sharing?
83 views
Replies
I think it can go two ways and it is all in the recipients mindset at the time.
Fear or failure increases or feels like this might not be good to pursue because person A failed trying to do something similar.
Increased belief in that the ones that succeed are not that different from "stupid me" , the difference is that they have tried, failed, learned and tried again. So i nee to be brqve enough to try, and smart enough to learn a long the way.
I've really benefited from reading entrepreneurs autobiographies and listening to podcasts where failures are discussed, because it takes away the gloria from the "succesful people" and makes them normal, and doing the same thing is possible.
Product Hunt Wrapped 2025
@markus_kask Exactly this. It really depends on where the reader is mentally. For some, failure stories trigger fear and hesitation. For others, they do the opposite. They normalize the journey and make success feel attainable, not reserved for some special group.
That’s why I think they matter. They strip away the myth, reduce the pedestal effect, and show that most “successful” founders are just people who tried, failed, learned, and kept going. For me too, biographies and honest podcasts were huge. They turned success from something distant into something possible.
@alexcloudstar If you havent read richard bransons book, i highly recommend it! Like a virgin i think its called, after reading it i got the courage to start my first company and he's just a cool guy. Got any tips for me?
Product Hunt Wrapped 2025
@kilpatrick Totally agree. It really is a win-win. For the audience, failure retrospectives are often more practical and grounding than polished success stories. They show the real sequence behind success, including the forgotten attempts that came first.
For the founder, sharing those stories builds relatability and trust. People don’t just follow outcomes, they follow people. And when you’re honest about what didn’t work, many will stick around because they want to see what you build next.
I think founders should talk more about what didn't work. When I read failure stories, I learn faster than from success posts. It helps me avoid repeating the same mistakes. It benefits the ecosystem but honestly, it also helps me reflect better.
Product Hunt Wrapped 2025
@chaity_okpalanozie I agree. Failure stories compress learning in a way success posts rarely do. They expose the assumptions, timing issues, and trade-offs that usually get hidden behind polished wins. Sharing them helps others avoid repeating the same mistakes, but it also forces the founder to reflect more honestly. That reflection alone makes it worth sharing.
From my experience, talking about failures builds trust. I connect more with founders who are honest than those who only post wins. It benefits the person sharing by creating clarity but it also helps others make better decisions.
Product Hunt Wrapped 2025
@sulemna_ola Absolutely. Honesty creates signal. When founders talk openly about what didn’t work, it builds credibility and real trust. Wins inspire, but transparency connects. And you’re right, it’s a two-way benefit. Sharing failures brings clarity for the founder and better context for everyone else making decisions.
honest failure breakdowns are way more actionable than generic success advice.
Product Hunt Wrapped 2025
@greg_mason1 Completely agree. Failure breakdowns give you context, constraints, and real trade-offs. Success advice often skips the messy parts that actually matter. If you want actionable learning, the misses usually teach more than the wins.
Curatora
@alexcloudstar I think it helps both, but the ecosystem benefits more.
When founders share what didn’t work, it turns vague advice into concrete lessons about timing, assumptions, and trade-offs. It also normalizes the messy middle, which most people are actually in.
Our journey with Curatora has had plenty of quiet dead ends that taught us more than any small win. Those lessons shape better decisions the next time. Sharing them makes the path feel more real and a little less lonely.
Product Hunt Wrapped 2025
@imtiyazmohammed Well said. That’s exactly it. Failure stories turn abstract advice into real lessons about timing, assumptions, and trade-offs. They also reflect where most founders actually are, in the messy middle, not the highlight reel.
Quiet dead ends rarely get shared, yet they shape judgment far more than small wins. Talking about them makes the journey feel grounded and human, and reminds people they’re not alone in it.
yea whenever i try to do something new right , i always see who got success so that i could know what i could do !
but if i can see what's failed , i would have known what to avoid
Product Hunt Wrapped 2025
@mushabuilds That’s such a real point. Looking at success shows what might work, but looking at failures shows what to avoid. Both matter, but failure stories save you from repeating the same mistakes. They give you boundaries, not just inspiration.
For me, some of my failed projects were due to lack of marketing skills. I'm a lousy promoter. If sharing a failed project got someone to perk up and say "whoa, you just need some awareness and I can help." it might save a failed project and create revenue for more people.
Product Hunt Wrapped 2025
@tinyorgtech That’s a great point. A lot of projects don’t fail because the product is bad, but because awareness never catches up. Sharing those failures creates surface area for help. Someone with marketing skills might spot the gap immediately. In that sense, openness can literally turn a dead end into collaboration and revenue, not just learning.
@alexcloudstar exactly. That's why I haven't abandoned my Sapling project. I believe it's a good tool but I have zero marketing skills so my hope is that patience pays off and I keep adding features. And, it's a great project for maximizing my agentic coding shift.