We've gone from talking about deciding on your MVP, I think, to talking about designing and testing it. Is there anything specific about the designing and testing that we need to draw out?

Oh, definitely. Yeah. So when we agree on the MVP feature set, it is words. We've brainstormed the feature and here's like the, here's the features we plan to do. This is where I like to use user stories at this point. Once we've got a high level roadmap, we might have a box that says load inventory. That's like two words. So part of that definition is then we define it with a set of user stories. And then the set of user stories, we identify which of those are in scope, route of scope. That's the defined part. So even when we write a bunch of stories, we even further define what's in scope and out of scope. Once we have that high level roadmap of what big rocks are in this MVP, and we have the set of user stories that are in scope, feature those big rocks on the roadmap, then we go to UX design. And that's where the designers will design what that user experience will be. And if we're given set of features, for a given set of user stories, you could have a million different UX designs. So that is definitely an important step to work through. And then the goal of that is to create something that's usable, obviously, and hopefully delightful. And to have an artifact to work out the design, because we have to tell the front end developers what to build, that we can then go and close the loop with customer. Because that's where again, the next real learning happens. We've had all this internal discussion about value prop and features. And then we create a prototype. And then we test that. And that's when the real learning happens, if people go, ah, that's not really so important. This is important. So there's definitely a specific UX design step. And then on the testing step, there is an art to that of running good user sessions, not asking leading questions, like if I show you the prototype and go, Hey, that was easy to use. Wasn't it, Marie? That's a leading question or closed ended questions. Did you like that feature? Yes or no? You may feel good if they say yes, but you didn't really learn anything. So you want to ask open ended questions like how did you like that? What did you think of that? You're going to go out more information in the book. I go into details on how to kind of categorize the feedback across functionality, user experience and messaging and how to like pattern match and decide what you need to change. Because again, the first prototype, there's going to be things you have to change and iterate. And so we want to pattern match the top to small batches, like five to eight customers at a time with the prototype, stop pattern match the top feedback, go back to the hypothesized design test, learn loop revise our hypotheses, tweak the prototype and go back with a fresh batch of five to eight and rinse and repeat until you get to the point where there's no major concerns or questions that are coming up. And I've done this dozens of times. Your first prototype is going to have a lot of rough edges and then doing this process, you're going to smooth out those rough edges, iterate it. And then you get to the point where the problems or concerns of people bringing up and previous rounds of iteration are no longer coming up because you've adequately solved them. And then people start going, wow, this is actually pretty useful. I could use it. Then you can confidently proceed to building it at that point. And sometimes you have to pivot. Hopefully you can iterate your way to good product market fit, but sometimes you have to pivot and a pivot basically means you're changing one of those key assumptions, key hypotheses from the pyramid. You're changing what your value props all about. You're changing which need your trying to solve or you're changing the target customer that you're going after. And further down the pyramid, you have to pivot the more it disrupts everything that you've done. But pivots happen all the time. You just got to get out there with the prototype. And the longer I do this, I feel like if you do this well, if you use your prototype and you listen to what customers tell you, they will direct you, they will pull you in the direction of creating more customer value in higher product market

fit.