Roadblock is a series of articles where I interview other designers, developpers, and others involved in the industry, to do a deep dive into a specific issue they’ve dealt with in a project. The goal is to add concrete examples to the mass of game design advice out there.
JV: Today I’m sharing with you folks a discussion with Daniel Newman, designer of Dead Man’s Cabal, Rolled West, and Ahead in the Clouds.
JV: So Daniel, what game are we talking about today?
One of the games I spent a good portion of 2019 on was called Nebula, and then later The Well. It started with an idea for an action selection mechanism that I came up with while driving to Granite Game Summit. It involved a tray for 8 action tokens with a slider to select which actions you can do that turn, but depending on what ring of the board you were in you were limited to 4, 3, or 2 actions. I thought it would be cool to have a game where your position on the board would determine your effectiveness, with the fewer actions gaining you higher value rewards.
The first thought I had thematically was mining an undeveloped Nebula. I came up with a couple of generic resources (gas and minerals) and structures needed to harvest those, and actions revolving around moving through the nebula, building structures, and using those structures. It was…fine. I had a couple of people in my playtest group who said they enjoyed it but it didn’t really feel like it was doing anything special. I put it away for a bit and then had an idea to rework it, using the same general idea but with a hand of cards that cycled similarly to Concordia, and rethemed as spelunking in a cave system called The Well (because it was 3 layers of concentric circles). I thought it was more interesting and definitely had a better table presence. I generally got a better response with this reworking in the group as well, so was feeling pretty good about it by convention season.
JV: What was the problem, and when did you first encounter it?
I thought things were going along nicely, that it was pretty much ready to pitch. I showed it to a publisher at BGG.con and it was a disaster. It didn’t play anything like I thought it should. Things I thought were super clear were not. The publisher I was showing it to seemed angry and agitated for the entire game.
I realized that so much of how I wanted it to be played had been internalized by my regular playtest group – they had all played it a bunch and were just ignoring the obvious problems with it because they were familiar enough with the systems. It felt like it was smooth because of familiarity not because it actually was.
Because it’s so easy to bring things to this group twice a week, i don’t usually seek testing outside of the group.
JV: How did you handle the situation with the publisher?
We wound up finishing the game, as it was, and then I apologized for the experience being so bad. This is someone I show games to regularly so I was a little surprised at his reaction, but it just had a number of things in it that he really doesn’t like in games. He assured me that it wasn’t me personally that he was upset with. He’s someone whose opinion I very much respect, so seeing that reaction really convinced me it was time to shelve this one.
JV: Had you ever encountered a similar problem before? Why was this one different?
Not really. I tend to have a pretty good sense of whether or not a game is working, despite what feedback I’m getting from testers. I think I just really wanted this one to work even though it was never really feeling like it was coming together. This was also an unusual one because I tend to use an existing game as a starting structure and base my design on that – obviously things change pretty dramatically pretty quickly, but that tends to get me going much quicker and makes it so I don’t have to reinvent the gaming wheel every time. When I did the ground-up reworking as The Well, I used a couple of games as models for the systems I wanted to use, but it still never came together properly.
JV: Can you talk about the process of solving it? What worked? What didn’t?
Honestly, I never really solved it. I’ve shelved it indefinitely. Sometimes it’s the right thing to just put it aside. Maybe I’ll come back to it, I probably won’t. I have at least half a dozen games on my prototype shelf that I just decided wasn’t worth working on. There are a couple of nuggets of goodness in them, but I had another idea I wanted to work on and just didn’t want to devote more attention to this design that wasn’t working out.
JV: When did you decide to let it die? Did you try some stuff before then, or did that one pitch taint it so badly it turned you off the project entirely?
I’d been trying lots of different things over the life of it and nothing was really feeling right. The bad pitch was the nail in the coffin. I had scheduled a pitch meeting for it with another publisher later in the week and cancelled it because I just no longer had confidence in it as a game.
JV: And how do you avoid that problem with other projects? Have you changed your way since or was it just the exception?
This was actually very recent, just a few months ago, and one of the last games I pitched. I’m still mulling over exactly what went wrong in the process, as I had never had this happen before. I think I’m just going to be more aware of how many different people play my games before I bring them to publishers to show.
JV: In general, what do you think are the Pros and Cons of having a small but regular pool of testers?
Obviously it’s great to be able to get your design on the table super frequently. You can make a lot of progress in a short period of time, especially in that early stage when you’re constantly iterating and making big changes. If it’s a group that meets twice a week, like mine does, you can also not feel terrible about skipping one or two now and again because you know there’s another in just a couple of days (unlike groups that only meet once a month, in which case you’re going much longer between tests).
On the down side, you wind up testing with the same people over and over again and you can develop a meta where people generally understand the game and only slightly adjust to the new tweaks every time and are playing generally the same way. You just don’t get as much variation in approaches to the play and can miss huge problems because people get too comfortable with the game.
JV: How did you develop that “small but regular” pool?
I happened upon it kind of by accident, actually. This was a group that already existed and was meeting about once a month before I joined and started meeting once a week around the time I started attending. There were some fairly well known designers as part of the group, who I didn’t know when I joined, but later found out they had put out some fairly popular games. The group really started to flourish when Gil Hova (one of the aforementioned designers) took the reigns and started spreading the word a bit more. A lot of it was just due to better organization and finding a better, more reliable place to meet – the open seating at a Whole Foods, as a matter of fact, one of the few large semi-public spaces in NYC.
JV: You talked about usually starting from an established game: how does that usually happen? I have this list on my phone of games I want to “fix”, to design a different game based on the same central mechanism. I usually love half of the game, and hate the other half with a passion. How do you handle that?
It’s a bit different for each game but lately it’s either “I really like this game but I don’t like how ‘x’ works, so what if I take this mechanism and do something else with it” or “I have this theme that’d be fun to make a game around and I really like how ‘x’ does it, so I’ll just borrow that and change it up and use that as a starting point.” Usually it’s some sort of combination that happens simultaneously. How much I borrow or start with really varies depending on what I need and what else I have in mind. For example, the game I’m currently working on ostensibly borrows the upgrading of tiles from The Taverns of Tiefenthal but now that I’m a few iterations in it doesn’t really feel that similar. The rest of the game is pretty remarkably different.
JV: Well thank you for your time Daniel! You made a few very good points about varying testers, saving face after a bad pitch, and starting a design from an established game. Aside from being a bit of a bummer, I think you also brought up an interesting, under discussed aspect of game design: sometimes, you just have to admit defeat.
In addition to game design, Daniel Newman is sometimes on Twitter. [/sarcasm]