We had an awesome team coffee and brunch meeting on Friday. In between drinks and food and chats we did some quick retro work on what do we need to do to create awesome products. It was great to see the team give a mix of different themes of work, all constructively communicated. Product activities Clear product and strategy Understand the market Talking to customers Not reinventing the wheel where we can Improving the team Better use of time Aligning dev team to understand our UX choices Multi teams working well together More inter department collaboration Building our soft skills Better relationship with sales Can do attitude Growth mindset
Every now and then we need to replatform a legacy product. The product has been a success, it has been evolving for years, and customers love it. But for a set of technical and business reasons it has limited growth potential. I have done this a few times, and I have also watched while others have had to put their favourite toys away for good while they build new toys. So I thought I would share my journey, and hope that we don’t repeat the same mistakes Rich Mironov has a great article about replatforming: ... This is an essential part of the software product business, but fraught with poor assumptions and lack of experience/understanding. And the majority of replatforming and reimplementation efforts I’ve seen have failed. https://www.mironov.com/replatforming Migration is necessary if you want to move forward, we can't stay on legacy tech forever. Customer's demand new features, even though they love the old features. They want a simple and shiny UI, but they are exper