The Game Production Academy
About Game Production Academy
I'm Liam Wickham. Game Production Academy provides practical insight, training and support for game producers, production leaders and studios.
Here I explore how teams plan work, manage risk, lead people and make delivery decisions. The focus is on real production problems, practical examples and tools you can use with your team.
Game Production Academy also offers professional courses, studio workshops, consulting and advisory support to help teams improve their production practices.
I'm the author of Risk Management for Video Game Professionals (CRC Press, 2026).
Links
Newsletter — Practical insights into game production
https://www.game-production.com/newsletter/
Free resources — Articles, podcasts, templates and tools
https://www.game-production.com/resources/
Professional courses
https://www.game-production.com/courses/
Studio training and workshops
https://www.game-production.com/studios/
Consulting and advisory
https://www.game-production.com/consulting/
Risk Management for Video Game Professionals — The book
https://www.game-production.com/riskmanagementbook/
The Game Production Academy
Production Chats: Anthony Kyne, Lead Producer
Use Left/Right to seek, Home/End to jump to start or end. Hold shift to jump forward or backward.
In 2020, me and Anthony chatted about all things game production. Enjoy!
About Game Production Academy
I'm Liam Wickham. Game Production Academy provides practical insight, training and support for game producers, production leaders and studios.
Here I explore how teams plan work, manage risk, lead people and make delivery decisions. The focus is on real production problems, practical examples and tools you can use with your team.
Game Production Academy also offers professional courses, studio workshops, consulting and advisory support to help teams improve their production practices.
I'm the author of Risk Management for Video Game Professionals (CRC Press, 2026).
Links
- Newsletter — Practical insights into game production
- Free resources — Articles, podcasts, templates and tools
- Studio training and workshops
- Consulting and advisory
- Risk Management for Video Game Professionals — The book
My name is Liam Wickham, and I am the founder of games production. com, which is where we seek to enable games industry professionals to plan better, lead better, and stop the crunch culture through building a community of support, knowledge, and training.
Today, I'm delighted to introduce you to Anthony Kine, a lead producer at Mediatonic Games. They've made games such as Gears Pop, Murder by Numbers, and the upcoming Fall Guys Ultimate Knockout, which looks awesome. Anthony has worked on titles such as Madden, Championship Manager, and The Sims. Unlike nearly every producer that I've met or stalked on LinkedIn before now, Anthony has worked in games as both a lead designer and senior programmer.
This gives him a unique understanding of making games, which I'm looking forward to delving into. He was lead designer on Championship Manager Game back in 2009, which saw the franchise finally rise to become a viable alternative to Football Manager. Good evening, Anthony. Good evening, how's it going?
Yeah, it's going well, how about you? Very good. Thanks. Very good. So you've had a busy day, I presume. Uh, very busy. Yeah. Um, my, uh, my publisher at the moment's out in the U S so I'm, uh, getting up in the morning, sorting out everything that's coming overnight. And then as soon as the afternoon hits, they all want to have meetings with me for the afternoon.
So yeah, always busy. I have a morning of doing a lot of work and then straight into meetings after that. I take it because you, you love it. You wouldn't have it any other way. Oh no, not at all. Yeah, I love a meeting. I'm sure we'll be talking about that. Yeah, yeah, I imagine so. Um, so, I like to do a little icebreaker at the beginning.
So, um, I've given a brief summary of somebody else's life, but how would you give us the real potted history, and can you tell us what you're up to currently? What can I say? I'm, I went to school. I wasn't particularly very good at school, um, but found a love of computers. Uh, luckily, I think, due to the fact my grandfather was, uh, I was a bit of a geeky man himself, and was one of the first people I knew that had a home computer, which was an Acorn Electron, and persuaded my parents to buy me a BBC Micro, which was a really, really good computer, but horrible for somebody like myself who just wanted to play games.
Yeah, sort of fell in love with that, and I had a, I had reasonable skill at maths, and was terrible at everything else, so, and, and, Sort of got into computer programming from about the age of like nine. I was doing it with my grandfather and then one of the guys at school, he was a really bright guy went on to become a lawyer.
And even at nine years old, he was clever. Me and him used to spend break times with the school computer, learning to do stuff. And then I went off to secondary school and I got a Commodore Amiga. Um, which was more of a game machine, um, and by that time I'd sort of lost the love of real gaming. It was more about the programming that I loved.
So I got a thing called Amos, uh, which was like a unity of its day, really. Um, where you could make games in it with, with BASIC. So I did that, I made a, uh, great little game called The Adventures of Grant Gibber Morris, a guy I went to school with. It was meant to be the first case of cyberbullying. 1991 or whatever it was when I did it.
Congratulations, I'll look that up to see if that's, you should Wikipedia. There's a three level game where all the teachers are in the trees and you, you were Grant, friend of mine called Sam did the graphics and you, you threw bananas up at the trees and knocked, uh, knocked, um, knocked the teachers out.
And then the final end of game boss was the headmaster. And then I sold, um, Sold the discs on the playground for two or three quid, I think, so, uh, yeah, did that. And then you retired rich. Uh, yeah, there you go. And, um, yeah, and then sort of went through school thinking, okay, I quite like this computer program and I'm not particularly good at anything else.
Never really considered getting into games. Um, you know, I, I kept plugging away at making my own little ones at home because, you know, I really, really like football. I turned out I wasn't very good at it compared to most people. Uh, so I knew I was never going to play for Manchester United. So I created a world where I could, um, that's what I wanted to do.
Um, but yeah, finished school and was sort of hanging around like Anko, which was a big company at the time of the game called kickoff or in Dartford. And I managed to sort of get my foot in the door, sort of growing up around here, there as a QA and stroke, sort of junior programmer really, and then just work my way up the ladder and there, and I would still be there if it wasn't for the fact that the owner of the company died and left me and Steve Screech, who was the guy that made Kickoff, um, originally.
the company so me and him went off and sort of went on and did championship manager together and then we went our separate ways after that for about 14 years. Since then how come you've ended up where you are now? Um, well I sort of jumped around a bit so after championship manager I thought right I don't really want to do any sports games for a while I'm a little bit In a niche, so I went off and did some children's games for a little bit, P2, and that's when I really got into production, I thought, okay, that's a, that's a decent path, I reckon I can do this, so I had a quick go of that, and got Peppa Pig out, which was a really successful title on the Nintendo DS, got a Horrid Henry game out, which is one of the best things ever.
Yeah, yeah, yeah. So I did them games, and then HB over in Canada came up and said, oh, we want you to come over and, We need someone with experience with cricket and, um, rugby that would know how to make them kind of games. So I went over there, um, and made a baseball game, uh, two American football games, um, and a golf game.
Never got anywhere near a rugby game before. Ironic. Yeah, I think I've been employed three times to make a cricket game and I've never finished one. But okay, but so we're skipping around places you've worked, but I'm really interested in, uh, the experience that, uh, I know you've got, but you should tell our beautiful listeners about because you're, like I was saying at the beginning, you're quite unique to me in, in the, you've been a senior programmer, you've been, you've been a lead designer and led, led other designers, uh, designed entire games.
And I'm really interested in, How you managed to, to get through all of these different jobs and different areas of expertise and skill base and end up as a producer and not as one of those? Yeah, so I would actually most probably class myself as a computer programmer more, more so than anything else. Um, but much like I am a guitar player.
I only ever learned to play guitar because I wanted to play a song in a pub. I only learned to do computer programming because I wanted to make a game. And when I started at Enco, Enco was a very strange setup compared to modern studios. It was the boss. a group of programmers, a set of artists, and some QA.
And everyone just coded and did the art for the code. There was no producers, there was no designers. And Steve Springtree was the sort of creative director there and programmer, was running most things game direction wise. And I think I'm quite vocal and I was massively excited to be in games. I've always thought that if you're going to make games, don't just sit there and just do what you're told.
It's You make the game. So I think pretty much even as a teenager working there, I was, I was giving input on how we should do it. And it sort of just naturally, I sort of rose to the top to me and Stevie sit together and basically bounce ideas off each other. There's no documentation. There was no producers and there was no purples.
And so what happened at the end of each day was that everyone would give me the code and I'd merge by hand. So at five 30, everyone would give me the code. I'd stay at work till six 30 merging everyone's code. And I put the, uh, the code base back on the server and everyone would download it again in the morning.
I don't understand why they don't do things like that these days. Yeah, I know. Well, that was great because no one could fire me because I was apparently I was the only one to do it. But it wasn't even that hard. But what it did is it gave me a sort of background in making sure that I knew what everyone was doing.
So sort of that production style, like how the project is built. and what everyone was doing and sort of making sure everyone had enough work and stuff like that and I had to do that to make my life easier to merge the day. So that, that was sort of my first steps. But then when I sold Floodlit, which we renamed ENCO after Taking it over to Eidos.
Eidos said to, said to us, do you want to be a programmer? Do you want to be a designer? Do you want to be a producer? So I was like, I don't know what a producer does. I had no idea. I'd never seen one before. Um, and I knew I didn't want to be a programmer that programmed what I was going to be told to do.
So I went, okay, I'll be a designer. It was. It was a disaster really because I was really good at maths and really bad at English, so I had to write all these documents. So I learned, I learned on the job really and worked my way up there and I was there for seven years in the end. I was a late designer by the time I left.
What did the design documents look like then? They looked like huge, huge Like IBM manuals? Uh, yeah, they're like bought like huge I remember the 50 page documents and they were like written and nobody was ever reading them And it was like god and I remember I used to um, I used to complain all the time This is not the way it should be done it shouldn't be done like that and everyone was looking at me like I was insane, like, what are you talking about?
He just complained. This is why it's always done. And I was going, but surely this is not making games. This is just boring, but it felt like a sort of working at a full production plant where it's just, everything was going down one by one by one. And then a few of the production team went off to GDC and came back and they said, Oh, we're going to do agile and all of this.
And I was going, And they came back with Agile and I was like, wait, this is what I was sort of telling you to do before. But apparently, because I said it, I didn't have a name for it. It wasn't cool. Yeah. Um, so, so then we started doing that and I could see the benefits of that. And then as I said, I saw lots of producers come and go there and I was like, Hmm, yeah, I think I can do this better.
And then when the option came up to go and do the, the small children's games as a producer, I thought, all right, I'll have a go at this and then see how good or bad I actually am and see if I've got the. the ability, the belief I think I have. And, um, I remember when I did become a producer, I got quite a lot of messages from ex producers saying, you hate producers.
Were you right? Were you a good producer? Are you a good producer? Were you better than them? I believe so. Talking to people that I've worked with, In the last 10 years as a producer, they always think I'm good unless they're just telling me that to my face. But yeah, like I, I think, I think I allow people to, to do their jobs and then they feel that they're actually making a game.
And I think that's, that's the one thing that I think a lot of people, sort of get distracted from when they are producing. Just looking at your LinkedIn profile, you expressed some opinions in there about your experience being useful, and you're saying that it has a huge advantage as you understand where people from different areas are coming from.
Yeah, so I think like, what you find in production is that a lot of people come straight out of QA, and it's like a natural path in the games industry where You go in at QA and you work, you work really hard, you do really well and then you become a producer and then if you do really well you become head of studio.
It sort of goes in that linear path. And what happens is a lot of people that are in production that come from QA would prefer to still be in QA. The problem is, is that the industry doesn't allow itself to make you flourish in that, in that department, which is really disappointing. You should be able to, I know a guy that was extremely good QA, one of the best QAs I've ever seen.
Like he used to get in people's heads, he used to go and talk to programmers just to get in the head. So he knew how, how they'd screw something up and he'd go, I know how this guy's going to do it. And he'd break it. And it was superb. And the only way out of that was for him to go up into production. And, or design.
And then we got there and he was, he was no good at it. So he kept getting fired after that. And he doesn't want to go back to QA. So it's like, where, where, what I've found is, is coming from certain, like a different sort of route up is that I can, I can call bullshit a little bit on programmers, which is great.
Cause as a programmer, as I said, I'm actually classed myself as a programmer more than anything else is we're a lazy bunch of people. There's a reason we're computer programmers is like, if you write a piece Like does something you then put a loop around it so it can do it a million times rather than you have to do it By hand a million times.
It's like that's why you get into computer programming. Um, And you know We'll always have an explanation of why something can't be done. Um, so to be able to go Well, it can be done. What about this and come up with some, um, like different ways of doing it having a conversation With a programmer that they don't have to You know Simplify everything down to the most basic thing gives them I think a little bit more respect for you Yeah, and coming from design a design background as well.
You can always you can always look at Troubles that people are going to have along the way that you can point out and see Down the line saying that I have a huge problem because i'm only useless at art and I can't draw and it's the one thing I must be never doing that because mate Draw any art or anything that I don't see them problems in art.
And then that's why I always need a good artistic producer or a good art lead. Wherever I am because that really improves the project. Okay, so let's look at those things you said you mentioned about coders My experience of coders is that they are um born problem solvers They would love a problem that they can be given the rest of their lives to go and solve And it is it's a lot of coders are like that and I guess You'd be able to call bullshit on that sort of thing as well, right?
You can you can you know how long a thing should take as well, I imagine You Yeah, and, and like, I think the other thing about coders is that they'll always look for the most fun, technical way of Solving something. So you go, okay, we need to do this and this, and they'll go, okay, well, it needs to be written in a completely new language that we've never looked at before, but it means we can do that.
And you go, or you could just put an if statement around it. And there, and that's a bit hacky. It's like, no one cares. Like nobody knows. And like, they always want to make the perfect piece of code in the perfect world where as a, as a programmer, as a programmer, who's a, who's a game designer, I just, I concentrate on what the game does.
More than what the code does and yeah, yeah, there's a certain architecture to the code It has to be has to be right so you're not troubled with it for the rest rest of your time working on that product But you need to be like focused on what the output to the user is and not What the code look like and that's what a lot of programs unfortunately get bogged down So if we look at your design skills as well, your experience there as a lead designer on Championship Manager and others.
Championship Manager and onwards, you, you have held creative vision, haven't you? You've, you've wanted that vision. You've wanted to direct that vision. If you're a senior or exec producer. Yeah, I would say from before that as well, most probably from the player manager days back at ANCO, I was most probably holding the creative vision for that as well, in joint with Sticks Bridge.
So, kick off 2002, player manager, 98 onwards, most probably I was most probably holding that creative vision. And you made it pretty clear that you quite like being, well you sort of climbed up to the top because you wanted to be able to make those decisions and you wanted to influence and, and you think that to be in the games industry you're, you know, that you have a certain passion that you can contribute.
Do you think that that's a natural trait for any producer? I think it should be a natural trait for anyone in the industry because I don't understand why you would work in it. if you could earn more money being told what to do in banking or something else. It's like, we all want to make gains. It's like, we should all be willing to have an opinion on what we're making.
Like, if I'm a programmer and I want to see cool code, I can do that at Bloomberg, right? So, I don't get paid three times the money. So, like, I want to be able to read the game and go, okay, this is, I coded that. This is really cool. And I had this influence on the game. I think that's how I think people think.
So, if you, if you want your, your name and title on the credits, you want to make sure that you've contributed to all areas. And I'm wondering though, uh, I mean, I've worked in places where there are very strong design and art directors. On a, on a single game and they would not take kindly to a producer coming in and saying, right, well, I'm the EP.
I'm, I should be holding the creative vision here. They would expect that to come from them. Or a creative director, not a producer. How would you deal with that? And what's your opinion about that? It is a thing that you come up against, but there's two, three, several things from that is that the person is the, who owns the creative vision for that title should be the best person to hold the creative vision for that title.
I, I wouldn't like, there's a big thing around in the last 10 years that everyone's fighting to be creative. I know when I was doing, um, I was a VR director at Imagination, there was like all this stuff about, Oh, I'm a, I'm a creative. It's like, what does that mean? Like, um, like I'm really creative in making sports games.
Primarily because I really love sport and I can see stuff. I understand games. I understand sport. And it's like a really good melting pot for me to give my opinion. Sure. He's a carpenter. He's really creative at building sheds like that. I'm not. Yeah. And you know, X, Y, and Z. So everyone should have a creative opinion.
The problem I've always had with designers, um, is design isn't, isn't primarily a creative job. It's a, it's an architectural job. It's a mechanics based job. And this is the way I try and always run my teams is that you run in in pods of five or six. seven depending on the size of the feature and the The designer is the person who has the most background and knowledge about how mechanically it should work and the thought About how the knock ons will affect the user but that doesn't mean that the qa person is not cannot run with a, with an idea or the programmer cannot run with the idea or an artist.
You shouldn't be compartmentalized into you're not an ideas person and I am an ideas person. And I think a lot of people get into game design because they fancy themselves as blue sky thinkers when it's a mechanical job. That's I think one of the big surprises for me when I got into design as well. It was like, oh, well, I didn't just sit there and come up with ideas.
I have to mechanically think about everything. And it's a hard job. It's extremely hard job. It was like way harder than programming because you're thinking like a programmer, but don't have the output to bug test against. And then everyone hates you. Everyone thinks they can do your job better than you.
The cleaner comes in, she thinks she can do the job better than you. It's like, everyone can do this job better than me. And it's like UI as well. I think design and UI are two jobs which get as much criticism off the exec or anything because everyone thinks they can do it better than you. Coming from a programming background and my team that I had, Eidos quite, I remember they used to mention this quite a lot is that I was always the person standing there going Well, this is what we want They'd all come up with a lot of cool ideas And then we'd try and design it out and you go actually you don't necessarily don't need all this You can actually get away with it If we just do x y and z and it's a smoke and mirrors and no one would ever see And you'll go boom boom boom and it'll work that oh, yeah, cool.
We can do that and then where As, as I said, if you, if you've got programmers who are always looking for the coolest tech and you're, you've got designers who are always thinking out here, it's like, this can never be done, this can never, and then all these arguments start and there's always a simple route and that's what I've found, uh, that's always good in production as well is, I'm great at watching an argument between programmers and designers and I like to see them flourish for at least 10 minutes until I step in and go, I'm like, Well, let's have a listen.
Okay, we can actually simplify this by doing that and getting to the result quicker. So I guess, I suppose I see you holding quite a kaleidoscope of roles when you describe yourself as a producer. If I compare that to a lot of other producers, right, who don't have that luxury of that background. If you will, um, when you look at other producers when with its producers working for you or producers that you've seen elsewhere, um, what would you say is like the absolute bare minimum experience and skill set that a producer needs to have these days?
I think bare minimum, the one thing I look for most is personability, because if you can't deal with the people, there's no way out. And then it's, secondly, then it's keeping calm and like going, okay, how do we do that? Because as soon as, as soon as you start panicking, everyone else around you starts panicking and there's no, there's no way out.
You know, we, we make games for a living, no one's going to die. So it's like, calm down, like relax. And like, you've got, you know, be personable and relax basically. Yeah. Okay. So those are, I mean, anyone can, anyone can have that as a, as a, as a character trait or personality trait. Um, but in terms of.
Technical expertise in terms of training in terms of foundation knowledge Do you look around and despair a little bit and go I wish people had more of x y and zed One of the things I look for massively when interviewing people is a creativity within their approach. So as we were saying earlier about creativity is like my dad's got the creativity of building a shed and the same way it's like a producer should not just be happy that he went on a course and he learned agile and this is this, this and this.
And I always try and get out of people in an interview is, you know, if this, if this happened, what would you do? And they've always going to try and hit them notes that you, they think you, you want to hear about agile or waterfall or whatever. But I want to see like a way of their thinking to make them think, how can I do this better?
Because no process is ever perfect. So you always should go into a place and go, how can I get this better? How can I improve this? How can I reduce the amount of meetings? How can I like, and Agile has got a huge amount of problems, you know, It's got loads and loads of things that will slow you down if you're not doing it right.
So it's always like, how do I go into a place and improve that sort of thing? So that's what I look for when I'm, when we're interviewing people. And I think that's, you know, if you're just a by the book producer, you're normally going to hit your ceiling pretty, pretty quickly. And that sounds like you're, you, that would be a definition of a project manager rather than a producer, right?
Yeah, by the numbers. By the numbers, yeah. And that's the thing is, is. I've worked in places where I am the producer like when you're working on Madden and even the golf club. Like I was the producer that is the person that really holds, holds that creative vision and makes sure the right decisions are being made.
As well as having a project manager, I always feel like I'm the one. being in charge of exactly how much of that project management, I think we were doing. That's very interesting too. Um, uh, there's a strong dream in this conversation of the producer as a leader, the producer as a senior member of the team.
And I suppose I'd be really interested and maybe you're not in a position to tell me, but I can, I can ask someone else, but what's it like working for you as a producer? What, what, what are you giving your, the producers underneath you? What, what, what, how do you sort of mentor them and train them? Well, yeah, it's a good question.
Uh, one, it's fun. Um, because I've never in my 23 years of working in the games industry, woken up and not wanting to go to work. So I would definitely don't want to make that situation for anyone else. So try and have as much fun as possible. But I'm also, The person that will stick up for them, make sure nothing silly comes in and always be there to help them out.
Without being a micromanager, as as a person, I'm might bring up my father again, but like, he's a really good carpenter. I'm rubbish at carpentry because he can't keep his hands out of it. And the reason I got into computers is because he would, didn't have a clue about 'em. So I could actually sit there and learn.
And I'm a big believer in letting people run away, like. You learn stuff, try and do it yourself, and then when you hit some, some problems, come and see me and I'll help you out. And like, I'll let people go for, for a few days without having to stick my nose in and what they're doing if they're not asking.
Yeah, I'm, I'm a hands off producer really, in all disciplines. But as a, okay, but, but in the long term growth of a producer who's just started with you, let's say, Yeah. A junior producer. Um, I mean, I know you're pretty senior now, so you probably don't deal directly with junior producers in terms of mentoring training, but, but if they approached you and they said to you, you know, what's the three biggest bits of advice you could give me for becoming a successful producer in the future?
You're going to maybe talk about personality, et cetera, and creativity, but, but what sort of hands down practical, you know, go off and grind over there and learn about this thing here. What sort of advice would you give them? It seems I've trained myself. It's a hard question to answer, really. What can I go into?
I wouldn't Sorry, mate, I'm just, just to reassure you, I don't think there's a right or wrong answer, and I think everyone, you know, is going to give a different answer here, right? Because, because there's no foundation, is there? There's no set way of doing it. No, and like, and that, and that's the thing. I think from my perspective, what I try and like, I like to do is get my, my ducks in a row, so I sort of know exactly what's going on at all times, without being too in depth.
I don't try and overload myself. I try and keep my life simple. I simplify everything and that's what I always encourage people to do is simplify everything down so it's very edible chunks in front of you so you're not like overwhelmed and get that down. Make sure you've got a strong personality so you can go into certain meetings and you're not bullied out of out of certain certain situations.
which can rub people up the wrong way. But if you're personal about it, it normally goes okay. Um, and, and sort of just, just be, get yourself always like friendly with the lead programmers and the lead artists and stuff that them guys will really help you out when you need sort of backing. In certain situations and designers as well, obviously, but all your leads, make sure that then guys you're on the same level, like same level with, and you're going, okay, what are we going to do here?
The sort of mission over to them of what you're trying to do and make sure they can help you out and sort of push in the same direction. But like from a skillset point of view is. It's just, I think, be a strong personality, fully understand what's going on, and, like, because tools wise, that's one of the great things about production is that I can, I can run a whole project on a bit of paper, really, I don't need JIRA, I don't need anything else, I use them, but skill wise is like, I think it's definitely worth going on all the courses for Agile.
waterfall, everything you can possibly go on, but don't take them as gospel. It's like, always makes me laugh whenever you see a set of junior producers go off to an agile course and they come back with their sticky notes all over the windows and stuff. They've got religious clothing on. Yeah. And it's like, yeah, all them things were good, but it doesn't mean it's right.
A hundred percent. It means take certain things that you think will work in this team. That you work with will be different and every game you work with will be different because every publisher is different and every group of People you work with so let's ask you a little bit about what you just said then about agile because um So I was talking to calum godfrey a few days back on for a podcast and he's got a lot of mobile gaming experience And he had a lot to say about agile product management.
And of course in mobile gaming. There's a lot of there's a heavy emphasis on Agile software development type work and product methodology, et cetera. Whereas in PC console, it's, it's more free form really, isn't it? It's, it's like, um, a more unwieldy beast and, and for different reasons. And I'm wondering, why do you think it is that you can't, for example, turn up AAA, a couple of hundred people and say, right, we're all going to be doing Agile scrum.
Let's go. Why doesn't that work? How would you explain that to somebody new? Well, it doesn't work because of the certain set dates, and like, then, then, then dates in Greenlight meetings are in sort of concrete, and you can't move them. And the thing with the Um, the mobile development is that you can, you've got very quick turnarounds with releases, especially like a lot of free to play.
It's like you need to be getting the content out every two to four weeks. So you need that sort of running system where what you have with console and like, and don't get me wrong. And when you're starting out in a mobile game, I don't think it should be overly agile either. Cause what happens is you start to lose the confidence of the, of the exec teams.
That you're dealing with if you're like too agile and you go, Oh, we just don't worry. It's just done over and over the sprint and all this. We're, we're in console. I think. I, I sort of run a sort a normal on a console stuff, a semi agile system where we, we have a milestone. We might have a couple of sprints within that milestone.
It could be, could be a three month milestone. And I, I'm not a hard believer in two week sprints. That's another thing that winds me out, is people that read it in a book once, so they think that's what it should be. It's like a sprint is something, and this is why I really loved Agile when I first came across it, was that a sprint is something that gives you a.
and period of time to complete something and a contract between the team and the publisher or the team and the producer. So in X amount of time, we will get this to you. And within that team, everyone has buy in and can be creative to getting that to you in a way that's really cool and playable. And so you can do it in, in console like that, but you've always got to remember that you've got a deadline that you've got to hit.
In every X amount of months to free up the next chunk of money. And, and that's sort of why you can't, you can't slip it and you can't go, Oh, well, it didn't quite meet the thing. Like to, to move a story or an epic into complete, it needs to be everything. Everything's perfect. Otherwise it doesn't go and it goes into the next sprint at certain points in console development, you've got to go, it's good enough now, like boom.
Get to that and I don't think you can really do that with mobile especially for each play You've got to be so spot on 100 percent in the little the little tweaks that you make. Otherwise, it could have massive When you're first starting a new game and you're at the point of discovery and working out what it should be and you're putting a little team together, et cetera.
Would you use agile tactics then? Um, yeah. So what I try and always do in that situation is like, normally somebody will come to me and take, take the golf club for an example. We, we got told, okay. We're gonna want to be the first golf game on PS4. We know EA aren't making one. And I went, okay, cool. I always wanted to make a golf game.
Sweet. So we've got a team together and We'd already been working on a little tank demo to see what the, uh, Unity engine could do and stuff. So we went, okay, we'll use that, the terrain generation. And I set a little tech team and I said, okay, I've got four weeks to a Greenlight meeting. Let's see what we can do with this, uh, terrain generation.
It's tanks and golf clubs. Yeah, I mean, and see what we can do just to generate some golf courses because we weren't, we weren't going to have any golf courses in the game because we had no license money or anything like that. So it was cool. So they, they went off and I gave them a little fun four weeks to go away and play around with stuff and enjoy.
So, you know, we were saying about programs earlier, they love that sort of tech things like turn this tank sim into a. Golf game and let it be fun. And in that time, then I went away and, and create a document with the design team of what. The game should be sort of areas of the game like seven or eight features What then features were what they weren't what the visual guide should be what it what it wasn't going to be So there's gonna be no fire coming at the balls.
It was going to be ultra realistic like x y and z and then we go back to the exec with a powerpoint that says what the game is and what the game isn't and a little cool tech demo that showed we can create golf courses with three clicks of a button um in four weeks this has got potential yeah and then it's like okay nice okay what what can we do next i said well next Give us four weeks again and we'll have the game in play.
So we had a baseball player from the baseball game I'd made before, and the baseball player was hitting a golf ball around, uh, on one of the generated courses. But so I sent it up into four weeks sort of chunks of things that people thought was actually achievable. Because, and what happens a lot of time with two weeks, for instance, people can't see anything achievable, especially when you have sprint plan and retrospectives and all that.
You go, well, it's only actually eight days of development if you're lucky. So. You might as well, you might as well get pushed to a four week sprint in the, in the early stages of development. And then when you get further and further down the line, especially when you're doing updates and stuff, you go to a cadence of two months.
That always seems more sensible. So how do you, as the guy in charge of that, come to a decision during that month of when features aren't going well, when they are, et cetera, and when to cut them and how, how do you make those sort of decisions? How would you advise others? Who are producers to make those sort of decisions?
Well, I, I'm playing the game constantly. It's, it's one of the, one of the other questions that I always ask people. When I'm interviewing them, it's like, what will you do when everything's running perfectly? Because so many producers say, oh, I'll have a meeting. It's like, well, don't have a meeting.
Everything's running perfectly. Like, play the game. Do you know what? I, I have to interrupt you there. I cannot believe the number of people on game teams, generally, not just producers who'd never play the game or who don't really like it. Yeah. But, but just never play it ever. And you go, well, you know, that bit there, no, sorry.
I haven't played it. What? You're a year in. Yeah. And that's what blows my mind. And it's like, that's what I try and make sure that people, people do do when they're, when they're on my teams is that they do play the game. They do enjoy what they're doing and they can see what we do. And like, especially on the golf club, what, what we did once we got to a certain stage of development, we're still very early when we started a baseball player in like sideways and the ball was shooting off on the ground, but we had a Friday round of golf.
Everyone in the team was playing and then we had leaderboards and everyone had to get their code checked in by 11 o'clock on Friday morning. And then Friday afternoon, we'd sit down and we'd play, play the game. And the shame, I'm a big believer in shame. And I'm mostly like not doing myself any favors by saying that if I put it in a book, but like, it's the show, like if you're putting your work in and it's the worst bit of work for the week, it's like, Oh my God, I can't let that happen again next week.
And one of my best mates. Like he was the physics programmer on the golf game and he, uh, he, he'd done something completely wrong that week and he got so much grief for the whole round from everyone shouting across the studio that he wasn't working. He goes, I know, I know. And then the next week he was there till, he was there Thursday night and I remember driving past the studio.
Let's go to the grocery store. I went what's his car still there? So I went in and he goes I've just got to fix this because I can't have the shame of last week See it works, but these days you call shame intrinsic motivation. So you've got a nice american phrase for it So but I think that's true as well.
I remember we did the same thing at playstation home. We We did the same thing on a Friday and, and have, um, demos in the morning and people playing it on the afternoon. And, and it made a huge difference when we instigated that, when we were willing to make that sacrifice. And, you know, I've worked places before where you, uh, we, we haven't had, for example, a weekly presentation demo of the game to the whole team, and then it gets introduced and everybody starts going, Oh, wow, okay, that's what we're making.
And it does make a huge difference, doesn't it? It comes back to the very beginning of this chat. You, you don't want making a game to be. a mechanical thing where people are just going through the conveyor belt of I have made another art asset and checked it in. You want it to be more than that for everybody in your team, right?
And well, yeah, exactly. It's like, I always look, I basically break everything down into either music or football as an analogy. So like, Yeah. Um, so Bruce Springsteen, like when he, when he's writing, make him born to run, he's, he's like, he's not got a lot of musicians in there and said, right, play this note and then play this note and then play this note and then play this note.
It's like, okay, this is my song. Let's go smash it. And then they go and they just like jam until they've got good solos and stuff and they work it and they feel the music when they're playing it. And that's how you get what you want. That's sort of. The way I look at making games because if you've got to feel what you're making if you can't The user when they pick it up can feel it's a made by numbers type of game.
Yeah a clone Yeah, and that's you know what a lot of game studios fall into uh, it doesn't matter how much money you pile into a into a product if you If you haven't got the buy in from the team and the team aren't playing it Then it feels like a paint by numbers kind of game. You were saying a little while ago that producers You Uh, might turn around to you or produce in the past around you and said, why are you producing?
You hate producers back then. What did you hate? What, what was it that produces you have to name anybody, but well, I'd love it if you did, but what did you particularly hate back then? What was it? And, and, or now, what was it that really wound you up that made you think production just isn't being done, right?
My thing that really wound me up, and I made the point, and I actually got a warning for it, was that somebody, one of the production team was criticizing one of the QA guys, and I made the point that you could lock me and that QA guy in a room for half a day, and we'd come out with a game, where I could lock you guys up in there for 10 months and you still wouldn't have any.
And it's just like, It was just a bunch, a bunch of guys that sort of felt they ran things that couldn't really make anything. And I also felt that, especially at Eidos, the production team had a belief that programmers were like magic wizards that made the box talk. And so they, whatever the programmer said was, was gospel.
And it was like, what are you doing? This is not true. And like, they're going, Oh no, we don't need designers. We don't need this. We're production. We can do it. And And so many bad decisions were made. It wasn't until we got a, a new studio manager and I got promoted onto the, onto the top table that we actually made a nine out of 10 game, which was championship manager 10.
So that was the nine out of 10 game. Um, you know, and we had, we had a really good, strong quality team that we were painting by numbers at that point and up until that point. And then we went, okay. We can do this better. And we still had a, like, we were carrying a lot of people that we shouldn't have been carrying, but.
But what were the producers doing wrong during that time? I think, well, one that they had, no, they didn't have a concept of making the game, I don't think. And how to go about it in the way that I would have done, anyway. And I don't know, if I look back on it now, I'd most probably go, Oh God, they were most probably right, because of the experience.
But coming from a point where I was making a game from scratch as a programmer, I With a group of about 10 people and then over a period of six years with a hundred times the budget These people weren't making games as good. It was just blowing my mind. And there was a lot of meetings that were just pointless.
It was like, I remember sitting in a meeting and the first 20 minutes of one meeting was constantly about what people did at the weekend. It's like, I don't care what you did at the weekend, trying to make this game. It was just general chit chat. And it was like a meeting room has been booked for an hour and a half.
So we're going to definitely make sure we're in it for an hour and a half. Right. No real decisions were ever being made. And that's, I think, and that's the other thing, I think was a huge, huge thing with very, very few producers are very good at. is that you should be the person that makes the decision and is not scared of making the decision.
And there's an extreme amount of talent in being able to get a game out the door that people, there's no way of really just like, um, sort of seeing it on a CV or anything, but it's like getting a game out the door. A lot of people get to the point where when they're a game director or or whatever the person with the buck stops at, they get scared and they go, we can't release yet.
We'll just do a little bit more. We'll just do a little bit more, just do a little bit more. And I've seen so many people do it and the money gets thrown away. It's like, just release it. Day one patch, mate. Yeah, exactly. That's my favorite. So again, we're back to this, this, this common point that you're making, which is really interesting.
And I hadn't really, Thought about it exclusively before, but you're saying that at all levels of production from a junior producer upwards, there's going to become a point where you have to lead, you have to make a decision. You, even though it's junior producer, right? Who's, who's been in charge of a smaller team.
There's a point at which they have to say, well, no, you're not going to do that. Or yes, we need to do this. And I think that's probably why that the producers who survived that experience go on to become senior members of a game studio. You need to be the person that's not scared to make a decision. And I think you most probably survive by making more right decisions and wrong decisions.
And I like, and that's why a lot of people, a lot of people don't, don't make the decisions and they survive with a nice tasty career for most of their life because they've never made a wrong decision. And you're going, well, yeah, if you've not made any, any decisions, then it's like, I'm always, I'm always going to be the one that makes it like he's going to have a, have an opinion and make a decision.
I could be wrong. I'm lucky that I haven't made huge ones in the past. I'm normally like pretty, pretty good at feeling what the game's about. And I think that's, that's what, what I say about, um, like holding a creative vision and stuff in the past is that if I do hold the creative vision and the plan, and I'm going to make a decision, I can make the right decision it's when it like.
If you've got a project manager and you've got a creative director and they're both going well one person's got to try and get it out on this date and the other person doesn't care unless it's got x feature there's two people pulling in different directions and it never really works so it always has to be one person that the decision lies with and that's why you've got your game directors or whatever they're called now, product directors and people like that because they've got to be that person that makes the decision.
It seems to me a lot of the roles that have been created in the fledging gaming industry have been created to address the tensions that you're describing. That basically they can see something being pulled in a direction so they just create a role to try and balance it out. It's like creating pieces on a chess board that weren't there before and it seems to be becoming more and more complex, not necessarily for the right reasons.
Yeah, and I think the more cooks you put in the kitchen, the more complex it's always going to be. Uh, and that's the thing is like for every, every person who has a, just like a deciding vote, the more watered down your product becomes. Because, you know, you're trying to give people their easy win and this was one thing I had to learn over a period of time was that, you know, I had to bite my tongue sometimes, um, but I always hated that as I'll just give him the easy win there and then you'll win the next one.
It's like, we're making a game. We should all be making the right decision all the time. I struggled with that. And I still do. I'm very lucky that I've worked at particularly good places, really, I think, over the, especially as a producer, you know, HP, Mediatonic, they're really nice companies to work for, um, that let you, like, don't, don't feel that you have to get your easy win out of the way or you, you know, you've been given a win to do that.
Everyone's pushing in the same direction. So it's, yeah. Like handy in that respect. But yeah, it's like, I just, yeah, the more people you have, the more it waters it down in my opinion. I think if you've got one man's vision, one woman's vision, and that person should be the person. They don't have to own everything, but everyone should be created within the pillars of what's been set out.
But the final decision needs to be made by somebody. Yeah. Okay. And I, and I think if you look at any kind of leadership training or model leadership training, the death by committee thing is, is, is pretty much always, um, is always spoken about as something you want to try and avoid that strong leadership is is something where you you're kind of extolling the virtues of everybody on your team but you're also the person they know they can trust that when the shit hits the fan you go i'm making a decision and not only that i will back the fact that it was me who made this decision i'm not going to stab you in the back with it there's so i think i imagine your style would lead um if it's consistent to people trusting you quite a lot Uh, definitely I think, I think most of the people that I've ever worked with will always work for me, uh, work with me again and would always recommend me for jobs because of that.
Because I'll, I'll always back them. Uh, I've never thrown anyone under the bus, you know, if, if I thought something wasn't going the right way and they were making bad decisions, I would make sure that I got there first to stop that from anyone else seeing it. Um, and then if I make the decision that everyone else is not happy with.
Doesn't happen very often because normally after a discussion we, you know, we come to a conclusion, you know, I'm not, I'm not the person who goes, Oh, this is what it should be. It's like, I come to a decision and make the decision off of the back of a conversation with everyone. Then you go, I'll live with that.
I've made that decision and I'm going to be the person that lives or dies by it. Because that I think is one of the biggest parts of the job. Do you think that's where producers are accountable to communicate properly and to, and especially at a senior level to communicate to the team what's going on?
Definitely, like I know from my personal experience saying when I was a lead designer at Eidos there and you're writing 50 page documents that you knew nobody was going to read, it's like you're sitting there and it's just like, I stayed there because I always wanted to make that game and I loved making it, but the day to day of the office was like half of what you were doing just felt like it was pointless.
And. And it's the reason I got into production was so I could I could stop pointlessness happening on On development teams, you know, do I succeed? most probably not like when you've got a team of 60 70 people sometimes and Publishers are asking for stuff that you know is not going to happen but It ticks a box to keep them happy, you know, a little bit.
It's like, okay, you've got to do it. And sometimes, you know, the decisions are made, but I try and reduce it down. You know, I constantly look around the room and go, people are looking bored or they're looking upset or agitated. It's like, okay, we've got to make sure that if that's the case, then they're doing something that they can really enjoy.
Because, you know, we say that people, people do it for a reason. They want to make games for a living. I was going to say pick one game that you've worked on and tell us what you were responsible for and how you've, you've picked the golf club. Do you want to tell us a little bit about that? Yeah, so the golf club was, as I said, we, um, we knew that the Tiger Woods game wasn't coming out on the PS4 and the PS4 was just about to come out and we weren't, everyone buys a golf game.
I remember the head of studio said, let's make a golf game. So yeah, so then we went off and we decided we would try and make a game. Like I remember picking up The Tiger Woods game and I put it in the PlayStation. I don't think I got on the first tee for about 20 minutes because it was just so much going through with Fatui and update downloads and everything else and it was like, this is horrendous.
I don't even want to play it now. Um, and then I played around and I got a hole in one on the 18th hole of the first round. And I went, this is nothing like the golf I've played. We knew we didn't have any licenses. Originally we said, okay, we'll make it a three click through from the main menu or auto generate a course and you play it.
We, we overachieved so quickly on the auto generating of golf courses that we started adding feature by feature to that. And we had a little pod of people working on that and We just get, okay, now let's see if we can place bunkers. Let's see if we can do this. And by the end of it, into the whole product, we had such a great course creator and then the ability to share cross platform.
So you could make one PS4 and it would come out on the X Box or PC that people were making Augusta. Pebble Beach and all these other famous golf courses that we didn't have the licenses for, but it didn't matter because people made them, we didn't. So we had all the licenses that were coming out. Plus my point for the game at the beginning was it should have been a game for the everyday golfer.
It should represent what we were doing out on the course. So I'm like one of the worst golfers in the world ever, but I do enjoy going out there. I say I enjoy, I enjoy the idea of going out there and then I get out there and start throwing my clubs around. So I we should be able to. Play the game with thought processes that go through your head, but without the skill needed to make the ball not curve into the woods every time you hit it.
So that was always the mantra of the game, and it would be good to play on home style courses. And there would be one level for all. There's no difficulty levels, no options to turn certain things off and on. And the difficulty was by choosing the course. So if you choose a really hard course, that means you've won a hard challenge.
And that was the way it was. And then we got all these golf courses coming by the community. It blew up. EA released their game. I think it had eight courses. And by that time we had 147, 000. And they ran into the distance and never released a golf game again. And then, yeah, the Golf Club Court picked up by 2K.
So 2K are releasing it now. And I had a vision for what it wanted to be. It was shared with the head of studio at the time, Jeremy, who was also a big golfer. And he, he wanted to make a hard golf game as well. So that was sort of shared. But what we, what I did, I think the biggest thing that I added to that project was that a lot of people came on the project going, Oh my God, this is going to be an absolute shit show.
What are we doing? Why are we doing this? And I got everyone bought into it. Until we were the core project in the studio and everyone wanted to be on it and we were having fun. There was a lot of laughs. There was some overtime as well. But as a team, we just really bonded and everyone knew what they were making.
And I got, I got some really good people. I got people that were thought of as being average to become superstars as well because. of the way that they were allowed to, um, work, which was nice. I think that's a wonderful thing to be able to look back on and recognize in any career, isn't it? Can you give me any, any examples of how you did that with anyone?
Well, I think it's just the fact that I got, because it was our own project and it was self published, I didn't need to please a publisher. I only had to please The head of studio is funding it with his own money. He's of a similar like mind to myself. He's, um, he's the guy that wrote Emily and Hugh's Soccer on the Commodore 64.
So he's more old school than myself. Um, and he was just, he just wanted to see the game monthly and it getting better. And him to be able to give feedback on it. And, like, we built something for him that he could play around with after a month and he was stuck in his office. He didn't move from his office for, like, the whole time of development.
He was building more stuff, only to come out and tell me more bugs he found. But he loved it. You know, and without him, he had an amazing eye for art, which I don't have. And without him, our game would not have looked as good. Without our lead artist, Jim O'Brien, it was amazing as well. So it was, like I was just saying, because there wasn't any publisher or anything else, it meant that I could just get to the nitty gritty of making the game, and letting people be creative at making the game.
So it was like, okay, here's a group of you, you're on the course creator, you're doing that. Let's say, three weeks, let's try and get x, y, and z in, see what we can do. Okay, do I need a tech, uh, tech document? No, don't worry about it. Just smash it in, like, and we'll see where we are. And if we don't like it, we'll scrap it.
And just really quick, iterative, fail fast development. So we got rid of design docs. You know, we had a confluence page where the designer would sort of fill out what, We sort of had discussed and we go, okay, we want this feature to be that when this feature to be this. And then people just work together as a group.
And that was my point to a lot of the other producers at the time. I go, that is scrum development. When you see people sitting around in a huddle and literally, yeah. And it's not standing there in a room with 29 people going yesterday, I did this. And today I did this. It's like, there's nothing more boring.
Like, and, If I find something boring, I think, you know, I'm touching on ADD, I think, most of the time, because if it, um, my attention cannot be held for more than five minutes. If I find it boring, then it's normally cancelled because everyone else must be finding it boring as well. That, that is scrum development.
I think that's, once people got into that, and they could work as a team, and they could feel, oh, I'm programming, To do this i'm not just doing what this tech design document told me i had to do They became superstars because most people that said they're creative people and they weren't there to just try and please um Like their bosses and work through a document and that's I think one of the things big problems with british education system Don't even get me started there but it helps people work in a A way that they work x y and z and it doesn't give any hope to anybody outside of that And if it wasn't for me getting my shoe in the door, I'd be Amazon, like, shift worker now, like, if I was lucky, you know, and I try and make sure that people with the same kind of skill sets as me get the chance to show off them skills.
I can see why people would trust you and want to work with you again, with that sort of attitude. So how much of your job was project management? What form did this take? I was the only project manager on the golf club games. So I was a producer, project manager. We did have project managers, but I think I got rid of one to free up the budget so I could get another programmer.
Very common, I find. Yeah. Yeah. Um, so, and as I said, because we didn't have the, um, publisher syndrome, I didn't have to show off a load of burndown graphs constantly of how well we were doing. I just managed, managed the team. As simply as possible, we endure and just said, okay, these are what we're doing. We don't need like, I don't believe in the healing power of graphs.
I don't care where these things are going out. This is just a brief set of epics of what we've got to do. This is the backlog of where we are. We'll put some estimates and story points against it and we had a cut line. And we constantly say, we go, okay, bang, bang, bang, bang, bang. We're mostly going to get to here and that's where it is.
And then when other features would come in and we go, okay, we, we're going to do this. Is this more important than this? And then it was basically just me, the head of the studio and the COO would sit down monthly and go, if we want these things. That means these things are going to drop or we extend the time and the team the same way.
It's like, okay, well, I'd like to see this extra feature in, okay, we can fit that in. Is it more important than this? Yeah. Okay. We lose that. And everyone had a good concept of this is what we're going to release with. And do we want to give it extra time? So that little triumvirate of, of people making those decisions was that work because of the closeness to the team and the, and the communications.
Cause I can imagine in some, In some game companies, in some game teams, there's no way the people, a couple of people at the top, really know what's going on, right? Um, well yeah, like if you go over to EA and stuff, the people at the very top, but then my, my belief is that should they really be making any decisions then, it's like, that the only decision they should make is, more budget, more time, or it's coming out, you know, and then they have to rely on the people that have got their hands dirty, really on making a decision on, on if it's good enough to put their name to it.
That's what was very good at HB is that the COO was Really cool guy could see the game was good. Um, really solid, but he wasn't getting himself involved in, in, in creative in any way, just saying, this is the money we've got, we can continue doing it if we want to do it. And the head studio owner was like, this game is really good.
I'm really enjoying it. I'm playing it in my office all the time. Keep going. And I want to add this feature and I want to add that. Right. And so, alright, so two things there. Firstly, what it's, I take it because he's a good guy, it wasn't a big problem when the owner wants to add to a feature, but it can be, right?
Yeah. So that's, um, that is an interesting one because he, he always had opinions and not all of them were right, you know, there was always an interesting conversation. Like at the end of the day, my, my thought is always, it was his money. Yeah. And if he really believed in it, he's, he's going to get his way.
I would always go about it and tell him that I was looking out for him and his money and the game and the team felt this and we all felt this. And should we do this and that? And he would, he was a good guy, listened and he said, yeah, okay. And you know, 50, 50, either go, okay, I'm listening to your half time going, no, it's going to my decision.
And it's like, okay, if you want money, but that does mean you lose these things. Yeah. Thanks. And as long as you can make them things clear, I think that's, that's the, your job really at that point is to go, if you do this, it's going to cost you x, y, and z. And if you can always make that argument clear.
then the decisions on them. It's funny, isn't it? I think as a producer over the years, you become a bit of philosopher around the concept of sacrifice and how everything costs something and it's only finite. As you approached the point of no return in terms of shipping it, or in terms of just deciding to go live at some point, did tensions emerge then about how it should be another six months?
No, we've got to get out now or anything like that. How did you deal with that? No, I don't, I don't think there was, there was a, there was a tension that we had to be out by a certain point. We, we'd gone, we'd gone a little bit long and we did want to come out before anyone else. Announced that they were doing a golf game.
So there was that, but we had our set of features and then there was like, we dropped a couple of new extra things that we thought would be really good. Tension wise. No, there was, there was like, I'm presuming some heated discussions, um, as there normally is, but like, it's like, this is what it is. What happens and then yeah, we did we did some overtime.
We did quite a bit of overtime I think it was about three four months We knew what the cost of that was going to be and everyone was happy with the cost of that. So How how I should have already asked you this really but how big was the team team was about? What was it at that point? It was around 30, I think okay.
So what's that about four or five pods? Um, yeah, it would be about that. So we had um, you know course creator. We had gameplay team we had the server guys we had the um, What was the other things? Yeah, game plays, physics. Yeah, so the physics team was all by itself as well. Uh, I asked that because I'm just wondering and you know with 30 people, I guess it's it's easier for me to envisage that you really could do, you know, the way you told me about planning and scheduling, et cetera, I can really see that how that works.
Um, with far larger teams, I imagine, well, we know, right. There comes a point where planning's not that easy, where you have these kind of disciplines running into each other and methodologies running into each other and insourcing and outsourcing and all this sort of thing. How, how much How experienced have you got with the sort of the, the, the bigger teams and that kind of complex scheduling?
And can you give an example to starting producers on what to expect when they hit that kind of next step up? Yeah. So like, yeah, so you'd always like, especially when you get to like teams of 70 to a hundred and stuff like that, it does, it does get more complex. But as I said earlier, it's like, I always try and simplify things down.
So it's always in edible bite sized chunks for mine. Brain to understand. So what I normally have is you have your pods set up and you have like a sort of mini backlog for each of them set out and go, okay, these are the things we're going to do. And then you have sort of semi leaders within them. So it might be a producer, it might be like a designer, it could be just a programmer.
Anyone I felt always had the, the most vocal like aspect of that feature. And it was like, okay, we're going to do that. You, you run it for the next X amount of time. A mini vision holder. Yeah, and that that would be the person that you go, okay, do that. You own it for the next X amount of time. Go off and run with that over the next set of like months.
We need to deliver this and this and this, and by these times, each week, I want to see whatever it is in the latest build, we play it, we all comment on it, but this is the date we've got to get it done by, and I think, like I said, it simplifies everything down, like, I'm never going to be the guy that gives out a task to everyone, I don't care if everyone's 100 percent flat out or 80 percent flat out, I don't care, I'd rather people be 40 percent flat out, 40 percent not flat out, and playing the game.
You know, as long as while they're waiting for someone else, I don't care if, if one guy is sitting there doing something or not doing something and he's going, well, I'm about to pull in some more tasks from something else to keep myself looking busy. It's like, I played the game, play the feature you're working on, make sure it feels right feedback to it.
And so that makes planning a lot easier because you're not micromanaging exactly what people are doing. You're just saying as a group, make this for me in X amount of weeks. How do you deal with dependencies? Um, As in this feature is going to have a knock on with this feature. So, so I guess in this case, the cross pod dependencies to invent a new term.
So where one team's going to have an impact on another team or one team's waiting for another team. Do you just deal with that in a nice, simple, simplistic fashion, or have you got a system you can share? Um, no, not really a system. It's normally what you'll do is I'll say to. To the guys, if there's something they're working on, say it's like an API or something, you just go set up like a little black box of emptiness that has got the outputs of random numbers for the time being that you can plug into.
And then when they finish their work, it will plug in and work. Or you just say, well, if it's not just not going to work, we go, okay, park back there for a little bit, go off and do this as a group. And then once this stuff's done, we'll come back around and circle around and get it. Let's say you're relying on an art team to supply a bunch of different pods and, uh, if that's how it works, would you rely upon a, a producer to, like a more junior producer than you to, to look after that particular aspect?
It depends on, on previous experience with the producer. I'd always give them a few goes at it, um, and then see how, how, how well they do. But. Most of my pods always has an artist on it, always has a QA on it. Always has a couple of programs on it. So as a group, they're making it as a game like feel. So it should feel like a game jam team.
Yeah. Really. So they're working as a group together to, to do something. So there should no be, should never be a dependency on. a skill set, it should always be on a feature. Okay. Yeah. And that makes sense with, with agile and the way you perform teams. And I like the use of the game jam. I was thinking about that earlier with some other things that you said.
I think that that approach naturally leads itself to empowering the creativity that you spoke up at the beginning, right. With, with people. So a lot of people actually get a bit scared when I say that because they go, Oh, but game jams never work because the game always falls apart. Like really easily.
It's like, well, you don't Use the quickness of a game jam, use the, like the mental sort of how you get into a game jam and go as a group, we're making this, but you know, you've got six weeks to do something. So you're going to do it right. You're not just going to rush it out the door. And I think maybe back to what we were saying earlier, or maybe I was about personalities.
I think there are a lot of people in the games industry who have picked it because not just because you make games, but because they don't really want that kind of added responsibility. So I think you probably do terrify a few people. Yeah, and I think, you know, I'm a believer in you got to take a jump off the deep end sometimes and, you know, and find out you can do it, you know, and I'm never gonna let anyone struggle.
If somebody looks like struggling, we'll make sure that they won't do that. But I want people to try and show me. All the things that they in their head would love to do, but haven't quite got the confidence because that's when they'll get confident. Yeah, that's, that's, that's where growth lies, isn't it?
Yeah. So can you tell me about a time when the planning failed and you had to step in and sort things out? How did you do that? When the planning failed? Hmm. I think, I think I'll go to another project for that actually. I've done, um, I've done a couple of free to play games with the Major League Baseball guys over in the U.
S. We massively underestimated how many people we would need to do it. There, there are very demanding client, um, majorly baseball, gaming group. Um, but I'm really good. Top bunch of guys are still good. Great friends of mine. Um, if main guy over there ever in London, we normally meet up for a pint, but yeah, demanding of what they wanted.
Their demand, their demands are on them because their bosses are putting a lot of pressure on them as well. And yeah, we, we went about, uh, We signed, signed two games with them and we just didn't have enough to do the two games, really. And the plan I'd set out at the beginning was just like, no, this isn't going to work.
It was our first ever title in unity as well. So we were learning that. Right. Yeah. So we made the home run derby game, which is amazing, by the way, if you've got to download it, um, on, on the phone, um, looks amazing. Um, but we had a sort of semi management game where you, you looked after one player's career and built him up through the thing, which I absolutely loved and played with it.
looked horrendous and yeah, I sort of rushed out in the end just to meet a deadline. How did I fix it? I basically just begged and said, look, we're not going to get it done on time. We need more time. That is one of the massive problems though, isn't it? Of, um, being given a lot of responsibility and kind of inheriting it by just being promoted to a position where you're in charge of a game, that you're given budgetary responsibilities.
You're told to make things happen by a certain deadline. And almost inevitably, because it's life, uh, money gets cut, time gets cut. Um, remarkably, you don't normally get more money or more time. And there is a kind of a gray area where you just have to sit there and go, well, all right, we'll do our best day, see what happens.
Do you think that's a natural part of, of making a big game? I think it's more about the big games or all the high profile games. It's a strange one. I worked at a place called Asylum. Absolutely shocking place. A guy called Simon Bailey, uh, ran it. Refused to pay off his staff. He, uh, they used to, they made a Doctor Who game while I was working there for a few months.
And, um, they'd done it in like six or seven months. And Then he went off and I think they go and sign another game and go, okay. Um, that was, uh, we've done the last one in six months, right? And we might, we can do this one in six months. So we didn't, you don't in 12 months, it was just in six months, actual time, but you don't double well as every day.
What was really good when I went to HP and they're based in Nova Scotia, Nova Scotia law means that if you work over a 40 hour week for every hour, you worked more. You got half an hour back until you got to 50 hours, I think. And then you got an hour for every hour back. Um, and that really puts the pressure on the company to make sure they budget correctly.
Because what happens, and it works fine as well, because like, one of the things when we get to golf club is that we did like a ton of overtime. We worked till 10 11 o'clock every night for three months, but it it came at a cost in the fact that all of us were out for Six weeks after that, um, and we couldn't come back into work, which was great So the company knew that and they go it's worth that cost and everybody that works on the game Loved it as well because I don't mind putting the effort in in a nova scotia winter when it's minus 30 For me to have the whole of June and July off when it's nice and sunny enough to go to the beach in 30 degrees.
So, and so everyone else felt the same. So it's like, if things are working like that, and you know, the cost, it's not too bad. It's, you know, there's a lot of, I'm, I'm anti crunch in the fact that I don't want people to think it's free work for the, For people's passion. I think that's completely wrong sacrifice again, isn't it?
Yeah, but again going back to the bruce bruce ringsteen's born to run is that you don't make born to run going For nine to five, you know, it's a passion that you know you you go Okay, I want to stay late because I want to get this thing right and I want to get this right and as a team Bonding thing it works really really well as well.
So there's a fine line It's making sure that people want to do it making sure people are excited to do it and making sure that you Get reimbursed for doing it You know, and, and the thing is, it's got, it's got to the point in the games industry now that crunch is looked on so badly that if somebody's done five minutes extra, it's like, I'm not crunching, it's like, that's five minutes extra.
Can I ask, just, if you're a new producer and, and particularly looking at your experience, do you have any top tips for how to form good relationships with your teams and, and particularly with discipline leads? If you maybe not have had the same background in design and code as you? Hmm. It's, I don't know.
It's, it's one is. Try not to be too chummy and it's it's like I don't know it's a it's a personable skill. It's funny like I employed a Lead programmer several like years ago. So five six years ago, and he was so desperate It was his first chance at being a lead. He was so desperate to Have everyone on his side, everyone just have just wound up by him because he was like, Oh, yeah, I'm your friend.
I'm your friend. It's like, it's creepy. Yeah, it was. It was like, yeah, very, really creepy. And I had to have a word with him going, Look, just be yourself, man. It's like, but yeah, I'd say be yourself. Make sure that you know, you're bought into the game. Um, be nice to people ask, especially discipline leads, like their views and thoughts and things make people feel included.
In the game and once people feel included and they feel that you're helping them out They'll be on your side, you know, and that's one of my things of always what is a producer a producer is somebody who's like holds the umbrella to all the shit that's coming down from above and has the like a big snow plow that plows all the risks out of the way.
So it's just like seeing what's coming down the road, make sure that everyone can just continue working and not be bothered by pointlessness. How much of production is is what you've just described and how much of it needs to be At least a competent grasp of project management
Interesting because maybe people would say i've not got any grasp of concept of project management Um, I would say it's I don't know 50 50 60 40 maybe It's strange because I don't think I'm a particularly good project manager, but then a lot of the studios I've gone to have all gone, Well, you know a load about project management.
I think, you know, my life is made easy. I'm a, as I said, I'm a programmer, so I'm a lazy man. I'm a lazy producer. I'm going to do things that is going to make my life easier so I can play the game more at all times. The best asset you can have as a producer if you want to be really good is to see the amount of risk coming down the road and de risk it before it even becomes an issue and that anyone's even seen it.
I'm so happy to hear you say that. And I've written some stuff on risks and issues because I thought that was the most important thing to write as a, as an opener on game production. com was like, you need to understand risks and issues guys. You know, I know you're joking, you're calling yourself lazy. I would call it lean.
I would say what, what you're actually describing is you wanna reduce waste, right? You wanna make sure that people are only doing what they actually have to do if people are working until midnight because they want to, 'cause it's fun for them. 'cause it's it giving them something you wanna at least know that your producers have given them a bit of work, which is actually gonna come out and, and is actually a sensible thing to be working on.
Right. And I, I think. That level of project management, I can, I can totally understand that producers need. I've worked in places which have got separate project managers, which I didn't personally think worked very well. And I think from, you know, going back to what you were saying about it being poor, it pulls people in different directions, doesn't it?
Yeah, and that, and that's the thing and what it works very well for me now at Mediatonic actually, um, I've got, um, a producer working with me and she's more project manager based than myself and she's like on the button. You can ask her about anything and she knows exactly what it is and what percentage it's through and it's like, and it's great.
Like, and she's, she's completely bought into what I brought in and I. Think like she's she's amazing at the amount of stuff She's got in her head at the time and she can run it And then I do all the things That she doesn't want to do as much where like I deal with a publisher and uh, I stop all the issues so she can continue to project manage And the team can continue to work and I think that's working really really well But it's not worked.
Well, a lot of times i've worked. This is mostly the best relationship i've had With a co producer stroke project manager. Okay, interesting So just um going back to the golf club briefly, uh, just finishing off a few questions there What was the hardest part of making that game the hardest part from a production point of view or from a just a?
This is a really hard game I know, actually, I do know it. Cross platform on Sony, Microsoft, getting that, um, meeting happening. Because we were the first company to do it. Were you? I had no idea. Yeah, and I had to really set that up and like, Microsoft were like, no. And then Sony were no. And then I think I said, one of them had said yes.
And then I wondered, yeah. I can't remember exactly what happened. But yeah, we, it was, it was coming like how we were going to show usernames. Yeah. across the thing because some people could be called the same name that weren't the same people. Um, stuff like that. So we, it was like, we just go, I think it was the golf club user, if you weren't a PS4 and the same if you weren't an Xbox Live person, they've made another platform.
Just, you've made me think now about QA because just because I've worked with um, both Sony and Microsoft QA teams being kind of shipped in at the end to see if they can find more than a thousand bugs in your game. Have you had that kind of experience as well of working with external QA teams? Uh, yeah, done quite a bit with external QA teams as well.
Um, yeah, like I always, one of my big things when especially when I'm working on a console game is to make sure there's enough in the budget to get it. a top, um, compliance QA team in, because it's like, I know when I was at team six, they couldn't believe that we passed, I think, second submission. And the only reason we had to submit a second time is because there was one bug, um, that was stopping us.
And they were going, we normally have to do like eight or nine. And I was like, just get these guys. And I, you think it's going to be expensive, but in what it saves you. It's cheap. I detected a healthy respect for QA when you were saying a few things earlier. Is that correct? Because I know, you know, we all know, right, that QA don't get the love they deserve.
Yeah, well, I always say this because I always say there's no bugs in any of my games who have put QA on them. But, um, but yeah, no, there, there is a vital part of the game process as anyone else. And, and as I said earlier, it breaks my heart that people who are really, really good at it. feel they have to get out of it if they really want to, you know, there's a, there's a set few jobs that you can earn a decent living out of it.
You can't just stay in QA and be good at QA. Like you could be good at being a programmer or good at being a designer. Um, final question about the golf club, if I may, um, if you could have gone back and done one thing differently, what would it have been? Could have done one thing differently on that game.
It was near perfect. Um, good answer. Yeah. Made it more perfect. Yeah. It's like, I would have liked, like from a production point of view, like, I think we got it just right. Like I'm. We chose the right decisions. We, we, you know, we wanted multiplayer, but instead of going down the route, where we'd have to get a ton of QA and do all the like, um, Sony and Microsoft multiplayer stuff, we, we created an ability to, to record ghost ghost balls, to record the ghost ball.
And it showed it like a second later, but it still looked like it was live. No one ever knew, but you weren't live. And it was like, Sony were going, no, you haven't, you can't do this. And again, we can, and again, Oh, you can. Yeah. And things like that. We were, we were smart. I had a good, really, really good tech lead.
Um, and he was very clever guy and, um, we were smart about how we went about them kind of things. We were really lean. We got so much out of the small budget that we had to be able to get like eight, eight, seven, eight out of tens. Um, my biggest mistake was leaving, leaving after golf club two because I thought, uh, it's run its course now.
And it seems like it's got even better. Run its course. Good one. Yeah. Boom, boom. Um, that's interesting. I wonder how much is, is a direct result of your approach to the pods and the creativeness that you foster in teams that you did manage to keep it lean, and you managed to keep it that people were coming up with these sort of really dynamic, interesting, uh, solutions to problems, right?
That maybe if, if they had felt they were under the cosh, they wouldn't have even bothered thinking about. Yeah, definitely, like, not to blow my own horn, but, like, the original budget and what the original idea for the game was was, as I said, three clicks, golf course, you play it, and that's what the budget, plus, I think, half a million extra for the extra features that we went for in the end, um, we got a huge Golf game that beat EA's Tiger Woods series that basically buried it.
So that was, that was immense and it proved justified. I felt justified in the way I managed the team because a lot of people thought that I was, I was wrong at the time. And then that gave me huge amounts of confidence to go and do that in other places. Why did they think you were wrong? Well, because I wasn't doing it by the book.
You know, I got in and I canceled all the daily standups like I always do. And they're going, well, you've got to have daily standups. It's like, why? Well, because the book said. Scrum of Scrums? Where's your Scrum of Scrums? Yeah. Were you able to do that with Championship Manager? Because of course that, you know, the reviews for that were like, this has come up with so many great new ideas, and the way that this game has been designed and carried out, it's, yeah, it's a challenger to the biggun, and, you know, it was seen as saving the franchise, wasn't it?
I think, I think what we did with Championship Manager, and some of the good decisions that were made that weren't part, of my stuff was that we went from the very beginning and built an extremely solid bass game and That allowed us to do things that when we got to the point where I was the lead designer, the things that I wanted, like a free kick, uh, set piece creator, training drills, things like that.
Um, they were a lot easier to do with the, with the tech that we had. Where our competitor football manager still to this day hasn't got it because I know that they struggle because the tech it wasn't built in a way that allowed them to do them kinds of things. And, you know, every, every year I smile when I see football managers latest, um, latest feature list and I go, Oh, there's one of mine from 2004.
You know, and it's like, I think, I think a good, a good start. You know, well, well thought out tech plan at the beginning of that, that project. And then. me getting there and, and having some ideas, you know, it was a group of us. It wasn't just me, the group of really big football fanatics and football management fans that were creative, um, and wanted to push, you know, and we did some cool stuff, you know, and I think that's what helped it.
I don't know. It wasn't definitely the way that production was run because It was strangely poor. That's why I think it could have been even better if I think we most we would have hit that goal, maybe a game or two earlier if we, if we'd done it right. Yeah, so it's kind of like you were fighting your own battles internally as the lead designer, but not in the position to do much more, right?
Yeah, exactly. I spent, I used to go to bed with a headache, dream I had a headache and wake up with a headache. It was shocking. All you want to do is play football for Manchester United. Yeah. And I did learn a great deal from the senior producer there though, in the last year, because he was so bad. I mean, this, this, this, He's an easy job.
I can do it better than that guy. So I really am fascinated. What, what, what gave it away that it was so bad that what, what the He was ultra aggressive. Um, I remember interviewing people with him and he, it was the most uncomfortable thing. He'd just stare at them to see if they'd ramble. He, He sort of semi chased me around the office once to have a go at me because he'd been undermined in some way and he didn't like, and he was sort of chasing me around the other like he was going to have a bar fight with me.
It was like, mentor that guy. Everybody hated him. Like it was, it was just like, you're not, you're not doing what you meant to do. You're not making the team bond together. It was, I think he, he saw it as his chance to be king of the world. He was trying to, and that was, that was the problem. And that's what you can't do because that's not, You're, you're in charge of the project, you're not the boss of everyone.
I think that's what people need to understand. And you've got to nurture them, haven't you? Because there can be a lot of burnout when you're heading towards those midnights and all that. Dying breed probably, right? Yeah, I just don't, I don't think you can get away with it anymore. Right, I don't know what it's like at some of the old school places, but like, I know like Mediatonic would just not never allow that and it's why it's one of the nicest things after me spending the year at Imagination doing stuff with Jaguar Land Rover, it was It was great to get back to Mediatonic and just like, oh, so nice.
Everyone is nice. Everyone's lovely. It's a lovely place to work. And you just don't get any of that, that sort of just, yeah, bullying. It's like, no, no one's really bullied. It's like, everyone's been given the chance to do their job and to impress. And that's what you want. With a minimum of politics and backstabbing.
That's all you want. Yeah. Stay in the games industry, kids. Just make sure you choose the right place. I'm going to skip a lot of the, the rest of the production questions and career advice, because I think you've given a lot of career advice. And, and, uh, there, there is one that I like though, which is what, what are really bad recommendations that you could give producers, like what have, what have you heard producers being told that you would go?
No, no, no, no. That just, you don't need to know that. Well, what's really bad advice. Yeah. I think the thing that I always laugh at and, and point out to young people not to do is if I see it's like micromanaging, meeting, meeting, meeting, meeting, and it's like, you'll see it like I've been at studios where you see, um, You sit in there and you see the producer and what's happened and I think that this is how it normally goes is They've got like a imposter syndrome about them.
They've been put in charge of something. They're worried that they don't really know what's going on and Instead of just being relaxed and calm and going, okay, I've got the people here in my leads that are trustworthy and can get the job done. Everyone here has got a skill that they can get this job done.
It's like we got, we're going to panic. And then you grab everyone to constantly get status updates at all points until there's no status update because nobody's done any work because they're constantly sitting there telling you the status updates. And one of the most important things, and this is a, The good thing about being a programmer is that it takes a long time to sit down and get your head in the right mindset to code.
And then when you're coding, you're in a flow. And then if you stop that person from coding to get a status update. They then lost for another hour. So you are losing chunks and chunks of days every time you do these. And that I think is a big thing is let people sit there, get on with their work and keep their flow going.
I think that's huge. It almost, um, kind of makes you think that. Producers should just be able to go to a place and, and get kind of like advice on the different personalities, the different departments and how people work, like when, when and when not, and how and how not to interrupt, et cetera. I think that you're quite right with the coders.
I think that's a huge thing. I've known producers in the past that I've had to stop who do exactly that. They're walking around desk by desk going, Oh, hi, I've been asked to get an update from my senior producer. What are you up to? What you've been working on? How's it going? How many hours you've got left?
Well, that's more hours than you had before. How many hours have you really got? But why has that gone up? And, and it just, just winds up coders so much, doesn't it? They just want to, yeah, that's one of the reasons. One of the reasons I love story points. is because it takes, you don't need that how many hours you've got left.
The story points are only burnt once you've completed the story. And it's like, they're burnt now. So I don't have to go around and go, did you do eight points today? Like, does that make any sense? So you, so it gets rid of that. Again, another lean or lazy, whichever one you want to choose, way of doing things.
It's like, there's nothing worse than seeing a producer going around saying, I'll update your tasks in Jira every evening. I think we're going to brand Lazy Lean right now on this podcast. Anthony style of lazy lean. I like that. Just going to write that down. Done. Right, that's ours. Why would anyone want to be a producer, do you think?
That's a good question. Um Let me interrupt your answer to say the reason I'm asking you this is if you look at people's first choice in the games industry of a job, no one says, Oh, do you know what? I'm 18, 16, whatever. I'd really like to be a games producer. That sounds like a great job. I say no one, but I think the I think hardly anybody thinks that way.
They think I want to design a game. I want to be doing the art for a game. I want to be doing whatever in the same way that they don't think about going into QA. They, you know, no one goes and says, I've done a design, I've done a degree in QA so I can join the game industry. I think with production, it's the same thing, right?
This, I mean, there are no degrees in doing whatever for production. So what's the appeal? Why would somebody sort of sacrifice other choices and become a producer? Or would you say from your experience, don't bother me again, go and get some experience around the games, actually doing other things first and then become one.
I personally enjoy it. more than any other job most probably available in the games industry at the moment. I love it. Like, if I can go back to my days at Anko and program, produce, and design all at the same time, that's what I'd want. But that job doesn't exist anymore. Um, but, like, to be able to run with the game, Like, and be the person that everyone goes to, to go, How's this game doing?
Is it running well? You're in charge of it, make sure it's good, blah, blah. And, and put, like, I enjoy the pressure. I enjoy the fact that when the game comes out, you go, Okay, I made that. I don't know, why wouldn't you choose it? It's like, is it, I think, I think you've got the most amount of fun if you are personable and like, To be dealing with people that are going to put a bit of pressure on and you can, you can protect your team.
I mean, it's a bit like, why would you be a football manager? And it's like, why would you take that pressure on dealing with the media and dealing with players and dealing with all the results in the crowd? Well, you know, sometimes you make a great game like the golf club and it's like, Hey, and then other times you make games really bad and you go, Oh man, that was me.
Um, but yeah, it's like you have a chance to do something and touch, touch everything. Like if you, if you improve the way the game is built, From a methodology standpoint and the game becomes better because of it. That's a huge, huge bonus. I think, you know, and the other thing is you, you only see people leaving with a smile on their face because they enjoy working with you.
It's always good. Thank you. Thank you. That's a lovely answer. And, and so what's next for you? Is it the shed MMO for your dad and you to work together? Um, that's a, that's a good thing. Um, I don't know, really. Um, career wise, I'm quite happy. Uh, Mediatonic, you know, I'm, I'm in a sort of lucky position that I don't need to strive for the stars.
I just like making, making games, you know, I'm not, I'm not out to be king of the world. Um, so I just want to keep making games and having fun, really, and Okay, I get to do that, so. Dare I ask, uh, and I don't have to record this bit, I can get rid of it if you don't want to talk about it, but you had mentioned a book.
Well, I did, and like, the thing is, my book would be, would be very, very lean, in the fact that it's, like, the process that I come up with. Yeah, it's, it's like, I don't, yeah, I don't even think it could be a book, because it, like, Talking about what we have done is like I try and I take our jar as a base and then I cut it back and it was always given the the code name zone processes where it sort of came back on the golf club properly.
But it was keeping everyone in the zone and that was what it was all about it was making sure that people stayed in the zone, there wasn't any meetings outside of the core working out most people just stuck to it, and I used to spend most of my time in the kitchen. And then get status updates and everything from people when they were getting coffee because that's when they were already out of the zone.
But as soon as you put something in the calendar for someone and you, and you go, you've got a meeting in half an hour and then you finish the task and they go, okay, I've got a meeting in half an hour, there's no point in starting another one. And then that meeting goes on and then you finish that meeting, you go, well, lunch is in 45 minutes.
At that point, you're really starting anything now. So you've lost nearly a whole morning where if you just stand out by the coffee machine and you grab them and you go, okay, I was thinking this and thinking that. They'll go, okay, yeah, yeah. They've had the whole meeting that they thought they were going to have in 10 minutes, sit back down, boom, they're away.
And so I was going to call it the zone process and sort of write a process around that. But I don't know if it's possible as I said, it could be a pamphlet. That's what's next for you. Um, I'm quite personally gutted that there's no shed MMO on, um, You never can tell. So I'm always messing around in unity in the evening.
So I've got a little, so, um, like over in Ireland, there's this little, um, old card game, uh, called 25 that only old people really play and it's sort of dying out. And, uh, I started building that in unity just to see if I could, Um, learn unity, and I thought, oh, card game would be nice and easy. It turns out card games are harder than first person shooter in Unity
Um, yeah, massively hard and a real pain, but I'm, I'm doing that, so I would really like to get that out, um, at some point this year. Um, and go, okay, there you go. I did one thing for Irish culture and there. 20 gaming, 25 gaming. So that that would be my next thing. I can get that out. Uh, thank you very much for having me on.
It's been a real pleasure talking to you and I hope to learn a lot more from your website.
Thanks for listening. As always, we really appreciate your thoughts and feedback about the show. You can reach out to us by visiting game production. com's podcast pages and leaving comments under each episode. We have a Facebook group and YouTube channel that you can find linked from the website. If you want to contribute or fancy a chat in the future, we'd love to hear from you.