5 Large-Scale Feature Rollout & Redesign Strategies

Very often in a startup’s journey or even in enterprise software, you have to launch an MVP and prove the market, marketing, and pricing first. Time to market is important. So, you flintstone something into production.

It works, and it looks great! Congratulations.

Now the hard work begins, you have to fundamentally change the way the product or service is built and/or add large-scale features that are not compatible with the current design or addition of complementary features that won’t impact original features but need to co-exist side-by-side.

Photo by Waldemar Brandt on Unsplash

I am not referring to Application Refactoring — This is not that.

I am not referring to Martin Fowler, Kent Beck, or Robert Martin’s seminal topics of Clean Code, Refactoring, and Enterprise Architecture Patterns.

Yes, you follow them as much as you can, and I refer to some below, and sometimes the frameworks we use dictate them (MVC, MVVM, Hexagonal, Viper, etc.,).

I am not referring to Blue/Green, Canary, or other deployment models.

I am not also referring to Technical Debt, which by the way, I think is at a healthy level a good thing. Some engineering managers obsess with Technical debt from V1, which I think they…