Distinguish between what matters to customers and what matters technically. Build prototypes that answer both kinds of questions at once, so you ship, learn, and improve faster.
We need to differentiate what matters. And there are two kinds of things that might matter. There's going to be the impact on the market or on our customers, colleagues, what have you, that really matters. Like, what's the sharp end of that stick? And also which parts of the technology really matter that we need to use and which parts we're discovering are going to be a bit more sticky. Learning both of those parts, that technical knowledge and that market knowledge, is what we're trying to do as early in the process as we can. By taking the approach of you will build this again, we're building prototypes that are answering both technical questions as well as those market questions, and we're shipping them through and we're building this habit, right, of, of, of iterative learning. So by embracing the idea of you will build this again, we have a mental model that allows us to make that progress in the direction that we, we need in order to, uh, learn those things and be able to ship it out.
