Re:A Methodology for Retiring Products
by cheez on Friday April 22, 2016 @07:30PM
(#11553275)
Here's my strategy, which seems to work. Build product A to the point where it can run on its own with a skeleton support team.
Build product B such as if it is a completely new product. Incentivize people to move from A to B. Don't bitch if they don't. They'll keep paying you and won't cost you much to support.
If the domain changes such that it requires drastic changes to product A, then you didn't do step 1 properly.
It's working so far for the product I have now. The biggest complaint is "Hey, I hate the way you did X, I want the other one back." "OK, here you go: <url>".
They keep paying.
I don't understand it. The new one is awesome. Ah well.
Build product B such as if it is a completely new product. Incentivize people to move from A to B. Don't bitch if they don't. They'll keep paying you and won't cost you much to support.
If the domain changes such that it requires drastic changes to product A, then you didn't do step 1 properly.
It's working so far for the product I have now. The biggest complaint is "Hey, I hate the way you did X, I want the other one back." "OK, here you go: <url>".
They keep paying.
I don't understand it. The new one is awesome. Ah well.