You are viewing an old revision of this post, from March 10, 2010 @ 22:36:18. See below for differences between this version and the current revision.

Today’s talks:

10am: How to Manage an Exploratory Development Process, by Kellee Santiago and Robin Hunicke.

I heard Robin speak in the microtalks last year; she’s at thatgamecompany now. Good talk, and surprisingly moving: they started off by talking about how, at E3 2008, they debuted Flower, the press and their publisher loved it, yet the team’s morale was at an all-time low! Their development process was putting all sorts of stresses on them, which they needed to fix lest the company implode soon. (Which, I should emphasize, isn’t anything particularly negative about their company, just typical game development culture.)

Some of the key points for how to build a sustainable development process, so they can keep making the games they love indefinitely instead of burning out after a few years:

  • They needed to distinguish between commitments and estimates.

Both are important; but, if you don’t hit an estimate, that may be a learning experience (or may not, variability is natural, especially in creative work), but certainly isn’t anything to beat yourself up over (or for others to beat you up over), whether consciously or subconsciously.

Also, in an exploratory phase in your process, who knows how long it will take to find the game’s real core mechanic. (Shades of Iwata’s keynote last year.) So estimates there have a particularly large margin of error. Be confident that you still have a vision for the game inside of you; it will come out eventually.

  • Planning and feedback is important.

They have a big board sketching out milestones over the entire lifetime of the project; on a smaller level, they have two-week sprints, with standups three days a week. Their sprint goals aren’t as rigid as some teams do them, but it’s important to have the task cards up there, as a point for discussion.

Which leads to what I saw as their main takeaway:

  • Have conversations; don’t shy away for them, especially if they’re difficult.

The point of having task cards is so that you can see and talk about them if they’re not moving as you expect: are they harder than expected, are they unpleasant, are they simply something that nobody cares about? Or, if your explorations suggest that expected mechanics won’t work or that you’ll need more exploration than expected, don’t hide, even though you’re really nervous: talk to your publishers, talk to your marketers. And don’t just give the bad news: talk about your vision, talk about why you think this will make the game better. More broadly: remember that conversations aren’t part of a zero-sum game: they’re all on the same team!

One other amusing bit from the talk: we call a task easy in one of three cases: 1) we really want it to happen; 2) we have no idea what it entails; or 3) we don’t have to do it ourselves!

And, finally, the summary:

  • Be honest.
  • Wandering is okay.
  • On every project.
  • Until you die.

11:15 am: Kids and Parents Playing Together Online: the Next Frontier of Casual Gaming, by Jesse Schell.

Lots of good points here, starting from the basic point that you have to decide to design for this, not just (for example) build a kids’ game and hope that the parents will like it. Looking through my notes, I don’t see any huge insights that I’ll be able to provide beyond what you’d get from his slides, so I’ll just embed them here.

11:45 am: Lessons Learned building Moshi Monsters to 15m Users, by Michael Acton Smith.

Moshi Monsters was done by a company that had just burned through most of their venture funding, on a real-world cross-media game PerplexCity that sounded fascinating but wasn’t profitable. So they didn’t have much margin of error. Failure was still okay, but they needed to fail fast: which they started off doing, by trying a Webkinz model of physical goods linking to an online world. They stopped doing that, and immediately got a lot more signups, which they eventually managed to monetize quite successfully.

They monetized using a subscription model; he said that a good subscription model is sliced (so free players get to see parts of it), and visual (so free players can see what subscribing players have). The price points matter: they had 1 month, 6 months, and 12 month plans, and initially set them up so the longer plans were a modest savings over shorter ones. That led to most people signing up for 1 months; so they switched to putting a much narrower gap between the 6 and 12 month plans (5 / 24 / 30 pounds, respectively), and all of a sudden almost everybody signed up for 12 months! Another anecdote along those lines: when the Economist had an online-only subscription for $59 and a print and online for $125, then 68% of people chose the online-only version; but when they added a print-only option to their price list, also priced at $125, then it switched to 84% of people choosing the print and online option!

