Skip to content

Latest commit

 

History

History
77 lines (44 loc) · 1.78 KB

File metadata and controls

77 lines (44 loc) · 1.78 KB

Creative Incubation 2019-08-27

PAX Dev Tuesday 8/27

overview of critical issues for a video game startup

value of IP portfolio

trademarks cheaper than patents by an order of magnitued

copyrights are automatic. Add a circle c for clarification

The infinite storytelling of professional wrestling

babyface and heel

shine, cutoff, heat (hate), come back, finish

PAX Dev Wednesday 8/28

Worldbuilding

pictures of characters/places are useful. Consider this for story development, Look for pictures of characters and spaces.

Play Nice: how to build a healthy gaming community

Surviving in a crowded market

1000s of games. Everyone ignores yours.

lostgarden.com

Writing Effective Design Specs

  • use specs to review and resolve conflicts
  • How can we write specs to be as clear and effective as possible?

Designers are often really bad at writing clearly. Designers think their work is perfect.

Good writing and good technical writing are not the same thing. Interesting writing may get in the way of what you are trying to communicate.

You are not your spec.

  • your design is stupid
  • it's obvious and trite

Get your ego out of the process. You have actually just created a starting point of a conversation.

Specs are not arguments. Get some amount of by-in early.

It helps to think that your spec is crap, then you will be better able to get constructive feedback and incorporate it into your bad spec. Don't let your team on to this. It may look like false modesty.

two objectives

  • technically correct
  • easy to understand

be honest if the design is broken

lose an argument

slide deck available at twitter: @HBS_Kiva

https://t.co/Pn09UaxbSR

The Creative Battery

How do we ensure that our creative discussions and collaborations focus on positive interactions?