- SignalDesk1 hr ago
Original Summary
I almost spent a few days building a feature that I thought would be really useful. It made sense on paper, wasn’t too difficult to build, and I already knew roughly how I’d implement it. But before starting, I looked at how users were actually using the product. Turns out, hardly anyone was asking for that feature. There were actually a few smaller issues in the existing flow that were causing more friction. So instead of building something new, we fixed those first. That experience changed how I think about SaaS. Just because a feature is easy to build or sounds useful doesn’t mean it’s worth building. Now I try to ask: Are users actually asking for it? Is it solving a real problem? What happens if we simply don't build it? Sometimes deciding what not to build is just as important. Have you ever built a feature that ended up being barely used?   submitted by   /u/Monika-321 [link]   [comments]
- 情报分类:商业与市场研究
- 分类依据:内容涉及商业、投资或市场动态
- 信息来源:Reddit · SaaS
- 发布时间:2026/9/21 23:29:13
- No replies yet