Should the product be opinionated, or flexible enough for everyone?
I keep getting feature requests from people who want to use the product in a way I never intended. Not better versions of what it does — completely different jobs. They want it to be more configurable, more customizable, more "just give me the building blocks and I'll figure it out."
Part of me wants to say yes to all of it. Flexibility widens the market, makes the product valuable to more people, and means I never have to turn a customer away. The more it can do, the harder it is to outgrow.
But the other part of me knows that "flexible" is how products die. Every setting is a decision the user now has to make. Every option is a way to configure it wrong. And the moment I make it do everything, it stops being great at anything — it becomes a toolkit instead of a solution, and nobody recommends a toolkit to a friend.
The most loved products I use are the ones that made decisions for me. They said "this is how it works" and I either accepted it or left. And I loved them precisely because they refused to hedge.
Do you build the opinionated product or the flexible one? And if you chose opinionated, how do you handle all the people who want it to be something else?
Replies
For me it's somewhere in between. I listen to what customers ask for, then decide based on whether other customers would need it too. It's hard at first, but I think you get used to making that call.