1:45 pm: The Convergence of Flash Games and Social Games, by Daniel Cook.

I went to this talk because I love Lost Garden and because slides from talks he’s posted there before looked good. But it was mostly focused on how to use ideas from social games to be successful on Flash portals; not so interesting for somebody who has been reading Dan’s ideas on his blog for years, who is already in the social game space, and who doesn’t want to be successful on Flash portals.

3:00 pm: Seriously, Make YOUR Game!, by Paolo Pedercini and Jason Rohrer.

Paolo’s bit was amusing theater. Jason’s went into the details more: it turns out that his upcoming African diamonds DS game didn’t have its origin as a social statement, but rather from thinking of what multiplayer strategy video games can do that board games can’t, deciding that hidden knowledge (e.g. spying on the other player’s position) is one possibility, and coming up with a game mechanic where hidden knowledge about knowledge would work. (Having agents in the field buying diamonds, who can possibly be bribed.)

Also, when playtesting the basic purchasing mechanics with a physical game, he found that they weren’t much fun; going into it a bit more, he discovered that they’d stumbled on Nash equilibrium behavior. He broke that in two ways: by introducing a nontransitive relationship (basically, a hidden rock-paper-scissors mechanic, to avoid a dominant strategy) and by having bids where both the winner and loser pay (to avoid having the bid price settle at the item’s value).

4:15 pm: Indie Gamemaker Rant!.

No super standouts, though certainly better than yesterday’s AI rant. I guess the part that clicked the most with me was Robin Hunicke talking about the many ways in which having a male-dominated industry is a problem. Certainly her and Kellee’s talk earlier this morning struck me as a good example of how bringing a broader set of perspectives is likely to have a positive effect on your game’s development.


So that was today’s talks; my first time going to the Summits part of the conference, it’s mellower than the main conference. Very nice dinner, too, and I was glad to finally get to meet Jorge Albor!

Post Revisions:

Changes:

