On July 28, the Georgetown University Wargaming Society and PAXsims will cosponsor a virtual presentation by Tom Fisher (Imaginetic) and Matt Stevens (Lessons Learned Simulations and Training) on serious games for humanitarian training. They are the authors of a recent report on Serious Games: Humanitarian User Research, conducted for Save the Children UK. The study, completed in January 2020, explored the potential of games-based learning for humanitarian training in Jordan and Kenya via a series of workshops in Amman and Nairobi. Among the issues addressed are the effectiveness of games-based learned, the strengths and weakness of analogue and digital gaming, and best practices.
Tom Fisher is President of Imaginetic Simulations + Design, a serious games, training, development, and design firm based in Montréal, Canada; and an associate editor of PAXsims. With over 30 years of scenario design under his belt, and 15 years of games-based learning and serious games design and development experience. Tom’s design and development products have been used in training and analysis around the globe, from Aftershock to MaGCK, as well as numerous projects for the World Bank, NATO, and over 100 international agencies, universities, companies and NGOs.
Matthew Stevens is Director of Lessons Learned Simulations and Training a professional development training firm for humanitarian workers with a focus on simulations and serious games. Matthew has worked with refugees and migrants globally since 2008, from downtown Cairo to the Peruvian Amazon. Before returning to Canada in 2017 to found LLST, he served as Country Director for an INGO in Amman, Jordan, delivering online higher education to displaced youth.
The online presentation will take place from 6pm to 8pm Eastern. Registration is via Eventbrite.
There has been some recent discussion within the community about how to move people from “not a game designer/controller” to “professional (paid) game designer/controller” in an effective, efficient, and inclusive way. As someone who once upon a time had the ability to hire, mentor, and promote game designers (and analysts) I thought I’d weigh in a bit on this issue. Since I now run classes on wargame design for the Military Operations Research Society I still have some stake in the problem.
I’d like to talk about two questions: how do people transition from “not game designer/controller” to “professional game designer/controller?” Why is it so darn hard to make the transition? What would I say to someone looking to become the next Peter Perla? (Other than “Oh, my!”) I’d also like to talk about and “what, exactly, are we doing with all this education on wargaming?” And are our classes building the next cadre of game designers, or are they building better consumers of games? Or a little of the first and a lot of the second?
First of all, as usual, let’s play the definitions game. I’m talking about games that investigate or explore important and complex issues in a professional context. These games involve players who are familiar with the profession and context of the game and are often doing something that resembles the job they have outside of the game. I do not mean games for education, training, or entertainment, or even games that address broad policy or conceptual subjects. Specifically, I’m talking about detailed, technical, games, whether they involve military units, disaster response, law enforcement, or disease response. For military operations we’d call these “force-on-force” games but the forces don’t have to be military units – figuring out how to respond to a pandemic can be just as challenging. These are the games that involve the most technical detail to build, and the ones that people are coincidentally willing to pay the most for. Note that I said “technical detail” as policy games can be just as difficult to build, requiring the designer to often extrapolate knowledge that no one, including the intelligence community, has.
Because of this when hiring I gravitate toward people with technical degrees. When you’re running a game and someone turns to you and says “I’m using an AI-enhanced, spread-spectrum, wideband, emitter/receiver to manage the EM spectrum of the warhead” you cannot stare blankly at the person or guess what the impact will be. Even if you had never heard of it before. You have to have the technical prowess and engineering knowledge to be able to understand the technology and make a split second assessment that someone from the program office will buy into. Or at least meet them halfway in a conversation.
The nature of modern joint warfare requires a baseline level of experience with science and technology. That often comes from experience in the military. But with technology and systems moving quickly military experience alone can be inadequate to assess things we don’t understand. Without a mathematical and scientific background, it can be difficult to imagine scenario details and extrapolate outcomes in games of exploration. It’s not that it is impossible to do it, it is just harder when you don’t have the scientific or engineering background.
That means the first hurdle to becoming a professional game designer is having the technical chops to manage the kind of systems that we use in modern warfare (and disaster response and disease response and cyber response: the list could go on). You can get that from experience, but mostly you get it from having a technical degree in science or engineering.
It’s easier for me to teach someone with a technical degree how to design games, and how the military works, than for me to teach a game designer or military professional science or engineering. For professionals with degrees in the liberal arts who want to be game designers – there are ways to make it work – but I can’t have only philosophers and political scientists on my team (I’ve had both working for me).
So that is the first hurdle. You have to be familiar with engineering or science. You have to be able to do good operations analysis because a lot of game design and control involves operations analysis.
You also have to understand how the military, and organizations, work. This requires, in my opinion, no small amount of cynicism and experience. Games are about people, and about organizations. How the 3 doesn’t get along with the 5, how the CDC ignores HHS, and how everybody screws up the public information message. Where I used to work we’d solve this problem by sticking a PhD with a physics degree out on an aircraft carrier for a year or so. Problem solved. They came back with a lot of appreciation for how the military works, and how staffs and complex organizations try to get things done despite all the people who work there.
I can’t have a game designer who doesn’t know the subject area in enough detail to build in the tricks and complexities of real life, but I also need someone with enough technical chops to stand up to the O-6who has flown the aircraft all his career.
So that’s another hurdle.
Then there is the small, and really tertiary, problem of knowing how to design games. I can probably teach you that if you fit all of the above criteria.
But you have to be interested.
That, frankly, is a huge challenge. People who are good analysts and have knowledge of the subject area have lots of potential opportunities. Watching me do the same force on force scenarios over and over again while getting fussed by the players is not necessarily an attractive advertisement for a long-haul career in gaming. You have to be dedicated, which is something that hobby gamers have in abundance.
Hobby gamers’ role in professional games also raises another issue: some groups not traditionally associated with hobby gaming can feel unwelcome due to hobby gaming’s culture. That is not appropriate in a professional environment but it does happen. In my opinion some of the fault lies in the blending of the hobby culture, which can be quite misogynistic, with the profession. If you don’t believe me look around the next time you are at Con and note all of the magazine game book covers with buxom women on the front, or the “joke” minis of the same. It’s a bit awkward and a lot embarrassing. I tend to think we need to work on it by distancing ourselves from that culture, but that is another essay.
But this is where we lose a lot of our best candidates: the field is not that exciting once you get in the trenches. It’s a lot of slogging through sponsor’s bureaucracies, same scenarios, and endless arguments about systems. And pitching for new funding. You can’t run a game unless someone pays for it. But if you are a hobby gamer this is your life’s dream and all the nonsense is merely the pain that lets you appreciate the joy of your job.
Unfortunately for hobby wargamers there is a fourth hurdle. You have to actually know how to behave yourself in a modern, high-speed, progressive, organization (see my remark about Cons). That can be a bit of a problem. Organizations like to screen out the difficult and challenging during the interview process. That screening works pretty well.
The upshot is that it’s really hard to hire a game designer/controller, and you are almost better off building them yourself instead of trying to hire one from outside your organization. (But wait, you say, “I’m a hip hobby designer who majored in operations research twenty years ago.” kbye.)
The good news is that you really don’t need a heck of a lot of top-level designers. You certainly need analysts and support personnel, but the amount of business probably supports one or two top level designers per FFRDC, and one or two per major staff element within the military. That’s not a lot of people.
And once they get established designers don’t tend to die very quickly (despite their lifestyle choices) and don’t tend to leave because – “I’m a freaking game designer why would I ever leave that job?” (Other than the constant travel, need to work hard for funding, and dealing with all the unrelated organizational issues you have to deal with, like hiring people.) This means that the pipeline is narrow, and long, which is even more discouraging to that new, highly educated, smart, and marketable analyst I’ve just hired to do wargaming.
So, “why are we doing all these classes on designing professional games?” Let’s ignore the obvious answer that staffs think if they train a couple of guys on staff they will be able to avoid the rather expensive cost of paying contractors or FFRDC’s to do it for them. Or the pain of getting their commander to task another over-tasked, wargame-providing, command to do it. Instead I’d say that we are not actually building a lot of high-speed game designers in our classes. Rather we are teaching people to:
Be good consumers of games.
Be better players in games.
Be better sponsors and funders of games.
We do this by telling people about the basics of game design, and, I believe more importantly, helping people understand what games are and are not. For designers that take our classes we can pass on pointers and tricks that we have learned from years of experience: but I don’t believe that in one or two weeks we can build a professional game designer that can hold their own against a crowd of unruly O-6’s. Our classes may be a stepping off point for a long period of apprenticeship and learning to be a game designer. But for the vast majority of people it will be a (hopefully) pleasant introduction to the things they should ask, task, and review when they encounter a game in their day jobs.
Now I have outlined a somewhat unhappy and difficult path into game design. It is one path and based on my experiences doing complex games for demanding sponsors. There are other routes you can take, not the least of which is that you simply declare yourself a game designer and do what the last guy in the job did. But I’m talking about building people who will move the field forward, will bring in considerable funding for their organization around gaming, and will build a cadre of new analysts who are capable of, and enjoy, doing gaming. Analysts that will become insightful, creative, and critical game designers. That is a narrow path which, unfortunately, can be quite discouraging.