Aspirations in Narrative Design

Working in the Industry

2008-03-05T07:40:00.000-08:00

For the past month, I've been luckily (blessed) enough to be working in the industry doing exactly what I set out to do. I've landed a position as a writer/level design with a RPG mod group and have learned something new everyday. The position has also bolstered my confidence that working in the video game industry is precisely what I want to do with my career, it may be hard work and long hours but I'm loving every minute of it.

Over the past few weeks I've written a wide array of content and wanted to share my experiences because they've been very different than what I expected.

Besides writing dialog, item descriptions, quest material and character sketches you may also be called on to write 'design documents'.

In any game, before the level was created, a writer had to create a long, complex, detailed document that lays out everything and everyone in the level, which allowed level designers to create the content the player will see. In a design document, a writer has to specify the general feel of the level, all the characters within the level, any locations that are subsets of the area, any quests associated with the area (that start or end) and any assets that may be used (dialog/scripts/FX). This document has to be detailed enough that a designer can build the world you create in words.

If you're creating your own game or just want to show potential employers that you can create a design document, you have a few options.

Create a design document for a game that you're familiar with. Pick any level/area in the game and write up a design document for that area.
Create a design document that details a level/area in the game you're working on.

To write a design document...

Start with an overview of a main area (ie. a town, a city neighbor hood or an outdoor level). Where is it located in the world (or your game), how does it 'feel', what do the buildings and people look like, who inhabits the area, how challenging of an area is it for the player, etc? Include brief art direction and history if you feel that your description has missed important pieces of your vision for the area.
List and detail all the areas connected to the main area. For example, if you're writing a design document on a town, what shops and homes are in the town that the player can enter. If the player can transition from the main area into a smaller subset of the level describe how the player can get there, what the area looks like, who inhabits it etc. These are mini-versions of your main overview for all the areas correlated to your main area.
List and detail all the characters in the area. Include who they are, what they do, appearance, stats (height, eye color, hit points, etc) and how they interact with others.
List and detail all the quests/missions that take place in the area. If a quest starts or ends in the level, explain what the quest is, what the player is expected to do and how the player can complete said quest. Be sure to include any information that is important to the quest. If the player needs a key from the bartender, include that information.
List and detail all the assets needed for the level. Assuming that you game has dialog, you'll need dialog files, which count as assets. However, you may also need scripts to run when a mission is completed or when a player enters an area that is plot related. If something happens in your area that isn't static and needs to be written/coded into the level, list that something.

Just as a note: A design document, depending on the size of your area, can be a monstrous document. Writing a design document may seem overwhelming at first, so just deal with bite sized amounts and all the little pieces will fall into place and you'll end up with a document that fully and imaginatively details the area you can see so vividly in your imagination.

Courtney Keene

2007-12-11T17:34:00.000-08:00

Courtney Keene has a personal blog / resume of her experience with narrative design and her transition from being a fiction writer to a game writer. She has some great insights and 'how tos' but most importantly she was kind enough to post sample material of her work, which is invaluable and a great resource of aspiring writings. Read through her posts and be sure to check out her resume material here.

The Job Hunt

2007-12-04T10:10:00.000-08:00

GameDevMap is an invaluable tool for locating game developers and producers around the world. You can search for companies by name, city, state/province and country. Obviously, this becomes an invaluable tool for anyone searching for companies to apply to within close proximity. Sadly, studios tend to be clustered together, so if you're unfortunate enough to live away from a game 'hot spot' you might be applying to studios far from home.

Check the site out at...
GameDevMap

Gamasutra is the Monster.com for the game industry. You can search for jobs, post a resume and contact companies that you'd like to apply to. If you're not already a member, sign up and create a resume.

Sign up at...
Gamasutra

My Application

2007-11-27T08:33:00.000-08:00

Just yesterday I submitted my application, to the developer that I've been hoping to work for all these weeks. Having finally sent in my application has left me with numerous mixed feelings.

On one hand, it's wonderful knowing the stress of preparation is temporarily over. I'm giving myself a few days to relax from the editing, drafting and polishing that has taken over my evenings. On the other hand, it's terrifying that I can't polish my work any more and that it's finally going to be reviewed by someone who may or may not decide to employ me. Regardless of the outcome however, I'm determined to continue working until I finally fulfill my aspiration.

