no show 2012 - tim crosby - can you write that down
DESCRIPTION
Six flavor of quarks, six colors of M&Ms, and six varieties of game design documents: coincidence? Almost certainly. But can you really take that chance?Whether you’re trying to record design decisions, refine project scope, or get investors on board, a good game design document can be critical factor in success. Get vital tips on choosing the right format and crafting the perfect document to lead to a more perfect game design. We’ll discuss document structure, defining goals, best tools for the job, place in a game’s lifecycle, pitfalls to avoid, and examples of both good and bad design documents. Whether you’re a fledgling developer or long established and looking to improve your process, you’ll walk away with a clearer understanding of how to make the best design documents possible. And maybe, just maybe, you’ll learn to love great documentation as much as I do.TRANSCRIPT
Can You Write That Down?The Six Types of Game Design Documents and Finding
the Right One(s) for You
No Show Conf 2012
Tim Crosby
Outline1) Orientation2) Lifecycle of document3) The six types of documents4) Examples5) Best Practices6) Questions
OrientationWhy do you care?Better design docs make for better (faster, stronger): - Ideas- Processes- Games
Documents are not:- Unchangeable- Solitary- Universally useful
Development Timeline
Concept Design Production
This isn’t accurate
QA
Two Pager
Brainstormer
Bible
Review Copy
Documentation
Prototype
… little better
When design documents are written
Development Timeline
Concept Design Production QA
Two Pager
Brainstormer
Bible
Review Copy
Documentation
Prototype
When design documents are useful
What’s the Design Document Purpose?
Same as the purpose of a game designer
Communication
The Six Types of Game Design Documents
Truly necessaryA component of most other documents
• Elevator pitch• Vision• Keywords• What game is like• What makes it different• Maybe one picture• Sentences ≈ Paragraphs
Talking to the World Two Pager
Technology:• MSWord / OpenOffice• Webpage• Whatever works for you
Talking to the WorldTwo Pager
Talking to the Game DesignersBrainstormer
Early stage, collaborative, blue-skyNeeds a designer to drive it
• Document all ideas• Can organize / sort ideas later• Can be in sessions or over time
Talking to the Game DesignersBrainstormer
Technology:• Wiki• Evernote• Google Docs• Dry erase board with notes and dissemination
Talking to the TeamBible
Communicate design ideas to the entire teamBring new team members up to speed
• Include many many flowcharts• Not one thing – really a set of documents– Documents– Sample Text– Illustrations / Style Guides / Concept Art– Spreadsheets / Formulae
• Repeat information for redundancy of concepts
Talking to the TeamBible
Technology:• Google Docs• MSOffice (Word, Excel, Visio, PPT)
+ Source Control• Wiki• XML / YML / Other markup languages• Email and Skype or other IM
<>
Talking to OutsidersReview Copy
Snapshot of design thinkingSimilar to core document of the BibleCan be early marketing/investing materialHave graphic design pass in addition to writing
“No one will read it”Except: “They will only read the first page”Except: One person will read it, and give invaluable feedback
Talking to OutsidersReview Copy
• Hierarchy / Structure– Logo– One pager at front– Player types– Game description and features– Market analysis / competition
• Many pictures• If it’s an external property, show love and respect• Show capability for deep thought
Talking to OutsidersReview Copy
Technology:• MSWord – better than OpenOffice– way better than wikis
• + Photoshop• + PDF converter
Talking to Your Future SelfDocumentation
To remember what you thoughtTo remember what you said
May be set of documents for different purposes
Must have explicit references to other documents / consistent naming scheme / clear folder structure
Talking to Your Future SelfDocumentation
Technology:• MSWord, Excel, Visio, Powerpoint• Google Docs• Whatever works to communicate with others
Talking to the GamePrototype
For some games, prototype is rules(such as tabletop RPGs)
You can throw it away
Not same code as full game
“Non-Document”Good for determining / displaying interactions
Talking to the GamePrototype
Technology:• Paper, post-its, index cards, markers• Whatever tech you work in fastest • Quick prototyping software (e.g. Moai for 2D,
Protoshare for web)
HybridsFurther specific purposes
Bible x Documentation: long-running projects or part-time projects (e.g. student work)
Brainstormer x Bible: future features list
Review Copy x Prototype: investor packet
One Pager x Prototype: kickstarter video?
Two Pager: FanSwarm Two Pager: Brainstormer: 50 Cent’s Blackjack: 23 pagesBible: 50 Cent’s Blackjack: 59 pagesReview Copy: 50 Cent’s Blackjack: all documentation exposedDocumentation: 50 Cent’s Blackjack: ~100 documents ; FanSwarm: ~50 documentsPrototype: 50 Cent’s Blackjack Tech prototype to ensure simultaneous play possible, included game rules
Examples
Two Pager: Executive Summary; Vision; Overview; Market DifferentiationBrainstormer: 20 text-heavy pagesBible: v2 had no pictures, incomplete, 26 pages ; v8 had painted concepts, incorporated external feedback, 154 pagesReview Copy: same as Bible from v5.1 onwardDocumentation: well over 100 documentsPrototype: paper prototype confirmed core mechanics ; prototype city layout decided to go different art direction
ExampleGame of Thrones Ascent
Best PracticesIntegrated designer better than short-term contractorIf you believe a design doc is useful that makes it usefulVision-holder should be in charge of design docsSolicit feedback about doc contentSolicit feedback about doc structureThere is always time to iterateAdapt doc structure to fit how the readers learnUltimately document less useful than making the game
