Skip to content

Tag: design

People like us

I hear at almost any meeting and occasion to speak about game design people’s personal opinion. To me this is not clear. I like when I do this and that happens. When I see something like this I feel angry. And so on.

That is because we naturally relate with people like us. Fact is that people like us are a myth. A utopy. Each one of us is unique and we have our tastes and behaviors. Which makes our job as designer so interesting.

Instead of referring to people like us it is better to think in missions, journeys and more in general activities that those people like to do. People who like to run with their dogs. People who play chess with friends on thursday afternoon. People who only eat vegetables.

That is where the most interesting things are considered.

Games and stories

I am taking a course on game writing and learning the hard way how a game can live and be successful without a story. Games do not need stories.

When gameplay and story marry well the story can boost the experience for it be remarkable and memorable. This is because play is a problem-solving activity, useful to improve some of the skills useful to survive. Stories instead help us understand better people and how to relate with them. Games are about things, stories are about people. This is why is so hard to link a game with a good story.

Point of touch among design and writing is that designers look for fun. And fun is a feeling. Writers look for feelings. You can easily spot there is an interesting overlap.

How to analyse any game

When you work as game designer for companies you will invest a lot of time studying other games. The best thing you can do is to prepare and evolve a personal framework to optimize this job. This post is to detail what I would focus my efforts on.

Specializations

Game design is a huge word, the word for a container. Jesse Schell writes that game design is “the act of deciding how a game should be”. As you can read, everyone practices that. We, game designers, are facilitators of that act.

To me, game design has four main specializations:

  1. Level design
  2. Narrative/Content design
  3. Gameplay/UX design
  4. Systems design

If you work as a generalist, you should focus on all four. If you are a specialist, it is still good having clear the relationships and overlaps with the others

The Experience

The most important thing for a game designer is NOT the game. Really, it isn’t. The game is a medium to an end. And that end is called: EXPERIENCE.

We can write a book only on this term, but for the sake of the article it is important to mention that we game designers should be able to understand the experience of other games under two lenses:

  1. what is the intention behind them
  2. what does them say actually

Understanding the intention is a matter of dealing with lots of analysis, but nowadays developers publish a lot of content. My suggestion is to watch videos and read articles and hear podcasts to try to spot all that’s possible. Playing the game completes everything, and it is very important to play it deeply. For example, if you are really analysing a free-to-play game you should also buy something to understand how it feels.

In order to really understand what the experience says, the best way is to take notes on everything related with your specialties. And when I say everything I mean absolutely everything.

  • Record all game sessions and take screens
  • Copy all texts, level maps and try to empathize with those designers
  • Create documentation and be detailed.

Practices and frameworks

I discovered recently a great article on how to think in the first steps of the design for a new game. I can’t wait of facilitating some workshop based on this framework.

How to use any framework

  • First you test it with a workshop facilitation. In this way you can understand how the framework you consider is really useful inside of a team. You will see other people interacting with it, which is great.
  • Then you use the framework in question to breakdown and deconstruct existing games, especially competitors.
  • Finally you take notes of all of your learning and create a new framework starting from it. It is almost never a good idea to use a framework in the same way it is. Remember: a specific context and a group of people created that framework, you cannot adapt it to your reality without changes.

Very often we hear about best practices like things we should apply religiously without questioning. That is almost never the case, also because when a practice becomes a best practice, usually it becomes also an old one.

Has “put genre here” died?

Online discourse regarding the gaming industry is very often monopolized by marketing and business people. Which is normal, since they are “selling” ideas and spreading new and old trends.

What makes me smile often is when I read that a specific genre has died. It is like “hey, everyone! Stop doing this because now people don’t want to play this kind of game anymore.”.

As a designer, anyway, I know that Players look for experiences capable of satisfying fantasies. This has nothing to do with a specific genre. Good games start with an assumption on fantasy. “Be a cat” can be a fantasy (STRAY, an indie game). “Win big at Casino” can be another one (SlotoMania, free to play mobile game). “Dominate your opponent mind” (Chess, classic game).

Starting from fantasy, then you build your actions and mechanics on top. And then you design your economy starting from goals structure. You can eventually add up a setting/world and, finally, the story.

During the process of defining your actions and economy, you should study the market and its trends of course. But I would like to invite you not falling into the trap of riding a trend for the sake of it OR rejecting ideas just because there are not much success cases.

When the market is emptying of a specific genre there are usually a series of reasons. Something that doesn’t work for the most can be a huge opportunity for your reality. Don’t be a follower, write your own story.

How to build the next Supercell

I have a secret to build the next Supercell. Really, I have it! Have I ever built a company like Supercell? Of course not, but I mean: we live in the age of suggestions, advices, best practices, influence, likes, follows… So why shouldn’t I write some wise article about how to do things, right?

As any secret, this one is very easy to understand too: stop treating people like children. Easy, right? Let’s see three common ways in which you are treating your people like babies, including before they join your company.

Technical tests and assessments

In some case those are necessary, especially for junior talent or for talent that is switching radically the sector. For instance, passing from free-to-play to AAA. Anyway, if you are hiring a person in his forties please: give me a break!

