Has your community ever completely changed what you built? Ours did. Three times.
I want to talk about something that doesn’t get discussed enough in product development: what happens when you actually listen to your community instead of your roadmap.
When we launched v1 of Second Brain here on Product Hunt, we had a plan. Then the comments came in. People told us newer isn’t always more correct. That conflicting memories needed an authority model. That compression should preserve the through-line.
We threw the roadmap out and built what they asked for. That became v2.
Then v2 launched. Comments came in again. People told us the terminal was scary. Git was a barrier. They wanted to use the product but couldn’t get past the setup.
So we built the no-code path. That became the desktop app launching this Saturday.
Three launches. Three times the community told us what to build. Three times we listened.
Has this ever happened to you? Did community feedback completely change your direction? I’d love to hear how others are navigating the balance between their vision and what their community actually needs.
Replies
Really appreciate you writing this up, Rahil — most "we listened to our community" posts stay vague, and you actually named the three things that flipped (an authority model for conflicting memories, terminal-is-scary, git-as-a-barrier). That specificity is the useful part.
What your three pivots have in common, reading them: none were preference — each was the community surfacing a truth about the problem you couldn't see from inside. "Newer isn't always more correct" is a correctness truth; "the terminal is scary" is an adoption truth. That feels like the real filter — the feedback worth throwing the roadmap out for points at the problem, not at one loud user's workflow.
I hit a version of this building merchant integrations: you design a clean abstraction and the moment it meets what a specific partner actually does, it's wrong. I've mostly stopped fighting that and started building abstractions to be cheap to throw away, because I know I will. Your "three times we rebuilt" reads like the same muscle.
Curious how you tell the two apart in the moment though — when the comments land, what's your tell that a piece of feedback is a real constraint vs. just the loudest corner of the room? 🙏
Second Brain for AI
@akbar_b The tell for me is whether the feedback points at the problem or at a preference. “The terminal is scary” isn’t someone asking for a feature. It’s someone telling you they can’t get in the door. That’s a constraint. “I wish the UI was darker” is a preference. The constraint ones tend to come from multiple people using completely different words to describe the same wall. When three people who don’t know each other all hit the same ceiling, that’s the filter. Your abstraction point is the same thing. The partner isn’t being difficult. They’re surfacing a real structural mismatch your clean model didn’t account for.
@rahilpirani That's a clean filter, and I like that it's about independence of framing, not volume of requests. The thing I'd worry about applying it, though: 'three people who don't know each other' can quietly become one person's complaint getting relayed through a shared Discord or a vocal power user's thread, so it looks like independent multiplicity when it's really one signal echoing. Do you have a way to check that the three are actually unconnected — different contexts, different use cases — before you treat it as a structural wall rather than a loud corner? Really appreciate how concretely you're willing to walk through this 🙏
three times is the pattern. what nobody talks about is the filter you develop for which comments to actually listen to. early on you listen to all of them and half the pivots are wrong. after a while you start hearing the difference between 'i want this' and 'the thing you built already assumed something i dont share.' the second kind is the pivot. the first is a feature request. 'newer isnt always more correct' from your v1 comments sounds like the second kind. thats why v2 stuck and v1 didnt.
Second Brain for AI
@thenameisarian That filter took me an embarrassingly long time to develop. Early on I’d see ten comments asking for the same feature and think that was signal. Turns out volume is the worst indicator. The one comment that stops you cold because you realize you designed around something that isn’t true, that’s the one. And those rarely come with upvotes because most people don’t even recognize what they’re pointing at.