Test fast with real users, not assumptions

We would have an idea in the morning, come up with some sort of functional prototype, recruit a bunch of people that are legitimately good prospective users, but have zero skin in the game, ship fast so people can start playing with it. In the afternoon, we're already running pretty full scale experiment. You start actually hearing other people describe their usage of the product. We can also watch them struggle. By the evening or by the next day. We can actually go through all of it together and say, okay, we're going back and we have to fix this. This is not usable and we've done that for everything.

You want to bring on cohorts of users and then see what's going on, then learn, and then bring on new cohorts of users. Going and doing 100 at-bats and then being like, 'Did it work or did it not?' We want to break it up and then constantly just be iterating.

MVP is simply for whatever the hypothesis is that we're trying to test, what is the most efficient way to get the validation we need about whether a hypothesis is true or not?

"This shift" and "the stakes" refer to Raskin's strategic narrative framework where companies identify an old game/new game market shift and its high-stakes consequences.

When we talk about this shift and the stakes and do they stick. Do they kind of say, 'Yeah, let me tell you how that's playing out for us,' or, 'Am I? Yes, I'm seeing that.'