What’s the Flow?
The concept of Flow (Csikszentmihalyi, 1990) defines the mental state in which a person performing an activity is fully immersed in a feeling of focus, full involvement, and enjoyment in the process of the activity. It is a state of complete absorption with the activity at hand. It is a state in which people are so involved in an activity that nothing else seems to matter. For purposes of this article, we’ll simplify it asserting that Flow is the Optimum Challenge.
Why is the Flow Important for Us?
Because when we enter the Flow, we feel intrinsically motivated and happier, which is related to our perception of fun. As a side note, you’ll always want your players to be as much intrinsically motivated as possible, and since it is hard enough to foster intrinsic motivation, this is another reason why the state of Flow is an important game design element.
What Are the Requirements of the Flow?
1. Clear Goals and Progress
The player must know what is she trying to achieve and how to track her progress.
2. Clear and Immediate Feedback
This helps the player react to changing demands and allows her to adjust her performance to maintain the flow state.
3. Optimum Level of Difficulty
The player must have a good balance between the perceived challenges of the task at hand and her own perceived skills. The player must have confidence that she is capable to do the task at hand. We must ensure that we are communicating to the players correctly the difficulty of the task, and that they are able to evaluate accurately their level of skill. If they fail to understand one of these two things, the Flow state will be much more difficult to achieve, and it will be lost easier.
How Do I Get Players in the Flow?
Players enter and stay in the Flow when the game offers them the Optimum Challenge, this is to say, a balance between the difficulty of the task against their skill. The comparison of difficulty-skill will determine how the game experience will be (see the image below). Through his research, Csikszentmihalyi identified eight different experiences. I encourage you to think of examples of each one as your read them:
- Low challenges versus high skills can serve as relaxing experiences.
- Low challenges versus moderate skills lead to boredom.
- Low challenges versus low skills give place to apathy.
- Moderate challenges versus low skills foster worry and concern.
- Moderate challenges versus high skills create experiences of control.
- High challenges versus low skills make the players feel anxious.
- High challenges versus moderate skills create activation
- High challenges versus high skills enable the players to enter in the Flow.
Remember that “High challenges versus high skills” doesn’t mean that the task is very difficult per se. If the player doesn’t know anything about your game, learning even the basics can be a challenging task, no matter if these basics are really simple. On a side note, this is out of the scope of this article, but I figured it would be worth to mention that there are more elements you should consider when creating your game experience, namely that it should be able to be perceived as challenging for inexperienced players while not resulting too easy for the experienced players. If the new players find it too difficult or if the experienced players feel you are insulting their skills, there is a good chance that they will abandon your game. It doesn’t mean that you should satisfy them all; rather, there are techniques that allow for experienced users to squeeze more performance out of a system when interacting with it, which new users don’t even are aware of.
How Do I Keep Players in the Flow?
As players repeat the activities of the game, they improve their skill. In order to keep them in a state of flow, the difficulty of the activities must rise to match their skill. If the difficulty of the activities doesn’t change, eventually the player will move from a “High challenges versus high skills” experience (Flow) to a “Low Difficulty with High Skill” experience (boredom). If the difficulty rises too fast, the player will end up in a “High challenges versus low skills” experience (anxiety).
We want our players to enter the state of Flow. We will get them there by presenting them with challenges that match perfectly their skills. As players play our game, their skill improves, so we will need to rise the challenge to keep them engaged.
I stumbled upon this presentation today and I loved it. I don’t really think it would be enough explanation just by itself for someone that is not already somewhat into this matter, but I believe that it’s a great starting point.
In case you never heard of IA before, it guides your criteria when you analyze, organize and label information in your game. It defines how content is structured, what components are needed in each screen and which routes exist to that content. It cares about that info being understood, it tries to homogenize cognitive load all across the system and ensures that everything is findable, too. In short, if you want to design games you should be proficient Information Architect.
Maybe some other time we’ll have some time to write about IA. In the meantime, if you have five minutes, I’d recommend you to enjoy this:
Este es un correo que respondí a alguien que nos escribió para preguntarnos qué debería estudiar si quería enfocarse hacia una posición de diseño de juegos. Espero que resulte útil para las muchas personas que nos escriben desde las mismas inquietudes.
Frecuentemente nos preguntan que qué es necesario estudiar para ser diseñador de juegos. La respuesta es que no hay unos estudios que te vayan a garantizar que sepas todo lo que necesitas, especialmente porque cada proyecto es un mundo y requerirá cosas distintas de ti. Sin embargo, hay algunas cosas que subyacen a cualquier proyecto normal, y que muy probablemente te ayudarán en todos los escenarios posibles.
Si te has hecho esa pregunta, sigue leyendo.
En un McDonalds…
– Quería un menú BigMac, por favor
– ¿Lo quiere con patatas y bebida grandes?
– Sí, gracias.
– ¿Desea coca-cola, fanta o agua para beber?
– Coca-cola, gracias.
– Son 10,95€, por favor.
– Aquí tiene.
(el empleado reúne los elementos y los pone juntos en una bandeja que entrega al cliente)
En la consultoría de un programador de Visual Basic…
– Quería una aplicación de gestión de clientes, por favor.
– ¿La quiere con gestión de usuarios y panel de control basado en web?
– Sí, gracias.
– ¿Desea SQL Server, Access o MySQL para gestionar su base de datos?
– SQL Server, gracias.
– Son 2.000 €, por favor.
– Aquí tiene.
(El programador reúne los elementos y los pone juntos en un proyecto de VB que entrega al cliente).
Trabajar apoyándonos en una tecnología ayuda a desarrollar las cosas rápidamente y con bajo coste. Pero ¿es una buena solución para hacer juegos?
Si querías una hamburguesa has hecho bien yendo a MacDonalds, pero si no sabías bien qué querías, y has descubierto que querías comida china por el camino, vas a tener que aguantarte.
Aplicándolo a nuestro entorno de trabajo, ¿sabes perfectamente qué juego quieres hacer antes de ponerte a hacerlo?
¿Qué es lo que buscan los jugadores en un MMORPG?