This post is the third in a series about increasing accessibility for those with dyslexia. Today, I want to cover how people with dyslexia process information differently. I'll introduce the tasks that can be harder for people with dyslexia, then apply it to game design in a practical way.
Since information processing affects many parts of gaming, this post covers the widest range of examples and topics. Think of it as an introduction to thinking with a dyslexic brain, with just a few illustrations of how that affects gaming.
Procedural Learning: Not so natural
There is evidence that those with dyslexia have a harder time with "procedural learning", i.e. learning by doing or observing. This is also called implicit learning.
A classic experiment illustrates the process of implicit learning. Scientists let a mouse wander around a maze several times with no rewards or incentive. Then they put the mouse in the same maze with food at the exit. The mouse that had explored previously found the exit much faster than a mouse that had never been in the maze before. Even though the mouse hadn't been taught to find the exit previously, it had "implicitly learned" the layout of the maze during its previous wanderings.
As humans, we rely heavily on procedural learning. We teach through observation followed by practice. This is summed up in the medical strategy: See one, do one, teach one.
Many people with dyslexia demonstrate a limited ability to learn through practice. Watching and even practicing an activity leads to limited improvement. Instead, many people with dyslexia require explicit learning, i.e. being told, "First do this, then do this, then do this, etc." People with dyslexia often need to build up a mental map of explicit rules and processes to understand how to complete a task.
For myself, I can only survive the extensive writing in my job because I created templates for documentation that explicitly state: write this here, then this here, then this here. Any novel writing tasks outside of this explicit structure tend to overwhelm my brain and take much longer. Similarly, I have never been able to learn a foreign language through immersion. Instead, the classical method of learning languages with charts and grammar rules is much easier for me.
How does this relate to game design?
Tides of Gold was the one-weekend experiment that ended up becoming the game that shifted how I thought about Forged in the Dark (FitD) game design.
Rather than do a full post-mortum on the project I want to highlight one aspect that turned out to be really important: the role of playbook concepts.
In Blades and my previous game Karma in the Dark, playbooks were primarily about the type of professional you are, i.e. your skill set. A Whisper is about tapping the occult in Blades; a Broker is about social manipulation in Karma. The playbooks were about what you do (with some flavor of how you do it in the xp triggers).
For Tides, playbooks are more about your role in the crew. If you choose the Compass it isn’t just about doing mystical stuff, it’s about being the moral anchor and voice in the group. Think Cassie in the Animorph books or often Kayley in Firefly. If you are the Old Timer it’s not just about being skillful with surviving, it’s about being the one who has seen tragedy and wants to prevent it from reoccurring by sharing wisdom. The Firebrand, one of the new playbooks, is about being the one who pushes people to take action, to be passionate, to challenge and act fiercer in pursuit of what you care about.
All of this ties back to the central theme of the game. Tides is a game where you play as pirates, but it’s actually about the intersection of family and purpose. You have an anchor that motivates you along with some purpose for striking out into dangerous waters and trying to gain money (and perhaps respect/power). You have a crew that is more like a found family. And your playbook is a way of saying, “this is the role I want to take within this (probably dysfunctional) family.”
This blog is a mix of game design analysis, commentary on issues affecting indie dev spaces, and some personal reflections.