Hey everyone. I have been thinking a lot about the product life cycle lately, especially how it applies to the internal tools and enterprise apps we deploy. We always hear about pushing software to stay in the growth or maturity stages forever. But is there a point where fighting market saturation actually hurts you?
I am looking at one of our legacy deployment apps. It is definitely past its golden phase and heavily entrenched in the saturation stage. Management wants to keep bolting on new features to force a new growth phase. Honestly, I feel like we are just creating bloatware at this point.
When is it strategically smarter to just let a product enter the decline phase gracefully, strip back the budget, and funnel that cash into the development stage of an entirely new project? Have any of you successfully pitched a sunset strategy to a growth obsessed leadership team?
12 Views
