(This is the first in a series of posts on misfit ideas for helping people work with stories. I think they have potential, but they have not yet found anyone who wants to fund their completion. I'm posting them here to see if they can find good homes with people who need them.)
The idea of a universal story translator came about around 1999 when I was at IBM Research working with John C. Thomas. It wasn't any one person's idea but arose in conversation, as far as I recall. The question we posed then was:
What would make any story, told anywhere, at any time, understandable to anyone else, anywhere and at any time?
- The plaques on the Pioneer spacecraft that announced our form and intelligence to other life forms;
- the universal translator on Star Trek and elsewhere;
- the Darmok episode of Star Trek, which addresses the issue of cultural structures far above the level of language, specifically metaphor and story; and
- the footnotes on old novels that explain things such as why "He lived in a wooden house" is a put-down rather than a simple description. (Actually, that isn't in the footnotes in old Russian novels, but eventually I figured it out. I've noticed that the level of detail in footnotes corresponds to the year of publication; some things that were obvious in 1920 aren't so obvious today.)
In each of these cases context annotates content so that the content can be better understood. The first is minimal; the second fanciful; the third a near failure; and the fourth only a partial success. The reason this matters is that, as I said back in the first of my eight observation posts, most projects that involve helping people work with stories involve the paradoxical elements of narrative compression (which requires context trimming) and narrative distance (which requires context for translation). Manipulating the interplay and tension between compression and distance is important to maximizing the utility of story projects.
This is the sort of thing I'm talking about: on this site, the students of Copper Giloth at the University of Massachusetts at Amherst have created traditional and modern versions of many of Aesop's fables, exchanging the troubles of foxes and birds for the dilemmas of today's young people. The fox invites the stork to a baseball game; belling the cat is starting a neighborhood watch; sour grapes are a potential girlfriend. This is a perfect example of narrative translation and shows the potential of the idea, which could go much further.
Consider for example the division between city residents, usually immigrants, who butcher livestock in their back yards and residents who have their butchering done by others in remote locations. Each has a story to tell, but important elements of context are left behind, and the gaps are filled by assumptions on each side.
Our original work on this idea revolved around tools that might give people easier ways to annotate and view stories with contextual information added, to make what is unsaid in the story explicit. At the time I built a very simple Flash prototype to play with the ideas, which simply displayed some "canned" contextual notes I had added to a fable from Aesop. I've tried to duplicate it here using the "title" attributes of links. The links go right back to this post, so don't click on them, but if you hover over them you should be able to read the annotations.
A shepherd once found the whelp of a Wolf and brought it up, and after a while taught it to steal lambs from the neighboring flocks. The Wolf, having shown himself an apt pupil, said to the Shepherd, "Since you have taught me to steal, you must keep a sharp lookout, or you will lose some of your own flock."
From playing with this idea I learned a few things.
- The process of adding context annotations is both difficult and useful. Both attributes are important, and neither can be taken away by automation without losing something. It's difficult because it's hard to see context when you are in it, and it's useful because you find out things you had not realized about the story by forcing yourself to make context explicit. This less obvious utility complements the more obvious utility of communicating context to story readers.
- The technological part of the task is much the smaller one, and we already have the tools we need to do it. Everything is hyperlinked today, and with services like diigo, adding "sticky notes" to content is easy. At this point it's more about habits, social cues, and group techniques than anything to do with technology.
If the idea of a universal story translator was to be made fully real, it would be a set of ideas and techniques people would use for several context-requiring purposes, including:
- conflict resolution - helping groups understand each other
- international understanding - helping people understand and appreciate other cultures
- group sensemaking - helping people surface hidden assumptions
- persuasive communication - helping people reach a disagreeing audience
- ethnography - helping researchers understand people in context
- education - bringing out the context of learning
Software tools could embody understandings and social cues about story context annotation for translation and sensemaking. But my feeling is that people are so overwhelmed with helpful tools that they can't keep up with the scaffolding they have already. My rating of what would be useful in this area is techniques first, habits second, and software tools a distant third. Group exercises that more explicitly address drawing out context for translation might be a helpful addition to the body of techniques for narrative sensemaking. For example, perhaps two groups with different backgrounds could come together and pick apart each others' stories, asking questions like, "Why do you say he is an outcast?" and so on. This could be revealing for both groups and for the combined community.
Without full realization of this idea, whether in tools or techniques, how could you use it today in your work with stories?
First, just try out the idea of context annotation, by yourself or in a group. Take a story you know well -- a favorite folk tale, something from your childhood, the story of your wedding -- and pretend you are telling it in the year 1200, or on the planet OOpahN, or in an ant colony. Explain everything, the way you did when "explicating" poems in English class. If you can get some naive outsider to help, that's even better. Why do people throw rice at weddings? (Or why don't they anymore?) Why do little pigs go out into the world and build houses? Why do wolves blow houses down? And so on. It's a great way to understand more of what is riding along unstated in a familiar story. Sometimes you can come up with some amazing insights that open your eyes to what is in plain sight.
I've been doing this a lot lately because my son loves to have long conversations with every character we read about. Lately Gulliver (he of the Travels) has been asking a lot of questions about the crazy things we do every day, like put our dishes into a box and talk into a stick and poke our fingers into boxes of little marked buttons. (He knows a lot more than we do about leeches, though.) Kids are in fact great helpers when it comes to bringing unspoken context out into the open. Tell a kid your story and ask them if they have any questions; you may be surprised by what you didn't tell them.
For eliciting stories, think about possible areas of context: character, plot, setting, conflict, subtlety, subtext, for example. Look at any book on narrative form to find areas you can think about. Then during interviews or when planning story collection forms, ask follow-up questions that fill in any annotation gaps you see. Pretend to be ignorant about the subject you are asking about, even if you are not. Think what people will need to understand it. If you do this well, you will not annoy your storytellers, because they will gain their own insights during the process. Make the storytelling a sensemaking session for them, and you'll get better stories as well.
For facilitating narrative sensemaking, think about the needs of the group in question and what areas of narrative context might be useful to bring out. For example, if the subject matter is full of taboo topics, help people bring out story subtexts. If people need to think about players in a situation, ask them to annotate elements of character. Plot elements can be useful if you want to help people think about knowledge use or decision making. One way to do this is to ask people to write out a story on pieces of paper, one word at a time (leaving out "a" and so on), and then think of what they would need to add to each word to make the story fully intelligible to someone from a century ago, or from another profession, or from another country, or anything that will draw out detail. Going through this process will not only help people surface issues they have not noticed; it will also bring out taboo topics with an excuse that allows them to be more freely talked about.
So in coming back to this idea, I'm not sure a fully universal story translator has any real utility, because the boundaries around human groups do have beneficial uses. But there are times when bridging boundaries has great utility in context, and for that this idea can come into useful play.