March 10, 2010 @ 22:36:18Current Revision
Content
Unchanged: Today's talks:Unchanged: Today's talks:
Deleted: <strong>10am: <a href="https:/ /www.cmpevents.com/ GD10/a.asp?option= C&V=11&SessID=10393">How to Manage an Exploratory Development Process</a>, by Kellee Santiago and Robin Hunicke.</strong> Added: <strong><a name="santiago- hunicke">10:00 am: </a><a href="https:/ /www.cmpevents.com/ GD10/a.asp?option= C&V=11&SessID=10393">How to Manage an Exploratory Development Process</a>, by Kellee Santiago and Robin Hunicke.</strong>
Unchanged: I heard Robin speak in the microtalks <a href="http:// malvasiabianca.org/archives/ 2009/03/gdc-2009- thursday/">last year</a>; she's at <a href="http:// www.bactrian.org/~carlton/ dbcdb/1219/"> thatgamecompany</a> now. Good talk, and surprisingly moving: they started off by talking about how, at E3 2008, they debuted <a href="http:// www.bactrian.org/~carlton/ dbcdb/1221/"> <cite>Flower</cite></a>, the press and their publisher loved it, yet the team's morale was at an all-time low! Their development process was putting all sorts of stresses on them, which they needed to fix lest the company implode soon. (Which, I should emphasize, isn't anything particularly negative about their company, just typical game development culture.)Unchanged: I heard Robin speak in the microtalks <a href="http:// malvasiabianca.org/archives/ 2009/03/gdc-2009- thursday/">last year</a>; she's at <a href="http:// www.bactrian.org/~carlton/ dbcdb/1219/"> thatgamecompany</a> now. Good talk, and surprisingly moving: they started off by talking about how, at E3 2008, they debuted <a href="http:// www.bactrian.org/~carlton/ dbcdb/1221/"> <cite>Flower</cite></a>, the press and their publisher loved it, yet the team's morale was at an all-time low! Their development process was putting all sorts of stresses on them, which they needed to fix lest the company implode soon. (Which, I should emphasize, isn't anything particularly negative about their company, just typical game development culture.)
Unchanged: Some of the key points for how to build a sustainable development process, so they can keep making the games they love indefinitely instead of burning out after a few years:Unchanged: Some of the key points for how to build a sustainable development process, so they can keep making the games they love indefinitely instead of burning out after a few years:
Unchanged: <ul><li>They needed to distinguish between commitments and estimates.</li></ul>Unchanged: <ul><li>They needed to distinguish between commitments and estimates.</li></ul>
Unchanged: Both are important; but, if you don't hit an estimate, that may be a learning experience (or may not, variability is natural, especially in creative work), but certainly isn't anything to beat yourself up over (or for others to beat you up over), whether consciously or subconsciously.Unchanged: Both are important; but, if you don't hit an estimate, that may be a learning experience (or may not, variability is natural, especially in creative work), but certainly isn't anything to beat yourself up over (or for others to beat you up over), whether consciously or subconsciously.
Unchanged: Also, in an exploratory phase in your process, who knows how long it will take to find the game's real core mechanic. (Shades of <a href="http:// malvasiabianca.org/archives/ 2009/03/gdc-2009- wednesday/">Iwata's keynote last year</a>.) So estimates there have a particularly large margin of error. Be confident that you still have a vision for the game inside of you; it will come out eventually.Unchanged: Also, in an exploratory phase in your process, who knows how long it will take to find the game's real core mechanic. (Shades of <a href="http:// malvasiabianca.org/archives/ 2009/03/gdc-2009- wednesday/">Iwata's keynote last year</a>.) So estimates there have a particularly large margin of error. Be confident that you still have a vision for the game inside of you; it will come out eventually.
Unchanged: <ul><li>Planning and feedback is important.</li></ul>Unchanged: <ul><li>Planning and feedback is important.</li></ul>
Unchanged: They have a big board sketching out milestones over the entire lifetime of the project; on a smaller level, they have two-week sprints, with standups three days a week. Their sprint goals aren't as rigid as some teams do them, but it's important to have the task cards up there, as a point for discussion.Unchanged: They have a big board sketching out milestones over the entire lifetime of the project; on a smaller level, they have two-week sprints, with standups three days a week. Their sprint goals aren't as rigid as some teams do them, but it's important to have the task cards up there, as a point for discussion.
Unchanged: Which leads to what I saw as their main takeaway:Unchanged: Which leads to what I saw as their main takeaway:
Unchanged: <ul><li>Have conversations; don't shy away for them, especially if they're difficult.</li></ul>Unchanged: <ul><li>Have conversations; don't shy away for them, especially if they're difficult.</li></ul>
Unchanged: The point of having task cards is so that you can see and talk about them if they're not moving as you expect: are they harder than expected, are they unpleasant, are they simply something that nobody cares about? Or, if your explorations suggest that expected mechanics won't work or that you'll need more exploration than expected, don't hide, even though you're really nervous: talk to your publishers, talk to your marketers. And don't just give the bad news: talk about your vision, talk about why you think this will make the game better. More broadly: remember that conversations aren't part of a zero-sum game: they're all on the same team!Unchanged: The point of having task cards is so that you can see and talk about them if they're not moving as you expect: are they harder than expected, are they unpleasant, are they simply something that nobody cares about? Or, if your explorations suggest that expected mechanics won't work or that you'll need more exploration than expected, don't hide, even though you're really nervous: talk to your publishers, talk to your marketers. And don't just give the bad news: talk about your vision, talk about why you think this will make the game better. More broadly: remember that conversations aren't part of a zero-sum game: they're all on the same team!
Unchanged: One other amusing bit from the talk: we call a task easy in one of three cases: 1) we really want it to happen; 2) we have no idea what it entails; or 3) we don't have to do it ourselves!Unchanged: One other amusing bit from the talk: we call a task easy in one of three cases: 1) we really want it to happen; 2) we have no idea what it entails; or 3) we don't have to do it ourselves!
Unchanged: And, finally, the summary:Unchanged: And, finally, the summary:
Unchanged: <ul>Unchanged: <ul>
Unchanged: <li>Be honest.</li>Unchanged: <li>Be honest.</li>
Unchanged: <li>Wandering is okay.</li>Unchanged: <li>Wandering is okay.</li>
Unchanged: <li>On every project.</li>Unchanged: <li>On every project.</li>
Unchanged: <li>Until you die.</li>Unchanged: <li>Until you die.</li>
Unchanged: </ul>Unchanged: </ul>
Deleted: <strong>11:15 am: <a href="https:/ /www.cmpevents.com/ GD10/a.asp?option= C&V=11&SessID=10370">Kids and Parents Playing Together Online: the Next Frontier of Casual Gaming</a>, by Jesse Schell.</strong> Added: <strong><a name="jesse-schell">11:15 am: </a><a href="https:/ /www.cmpevents.com/ GD10/a.asp?option= C&V=11&SessID=10370">Kids and Parents Playing Together Online: the Next Frontier of Casual Gaming</a>, by Jesse Schell.</strong>
Unchanged: Lots of good points here, starting from the basic point that you have to <em>decide</em> to design for this, not just (for example) build a kids' game and hope that the parents will like it. Looking through my notes, I don't see any huge insights that I'll be able to provide beyond what you'd get from <a href="http:// www.slideshare.net/ jesseschell/ designing-for- kids-and-parents- playing-together">his slides</a>, so I'll just embed them here.Unchanged: Lots of good points here, starting from the basic point that you have to <em>decide</em> to design for this, not just (for example) build a kids' game and hope that the parents will like it. Looking through my notes, I don't see any huge insights that I'll be able to provide beyond what you'd get from <a href="http:// www.slideshare.net/ jesseschell/ designing-for- kids-and-parents- playing-together">his slides</a>, so I'll just embed them here.
Unchanged: <div style="width:425px" id="__ss_3388046"><object width="425" height="355"><param name="movie" value="http:/ /static.slidesharecdn.com/ swf/ssplayer2.swf?doc= designingforkidsandparentsplayingtogether- 100310123151- phpapp01&stripped_ title=designing-for-kids- and-parents-playing-together" /><param name="allowFullScreen" value="true"/><param name="allowScriptAccess" value="always"/><embed src="http://static.slidesharecdn.com/ swf/ssplayer2.swf?doc= designingforkidsandparentsplayingtogether- 100310123151- phpapp01&stripped_ title=designing-for-kids- and-parents-playing-together" type="application/ x-shockwave-flash" allowscriptaccess="always" allowfullscreen="true" width="425" height="355"> </embed></object></div>Unchanged: <div style="width:425px" id="__ss_3388046"><object width="425" height="355"><param name="movie" value="http:/ /static.slidesharecdn.com/ swf/ssplayer2.swf?doc= designingforkidsandparentsplayingtogether- 100310123151- phpapp01&stripped_ title=designing-for-kids- and-parents-playing-together" /><param name="allowFullScreen" value="true"/><param name="allowScriptAccess" value="always"/><embed src="http://static.slidesharecdn.com/ swf/ssplayer2.swf?doc= designingforkidsandparentsplayingtogether- 100310123151- phpapp01&stripped_ title=designing-for-kids- and-parents-playing-together" type="application/ x-shockwave-flash" allowscriptaccess="always" allowfullscreen="true" width="425" height="355"> </embed></object></div>
Deleted: <strong>11:45 am: <a href="https:/ /www.cmpevents.com/ GD10/a.asp?option= C&V=11&SessID= 10586">Lessons Learned building Moshi Monsters to 15m Users</a>, by Michael Acton Smith.</strong> Added: <strong><a name="michael- acton-smith">11:45 am: </a><a href="https:/ /www.cmpevents.com/ GD10/a.asp?option= C&V=11&SessID= 10586">Lessons Learned building Moshi Monsters to 15m Users</a>, by Michael Acton Smith.</strong>
Unchanged: <a href="http:// www.moshimonsters.com/ "><cite>Moshi Monsters</cite></a> was done by a company that had just burned through most of their venture funding, on a real-world cross-media game <cite>PerplexCity</cite> that sounded fascinating but wasn't profitable. So they didn't have much margin of error. Failure was still okay, but they needed to fail fast: which they started off doing, by trying a Webkinz model of physical goods linking to an online world. They stopped doing that, and immediately got a lot more signups, which they eventually managed to monetize quite successfully.Unchanged: <a href="http:// www.moshimonsters.com/ "><cite>Moshi Monsters</cite></a> was done by a company that had just burned through most of their venture funding, on a real-world cross-media game <cite>PerplexCity</cite> that sounded fascinating but wasn't profitable. So they didn't have much margin of error. Failure was still okay, but they needed to fail fast: which they started off doing, by trying a Webkinz model of physical goods linking to an online world. They stopped doing that, and immediately got a lot more signups, which they eventually managed to monetize quite successfully.
Unchanged: They monetized using a subscription model; he said that a good subscription model is sliced (so free players get to see parts of it), and visual (so free players can see what subscribing players have). The price points matter: they had 1 month, 6 months, and 12 month plans, and initially set them up so the longer plans were a modest savings over shorter ones. That led to most people signing up for 1 months; so they switched to putting a much narrower gap between the 6 and 12 month plans (5 / 24 / 30 pounds, respectively), and all of a sudden almost everybody signed up for 12 months! Another anecdote along those lines: when the Economist had an online-only subscription for $59 and a print and online for $125, then 68% of people chose the online-only version; but when they added a print-only option to their price list, also priced at $125, then it switched to 84% of people choosing the print and online option!Unchanged: They monetized using a subscription model; he said that a good subscription model is sliced (so free players get to see parts of it), and visual (so free players can see what subscribing players have). The price points matter: they had 1 month, 6 months, and 12 month plans, and initially set them up so the longer plans were a modest savings over shorter ones. That led to most people signing up for 1 months; so they switched to putting a much narrower gap between the 6 and 12 month plans (5 / 24 / 30 pounds, respectively), and all of a sudden almost everybody signed up for 12 months! Another anecdote along those lines: when the Economist had an online-only subscription for $59 and a print and online for $125, then 68% of people chose the online-only version; but when they added a print-only option to their price list, also priced at $125, then it switched to 84% of people choosing the print and online option!
Deleted: <strong>1:45 pm: <a href="https:/ /www.cmpevents.com/ GD10/a.asp?option= C&V=11&SessID=10404">The Convergence of Flash Games and Social Games</a>, by Daniel Cook.</strong> Added: <strong><a name="daniel-cook">1:45 pm: </a><a href="https:/ /www.cmpevents.com/ GD10/a.asp?option= C&V=11&SessID=10404">The Convergence of Flash Games and Social Games</a>, by Daniel Cook.</strong>
Unchanged: I went to this talk because I love <a href="http:// lostgarden.com/">Lost Garden</a> and because slides from talks he's posted there before looked good. But it was mostly focused on how to use ideas from social games to be successful on Flash portals; not so interesting for somebody who has been reading Dan's ideas on his blog for years, who is already in the social game space, and who doesn't want to be successful on Flash portals.Unchanged: I went to this talk because I love <a href="http:// lostgarden.com/">Lost Garden</a> and because slides from talks he's posted there before looked good. But it was mostly focused on how to use ideas from social games to be successful on Flash portals; not so interesting for somebody who has been reading Dan's ideas on his blog for years, who is already in the social game space, and who doesn't want to be successful on Flash portals.
Deleted: <strong>3:00 pm: <a href="https:/ /www.cmpevents.com/ GD10/a.asp?option= C&V=11&SessID= 10604">Seriously, Make YOUR Game!</a>, by Paolo Pedercini and Jason Rohrer.</strong> Added: <strong><a name="pedercini- rohrer">3:00 pm: </a><a href="https:/ /www.cmpevents.com/ GD10/a.asp?option= C&V=11&SessID= 10604">Seriously, Make YOUR Game!</a>, by Paolo Pedercini and Jason Rohrer.</strong>
Unchanged: Paolo's bit was amusing theater. Jason's went into the details more: it turns out that his upcoming African diamonds DS game didn't have its origin as a social statement, but rather from thinking of what multiplayer strategy video games can do that board games can't, deciding that hidden knowledge (e.g. spying on the other player's position) is one possibility, and coming up with a game mechanic where hidden knowledge about knowledge would work. (Having agents in the field buying diamonds, who can possibly be bribed.)Unchanged: Paolo's bit was amusing theater. Jason's went into the details more: it turns out that his upcoming African diamonds DS game didn't have its origin as a social statement, but rather from thinking of what multiplayer strategy video games can do that board games can't, deciding that hidden knowledge (e.g. spying on the other player's position) is one possibility, and coming up with a game mechanic where hidden knowledge about knowledge would work. (Having agents in the field buying diamonds, who can possibly be bribed.)
Unchanged: Also, when playtesting the basic purchasing mechanics with a physical game, he found that they weren't much fun; going into it a bit more, he discovered that they'd stumbled on Nash equilibrium behavior. He broke that in two ways: by introducing a nontransitive relationship (basically, a hidden rock-paper-scissors mechanic, to avoid a dominant strategy) and by having bids where both the winner and loser pay (to avoid having the bid price settle at the item's value).Unchanged: Also, when playtesting the basic purchasing mechanics with a physical game, he found that they weren't much fun; going into it a bit more, he discovered that they'd stumbled on Nash equilibrium behavior. He broke that in two ways: by introducing a nontransitive relationship (basically, a hidden rock-paper-scissors mechanic, to avoid a dominant strategy) and by having bids where both the winner and loser pay (to avoid having the bid price settle at the item's value).
Deleted: <strong>4:15 pm: <a href="https:/ /www.cmpevents.com/ GD10/a.asp?option= C&V=11&SessID= 10807">Indie Gamemaker Rant!</a>.</strong> Added: <strong><a name="indie-rant">4:15 pm: </a><a href="https:/ /www.cmpevents.com/ GD10/a.asp?option= C&V=11&SessID= 10807">Indie Gamemaker Rant!</a>.</strong>
Unchanged: No super standouts, though certainly better than yesterday's AI rant. I guess the part that clicked the most with me was Robin Hunicke talking about the many ways in which having a male-dominated industry is a problem. Certainly her and Kellee's talk earlier this morning struck me as a good example of how bringing a broader set of perspectives is likely to have a positive effect on your game's development.Unchanged: No super standouts, though certainly better than yesterday's AI rant. I guess the part that clicked the most with me was Robin Hunicke talking about the many ways in which having a male-dominated industry is a problem. Certainly her and Kellee's talk earlier this morning struck me as a good example of how bringing a broader set of perspectives is likely to have a positive effect on your game's development.
Unchanged: <hr />Unchanged: <hr />
Unchanged: So that was today's talks; my first time going to the Summits part of the conference, it's mellower than the main conference. Very nice dinner, too, and I was glad to finally get to meet <a href="http:// experiencepoints.blogspot.com/">Jorge Albor</a>!Unchanged: So that was today's talks; my first time going to the Summits part of the conference, it's mellower than the main conference. Very nice dinner, too, and I was glad to finally get to meet <a href="http:// experiencepoints.blogspot.com/">Jorge Albor</a>!

Note: Spaces may be added to comparison text to allow better line wrapping.