The Studio Producer knocked politely, but urgently on the Director’s office door. After stepping inside, Producer says plainly, “I know we’ve already got a handful of games going right now, and we really need to focus on fewer if we’re going to make any real progress on any of them…”
The Director looked up from her monitor and said, “It sounds like a ‘but’ is coming.”
“But…”
(Knew it, she thought.)
The Producer goes on, “…we have an opportunity that I want to take advantage of, and I believe is worth a temporary shift in priorities. A simple slot game that can demonstrate a few key items.”
A slot game? Simple in theory, but 15 years in the gambling industry has taught her that slot games can get complicated very quickly.
“Well,” the Director responded, “let’s hear what you want to demonstrate, and I’ll tell you if it’s going to be simple or not. We can decide together if it’s worth reprioritizing projects.”
“Okay, great! So here are the requirements:”
The Producer then outlined the following:
- A video slot game, with 3 reels, based on older mechanical titles.
- Very limited paytable, less than 10 possible payouts.
- Single denomination, bet up to 10 per play
“Simple enough, yes?” The Producer says, before going on.
- We’ll do a junkyard theme. Like this slot machine is put together quickly from scrap pieces.
- We’re trying to stick to “simple”, so let’s do a retro-pixel art style, because it’s a popular aesthetic, and the intentionally scrappy nature of the theme means your artist doesn’t have to create perfect assets and we can focus on speed of development.
- Traditional reel strips, so bars, 7’s, cherries, that kind of thing.
The Director nodded, “Okay, sounds simple so far. So what do we want to demonstrate?”
“All the things we exist to demonstrate, but namely, we want to demonstrate game design principles and execution, architectural and technical design chops, and the management principles around it. We’ll also get to have fun with some art that’s easy to do and can be eye-catching. So with that said, here are some technical requirements:”
- The game should run on web and mobile, because it needs to be shown and be easily playable.
The Producer hesitates for a second. The Director picks up on the hesitation, and senses a catch, but only raises an eyebrow. The Producer continued..
- It needs to be Class II.
Startled a bit, the Director sat up in her chair. “Wait, what?!”
“Yeah, I want it to play bingo, not just run off a straight RNG. It should demonstrate a ball-call server, bingo-card evaluation, and translation to reel presentations and the clear segregation of those duties required to be considered Class II.”
“And that’s where the simple stops.”
“True, but we know this area, and this will demonstrate industry familiarity, design expertise, problem-solving, and more. The game itself needs to show this, so exposing the ball call, card plays, and communications… it will all have to be part of it.”
“That’s why the overly simplified slot play.”
“Yes. Once the structures are in place, we can do a second theme. Expand to five reels and a more complex paytable. Show the extensibility of your design.”
“I see.”
“There’s one more thing.”
“Uh oh. What is it?”
The Producer hesitates again.. then spits it all out in a rush. “We also need to show RTP [Return To Player] of the paytables.”
The Director, instead of spontaneously suffering from exploding head syndrome, folded her arms as her expression went pensive… curious even.
“RTP is hard to calculate. And generally expensive. But you’ve got my attention. There’s some new tech that just landed a week or two ago that might actually allow us to do that and would be incredibly fun to explore.”
The Producer, a little surprised and very pleased that the Director seems to be on board.
“Of course, it means the other projects are going to stall again.”, the Director cautioned.
“It’s okay. They’ll still be there, and this is all about learning and sharing, right?”, the Producer responded with a smile.





Leave a Reply