Continuous Improvement has long been encouraged in software development practices. It’s been used to solve engineering problems faster and focus work around learning. But what if we took the same processes that have made development so strong and applied them to Product Management?
During product discovery, we usually rush through the designing, speccing, and building processes without stopping to analyze if this particular idea is the right move for our products. Many Product Management roadmaps and processes don’t even include time to look at existing products and improve them. If we only do Continuous Improvement on the development side, we only solve half of the problem. We end up creating really fast and efficient processes to develop products that users end up hating.
If we only do Continuous Improvement on the development side, we only solve half of the problem
Melissa Perri talked about how your team can use Continuous Improvement techniques in product discovery and iteration to create products that achieve business goals and satisfy user needs. We explored how Toyota Kata can be used during product discovery to reach business goals. We also looked at how Kaizen in the whole product development team helps bring about a culture of collaboration, experimentation, and metric oriented results.