A short transcript of a talk advocating for accelerating product development by favoring smaller, faster cycles (e.g., weeks instead of months) and using MVPs to learn and deliver impact sooner. The speaker acknowledges both the benefits of increased speed and the responsibility and risks that come with it.
From idea to launch in a much faster way. Does that mean we need to pare down our idea? You know, does that mean we need to try things more? Do we need, does that mean we need to try more things? And so a lot of our work tends to focus on, you know, this idea that is particularly popular in tech, which is the idea of an mvp, a minimum viable product. We try to focus a lot of our work on that. Rather than spending six months to do a thing, is there a way that we could spend six weeks to do a thing? Because maybe it'll be cheaper that way, maybe it'll be faster, maybe we'll learn things more that way. And so that probably is one of my biggest frustrations in tech and in design is that the speed of which we can have impact is too slow right now. And I think that's gotten faster over time. I would like it to go even faster. And I know that that will be, you know, with great power comes great responsibility. I know that will be a wielded in the wrong hands, that will be just as bad as it can be good. But I like to, I hope to look at the glass half full version of that to go. Maybe we can deploy systems and solutions that help people faster.
