Conferintele Softbinator - George Lemnaru - Should devs make product decisions?

Transcript

1. Should devs make product decisions? by George Lemnaru Cofounder Green Horse Games
2. Case 1 - The corporation • huge gaming company (20+ studios) • great console titles • wants to make a social game in Romania
3. Case 1 - The recipe • cheap Romanian team • add a game designer (in France) • design by committee • a marketing test budget of 200k eur
4. Case 1 - The result • A "me too" game • close to 0 Retention • closed game => money and time lost • frustrated team leaving the company
5. Case 2 - eRepublik (2009) • medium to small company • launched an innovative concept • team 95% in Bucharest • just got 2 millions eur in funding • wants to take the game to the next level
6. Case 2 - The recipe Let's become a serious company: • hire a lot (we have money) • hire in Madrid (we want to be .com) • Romanians should just build tons of features • build a great eRepublik V2 • let's copy latest concepts in the industry
7. Case 2 - The results (2010) • All the money spent in 1 year • Romanian team disintegrating • Users rage quiting • Sells dwarfed • A great technical implementation • Almost closing the company
8. Case 3 - eRepublik recipe (take 2) Moving back the product decisions to Bucharest
9. Case 3 - The results • Double the users in 2 months • Sales increased 6 times in 6 months • 2011 was the most financially successful year • More games to be launched
10. So what makes or breaks a company Company values
11. Some cool company values • Results and user oriented environment • Simplicity and care for your work • Autonomy and responsibility • Find the real cause (Why?)
12. Problem 1 Devs will write much less code
13. Problem 2 People might leave at some point
14. Problem 3 This doesn't work with every person
15. Problem 4 Democracy in design
16. copyright: Drive - Daniel Pink
17. Thank you George Lemnaru email: george.lemnaru@gmail.com Green Horse Games