Developing Discipline: Story Architecture — Part 1
Introduction
(This is Part 1. Continue reading more about SA on Part 2: Navigation and Part 3: Evaluation)
I would like to start off by saying that I am obsessed with storytelling, transmedia storytelling in particular. There, I said it (cue the eye rolls and slow claps of friends and family). This fervent love for stories and the art of storytelling itself started in college a few years back with my post-graduation project, but the truth is that the passion goes back to the time I had a baby tooth. College just made me acknowledge it. Now in my life-long journey seeking to master it, I somehow seem to align my career prospects exploring and honing my skills in areas that I believed are related (or will be) to this new field. I am sure my passion must have been visible in the job interview, given that I got a customised official designation: Story Architect
I admit, it is a bit of a fancy title and at the time it was created (with my inputs, of course), I did not put too much thought in its definition. I only realised over time how hard it became to explain my designation or even justify it. More often than not the phrase’s ambiguity and uniqueness works as a conversation starter at social gatherings (“Story…Architect? Whoa! That sounds fun. What exactly do you do?”)
But while it turns heads (rather than clearing them), there is a reason why I stick to it. Even when I end up doing content strategy or ideation, I somehow always try to find a way to make my work narratively more engaging. Regardless of whether I always succeed in doing so, I believe it’s a term that best describes my passion and method of working.
Here is a working definition I have created:
Story Architecture (SA) is the design practice of using the techniques of storytelling and narrative elements to enhance the audience engagement for a more immersive experience.
I know what you’re thinking. So, it basically involves writing...stories? Well, yes…and no. I mean, SA is rather a skewed subset of Information Architecture (IA), the practice that is a pre-requisite in User-Interface/User Experience (UI/UX) before actually writing the content. Having worked in positions that primarily involved IA and copy-writing, I do like to see the relationship of the two discipline this way. For one thing, IA was initially used only in the field of Information Technology (IT) before it got hijacked into the design discourse and the debate is still on about how to define it. Likewise, I believe that the origin of SA — while disguised under a different term perhaps — was in the Fantasy Fiction and World-Building where creators (primarily authors) would spend considerable time creating a backstory or a story-world before actually writing the story. I am only trying to bring the benefits of it in different fields while treating the audience as if they are (still) engaged in a story.
With regards to execution and engagement, it is rather analogous to Gamification but instead of game elements (such as points, badges, rewards, etc.), it uses narrative elements or parts (setting, plot, character, etc.). But more on that in the later posts.
Like any discipline, there are a few aspects to consider and acknowledge. While it is easy just to go with an intuition of what feels right to do, possibility of improving or perfecting the skills will only be possible if one approaches any practice with a bit of theoretical awareness. So putting on my ontological hat, my goal is to try to develop SA into a whole branch of knowledge, inviting more literature to be created over time.
I think the best way to explain a discipline is by outlining the methodology. While still a bit sketchy, I have created a framework that I consider to be the cornerstones or ‘pillars’ of SA, acting as the foundation that anchors the practice on a more academical ground (I see an architecture pun here somewhere).
PILLARS OF STORY ARCHITECTURE
Blueprint
Containing and structuring the scope of the experience through its objectives and vision
Entrances
Having either a meaningful motive (to do) or rigorous rationale (to know) or emotional engagement (to feel) during the introduction to the experience.
Fragmentation
Compartmentalising the experience into shorter consumable parts that can seamlessly gel back together, synergistically deepening the engagement.
Justice
Completing or moving towards poetic moments during the experience to have a satisfying emotional or intellectual transformation.
I will be going into detail for each of the pillars in the later posts.
Given the expansive never-ending nature of story-creation, it is an excellent practice to broadly outline the starting and end point of the project before hand. It is not only a matter of deciding the duration of the project but also about openly considering what will be required to make it successful in the terms decided. What is the takeaway we want for the audience?
It is important to know that SA isn’t supposed to be a one-size-fits-all solution, nor do I aim to make it such. While I tend to be more rational in my approach, I do have to rely on my instincts to tell me whether or not it’s working. When putting the discipline into practice, care must be taken not to make it forced. In fact, like CSS on a website or an HR department in a company, the way to know if it’s working smoothly is when the public is almost unaware or overlooking its presence. Only when something is wrong, they start to notice its presence.
The thing to remember is that even for the experience-seeking audience, the exploration of the story-world and story elements needs to be a seamless part of the story itself.
Until, next time.
(Continue reading more about SA on Part 2: Navigation and Part 3: Evaluation)
P.S. Due to Story Architecture as a design practice being fairly nascent, it is highly possible (or rather, imperative) that the associated terms and concepts will get refined and re-framed over time.
