Under what circumstances would you decide to shut down a product?

Question

1. Negative feedback from investors or other key stakeholders.
2. Consistent negative feedback from users.
3. Normal user feedback, but poor usage data.
4. Not making money for a prolonged period with no clear path to improvement

Business Marketing with Nika · Accepted Answer

I agree with @hyoji – when you invest too much time somewhere without any profitable results, it is time to move on.

At least, you have an experience but you can invest your time and money maybe into something better.

I also shut down some projects and after doing that, I felt more "free" – I felt like I should do it sooner.

hyoj · Answer

I think number 4 resonates with me the most. I think it's a huge sense of disappointment when you haven't been chosen by consumers for a very long time.

Answer

Typically, endings are due to reasons other than the project itself, like better opportunities or feeling drained, much like in a relationship.

Yahya Rogers · Answer

If the product isn't solving  the problem it was intended to, and pivoting doesn’t seem like an option, I’d consider shutting it down.

Zhiqi Shi · Answer

@yahya_rogers Need to judge for yourself, and that's the tough part

Zhiqi Shi · Answer

@hyoji @busmark_w_nika haha, profit is always the ultimate measure of whether something is truly useful.

Felix Sattler · Answer

It’s definitely a tough decision. While I understand why people lean towards option 4, I can’t help but think it might stem from a lack of a solid sales process or a sales-driven marketing approach.

For me, not making money wouldn’t necessarily be the reason to shut down a product. Instead, I’d focus on whether there’s a genuine product-market fit and if the product truly solves a problem for users. If neither is the case, that’s when I’d start planning an exit.

Sharon Owens · Answer

If the market is oversaturated  and the product can’t stand out, I’d think about closing it down.

Moaz Ahmad · Answer

For me, none of these would matter as negative feedback is part of the process but not working on improving is what's make a difference in whatever I would shut down the project or not.

Zhiqi Shi · Answer

@hyoji Yes, that's need to judge for yourself

Aarav Krishna · Answer

I’d shut it down if there’s consistent feedback that users don’t find value in it, even after multiple iterations.

Zhiqi Shi · Answer

@felix_sattler PMF is always the most important

Answer

Shutting usually comes down to opportunity cost. If the time, money, and effort you're putting into a product could yield better returns elsewhere, it's time to cut your losses.

Zhiqi Shi · Answer

@liulixin agree with it

Answer

When team morale drops significantly and burnout becomes an issue, I'd take a hard look at whether continuing is worth it.

Under what circumstances would you decide to shut down a product?

Replies