Skip to main content
Loading video...

You Need an MVP Right Now

Transcript 6:44

Hey gamers, this is Liz Davidson from Beyond Solitaire, and today I want to talk about maybe the most important lesson I learned as a game designer, uh and that is to get to an MVP as quickly as possible. So, what is an MVP? An MVP is a minimum viable product. Doesn't have to be pretty. Doesn't even have to work right. But, when you're designing a game, you need to get something that basically works on the table as quickly as possible. This is because if you don't do it, it has dire consequences for your game design, in my opinion. And if you do, it makes your game design accelerate a lot faster, uh and it's much easier to iterate and figure out what's wrong quickly, so that you can respond and end up with the game that you always wanted. So, again, I want to discourage you from sitting and thinking about your game for too long and thinking, "Oh, well, I just need to iterate it in my mind a few times before I put it on the table." The reason this is a bad idea uh is that the way the game looks in your head is just not the way it's going to look on the table, and you're going to miss a lot of weird little issues uh that won't occur to you until you're actually trying to move pieces around.

Also, uh this is true for me as a creative person. I spend a lot of time thinking, but if I spend too much time thinking, I'm not spending enough time doing, uh and that's actually a form of procrastination. So, if you're always doing things that are adjacent to actually making a version of your game and playing it, uh then you are denying yourself actually making the game in favor of sitting around thinking about being a game designer, and that is not something that I recommend if you actually want to get a game out of your brain and into a box. Instead, you should get something on the table as quickly as possible, even if it is bad or even if you feel that it is stupid. Trust me, it is not stupid, at least not compared to uh the evolution of Davidson and my current Civil War game we're working on, which is called Throw Down That Flag. Uh this is a game where you are the First Minnesota at Gettysburg, uh and we're having a really, really good time with it. We're making it for the indie market at SD HisCon in November. And so this is a quick and dirty design, but I think that getting things onto the table, no matter what kind of design you're doing, is really important. So, I'm just going to show you a picture of a prototype of one of the scenarios that David and I were working on a couple weeks ago.

Um so, this is what it looked like. It looks like a really messed up sprawling football play. And we did not really know exactly how things were going to work when we started messing around with it. We just put some hexes down, put some counters down, and started moving them around and seeing what felt right. And then we would just erase things in Tabletop Simulator and rewrite them in order to get things to kind of to where we wanted it. And because we were working this really fluid way, it really helped us communicate about what should we be doing, what seems to be working. Let's just run this a couple times on this ugly, not even a real map map. And so then, by the next week, we were able to make a map and actually play on that. And then we noticed that there was something missing on that one. And so we now have this version of the map, which still needs to be beautified, but is a fully functional game map with a fully functional scenario that we're now playing on it because we started with an ugly, ridiculous, barely even a prototype prototype. In other words, a minimum viable product. Within the Leader Studio, um you know, Alida just published her first design diary about Cart. I've linked it in the show notes, you should go read it. Um but, one of the reasons that we greenlit Cart after we saw it was because Alida has everything she needs to make it through a game. And I knew this because we discussed the pitch for Cart, and she just showed up the next day with a prototype. Was the prototype good? No. Was the prototype fully functional?

Also no. But, I was able to see that what she was thinking about, where her mind was at, um and it was really clear that she was going somewhere. And so, she would just keep tinkering with that prototype until it fully evolved away from something that was a little bit more like Fort, which was some of the original inspirational source material for Cart, and into what Cart is now. And the reason that it's done so well as a designer in the studio is that Alida is not afraid to gut parts of the work, to try new things, and she's very, very focused on making components and getting them on the table to try. She doesn't just sit there and think about things for an extended period of time. I mean, she does think about it. When we have a playtest, what I'd typically expect from her is that she will like take a couple days to think about it, and then suddenly she'll show up with something new.

Uh but, she's always going for that next MVP, minimum viable product. And so, it's by actually getting something on the table and messing with it that you understand what needs to happen next for your game. So, if you are avoiding that step as part of your creative process because you just want to think about it some more, because you're afraid of what it'll look like on a table, because making all the components seems annoying, um I suggest that you get over that as quickly as possible and start putting things down on a table. Um there are a number of other reasons to do this that are practical. So, one is I mentioned that not getting your game on the table is a form of procrastination, and that is true. But, I will also note that if you don't want to make the components for your game, are you thinking of something that's more complex than what you actually want to do?

And the other thing is that you may accidentally be inserting things in your game that don't need to be there, but you won't know that until you try to make everything. And the other thing that I think stops people from from creating MVP and just slapping it down on the table is I think that we're all afraid that when we look at our work it's going to be bad. Um I mean, yeah, it's going to be bad. That's okay. Um because you can't have something good without slapping something bad down first. And this is true of most creative endeavors. So, you know, when you are writing a story, the first draft is always garbage, and the rewrite is where where real writing happens. With a game, you just have to get something down so that you can start looking for where the real game is so that you can chisel away all the things that aren't working and then bulk out the things that are. And there shouldn't be any shame in this process. Having a prototype that is bad is just like part of what game designers do. You should be sort of pleased and proud with your junk prototypes because you should have faith that they're going to turn into something that's really cool.

And so if you are thinking about making a game, the absolute best thing that you can do for yourself today is do not think about it. Do not take notes on it. Don't write things about it. Don't talk to someone about it. Make some components, slap them down on the table, move them around and then see where you're really at because there is nothing that you can do that is going to do more for your game than that. So, go get that MVP going. Uh if you made one today, I want to know. Let me know in the comments. Uh and happy gaming everybody.

Progress saved