I remember in college, meeting classmates who simply knew what they wanted to do - the pre-med student who gladly studied for hours because she knew she wanted to be a doctor or the computer science kid that coded during lunch because he loved it. I was always jealous of them. I wanted to feel that passion, that excitement for one single goal. Now, finally, I have that passion. I know that I want to be a Narrative Designer, so if this application is turned down, sure I'll be upset, but I know that I'll keep at it as long as it takes. Which is comforting.

Finally, I'm having the classic conflict of feeling woefully under prepared and qualified but contrastingly absolutely confident that I would make an amazing Narrative Designer. I know that all I need is a chance to prove myself, a chance which is understandably difficult to grant to an applicant such as myself. So I'll simply keep on working hard but I'm not beyond having friends cross their fingers for me.

To anyone in a similar position, I wish you luck and hope that your hard work pays off!

Script Writing

2007-11-21T06:57:00.000-08:00

Since script writing isn't something that you learn in school or have (if you're like me) ever been brave enough to attempt, I've compiled some links to introduce you to the style of writing and how to format your script. Once you get started, script writing is actually a blast!

Script Frenzy

Script Frenzy offers a much more relaxed introduction to script writing. I would suggest reading the (linked) introductory page and then move about the site leisurely taking in the excellent tips.

Scriptologist

This is a fairly straightforward script formating article but since formating is important, give it a quick read through.

Daily Script

A great piece of advice is to read scripts from movies that you enjoy, to better acquaint yourself with how scripts are written. Enjoy!

Further tips

2007-11-13T07:53:00.000-08:00

I've been extremely fortunate to be in contact with a game writer, who I won't name in fear of others spamming him for help, and he's been instrumental in aiding me with the fine reworking of my portfolio. Not wanting to hog all the valuable insight, I've posted below the information that the very kind writer passed on.

Note: this information is pertinent to a portfolio in my style (the contents of which are mentioned in a previous post).

You have 5 mins of the readers time. Literally. As such, you're portfolio needs to be 5-6 pages max and those pages cannot be text heavy. Your portfolio is a rapid fire introduction to your writing. For my packet of writing my mentor suggested cutting down my work to a 5 page document. 1: the game bible and a map of the world 2: a scenario 3: screenplay (or a scripted cutscene) 4,5: Storyboard.
Any introductory sections need to be short and sweet, with just enough information to acclimate the reader to your story/world and to provide them the basics needed to understand the rest of your piece. In addition, your introduction needs to sell the game your writing for. Something to think about - what makes your game special? what would make someone want to play it? why are the occurrences/characters/races unique in this story?
A quest (scenario design) should be laid out on one page using ~300 words. Artistic detail and game play management should be left out, stick to the story basics. It's important to remember, that as a writer, you'll be working with a team of artists who'll already know what a location should look/feel like.
In a cutscene 1 page = 1 minute, therefore, excise any excess description that can be condensed. If you can, shorten a paragraph down to a sentence. Not only will it save paper and the reader's time, it'll make the scene feel more 'real'.
If you're submitting several different writing pieces as a packet use distinguishing font and format. i.e. while a scenario design may be in Times New Roman, a scene should be written in Courier New.
About storyboards - "Not necessary, but people have this (wrong) subconscious notion that a better picture means the story is better too... If you've got more time and talent, polishing the drawing wouldn't hurt."
"If you have the dedication to polish and study and polish some more, you'll end up with something fun to read. And one day, with something fun to play." An excellent adage to work by.

The Application

2007-11-08T07:16:00.000-08:00

The past six weeks have been a blur.

Six weeks ago, I had an inspirational epiphany. I finally knew the job I would enjoy doing for the long haul. I've always loved to write, I've always loved video games and I've always enjoyed creating (be it through writing, woodworking or art).

