Are you building features or killing features (i.e. simplifying your products)?
Just yesterday I prevented my team from adding an exotic feature to our product.
My hypothesis is that people don't like many features in a product as that complicates the product adoption e.g. many sales guys hate CRMs for this reason. In that sense, more features might equate to no features as users don't adopt/use the product. So, minimalistic products that solve 1 big problem (80% of the problem pie) is what people like.
That's what I think.
I would like to hear from the product hunt community on what their experiences have been?
88 views
Replies
Kalyxa
Totally agree — feature bloat kills usability. We’ve started thinking of new features as liabilities unless they solve a clear pain point users already feel. Every added feature adds complexity, support burden, and onboarding friction. Simplicity scales. Depth > breadth.
I've been on both sides. I had a better experience when our team started simple and then added a new feature every 4-6 weeks. In fact, one project I was on died because we spent too much time in development hell trying to add new features that sounded cool in theory but weren't validated.
The 100 Challenge (asking 100 random people a few questions gauging their interest) is a great way to determine whether a new feature truly helps to solve our overall problem fit.
Once I read in one of the @johnrushx posts on Twitter that makers should focus on one feature (simplifying the product).
Hard to say. I mean – from the very beginning, the solution is more understandable, easier for UX/UI.
But as you gain more users, they require more complex solutions.
And you can see this pattern in many products/companies.
Virgin started as a recording company/media – now, they have over a hundred subbrands and products (airlines, insurance).
Amazon started as a bookshop, then they evolved into an e-shop, streaming, etc.
Starting "skimmed" and then growing into something bigger is a part of evolution.
Right now, we're in build mode but fully locked into the features that we set for the MVP. Luckily, I have great co-founders who call out my tendencies for scope creep.
There are a lot of cool ideas in theory, but if it doesn't move the needle with our customers it doesn't matter.
I constantly fight with myself to not add new features and keep improving and focusing on the main value feature. I think it is super important to stay focused on one or two things/features even if you think that other/additional stuff can be potentially useful.
Pokecut
It’s tempting to think that adding more shiny bells and whistles will make a product irresistible, but often it just overwhelms users—especially when those extras don’t solve their core problem.
Pokecut
Totally agree with you! 🎯 Keeping a product simple and focused often leads to better adoption and happier users. I've seen firsthand how feature bloat can overwhelm users, especially in tools like CRMs where complexity kills productivity. 🚫📊
Focusing on solving the core problem really allows users to experience value quickly without getting lost in unnecessary options. Minimalism doesn’t mean lack of functionality—it means intentional design that prioritizes what truly matters. 💡✨
Curious to hear how others balance adding new features vs. keeping the product lean! 🤔🔥
Pokecut
Hi Manu,
I completely agree with your perspective. In my experience, adding too many features often leads to feature bloat, which overwhelms users and complicates the user experience. It’s tempting to keep building “just one more” feature, but that can dilute the product’s core value.
Focusing on solving one big problem really well not only simplifies adoption but also helps build a loyal user base who truly see the product as indispensable. Sometimes, saying “no” to new features is the hardest but smartest decision a product team can make.
Would love to hear how others balance feature expansion with simplicity!
We are completely minimalistic in our approach (1-mega problem solved at a time) right now. But after reading all the views from everyone, I am looking to create an internal 'Feature Repellent' process for future wherein the effort would be to prevent or repel a feature than support it. Will also share it here with the community - let me know if anyone would be interested.