Creating + Nurturing Your Indie Game Community
•
5 recomendaciones•1,820 vistas
A talk I gave the Independent Games Summit of the Game Developers Conference 2010
Recomendados
Más contenido relacionado
Similar a Creating + Nurturing Your Indie Game Community
Similar a Creating + Nurturing Your Indie Game Community (20)
Más de Jeff Lindsay
Más de Jeff Lindsay (19)
Último
Último (15)
Creating + Nurturing Your Indie Game Community
- 1. IGS 2010 CREATING + NURTURING YOUR INDIE GAME COMMUNITY Jeff Lindsay @progrium
- 2. SuperHappyDevHouse Event Hacker Dojo Place TIGSource / TIGJam Online Event
- 12. 10 (SORT-OF-CHRONOLOGICAL) TIPS FOR GROWING A C OM M U N IT Y
- 13. 1 Hold events 1
- 14. 1
- 15. 2 Make purpose 2
- 16. 3 Start small 3
- 17. 400 people 3
- 18. 20 people 3
- 19. 3 "A complex system that works is invariably found to have evolved from a simple system that works." 3
- 20. 4 Repeat often 4
- 21. SHDH 1 4
- 22. SHDH 1 4
- 23. SHDH 1 4
- 24. SHDH 7 8 months later 4
- 25. SHDH 7 8 months later 4
- 26. SHDH 7 8 months later 4
- 27. 4 "Release early, release often." 4
- 28. 5 Stay learning 5
- 29. 5
- 30. 5 "Fail early, fail often." 5
- 31. 5 "Release early, release often, and listen to your customers." 5
- 32. 6 Be inclusive 6
- 33. 6 Quality control? 6
- 34. 7 Identify values 7
- 35. 8 Think experience 8
- 36. 8
- 37. 8
- 38. 9 Teach promotion 9
- 39. 9
- 40. 10 Help duplicate 10
- 41. ‣Hold events ‣Make purpose ☺ ‣Start small ‣Repeat often ‣Stay learning ‣Be inclusive ‣Identify culture ‣Think experience ‣Teach promotion ‣Help duplicate
- 42. SuperHappyDevHouse 37 April 10, Palo Alto Hacker Dojo 24/7, Mountain View TIGJam 3 Fall, Hacker Dojo
- 43. THANK YOU. YOU ARE ALL RAD. STAY INDIE. @progrium
Notas del editor
- started devhouse, hacker dojo technical admin for tigsource, built tigdb helped start and influence tigjam
- going to focus on superhappydevhouse. i called it “devhouse” for short.
- “a party for hackers and thinkers” basically a hackathon, like a gamejam started in 2005 about every 6 weeks... almost 40 so far
- very open ended. no theme or focus. just come with your laptop.
- featured in the mercury news, cnet, sfgate, but mostly word of mouth
- we’ve done them in about 10 locations around the bay area. duplicated in over 20 cities around the world.
- last about 12 hours. currently, events range from 200-400 attendees
- full of discussions about things people are passionate about, sharing ideas... but its also about building cool stuff and working on projects.
- lots of regulars, lots of newcomers. very healthy community that led to...
- 24/7 physical manifestation of the spirit of devhouse. why community? free exchange of ideas/knowledge helps develop -- silicon valley. belonging, especially to things that stand for what you’re passionate about. “i found my people”
- NOTHING beats this. they’re easy to do and you get a lot from very little. this is the basis of the rest of the tips.
- really, you can build online communities, but nothing beats in-person. TIGJam shows this. GDC shows this. any excuse to get likeminded people together is awesome. parties, mixers... but great events happen when you:
- stand for something. i don’t so much mean “have a purpose” ... gimmicks and “attractions” (speakers, contests) make it about THAT. make it about something more and cultivate intrinsic value of people together with common values and purpose from OUTSIDE the event
- how do you start? start small. hardest part for people to do. indies know all about this. mvp: "if you're not embarassed by v1, you spent too long on it" remain light (we’ll come back to this)
- actually less than 20
- it’s important to remember: major events start from small events. gdc started in a living room with about as many people as devhouse. the key is to...
- this builds momentum and leverages buzz from last event for the next. annual events require much more marketing... if you look at blogging, improve readership: blog often, more importantly: consistently.
- let me show you. first devhouse. front room.
- kitchen.
- living room.
- 8 months later, doubling in size several times over... living room.
- kicthen
- front room. another advantage of often is allows more people to experience the event. one might not be able to make one month, but can the next. later you can spread them out if you want.
- experiment! challenge assumptions! which brings us to...
- build this into your culture
- how retrospectives work.
- if you do events often, it’s cheap to experiment. it’s ok to make mistakes.
- include whoever is around and wants to participate in retrospective
- another key to growth. both for organizers and attendees. organizers: whoever joins in. give them responsibility. attendance: don’t turn people away. welcome those on the fence.
- focus on what you DO want, not so much on what you DON’T want. positive reinforcement is more effective long term. have the “right” people from the beginning. always invite people that exemplify what you stand for.
- understand what you’re about, and try to be explicit about it. stay true and remember what you stand for. indie games is pretty easy and the ongoing debate of “what is indie” is healthy.
- ux, interaction design. creating spaces that influence desired experience... and behavior!
- used to have sign
- maximizing table usage. arranging chairs
- grassroots movements rely on word of mouth. engineer it. in fact, straight out teach it
- applied lessons from gdc keynote for shdh 30 to great success
- mexico vs the world. mexico was the only case where WE went to help them start it. then they send ambassadors to new events nothing beats in-person knowledge sharing!
- these are all the tips. feel free to ask me in person if you want more or have questions
- also feel free to come to any of these
- lots of communities are online, but this is about validating/bootstrapping. meetup.com kinda. all you need is a wiki. dojo started wiki, then google group. acts as a way to gather momentum. useful for massive things like dojo, but really you should just...