What started as an exciting dream soon turned into serious pursuit. I've spent the past six weeks consuming all the information I could get my hands on and I've been lucky enough to be in contact with writers in the industry, who have given me wonderful advice and warming encouragement. I've filled notebooks with ideas, samples and drafts. I've created a mountain of scrap paper splattered with red editing ink. I've created, killed and revived ideas, characters and happenings. And finally, I've created a portfolio that I feel proud of. Ultimately, all the work has been geared to land me a job as a narrative designer, but more importantly, I've discovered a passion that has been lacking. I don't want to be a narrative designer because I think it will be cool; I want to be a narrative designer because I truly love the work and want to craft material that inspires, excites and enthralls.

But I ramble.

For anyone reading this, who might be pursuing a similar dream, I've listed the breakdown of my portfolio and reasoning for each section.

An abridged 'game bible' or game introduction. I truncated the content of the introductory packet to only include the locations, persons and history pertinent to my other submitted work. For example, while I've created numerous characters, I only provided descriptions of characters that will be introduced in the quests and cut scenes I also submitted. Another important addition to this submission is a brief introduction to the game/world you created. What forces are at play? What is the conflict? [Edit: If you're sending in a sample portfolio limit the game introduction to one typed page, providing just enough information to understand the rest of your work. The readers don't have much time or patience to read through a description of every character, rock and building.]
A sample quest. It's important to remember that as narrative designers, we're writing for the developer, not the consumer. A prose overview of a quest might be interesting to read but it doesn't provide the necessary information for artists and programmers to recreate the quest in a game. In my sample quest I included...

A brief introduction.
Locations. Where is the quest taking place and what does that area look/feel like. [Edit: It's important to remember that if you work with a developer, the game artists will already know the look and feel of the world/level. As the writer, only mention aspects of the location that are essential to the scenario]
Music.
Characters.
Goal. For this, I provide one sentence summing up what the player needs to do.
Action. What steps does the player need to take in order to accomplish the goal?
Flowchart. Lists the actions the player may take and the resulting consequences. [Edit: If the scenario is straight forward, leave this section out. However, if you have a scenario with multiple pathways a flowchart can help organize the writing]
Notes. Anything additional for the artists or programmers or any other extraneous thoughts.

A storyboard. I feel confident in my conceptual art skills, so I added a quick sample storyboard that illustrates the entrance of a character into the scene.
A cut scene. Cut scenes are written almost exact like movie scenes, so if you're struggling look for sample film scenes. In a cut scene you need to provide information on the camera movements, game effects and dialog. [Edit: providing camera moves and FX direction isn't actually the job of a writer. Omit these additions and stick to the dialog and dramatic pacing.]

Keep in mind two important things. One: I haven't been hired, so I haven't a clue whether this portfolio will land me a job. Two: I purposefully keep the portfolio short. While I have little control over the first point, the second is very important. The hiring managers of a developer simply won't have the time or patience to read through an entire game script. What they need to see are key deliverables (can this person write a quest, a cut scene, back story etc). Submitting too much work might actually work against you because the readers will easily tire of a lengthy submission and might skip over the more impressive sections of your work. Which brings up another key point. Your portfolio will be graded by your weakest section. As such, only submit work that you believe best sells your writing ability.

Further confusion

2007-10-31T07:46:00.000-07:00

In an attempt to update my blog with as much valuable information on game writing/narrative design as possible, I'm adding another link.

Just today I stumbled upon Christy Marx's website, who is a writer for many different genres. Fortunately she's included sample work from games she's worked on. Unlike other writers, Christy seems to specialize in directing scenes and full motion videos (FMVs) with poignent directions for the animators, directors and voice actors. Check out the site here.

Christy also included an abridged 'Game Bible' which can also be seen as a 'Game Overview': characters, locations, history, etc.

I've also been in contact with Christy and another game writer, asking how to best present a portfolio. In summary, they've said...

You have roughly 1 minute of the reader's time. If you haven't impressed within that minute... too bad. However, if the reader likes what they see, you might be blessed with five minutes of reading time. The lesson being, only submit strong work. Don't include everything you've ever written because it simply won't be read. Instead, send out what you think demonstrates your strongest ability and keep it to a 5 minute read.
Stick to the developers genre. If you're applying to a company that makes fantasy RPGs, send sample fantasy writing.
Some of the best advice I've been give is...

