Don’t forget the “viable” part.

If you can't get anyone to use your MVP, it's probably not an MVP. Well, it's not the V; we're missing the V, which is viable. Like, basically, if it doesn't work for anyone, yeah, how hard to argue that it's viable? No, and like, shouldn't an MVP— it seems like the cool thing about an MVP is you can do things that don't scale and cheat. Like, you can make it; you can kind of will it to work for one person. Right?

So, the fact that it doesn't work for one person usually means that, like, you weren't even trying to make it work for them. Like, you were trying to do something else. This is something that comes up a lot when I'm reading applications or interviews for specifically developer tools. You ready?

Yeah, it'll be like, "Oh, cool, so I built this tool, and it helps you code, and you're way more efficient, and it's better, and it's, you know, we're building our MVP, and like, we're getting— we're we’re emailing people on LinkedIn now."

Yeah, what is the question I ask them, Michael? "Do you use it yourself?" Yes. I will say, "Great, so tell me about your usage of it," and they'll be like, "h..."