- Your development/engineering teams have been diverted for a number of months to migrate legacy/unsupported databases across the portfolio of products to new DBS.
- Your product is being migrated to a new CMS or other type of system.
- The platform is being rewritten from the ground up because the legacy technology is on its last legs.
Firstly realise that in all probability your product will be better off because of the technical work being carried out – especially if it’s going to empower your teams to do regular releases with minimal effort, therefore enabling you to create meaningful release plans, respond in a truly agile way to a rapidly changing market and to competitors who are much smaller, nimbler and don’t carry the overhead of a large company e.g. the checks and balances of Saranes-Oxley.
Secondly appreciate that the engineering and development teams would probably rather be developing and releasing features that are customer centric and data driven. That’s to say developers generally get job satisfaction in seeing the products they build being used and appreciated by users as opposed to implementing technology for technology sake.
Thirdly understand it’s a means to an end – it’s a case of replacing the land mine you’re sitting on with a gold mine that if rightly managed (identifying the right market opportunities, being customer led and data driven, collaborating with technology, UX to discover the right product blend…) will produce golden nuggets of user valued features for many releases to come.