Thank you for sharing this insight! I feel like this iterative, light-on-your-feet approach is crucial to prove a product can work. I would double down on keeping the team engaged and sharing the WHY. I have been through an experience where the reasoning behind project investments weren't clear. Turns out they were also quite misplaced so the team ended up working on a project that eventually (inevitably) died.
The most difficult challenge is delivering quickly while avoiding accumulating an ever-growing amount of tech-debt. I don't think there's a perfect solution but it's important to weight this as part of keeping the development agile. It was good to call out the quality doesn't need to suffer to deliver quickly.
Thank you for sharing this insight! I feel like this iterative, light-on-your-feet approach is crucial to prove a product can work. I would double down on keeping the team engaged and sharing the WHY. I have been through an experience where the reasoning behind project investments weren't clear. Turns out they were also quite misplaced so the team ended up working on a project that eventually (inevitably) died.
The most difficult challenge is delivering quickly while avoiding accumulating an ever-growing amount of tech-debt. I don't think there's a perfect solution but it's important to weight this as part of keeping the development agile. It was good to call out the quality doesn't need to suffer to deliver quickly.