Our curriculum, carreer and our ex colleagues speak from themselves. We have nothing to demonstrate anymore and we are completely capable of doing the job at a technical level. Do I really need to show you how I structure an economy in a spreadsheet? Do i really need to demonstrate my presentation skills? Do you want me to create a flow and a wireframe? Or worst, a single GDD bible? Please, I do this since probably before you joined that company. Again: give me a break!

Do this instead:

  • Interview for cultural fit
  • Review in detail past experiences
  • Ask for referrals of ex colleagues and employers

When I see a test proposal I just think: “ok, you are not capable of evaluating my kind of profile. Next.”

Show me the next things to do with no context

I remember when I was a little dude asking to my father: “Why should I do that?”.

“Because I say so”, was his answer.

35 years later, history repeats. And I am very tired of that. You give a task and a deadline, with no perspective. I will do that for you the best I can. I swear. But I will never understand anything like this. Why is this important for the project? And how will we demonstrate that in fact it was? When we shoud have some learning? What about the past iteration? How did it go?

Maybe you are too busy to explain well the vision behind any choice. That means that you are not doing the job you should, to me. Because if you are my manager, you should be focused on manage my team and myself. Not the game. Not the code. Not the art.

Put your hands on my work

This is tipically something that you do to game designers. And tipically something that occurs in small-mid sized companies. We spent weeks designing something, researching, getting the problem right, sync with all the people involved. And then you decide to change everything because you have your own idea in mind. You are the founder or the leader of the project and you have the last word.

I could be wrong and you right, of course. Still, you are stealing my opportunity to learn more about the audience and the kind of product we are doing together. I just feel that my solution will never be tested on the field. Your solution maybe can be successful. And probably you will be happy and still will recognize my work. But you stole my opportunity of seeing a design I made going out there.

Stop play with my toys, those are mine!

Being loyal

Year ago I was running a very promising free-to-play project in a local incubator. It was very promising, it was the future. My lead artist said: you are inventing the devil. Of course, it was just in my head. The project had no chance to go forward, because I wasn’t being loyal to my will of creating a new company around it.

Being loyal with ourselves is not just to maintain the promises we make. It’s not to respect the compromise. Is also to make well our numbers. If you want to build anything and we consider ourselves game designers it is necessary to stop and think well to all costs and scopes of the things we want to build. And then add a 20% of error to all of that. Otherwise we will most probably fail.

My project failed at many levels, but the main one is that you cannot start a free-to-play ambitious project without great professionals and lot of money behind. The art of giving games for free is very expensive, needs a good monetization strategy and the acquisition of new Players requires huge efforts.

I am glad that I didn’t invented any devil, and I am glad to be here happy telling you those stories.

Lore and freedom

I am playing Horizon Forbidden West and everytime I meet a new character, the game invites me to hear minutes of dialogues. The story is intriguing and well written, but I cannot just walk away such as in Skyrim for instance, leaving the NPC speaking alone. Different design pillars, different approach to narrative.

Still, a great game. This forceful dialog creates somehow a connection with the lore of the game. So that a new intellectual property is reinforced.

I am also playing the classic Gothic. A game that says you NOTHING about what to do. A game from the past. You have to really strive to understand what to do, where to go and so on. I killed a man, today. I found him hidden in a mountain. I spoke with him and then I killed him. Why? The game gave me 40XP. There will be no consequences to my character.

And that fits into the game’s narrative of brutal freedom and high insecurity. So that I was the big fish eating the small fish, today. It fits. Gothic still has fans all over the World.

Humbleness and feedback

When someone asks me for a feedback for their game, I try to never give my opinion. In fact, I believe that working in games makes us liable of huge biases that come from experiences which are subjective.

I try to make them questions, instead. Try to understand really what’s behind their choices. Then I tell them what I would ask to playtesters to challenge their assumptions.

I believe that is the best way of giving feedback. From the other hand, the tendency is to say what one would do instead. And the worst is that then someone may follow blindly your advice. Applying that advice in their understanding, not what you said them in first place.

That is why it’s important be humble, somehow. Being humble is being completely honest. In order to be that, the right start is always a certain amount of questions.

Failing at premises

Successful games are games that manage to meet the right audience willing to invest their money in them to get the kind of fun they expect. And that is nothing new, it’s game design 101. It’s the very first lesson you learn anywhere when you start designing games. You should design a game for some audience.

There are many ways of failing at this. Actually, the vast majority of games fail to deliver this exact point. Which is why video games are a very risky business.

The experience may help you avoid some mistake, and mine has a almost constant issue that I see: failing at premises.

In fact, a lot of times I hear sentences like:

We want to make a game like <CoolGameTitle> but more [casual|hardcore|midcore], just like <NewTrendyGameTitle>.

Senior VP of Product Ownementshipssss (or some fancy title like this)

I don’t know if the syntax I am using is completely clear, I guess it is not. But the truth is that when you want to change a playstyle from a specific audience, that almost for sure leads to disaster. Casual, midcore and hardcore to me are a way of describing the gameplay session time.

It is good that you take your references, but if you are willing to force a significant change in gameplay behavior you are on the wrong way. If you know that a specific successful game has that playtime, you should consider that seriously as a pillar and not as something to change. We can be misled to think that “making things simpler” means “shorter/longer gameplay sessions” and that is almost never the case.

Never say never of course, but that is in my experience one of the false premise that make a game lose the money and efforts you and your team invested in.