Tips from Industry Vets – Julie Wotzko
summary
Fifteen years across card games, Cake Mania, Xbox dashboard and Hololens lead to concrete habits: carry a notebook and photograph ideas, find a mentor, and learn tools like Trello and Microsoft Project so producers can slot art straight into pipelines. Burnout is real — one year off to learn programming is given as an example. Representation and testing with non‑gamers drive new audiences. Break process when it blocks creativity but accept consequences, budget money (not just time), and ship early to learn what actually works.
AI-written summary · about
chapters (12)
- 0:00Intro
- 0:55Have a book
- 1:47Learn from rubbish
- 2:38Representation
- 3:16Process
- 3:48Art
- 4:43Sales Manager
- 5:12Innovation
- 6:08Storytelling
- 6:51Be aware of repercussions
- 7:36Know your fundamentals
- 8:44Easter eggs
related talks
31mPanel: Tutorial Mode: What Every Developer Needs To Know Before Joining the Games Industry.
57mHard truths and soft skills: 10 pieces of advice for novice game devs
54mHow To Survive Working At An Indie Studio
01h 05mFive Game Developer Habits That Help Software Engineers
51mSo you (or someone else decided) you're a producer
26mAll the things I learnt as a junior developer (so you don't have to)
37mPanel: What are the Things You Wish You Knew When You Started Developing Your Games
28mAdvice from a young designer to younger designers