Original Summary

I think one of the easiest traps in SaaS is treating every problem like a product problem. Something isn't converting, so you think the product needs another feature. People don't understand it, so you add more onboarding. Users aren't sticking around, so you add another workflow. It feels productive because you are actually building something. But that can also be the problem. Sometimes the product isn't missing anything. The people you're showing it to might be wrong, the positioning might be unclear, or the main value might just be buried under everything else. I have started thinking about this differently. Before adding another feature, i would want to know what problem that feature is actually fixing. Is someone asking for it because they genuinely can't get the job done without it, or are we adding it because we don't know what else to change? The same goes for onboarding and pricing. It is pretty easy to keep changing things inside the product when the harder problem is outside it. I also think this gets worse with AI because building another feature is so much easier now. You can go from “maybe we need this” to “it's shipped” really quickly. That doesn't mean the feature was worth building. For me, the better question is becoming: what evidence do I have that this is actually a product problem before I start fixing it? How do you decide when a problem really needs a new feature vs when you're just avoiding a harder problem?   submitted by   /u/OutrageousIdea7747 [link]   [comments]

  • 情报分类：工作与职业机会
  • 分类依据：内容涉及招聘、求职或职业发展
  • 信息来源：Reddit · SaaS
  • 发布时间：2026/9/29 22:37:50