"Limit your portfolio to a very small reading amount. Don’t expect them to read more than a couple pages. Excerpt a 1 or 2-page selection that highlights your ability to tell a story, economically in the medium of your profession. That can be printed for a nice quality hardcopy.

Of course extend quality to the presentation of your portfolio, but don’t let the formatting and materials get in the way of the writing (or drawing). They should remember your work, not your paper stock or layout.
The most common form of advice is simply "stick with it".

The Job

2007-10-29T14:54:00.000-07:00

I would like to preface this Blog by stating that since I am not (so far) a Narrative Designer, all the information below is strictly from sources on the Internet, people I've talked to in the industry and books. If you can elaborate on any of these points, please do. The more specific information you can provide, the better.

The job:

Hypothetic: Hypothetically being a Narrative Designer (ND) involves working on a game from start to finish, creating the necessary history, characters, descriptions and documentation of a game.
The truth: Every ND in every software development company has their own job description and duties, as the actual definition of a ND has yet to be defined largely because employing specific writers for a game, instead of using Designers/Producers, is a new step in game development. As games have become more complex, the need for writers to churn out compelling, well-written material has increased. As such, being able to pinpoint a ND's actual job description is so far impossible.

ND Strengths/Job Tips:

Obviously strong writing skills are essential, so be sure to spell check and proof read any of your work before you apply or submit work.
Everyone in the game industry has great ideas. So simply having an active imagination or a "great game idea" isn't going to land you a job. In fact applying to a job under the pretense of having the next big game idea is simply going to cause you to be overlooked as unprofessional and not knowing what developers need. That being said, ND's are responsible for pumping out loads of material for the software developer artists to work off and for programmers to work with, so being able to constantly produce new, exciting ideas is key.
It's also important to remember that as an ND, you're writing for the developer, not the player. The material produced therefore is going to be very different than simply writing a story.

Resume tips:

Do NOT include the fact that you have a "great idea"
Do NOT include work that isn't pertinent to the job you're applying for. Developers really don't care that you worked at BK for a summer... unless you were writing BK game scripts.

Begin your resume with 2-5 selling points - you have roughly 10 seconds to capture the reader's interest, so don't bore them with academic scores and bland work experiences
Include any jobs that highlight your team work or writing skills
List pertinent skills that make you unique and strengthen your ND prowess
Demonstrate your interest in games/gaming

Valuable links:
So far in my searching I've discovered very few examples of actual ND work. Below is a compiled list of links on writing types that an ND may be called on to produce, industry tips and other useful information.

Game writing-
Will Kalif, a fantasy writer and game designer, has an article posted around the Internet stating how to write a complete game packet to be sold to game developers. The article illuminates eight important aspects of game writing. You can read the article here.
In the article Will stresses that in today’s game development world there is more and more demand for interesting, complex stories. To accomplish the immersion players want, a writer must not only tell a compelling story but also allow the player to choose their own way through that story.

Game storyboards-
David Kennerly, a game designer/author/scripter, unlike Will Kalif, has a website stressing the importance of game storyboarding and script writing. David was also kind enough to provide sample work that's free to download and view.

Industry tips-

BigHugeGames has a very helpful page of job industry tips. While the tips are largely for artists the information is pertinent for NDs too.
Melissa Brewer wrote up a fantastic article detailing how to start through how to get the job.
Howstuffworks has a simple game creation article briefly detailing the steps taken to make a game. If you're very new to the game design world take a second to read over the article.
GameCareerGuide is community site dedicated to create dialog between professionals and aspiring workers. Sign-up, join the forums and see if you can't network.
Errant Dreams is a site for tabletop RPGs but the skills need to create pen-and-paper adventures has obvious relevance for console/PC games. Furthermore, there are articles with job tips and 'how-to's.

The Dream

2007-10-29T14:52:00.001-07:00

Recently I've been working towards a dream job that I wasn't aware of until last month, to be a Narrative Designer. Like the pursuit of any dream, the journey has been filled with obstacles, new experiences, learning, doubt and hope.

The hardest part of my pursuit however, has been finding information on what being a Narrative Designer actually entails and furthermore, how to become one. In this Blog I will attempt to post any scraps of knowledge that I've accumulated so far, so that anyone else who follows behind me can benefit from the experience I've gleaned.