How Early User Feedback Changed the Way We're Building Our SaaS
As developers, it's easy to think the next feature is what users need.
While building JustBlogged, we discovered that wasn't the most important question.
The better question became:
"What would actually make someone leave the product they already use?"
That shifted our conversations from collecting feature requests to understanding real user problems.
We've started focusing on:
- Reducing friction between writing and publishing.
- Simplifying the overall experience instead of adding complexity.
- Validating problems before building solutions.
One interesting lesson is that every feature has a hidden cost. Even if users never click it, they still need to recognize it, understand it, and decide whether it matters.
Keeping a product simple often requires saying "no" more than saying "yes."
We're still learning, but building in public has accelerated that learning more than any internal brainstorming session ever could.
I'm curious! What's the most valuable piece of user feedback you've received while building a product?
Top comments (0)