Storytelling by Design
I’ve been pulling together my thoughts on a design approach based on the power of storytelling. While I still haven’t quite figured out what it is, I have started to chain some realizations together.
The Failure of Thing-Focused Design
The failure of much design stems from the lack of engagement between creator and audience. As we creators grow more and more specialized, the tendency to describe what we are doing with precise bursts of jargon increases, balkanizing the creative landscape with specialists who spend more time talking to themselves than communicating ideas to regular people. And yet, it’s the people that matter most, both in terms of social fulfilment and in revenue.
While the idea of “story” in design is not new in the context of Human-Computer Interaction, Usability, and Experience Design, I haven’t yet seen a whole lot of emphasis on the quality of storytelling. The literature cites story as a way of defining a user, which is useful for workflow visualization; ironically, storytelling itself is not part of the toolkit.
Storytelling Doesn’t Just Describe Relationships; It Also Creates Them!
I’m interested in a process that’s more immediate and primal. I think of the “art of storytelling” (as opposed to just having a descriptive story) as a two-way modelling process. It’s a more engaging way to introduce individual people to new ideas and concepts. Stories and storytelling go back to the dawn of humanity; it is arguably the way we understand the world, and it’s also arguably the most compelling commonality in the development of all our media technology. Yes, specialized jargon is inevitable when discussing the inner workings of the technology amongst ourselves. However, we must recognize that the inner workings themselves are relevant only to other practitioners. What matters most to me is putting that technology in service of the storytelling; becoming a better storyteller is at the heart of being a designer with relevance in the real world. This is performance by proxy, showmanship applied with purpose. When you help someone understand new technology in the context of their understanding of the world, they can co-creation the new reality with you because they can envision their place in it. That’s the power of great storytelling. Great exposition doesn’t reach as far. It’s just boring, which anyone who has had to read a functional spec can attest.
The difference in approach can be illustrated as follows:
The specialist designer provides a menu of services and skills related to production, and then asks the client what they want. What format? How many colors? What’s the copy? How many pages? What should it look like? And then, they produce to an evolving specification based on user modelling and iterative testing.
The storyteller-designer, by comparison, first asks about motivation and desire, and designs for the dramatic moments. The primary goal is not to produce to a functional spec, but to create a story about the cllient, with the client in the hero-protagonist role. Only then are the production skills are applied to create causal elements in the real world. The difference is that the story doesn’t remain a fiction; when executed well, the story makes the client’s reality. And if all goes well, the story takes on a life of its own.
I believe the concept of the storyteller-designer is what I’m actually moving toward. It focuses not on process and technology, but on creating events placed in a meaningful human context. And that’s where all the action is, IMHO.
Mind you, I am not saying that Usability is useless. However, “user models” and “archetypes” are mere descriptive anchors; the role of “story” in the context of Usability is to package user behaviors into a concise blueprint useful for general systems modelling. The flow of information is one-way: behavior is observed, iterated upon, and re-observed. While the users are involved in the process as the “target” audience, they are more like statistical parameters in the system design. That’s fine, and that’s not what I’m talking about.
The approach of Storytelling by Design, as I’m trying define it, is about interfacing with clients using an approach that emphasizes story as the primary unit of understanding, as opposed to “pages”, “Flash”, “PHP”, “look and feel” and “rounds of revision”. You can also think of it as “speaking the language of the client” taken a little farther; using storytelling techniques in client communication to create engagement and understanding of the creative process. It’s also a given that storytelling is the focus of the creative work; this is well understood in any customer-facing endeavor that’s intended to be viewed by actual people (e.g. Advertising)
Later this week I’ll talk a bit more about how the process of practicing “Storytelling by Design” works.
UPDATE: I just found this article that talks about something very similar! So I’m not alone in this :-)
Story-based Design is the first attempt I made to clarify what I was trying to do.
Story-based Design II is a first exploration to distinguish between what I’m doing and the already-entrenched usage in Usability / Experience Design.
Story-based Design III: Shakers and Objects describes a related insight about “objects looking like objects, as opposed to like people”.
Story-based Design IV: When it Breaks describes a situation where maybe you shouldn’t tell the story.
Storytelling versus Co-Creation of Story describes “branded entertainment” and my reaction to the idea. I realize then that it’s not so much the storytelling that I’m trying to define, but the style of client interaction I’m trying to achieve.
Topic home is http://davidseah.com/storytelling-by-design