<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Christine Brownell on Medium]]></title>
        <description><![CDATA[Stories by Christine Brownell on Medium]]></description>
        <link>https://medium.com/@cbrownell?source=rss-607ce55ed14------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*pVKdLO197N6Erx-qW96_Jw.jpeg</url>
            <title>Stories by Christine Brownell on Medium</title>
            <link>https://medium.com/@cbrownell?source=rss-607ce55ed14------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 12:26:55 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@cbrownell/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Finding a New Path: How I Survived a Game Industry Layoff]]></title>
            <link>https://cbrownell.medium.com/finding-a-new-path-how-i-survived-a-game-industry-layoff-d97068ebff58?source=rss-607ce55ed14------2</link>
            <guid isPermaLink="false">https://medium.com/p/d97068ebff58</guid>
            <category><![CDATA[layoffs]]></category>
            <category><![CDATA[games]]></category>
            <category><![CDATA[game-industry]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[game-development]]></category>
            <dc:creator><![CDATA[Christine Brownell]]></dc:creator>
            <pubDate>Fri, 01 Mar 2019 03:31:41 GMT</pubDate>
            <atom:updated>2023-10-04T12:54:45.949Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TIYRe1BhMFLCVijk0euiMQ.png" /></figure><p>“Hey, I’m grabbing a bagel on my way in. Want one?” I cheerily answered an unexpected call from a coworker on what seemed like an ordinary Tuesday morning.</p><p>“I just got laid off.”</p><p>He related this information without any greeting, without giving details, and without trying to hide how he was feeling.</p><p>At the time, we were both designers at Blizzard Entertainment, working on the recently released World of Warcraft. Blizzard was an amazing place to work; we knew it to be different, special even, an anomaly within an industry that was rife with studio closures and layoffs. I was completely convinced that I had the best job in the whole world, and I was excited to get to work every day.</p><p>But on that morning, standing next to my car with phone in hand, I was suddenly confused and anxious.</p><p>“I’m coming right now.”</p><p>I met my friend in the back parking lot of the (now former) nondescript building that housed Blizzard Entertainment HQ at 131 Theory in Irvine, California. He explained that only a short time after he had arrived at work, he had been taken to a conference room and told that the company was doing some “streamlining,” resulting in several roles being cut from the team. His was one of them.</p><p>Soon others joined us in the parking lot, deposited outside the building as he had been. Each held a white folder with their name printed on it, and each had the same story.</p><p>I was terrified to go inside; not knowing what awaited me.</p><p>It was February 8, 2005. WoW had been released not even 3 months prior, and while it was very early in its life, it was already a wild success. Since launch, the 60-person WoW team had been hard at work on a major content patch.</p><p>I had joined the team as a Quest Designer around a year prior, and it had been the best day of my life, moving up from Quality Assurance to my dream job on the dev team. My main contribution to this patch was to be an elaborate quest line that earned players a cloak made from the scales of Onyxia, a black dragon (and at the time, one of the most challenging boss fights in the game). I had been enjoying it immensely and was looking forward to doing more work on it that day.</p><p>And so I summoned all my courage and ventured inside. Walking through the building past rows of offices, I scanned for anything out of the ordinary, but noticed nothing amiss. I arrived in my own office to find one of my teammates working quietly at his desk. It could have been any other morning.</p><p>“There’s something going on,” I told him. “People are getting laid off today.” He looked at me as if he didn’t quite believe me. I can’t say I blamed him; for the entirety of my career there, Blizzard treated their employees like family. Team 2 had become a very a close-knit group after months and months of crunch on WoW. We worked hard, but we loved the work, we felt appreciated, and above all we felt safe. This wasn’t just a company; this was our home.</p><p>I set my backpack down at my desk and headed immediately to the office of one of the other designers. Thankfully, he was there at his desk working, or at least maintaining the pretense of working.</p><p>“I don’t know exactly what’s happening, but look, you’re a great designer. I’m sure you’re safe.” It was an incredibly kind thing for him to say when it’s quite possible he was as worried as I was. And I wish he had been right. Not more than two minutes later, the Lead Designer on WoW (my manager), showed up, looking for me.</p><p>“Let’s go,” he said quietly.</p><p>I followed him out of the door and to the stairs, my mind racing, in an absolute panic. I barely felt my feet touching the ground. How could I stop this? There were no answers. We started down the steps.</p><p>“Wait,” I said, as we approached the landing between the first and second floors. This wasn’t over yet; we hadn’t made it to that room yet, so right now, I still had a job. He turned back and looked at me.</p><p>“What’s my move here? What can I do? What would you do if you were me?” Fight or flight in full effect, the questions spilled out on top of one another. Looking back now, I think it was just a very wordy way of saying, “Please, help me.” It was probably more effective than just screaming, which is what I really felt like doing.</p><p>He sighed, looked down at the floor, and then back at me. He reluctantly told me that I had been the last one added to the list, that it hadn’t been an easy decision. He advised me to let the dust settle, and then to call him, and he would help me in any way he could. In that moment, he showed me the only kindness he had to give, and I was grateful.</p><p>We arrived at a small conference room on the first floor. Inside I found the Blizzard CEO and a woman from Vivendi Universal HR whom I had never seen before. (At the time, Vivendi Universal was the parent company of Blizzard Entertainment.) She instructed me to take a seat.</p><p>A white folder slid across the table and was opened. The complete stranger proceeded to thank me for my hard work, say words like “streamlining” and “no longer needed” and then methodically explain my severance package.</p><p>I could barely process what she was saying as the world closed in around me. Both furious and on the verge of tears, I knew that if I opened my mouth I might end up saying something I’d regret later. So I maintained my silence throughout the entire meeting, only nodding when prompted to acknowledge I understood. I signed my name on the line.</p><p>The CEO stood to one side of the small room, looking deeply upset. I think he may have said something to me as I got up and made my way out of the room, but I can’t really remember. At that moment, it felt like any appreciation for the work I had done was nonexistent. Everything was a blur. I was led to the door, folder in hand.</p><p>Thanks, but get out.</p><p>I asked to go retrieve my backpack from my desk and was informed that I was no longer allowed in the building, effective immediately. While employed by Blizzard, I had been nothing but a loyal employee, so proud of the company I worked for. Out of everything that happened that day, this callous display of distrust was by far the most dehumanizing; the worst betrayal I had ever felt.</p><p>I arrived back out in the parking lot, sans backpack. As word had started to travel, teammates that hadn’t been affected trickled outside in small groups to express their sadness and to say farewell to those of us who had been let go. We were all in disbelief that such a thing could have happened at this place we all loved so very much.</p><p>In the end, there was nothing to do except say goodbye; to the colleagues that felt like family, to the best job I had ever known, and the place that had felt like home. My time at Blizzard was over.</p><h3>The Journey</h3><p>This happened fourteen years ago. In 2005, social media didn’t exist to the extent it does now, and the game industry news wasn’t nearly as mainstream, so layoff announcements were not typically blasted on the internet. This particular layoff went largely unnoticed by anyone that didn’t work at Blizzard at the time. In terms of numbers, it pales in comparison to the magnitude of <a href="https://kotaku.com/activision-blizzard-begins-massive-layoffs-1832571288">the recent Activision Blizzard layoff</a> (~800) or <a href="https://www.gamesindustry.biz/articles/2019-02-21-arenanet-reportedly-bracing-for-mass-layoffs">the ArenaNet layoff</a> this week (labeled only as “big”), or <a href="https://www.gamesindustry.biz/articles/2019-02-22-massive-layoffs-at-eas-australian-studio">the layoff at EA studio FireMonkeys</a> (~50), also this week. So why am I writing this now?</p><p>Reading articles about these layoffs, and scrolling through my news feed to see friends affected, my own story kept playing over and over in my head. I couldn’t stop thinking about all of us; the people impacted by a single decision that was made by the company they worked for. In the span of only a few hours, all of our lives changed dramatically, and we have all had to deal with the aftermath.</p><p>We are all part of a story that doesn’t change, whether it happened today or fourteen years ago. (It’s a story that happens far too often in games.)</p><p>I know how alone I felt in the days after I had been laid off, and while I was lucky enough to have some amazing, supportive friends that did their best to lift me up, there was a lot for me to work through before I could really process what had happened, understand how to deal with it, and come up with a plan for what to do next.</p><p>There’s no way for me to know how each individual has been impacted and how they might be dealing with their own situation — and that makes offering advice difficult. Sure, I can suggest you find clever ways to save money, compare replacement health plans, or point to the best sites to find job postings. But those things are the easy things. The biggest challenge I faced after being laid off was dealing with the emotional impact.</p><p>So what I can offer is my own personal experience — the complex feelings I had about the layoff itself, how I worked through them, and how I got myself back on the path and moving forward, back when it happened to me.</p><h3>The Day After</h3><p>Well over a decade later, the day I was laid off is still the worst day I can remember. (There’s a reason it’s taken me fourteen years to put this story into words.) But after that single day ended, I found that I wasn’t at all prepared for the days that followed; I didn’t yet know how long it would take me to process what had happened, how far-reaching its impact would be in my life, or that I would actually end up learning a great deal as a result.</p><p>Directly after it happened, it was so painful that I could barely talk about it, but simultaneously wanted desperately to talk about it — as if talking about it would somehow make it right and release me from the horrible feelings of loss that I carried. But it didn’t. Speaking about it seemed to help in the moment, but then afterwards I’d be again reminded that nothing had changed, and I was stuck with my situation, with all the feelings that I just really wanted to forget.</p><p>As the days passed, left alone with my thoughts, I started to fall into some unhealthy but predictable patterns. I began to wonder if the “streamlining” was actually just a way to hide what was more of just a personal hit list for the project leads. What if it <em>was </em>personal? While I worked at Blizzard, I had never been given a negative review, but what if getting rid of me (and the others) was just a reflection of some unknown mistake we had made?</p><p>My mind kept brainstorming ridiculous solutions to this unsolvable problem. What could I have done better? What if I had written more quests? Had more ideas? Fixed more bugs? Produced fewer bugs to begin with? What if I had come into work earlier? Stayed later? What if I had gotten along better with that one designer that no matter how hard I tried, I couldn’t seem to win over? My mind wrestled with these and other questions endlessly. I became convinced that what had happened to me was my fault. I felt ashamed and miserable.</p><p>So I did the only thing I could do at the time to give myself a break from the storm constantly swirling in my head — I found a distraction. For me, this meant throwing myself wholeheartedly into searching for a new job. Each morning I’d open my laptop and get to work, spending hours polishing my resume, hunting down job postings, and writing individualized cover letters to each potential employer. I kept a detailed spreadsheet of the companies I had applied to (like any good game designer would).</p><p>This distraction gave me a break from the negative feelings that just wouldn’t quit. I didn’t have time to think about how bad I felt because I kept myself busy with small goals. I could be successful at finding job postings. I could be successful at summarizing my skills into bullet points. I could be successful at typing words into the body of an email. These little successes helped me feel like I had at least a tiny bit of agency in a situation where I was, in reality, so powerless.</p><p>While I found comfort in spreadsheets and wordsmithing, I know there were also a couple of people that spent a few weeks just playing WoW. And that worked for them. We all need to find something that helps us get out of bed each morning, no matter what it might be.</p><p>If you’ve been laid off, take some time for yourself without judgement, and do it in the way that feels right for you. If you want to be productive, do that. If you want to be lazy, do that. But don’t sit around just thinking about how terrible you feel about getting laid off. What you need to do is to get yourself through those first few days when everything is raw and you are adjusting to a new reality.</p><h3>Moving On &amp; Letting Go</h3><p>For a very long time after the layoff, I continued to carry the weight of that moment with me, and it was heavy. It was an ever-present feeling that made me feel like I had a dagger stuck in my heart, a vice around my chest. I can still remember the feeling of that emotional pain, manifesting physically. And my swirling thoughts were so complex; comprised of sadness, loss, betrayal, anger, and shame. On the outside, I think I appeared to bounce back quickly, but on the inside, I hadn’t figured anything out.</p><p>I missed my coworkers immensely; they had grown to be my friends over the time I worked with them. But after I was laid off, talking with them was a painful reminder of the life I no longer had. That they’d casually mention that they’d received WoW bonus checks the size of their yearly salary probably didn’t help either.</p><p>By maintaining contact with them, I was well aware of what I was missing. I’d meet them for lunch and things would be just like they were — but then we would part, and they went back inside the office to work on the game we all loved, and I didn’t. I felt like an outcast, exiled and forbidden to return.</p><p>What ended up being necessary for me was to put some space between me and all those people I loved at Blizzard. I found that I couldn’t talk to them about what I was going through — it was awkward, they either felt guilty or couldn’t relate, and there were too many reminders of what I was missing out on. They unintentionally bummed me out. I remember this being very confusing for me at the time.</p><p>I ended up leaning on friends that had either been through the same experience at another company, or were not connected to Blizzard at all. They reassured me when I was full of self doubt about my own abilities, comforted me when I was having a particularly rough day, or simply listened when I needed to vent about WoW team members buying exotic cars with their bonus checks. (Yes, that happened.)</p><p>My friends were essential to my healing process. Find yours, and ask for help when you need it.</p><h3>The Shame of Failure</h3><p>Layoffs have a way of making you feel personally shamed. Everyone will tell you not to take it personally, and that it’s not your fault, that it’s just about numbers. It rarely ever helps when someone points this out, though. Being laid off impacts your life in a major way — it feels <em>very </em>personal!</p><p>If your entire team has been made redundant or your parent company is doing some cutbacks and you are all leaving together, then things are pretty clear: it’s not about you. There wasn’t anything you could have done differently to prevent the situation you’re in, short of never working there to begin with. Being laid off isn’t ever easy, but if you are able to understand why it’s happened, it is easier to move on to your next big thing.</p><p>But things start to get complicated if some of the team is cut and some of it isn’t — and some layoffs are like this. It’s really easy for a company use terms like “streamlining” or “budget cuts.” Reasons like that don’t explain anything about why specific people were cut and others weren’t. The truth is that if you were cut and one of your coworkers was not, at least some percentage of that decision was personally about you (your skills, experience, work ethic, or personality) and that reality can be tough to deal with.</p><p>Compounding this, it can be hard to find closure and move on because there isn’t a way to get the whole story. When I was laid off, yet others weren’t, I suspected that I wasn’t being given the entire truth. There was no one for me to ask, no one that was willing to give me a truthful answer, or possibly, no one that really had a good answer to begin with. And this was frustrating for me because I just really wanted to know — if only to understand what I could have done better. But that never happened.</p><p>The good news is that I long ago stopped wondering about it, and have accepted the reality that we don’t always get answers, even if we deserve them. I can’t even say that if I had been given an answer, that it would have helped me find closure, the way I assumed it would.</p><p>However, what finally allowed me to move on was a shift in my mindset regarding the way I view failure. Early on in my career, I viewed being laid off as my fault, my personal failure. I was ashamed of what had happened to me, and avoided mentioning it whenever possible. At the time I assumed I would be judged; that people would somehow hold it against me, that it would always be a negative mark on my pristine record. I imagined that it would somehow prevent me from attaining the career I hoped to have.</p><p>Over the years I’ve come to realize that failure is really just a step on a longer path of learning. Failures are the teaching moments that help us to become better, and internalizing this viewpoint has removed the stigma of talking about my experience. Being laid off is part of my journey, and it’s a moment that taught me many lessons.</p><h3>It’s Just Business</h3><p>My first learning was something very simple: A business is just that, a business.</p><p>No matter how warm and fuzzy your workplace feels, no matter how much you love your coworkers, and no matter how much your manager expresses appreciation for your hard work, a business is a soulless entity and it does not care about you. If a business is being run well, leadership will make decisions that are in the best interest of that business, regardless of their own personal feelings about you.</p><p>The company you work for is never going to choose you, advocate for you, or maintain loyalty towards you if doing any of those things poses a potential risk to the success or profitability of that business. Sometimes, you really are just a line in a spreadsheet, a single head in your department headcount, a box on the org chart.</p><p>When I worked at Blizzard, we believed we were all part of the family. When some of us were removed from that family swiftly and suddenly, we had to come to terms with the reality that what we had been told wasn’t actually true. Getting laid off was that much worse because we never expected it — and then we had to deal with feeling gullible as well. I’m sure we weren’t being actively lied to for nefarious purposes — but at the time, yeah, that’s definitely what it felt like.</p><p>At the point when the layoff occurred, I (and many others) had been working overtime for months (10–12 hour days, 6 days a week). My personal life had taken a backseat to the grueling pre-launch schedule that got WoW out the door. This is what we were asked to do, and I did it willingly, without hesitation. A few months later, I found myself jobless. I was loyal to a company that in the end felt no loyalty to me in return.</p><p>This was a harsh reality, but it helped me recognize that I had unrealistic expectations for what my employer and my job could provide to me. I assumed that my loyalty and hard work would be taken into account in all situations; that simply performing my job duties enthusiastically somehow guaranteed my eternal safety and inclusion. But business doesn’t work that way, and when I got laid off, I got the message, loud and clear.</p><p>How things ended for me at Blizzard wasn’t fair, but that’s because business isn’t fair. It’s a lesson I’ve carried with me since that day: to keep my expectations realistic, no matter the company or the role.</p><h3>Bad Experiences Can Motivate</h3><p>Being laid off was both the worst and best thing for me. I was completely destroyed when I lost that job — being a Quest Designer on WoW was my dream come true, and it was all I ever wanted to do. When I arrived at work each morning, I was still in disbelief that they paid me for working on a game I adored. I gladly worked overtime during crunch, I wore geeky Blizzard t-shirts to work almost every day, and I loved talking to WoW fans.</p><p>Having that all ripped away suddenly in such a harsh manner left a wound that took a long time to heal. But (and here’s why I say it was also the best) it also provided me with all the motivation in the world, driving me like an engine toward excellence, because I was determined to prove my worth in every role I accepted afterward.</p><p>The first design role I took after Blizzard was at a scrappy little game company in Colorado called NetDevil, where I worked on a game called Auto Assault. I walked through the door, committed to making it as a game designer — committed to proving to myself that Blizzard and its leadership had been wrong, committed to finding success in a new place.</p><p>“That will NEVER happen to me again,” I would think as I threw myself into my new responsibilities. I regularly delivered more content than I was asked to create, I stayed at work late every day, and I wrote up feedback and suggestions for the game on a weekly basis. I worked frantically to provide value to my new employer, running as fast as I could away from the ghost that was always right behind me — I was haunted every day by the thought that the job I loved could be taken from me at any moment.</p><p>An interesting thing started to happen over the course of that year. Fueled by my determination, all those little things I was doing started to add up, and those in charge began to take notice of my efforts. I found that when I spoke up in meetings, they listened to what I had to say. I became a contributor to the direction of the game; I was consulted when there were important decisions to be made and eventually I was offered a lead role on one particular area of the game. In contrast to being laid off less than a year prior, I was elated that I had found success in this new place.</p><p>My experience at NetDevil was a stark difference from my time at Blizzard, where being heard in meetings typically meant I would have to yell over the voices of alpha males who left few pauses in their design discussions for someone like me to join in. I was a brand new designer, and I was one of the only women working at Blizzard at the time. Although I was very excited to be on the dev team, I felt incredibly intimidated. My confidence in my own abilities was pretty low.</p><p>In contrast, once I dove in at NetDevil, I found that I could actually make valuable contributions by using skills and knowledge I had learned at Blizzard. Even better, my contributions were valued, so I began to have faith in myself and my ideas. After Blizzard, I realized that no one was going to wait around for me to feel the courage to speak up, and if I didn’t speak up, I wasn’t providing value to my employer.</p><p>As much as I don’t want to admit this, being laid off ultimately helped me find my voice and my confidence, and it started at NetDevil — a place I never imagined I would be when I began my career in games.</p><h3>Hidden Opportunities</h3><p>Before I was laid off, I had never, not even once in my life, ever seriously considered living anywhere except Orange County, California. I had grown up there, my family was there, and up until that day in February, my dream job was there. Once that was taken away, I realized that if I wanted to continue working in games, I had to apply at any company I could find, no matter where they were located.</p><p>So when I was offered that job at NetDevil, I took it, despite the fact that I had never been to Colorado before. I packed up my stuff and drove across a few states to my new home. Three weeks prior, I had been designing quests on WoW, eating lunch at our regular hangouts, and playing tower defense with coworkers; part of a team that had felt so magical to me. That was all gone, and I was in a new office building, working with people I hadn’t yet gotten to know, and it was snowing outside my window. Life changes that quickly.</p><p>Somehow well over a decade has gone by since I made that first jump. And that jump led to several more. From NetDevil, I joined a startup in San Francisco as the Lead World Designer on (yet another) MMO. After that, I joined The Sims team to work on The Sims 4. A number of years later, EA sent me to London to manage The Sims Social design team at Playfish. And since 2013, I’ve been running my own business. <em>(Edit: Since this article was written, I’ve had roles at Scopely, Media Molecule, and currently I am Game Director at PlayStation London Studio!)</em></p><p>My point in bringing this all up is that if I hadn’t been laid off, I never would have had the experiences I’ve had in the game industry over the last fourteen years. I’ve worked closely with people that I respect and admire; people that are varied and unique and have vastly different viewpoints of the game industry and of the world. I’ve had the opportunity to work at different types of companies from small startups to huge corporations; I have lived in so many interesting places. And I am positive that my path will lead me to many more. Being laid off opened the door to the world for me, and I’m incredibly grateful.</p><p>I will be completely honest here; had I not been laid off, I would never would have left Blizzard on my own. I was one of those die-hard employees that would have remained there forever, happy to be a part of a company I respected, and working on games I loved to play.</p><p>I sometimes wonder if I’d be happy or fulfilled with my career if my story had gone in the opposite direction. It’s quite possible that at Blizzard, with the dynamic that existed at the time (a total boys’ club), my skill level in navigating that particular environment (low), and the lack of a good mentor or manager that cared about my well being and success (which despite the love I had for that team, I did not have there), I may not have been able to reach my potential. At the very least, I doubt I’d be the designer or the manager I am today, had I not had the opportunity to do something different.</p><p>It’s taken me years to be able to recognize these things, and to reflect on them in this way. Truly, there is no way to know where I would be now, had I not been laid off that day in 2005. But I wouldn’t give up the experiences or the connections I’ve gained along the way for anything, and that’s the important bit.</p><p>Please know… I’m not trying to say that layoffs are ever a good thing. They aren’t; they are terrible for those that lose their jobs as well as those that remain. I won’t ever try to paint a silver lining on the situation. It’s awful, 100%.</p><p>What I am saying is that sometimes when unexpected things happen, you may be forced out of your comfort zone and it’s up to you to decide what you’ll do in that moment.</p><p>We can’t control when bad things happen. But what we can control is our own actions. There are always options, always opportunities, if you’re looking for them.</p><p>Choose to learn new skills. Choose to go places you’ve never been. Choose to work on projects you find fulfilling. Choose to find people you love and treasure and can’t imagine not being part of your life.</p><p>And know that in hindsight, you can credit a horrible moment in your life as the critical first step on the path to the wonderful place you’re at now. It is like this, for me. It turns out my career was only getting started at Blizzard, and the best was yet to come.</p><h3>What We Keep</h3><p>A few months after the layoff, I attended a party at the house of a former Blizzard coworker. As things began to wrap up for the night, the two of us began to talk about the time we worked together. Although the conversation was filled with happy memories, it became very bittersweet for me. I think I must have looked sad, because in that moment, my friend reminded me of something very important: that my work, my creations, they will always be a part of the game I loved working on.</p><p>They can take your job, but they cannot take the work you’ve done, the skills you’ve gained, or the connections you’ve made. Those things are yours, forever, no matter where your path leads you. It is such a simple thought — but it was the one I needed to hear then. So I’m sharing it, in case it’s what you need to hear too. The work you’ve done matters. Your teammates appreciated you. You will carry what you’ve learned with you, and you will move on, stronger, and better than ever.</p><h3>A Note for Survivors</h3><p>If you’ve experienced a layoff as a survivor, it can be difficult to manage your own feelings about what has happened. You may feel guilty about having a job when others do not; I know I felt this way when I found myself in that position in 2006 and again in 2007, when the company I worked for at the time did two different rounds of layoffs in two years, and I was one of the ones left standing. Team morale overall often takes a hit for quite some time, as the survivors learn to function with gaps in their team and a new dynamic.</p><p>As a survivor, there is one thing you can do that is incredibly important. Reach out to your former coworkers that have been laid off. Tell the people that you worked with that they are valuable, they are appreciated, and they didn’t deserve what happened to them.</p><p>When I was in the dark, feeling all alone, there were an important few that did this for me, and it made all the difference. It is one of the things that allowed me to move on with what small shred of confidence I had left and have the courage to start over. So take a minute, and write a quick note. Never forget that one tiny action can make a huge difference to someone else.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d97068ebff58" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Harsh Realities of the Game Industry — Part 3]]></title>
            <link>https://cbrownell.medium.com/harsh-realities-of-the-game-industry-part-3-e02f2d296382?source=rss-607ce55ed14------2</link>
            <guid isPermaLink="false">https://medium.com/p/e02f2d296382</guid>
            <category><![CDATA[game-development]]></category>
            <category><![CDATA[videogames]]></category>
            <category><![CDATA[jobs]]></category>
            <category><![CDATA[failure]]></category>
            <category><![CDATA[business]]></category>
            <dc:creator><![CDATA[Christine Brownell]]></dc:creator>
            <pubDate>Mon, 15 Oct 2018 21:52:04 GMT</pubDate>
            <atom:updated>2018-10-15T21:52:04.240Z</atom:updated>
            <content:encoded><![CDATA[<h3>Harsh Realities of the Game Industry — Part 3</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*r7FLGACrqr_lWivBr_l6NQ.png" /></figure><p>In Part 2, we focused on the reasons why games are sometimes canceled, and why they might not ever ship. Today we’re going to review one of the most commonplace realities of the game industry; crunch time, and then for a change of pace, we’ll get further into the most uplifting of topics: losing your game industry job.</p><p><em>This article was written with game development students in mind; but anyone that wants to make video games as a career may find it useful.</em></p><h3>Harsh Reality #5: Crunch time happens</h3><p>There is one almost inevitable reality for those that work in the game industry: crunch time. It usually comes into play during the last few months of a development cycle, where the deadline is looming, and everyone on the team is putting in long hours to get the game completed. Most companies try hard to avoid this, but the reality is that it still happens… A lot.</p><p>What does crunch time look like? A mild example of crunch might be staying a few hours later each work day. So you get home at 9 or 10pm instead of 7pm every evening. Or maybe you’re asked to work one day on the weekend in addition to your normal work hours.</p><p>And then there’s serious crunch time; that might be working 7 days a week, 12 hours a day, for example. During crunch, your employer may buy the team meals, in the hopes of keeping everyone at their desk just a little bit longer. This can go on for months, and there are even some examples of it happening over years (if you’re interested, look into the <a href="https://www.ign.com/articles/2011/06/24/why-did-la-noire-take-seven-years-to-make">L.A. Noire development saga</a>), although that, thankfully, is rare.</p><p>In early 2004, I was part of the quest design team for World of Warcraft, and worked 10–12 hour days, 6 days a week. This was the case for much of the team — we were on track to release the game in November and it felt a bit like a crazy train at full speed, barely hanging onto the rails as we rocketed towards the ship date.</p><p>Management couldn’t get away with telling us that crunching was mandatory, but at team meetings, as we went over the deadlines and assignments, it was very strongly suggested that crunching was a good idea. As a new designer, I was just excited to be there — crunch time didn’t phase me at all. I happily stayed late each evening and came in on the weekend, because it meant more time for me to do what I enjoyed doing.</p><p>But as the months rolled by, parts of my life began to suffer; because I was rarely home other than when I was asleep, I frequently forgot to pay bills, my place was a mess, and I hardly ever saw my friends. I loved my job, but there definitely was not a healthy balance between working and other parts of my life. I also began to feel that even though I was spending more time than ever at work, I was actually less productive than when I was working fewer hours.</p><p>In November of 2004, the crunch came to an end and we released World of Warcraft to the world. When WoW shipped, we were all given generous paid time off. My December was spent recovering, and playing WoW, of course. Slowly, things came back into alignment for me.</p><p>Indeed, 2004 was the year that things changed, and not just for me. At the same time that I was coming off of the WoW crunch, the wife of an Electronic Arts employee posted a <a href="https://ea-spouse.livejournal.com/274.html">very revealing essay</a> about game industry crunch time on Live Journal, using the name EA_Spouse. Her account of the terrible working conditions that her husband was subjected to on a project at Electronic Arts thrust the practice of crunch time into the spotlight, resonating with game industry folks everywhere.</p><p>This single essay had a massive influence. Employees of EA filed class action suits for the overtime wages they were due, and many game development companies actively changed their policies in order to provide a better working environment and eliminate crunch time wherever possible. (<a href="http://ftp.iza.org/dp8129.pdf">Data backs up</a> this approach well; when people work more than 50 hours per week, their output decreases, proportional to the hours they are working. In other words: Crunch time isn’t the best way to get the most out of employees.)</p><p>I’d love to be able to say that crunch time is now nonexistent in the industry, but 14 years after EA Spouse, <a href="https://www.polygon.com/2018/10/15/17979818/red-dead-redemption-2-crunch-dan-houser-interview">crunch time still happens</a>. Overall, things are better, because as the industry has matured, more employers prioritize things like work-life balance and the value of taking adequate breaks. But it still happens. Chances are that if you work in games, at some point you’ll end up working crazy hours in order to get a game finished. And if you’re not careful, it will take a toll on your family, your friends, your hobbies — your life.</p><h3>Harsh Reality #6: Losing your job is common</h3><p>It would be wonderful to be able to say that crunching always led to success. But it doesn’t. Sometimes, despite all the time invested, projects are canceled, and companies shut down. When these things happen, the next step is often that the people are laid off from their jobs. So think about that. You work super hard for months or years, and at the end of that, your reward is that you’re out of a job.</p><p>Unfortunately, layoffs are very common in the game industry. I know very few game industry professionals who have not experienced a layoff at some point in their career. When you lose your job, it’s hard not to take it personally, but layoffs within the game industry that are related to job performance are the exception. Usually they have much more to do with time, resources, and the ability of the team leads to plan well.</p><p>Remember my story in Part 2 about Auto Assault? After launch, when the game wasn’t meeting revenue expectations, NC Soft reduced funding for the team. When funding is reduced on a project, there isn’t enough money to pay everyone that once worked on the team. In short — that meant the team needed to get smaller, immediately. I can’t even imagine what it was like for the leads to sit down and decide who would stay and who would go, especially after the entire team had worked so hard during the four year development cycle. But they did what they had to do — games are a business, after all. When the dust settled, there were only 5 of us left on the Auto Assault team. Around 10 other lucky people were diverted to a new team and new project within the company. But anyone that wasn’t part of those two groups no longer had a job. Effective immediately.</p><p>And it wasn’t about how hard they worked, how skilled they were, how well-liked they were, or how late they stayed during crunch. None of those things matter when funding is cut. It’s painful for everyone involved.</p><p>Layoffs can be something the team sees coming, or can happen out of the blue. I have seen an entire team let go all in one day. Other times, only part of the team is let go. If a partial layoff happens due to lost or reduced funding, it is usually only a stalling tactic to see if the team can continue development with a smaller budget as they work to acquire more funding. Or sometimes it’s due to the larger business entity choosing to refocus on other projects. Either way, it can be a sign that the team is going to die a slow death, dwindling until the money and support runs out.</p><p>In short, the game industry is one of the most volatile fields in which you could choose to work. If job security is something you’re looking for, you should probably look elsewhere.</p><h3>A bit about why this happens</h3><p>You may be wondering about why this happens so often in games — why games don’t ship, or ship and then fail, and people end up losing their jobs. And it’s largely because there are several scenarios that tend to play out, over and over in the industry. Things start out well, but there are so many points at which things can go wrong.</p><p><strong>Startups are unpredictable</strong></p><p>Many game companies are startups that manage to land external funding from a publisher or investors. Startups are the greatest gamble out there — they can be both amazing and awful; a mixed bag, for sure.</p><p>A startup is an unproven venture: usually everyone is super excited to be there and they want to make something awesome, but that might not go smoothly, because the group may never have worked together before. Even if they do work well together, they may not be great at running the company, because being a good businessperson is a completely different skill set than making games. Even if they work well together and understand how to run a company, there’s no way to know if the game they want to make is something that the market wants — or if they will be able to execute the idea at an acceptable quality level.</p><p>Will they pull together and make something incredible? Quite possibly! It’s happened. But there are many startups that go belly up because things just don’t go according to plan.</p><p><strong>It’s just business</strong></p><p>Even at established companies, you may not be safe from losing your job. Large companies like EA often have many game teams, all working on different titles. If the company has a poor year in terms of revenue, that means that there is a possibility of layoffs and project cancellations. And there have been times when a large company like EA will choose to shutter an entire studio.</p><p>Publicly traded companies are responsible to their stockholders, which adds a layer of complexity that smaller studios do not have to worry about — shareholders care about the stock price, and the stock price is impacted by the number of games that the studio produces, the success of those titles, and when the launches are scheduled. Sometimes a game will be shipped before it is ready to meet the timeline; other times a project may be canceled when it just doesn’t fit into the lineup. And then that team is suddenly just gone.</p><p><strong>Planning, money &amp; other variables</strong></p><p>Whether a company succeeds usually comes down to how they use two things: money and time. In the beginning, they have some big questions to answer:</p><ul><li>What product should they make?</li><li>Is the funding adequate to make the product?</li><li>Do they understand enough about the process of making games in order to use the assets efficiently?</li><li>Are the leaders making smart decisions about how to use the time, money, and resources they do have?</li><li>Can they focus on a single product and see it through to completion, or do they change course every time a new industry trend appears?</li><li>Do they understand how to plan for success, ensuring that they can complete development using the funds they have?</li><li>Have they hired the right people for key roles? (This is a big one, especially for the department leads. Hire the wrong person for your technical director and you may have a game that cannot perform well or technology that doesn’t fit the game type. Hire the wrong person for your creative lead and you may have a development team plagued with lots of drama, little organization and poor decision-making. Things like this can kill a project, and there goes your job.)</li></ul><p><strong>Marketing is never optional</strong></p><p>Marketing is another areas where things can go wrong. Without marketing, players don’t know that your game exists, so they cannot play it, they cannot spend money on it, and they cannot tell their friends about it. Additionally, players are so bombarded by the sheer number of new games released that unless they get regular reminders, they may completely forget about your game, even if they had a fun time playing it in that first session.</p><p>In order to be successful, a game not only needs to be marketed, but it needs to be marketed at exactly the right time, to the right audience, in the right way. Without a method of acquiring players, your game is destined to fail — and you’ll be job hunting.</p><p><strong>It’s always a gamble</strong></p><p>The industry changes quickly, which makes it an exciting place to work. But it also means that it’s very possible that the great idea that you have in 2018 is no longer a great idea when you finally finish development in 2020. Maybe there are a dozen games just like it already when you finally release, or maybe your idea happens to be very similar to a game released at the same time as yours, or maybe the genre wave you hoped to ride is pretty much over by the time you jump into the water (Two examples: 2005–2008 saw many World of Warcraft clones, and 2011–2013 saw many companies jumping on the Minecraft cart).</p><p>So while it’s exciting and fun to make games, and there’s the potential to make a successful game, it’s also very high risk. The upside is amazing — a successful game that finds a large audience; being able to point to your favorite game and tell people, “yes, I worked on that!”— but on the other side of that risk is losing a job you love after working really, really hard.</p><p><em>This is the third part in a series relating the harsh realities of the game industry, (and trying to find a silver lining, despite the challenges!). These are drawn from my own personal experiences working at companies like Blizzard Entertainment and Electronic Arts, among others. If you were hoping it couldn’t get any worse, sorry, I’ve still got more. Harsh realities, part four is coming your way soon!</em></p><p><a href="https://medium.com/@cbrownell/harsh-realities-of-the-game-industry-part-1-19088a9573cb">Read Part 1</a>.</p><p><a href="https://medium.com/@cbrownell/harsh-realities-of-the-game-industry-part-2-101cc09368ee">Read Part 2</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e02f2d296382" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Harsh Realities of the Game Industry — Part 2]]></title>
            <link>https://cbrownell.medium.com/harsh-realities-of-the-game-industry-part-2-101cc09368ee?source=rss-607ce55ed14------2</link>
            <guid isPermaLink="false">https://medium.com/p/101cc09368ee</guid>
            <category><![CDATA[games]]></category>
            <category><![CDATA[jobs]]></category>
            <category><![CDATA[videogames]]></category>
            <category><![CDATA[game-development]]></category>
            <category><![CDATA[failure]]></category>
            <dc:creator><![CDATA[Christine Brownell]]></dc:creator>
            <pubDate>Thu, 04 Oct 2018 21:35:36 GMT</pubDate>
            <atom:updated>2018-10-15T21:56:35.899Z</atom:updated>
            <content:encoded><![CDATA[<h3>Harsh Realities of the Game Industry — Part 2</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IjrnFycJA0gl1_jfpOOkpA.png" /></figure><p>In Part 1, we went over about how likely it is that you’ll get to be the Creative Director (hint: you probably won’t) and how sometimes (or even a lot of times), you won’t get to work on your dream game. Today things are going to ratchet up a notch. Let’s talk about product success, how fleeting and unreachable that can sometimes be in games, and what happens when things don’t work out according to plan.</p><p><em>This article was written with game development students in mind; but anyone that wants to make video games as a career may find it useful.</em></p><h3>Harsh Reality #3: Many games are not successful</h3><p>I recently helped a group of students with an assignment from their Intro to Game Design course. Their assignment was to come up with a monetization plan and market projection for a game of their own design. When they came to me, their market projection consisted of finding two games of the same genre as their game, taking account of the revenue those games had made, and then choosing a median number between them as their target. According to their plan, they were all going to be millionaires! Ah, such optimists.</p><p>Looking at similar games isn’t a bad place to start when doing an assignment like this; the problem was that the two games they chose to base their estimate on were two very successful games in that particular genre. Highly successful games are the exception, never the rule — and therefore I advised them it was unwise to count on replicating that same level of success. While I hated to be the one to tell them that their dreams of making millions from their game were unlikely to come true, at the same time, if you want to make games, it’s very important to begin with a solid grasp of this concept:</p><p>The vast majority of games are not successful. Most don’t attract a large audience. Some don’t make much, or any money. You probably won’t become a millionaire.</p><p>I know what you’re thinking right now. You’re thinking that your idea is different. That it doesn’t matter that most games aren’t successful, because your idea is so amazing that it’s going to be that next big hit. And you know what, you could be right. I hope you are, because it would be incredible if you made a game that everyone loves! I can’t wait to play it. But what you should also think about is whether or not you still want to make that game if everyone doesn’t love it.</p><p>I once worked at a company in Colorado called NetDevil. When I joined the team, they were 3 years in on a 4 year development cycle, building an MMO called Auto Assault. You can think of it as cars + guns, with real physics — very reminiscent of Mad Max. I had been hired on as a mission designer, and I was soon immersed in the game lore, writing and implementing game content with a team of several other designers.</p><p>In early 2006, we were all excited when Auto Assault launched! All that hard work, the long hours, the late nights, we were finally going to reap the rewards of that dedication! Except… The game wasn’t a hit. As it turned out, players found it difficult to relate to playing a car as their character. Additionally, because of the true physics model, it was challenging to create environments that felt immersive and interesting to explore, because we had could only show a certain number of polygons on the screen. To make matters worse, the marketing angle chosen by the publisher was ineffective, so many gamers didn’t even know that the game had been released.</p><p>Auto Assault did find a small, dedicated audience, but the game struggled to meet its projected targets from the very beginning. After the first two months, our player numbers were so low that our publisher, NCSoft, chose to reduce funding for the development team. That sealed the fate of the game — with a small 5-person team, we couldn’t manage the updates that an MMO needs to survive. In August of 2007, the game was shut down, permanently.</p><p>So think about that. A team of 40 people worked on a massive game for over 4 years, spending an incredible amount of time and energy and blowing through a multi-million dollar budget, only to find out that the game they created is not what the market wanted. And instead of seeing their creation soar, they had to watch it crash and burn. Auto Assault is gone, without a trace of all the love and passion and effort that the team put into creating it.</p><p>This isn’t a unique story in the game industry. This happens all the time.</p><p>The truth is that extremely successful games are a crazy, lucky combination of a great idea, executed well, with perfect timing and excellent marketing. There’s almost no way to plan for a game to be a huge success — while there are ways to increase your chances, there are no guarantees. So you’ll need to make sure that’s something you’re good with from the start.</p><p>People that makes games do so because they love it. Whether or not the final game is successful, they enjoy the process of building and creating, and working with their team to make something awesome. If it does make money, all the better! That means they get to make another! But having the expectation that every project you work on is going to be an amazing commercial success is not a realistic goal for most people.</p><h3>Harsh Reality #4: Some games never launch</h3><p>If you’re interested in working in games, the fact that some games don’t ever launch is probably old news. You already know that for every game that successfully launches, there are several that don’t. Gather ’round and I’ll tell you a story about the time I worked on a game that didn’t launch…</p><p>It was July of 2006, and I had just joined a new team at a start-up called Perpetual Entertainment, which was located in a big high rise in downtown San Francisco. At the time, the company hadn’t released any games yet, but had two fairly large MMOs in development: Gods and Heroes: Rome Rising, being built by a team of over 100, and Star Trek Online, which had a smaller development team of around 40 people. I had joined the STO team as a Senior Designer, and after some minor reorganization, transitioned over to the a Lead World Designer role within a few months of starting.</p><p>In my new role, I spent months diving into Star Trek canon, planning out game content, and developing the world lore along with the Lead Writer on the game, a soft-spoken, brilliant guy named Mike. The two of us worked side by side, methodically designing out each sector in the game, complete with planets, space anomalies, ground locations, enemies, and encounters. We kept meticulous notes of our design on an in-house wiki, and gave weekly presentations to the team to share our vision.</p><p>While Mike and I were planning out the content far ahead of the team, the game went into production. Soon we were able to create and play through our first few ground locations, as well as fly through space. We were all incredibly excited, and I was living the dream. Game development doesn’t get any better than that!</p><p>At the same time that things were going well on Star Trek Online, the Gods and Heroes team began to struggle. While the game was almost content complete, there had only been a mediocre response from players. G&amp;H also had serious technical issues, the worst of which left the game unable to scale up past more than a couple hundred players. For MMOs to be cost effective and make money, a single physical server or “shard” needs to support thousands of players. If Gods and Heroes couldn’t do that, it was no longer financially viable to launch.</p><p>And that’s when the dominoes began to fall. In October of 2007, the company decided to suspend development on Gods and Heroes, and the majority of the team was laid off. Star Trek Online became the sole focus of Perpetual Entertainment. At the time, we believed this plan was in the interest of redirecting the budget of Gods and Heroes over to STO. And that seems like a great plan, although in order for that to happen, there needs to be money in the bank. After a couple of months and several creative business maneuvers on the part of the owners of Perpetual Entertainment, it became very clear that the company was in trouble. If we couldn’t find more funding, and fast, Star Trek Online would never come to be.</p><p>The details of October through the following February aren’t all that important; all that needs to be said is that despite our best efforts, we were unable to find that funding. In the end, the Star Trek license and all of what we had created up to that point was sold to Cryptic Entertainment. On the official last day of the project, they came and took the artwork off the walls. Those empty walls were a glaring reminder that the game we wanted to make, the one we lovingly crafted over the course of several years, was gone. Cryptic Entertainment did manage to launch Star Trek Online around two years later (To release an MMO so quickly is a testament to Cryptic’s streamlined development and the flexibility of their existing game engine — what an amazing feat!), although nothing that the Perpetual team created survived in the final release. Our version of Star Trek Online will remain just a story, forever.</p><p>If I said that this was anything less than completely devastating when it happened, I’d be lying. I spent most of my holiday break in December of 2007 dealing with the realization that the dream was over, my game was gone, my team was gone, and all of our hard work was for naught. Of course I moved on to bigger and better things after that experience at Perpetual, but I’ll always remember that last day on STO as one of the worst moments of my career.</p><p>Star Trek Online was canceled because Perpetual Entertainment ran out of money to continue development. But running out of funding is only one reason games get canceled. It can happen for many other reasons.</p><p>Sometimes the company you work for will suddenly change course. This usually happens when the executives at the top make some high level decisions about what the focus of the company should be. Some that I’ve personally seen include, “We need to make more Facebook games. Use all of our best IPs to make more Facebook games,” and “Forget Facebook; that’s over. We need to go all in on mobile games because that’s where the users are,” and, “Free to play is the future of MMOs. All of our MMOs in development need to be free to play!” As you can imagine, this can have a devastating effect on teams and projects that don’t fit the new vision. Some projects might be drastically changed mid-development cycle and others may be canceled entirely as the studio decides what stays and what goes.</p><p>Canceling games also happens quite frequently with company acquisitions. The parent company may have different goals than the acquired company, so it’s possible that projects even well into development are suddenly canceled (even if they are proceeding on schedule), as those goals come into alignment.</p><p>Some games are canceled because they do not meet expectations during development. This can include a multitude of “maybe” situations:</p><ul><li>Maybe the idea was solid, but the team didn’t have the skills or experience to execute on the plan at a high enough quality level.</li><li>Maybe the team was hindered by poor tools that didn’t let them build the game they envisioned.</li><li>Maybe the team lost their key programmer or designer partway through development and couldn’t find another fast enough, causing them to fall far behind schedule.</li><li>Maybe the goals of the Creative Director were too lofty at the start and the game just wasn’t achievable in the time they had.</li><li>Maybe there wasn’t a clear enough vision when the project began, so there were a lot of false starts, complete revamps, and design-by-committee, keeping the project from proceeding on course.</li></ul><p>Whatever the reason may be, sometimes companies choose to pull the plug, rather than continue on and hope for the best. Surprisingly, this is the least common reason a game might be canceled. Decision-makers are often hindered by the sunk cost fallacy — that once they’ve spent so much money and time on something, they think they should see it through, even if it’s not meeting expectations. But there are a few companies out there that know how important it is to try many different ideas, and then only develop the best ones: Super Cell, King, and Blizzard Entertainment are examples of companies that kill projects if they are not up to standards.</p><p>The worst reason by far for a game to be canceled is for what appears to be no reason. The project is on schedule, the game is fun (enough), yet sometimes, a game can be canceled just because someone at the top decides that development on the game shouldn’t continue. There are many reasons that this can happen: perhaps a similar game was just released on the market and releasing a competing product isn’t a smart decision, perhaps another game within the company went over budget and it’s more important than your game, so the funds are reallocated to that team.</p><p>There are too many possibilities to list here, but what they all have in common is that they are business decisions that have little to do with the game itself. The game industry is a business, after all, and at most companies, decisions about what games are developed are often made by executives that handle the business aspects of running the company, and don’t ever have a hand in actual development. Money is what drives decision-making at the highest level of any company (although us creatives like to think otherwise).</p><p>If you work in games, there is a possibility that one day, any one of these scenarios might happen to you. You could be years into working on a game you absolutely adore, imagining what it will be like when players get their hands on it, only to have it all taken away in an instant. You’ll likely have little to no control over this situation when it happens; you may be immediately shuffled onto a new team with little adjustment time, or in the worst case scenario, find yourself out of a job completely.</p><p>If you want to work in games, you’ll need to be okay with this situation. Keep in mind — I’m not saying that canceling games and laying off entire teams is okay. It’s awful, every time. However, what I am saying is that it’s a reality in this industry, and it could very well happen to you.</p><p>Are you willing to put energy into a game without the guarantee that anyone will ever play it? Do you truly love the journey of creating? Would you do it all again, even if it doesn’t work out?</p><p><em>This is the second part in a series relating the harsh realities of the game industry, (and trying to find a silver lining, despite the challenges!). These are drawn from my own personal experiences working at companies like Blizzard Entertainment and Electronic Arts, among others. If you’re enjoying having your game dev dreams crushed, stay tuned for more.</em></p><p><a href="https://medium.com/@cbrownell/harsh-realities-of-the-game-industry-part-1-19088a9573cb">Read Part 1</a>.</p><p><a href="https://medium.com/@cbrownell/harsh-realities-of-the-game-industry-part-3-e02f2d296382">Read Part 3</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=101cc09368ee" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Harsh Realities of the Game Industry — Part 1]]></title>
            <link>https://cbrownell.medium.com/harsh-realities-of-the-game-industry-part-1-19088a9573cb?source=rss-607ce55ed14------2</link>
            <guid isPermaLink="false">https://medium.com/p/19088a9573cb</guid>
            <category><![CDATA[videogames]]></category>
            <category><![CDATA[jobs]]></category>
            <category><![CDATA[game-development]]></category>
            <category><![CDATA[work]]></category>
            <dc:creator><![CDATA[Christine Brownell]]></dc:creator>
            <pubDate>Tue, 02 Oct 2018 21:27:13 GMT</pubDate>
            <atom:updated>2018-10-15T21:53:04.228Z</atom:updated>
            <content:encoded><![CDATA[<h3>Harsh Realities of the Game Industry — Part 1</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eMnwWD7oGjg1nSJ-5gDbFQ.png" /></figure><p>The video game industry is truly an amazing place to work. It’s creative, fun and fulfilling, taking a seed of an idea and working with a team to turn it into a fully realized game that potentially millions of other people can enjoy. But like anything else in life, there are also some downsides to working in games; things you might want to consider if you’re looking to make it your career. So let’s get real — what are some of the worst parts of the industry?</p><p><em>This article was written with game development students in mind; but anyone that wants to make video games as a career may find it useful.</em></p><h3>Harsh Reality #1: You probably won’t be the Creative Director, ever</h3><p>One of the most common questions I get from students is about how to become a Creative Director. Everyone wants to be the “idea person,” the chosen one that comes up with the initial idea for the game, and then guides the team to deliver against that vision. Students usually ask this question because they have an idea for a game, and they want to know how to get that idea out of their head and into reality. And when I say “students,” what I really should say is “most people in the game industry.” Almost everyone I’ve ever worked with has a game idea or two they’d love to pursue.</p><p>But the hard truth is that the large majority of them will never be in the position to make that a reality. That’s because at game development companies, there are very few creative lead positions. In most cases, there is only a single Creative Director on a game team, no matter how large that team might be. Sometimes, there is only one Creative Director in an entire company.</p><p>Most people working on a game are part of the “meat” of the team. They are the implementers — coding features, creating models and animations, or determining combat balance in a spreadsheet, for example. They are designers, they are artists, they are audio designers, they are coders, and working together, they make the wheels of development move. Perhaps it was the Creative Director that had the initial idea for the game, but without a doubt, it is these hands-on creators that bring the vision to life.</p><p>So what I am saying is that being a Creative Director may not need to be your goal. Unless your team is incredibly small, Creative Directors almost never get to work on the game directly; instead the job is more about carrying the vision, ensuring others are excited about the game, delegating responsibilities, and empowering others to create. It doesn’t mean it’s not worth aspiring for — building your dream game can be incredible — but just remember, no matter what role you hold on the team, you will always find ways to impact the game and leave your mark.</p><p>A note for indies: Yes, if you create games independently, you can become a Creative Director immediately! However, if you are planning on working with even one other person, you’ll find that soon all efforts become collaborative — creative efforts included. Truly, even a team of two people requires ideas to be shared. The only way you’ll ever have 100% control is to create a game from start to finish on your own. That’s no small task because you’d need to perform every role yourself — but <a href="https://www.gq.com/story/stardew-valley-eric-barone-profile">there are games out there</a> from people that wanted just that.</p><p>So, you may not get to be the Creative Director. While we’re on that subject, I should also mention something else — most of the time, if you’re working for a larger company, you won’t get to work on your dream game.</p><h3>Harsh Reality #2: Sometimes you have to work on a game that doesn’t inspire you</h3><p>When students think about game development as a career, they usually only think about what it will be like to work on games that they love to play. Of course — everyone wants to work on something they are truly passionate about. When I got my first game job at Blizzard Entertainment, I was able to work on games I already adored. But the truth is that I was very lucky to start out that way. In reality, it’s very common for game industry folks to work on a few (or even many) games they just don’t dig all that much.</p><p>Some studios crank out sequel after sequel for an existing IP. Other studios focus on movie companion games (a game that follows the basic general plot of a newly released film, scheduled to be released right around the same time). Sometimes studios focus on one particular target audience or game genre. The point is, you’re an employee of a larger entity, and generally, you’re going to have little say about the game you end up working on. You may love the game you work on! Or you may not be excited about it, at all.</p><p>So we know that once you’re hired onto a game team, you will be assigned to work on a specific game. But what happens when that game ships? At that point, you may stay on that team if there are further updates planned, but sometimes you might be moved to a different team to work on another game. And when that game ships, you might find yourself again on something new. Hopping from game to game, you can’t have the expectation that it’s always going to suit your tastes. Some, you may love. Others, not as much. It’s still your job to bring your best.</p><p>Shipping a project isn’t the only time this can happen, either, especially for programmers, who may be shifted around from team to team more often than other roles. If help is needed on another game team within the company, you may suddenly find yourself “on loan” to that other team. During pre-production on The Sims 4, several of the best programmers on the team hopped over to The Sims 3 team temporarily, to help get the game out the door.</p><p>Even if you do like the game you are working on, there are times where you might be assigned work you don’t particularly like. While working on The Sims team, I was asked to manage monetization, game currencies, and micro-transactions. At the time, I had been doing monetization research, and played many free-to-play titles to get a good understanding of the best techniques. My manger recognized that I knew more about this than anyone on the team, so the assignment made sense in that I was qualified for the job. However, I wasn’t all that passionate about it at that time in my career — I would have much rather remained on the world team, working on game content.</p><p>When this happened, I had to find a way to keep myself motivated. So I made my new role about building relationships. I reached out to other teams within Electronic Arts that were running free-to-play games. I asked questions, gathered information and even traveled to several other EA studios, exploring the ways that each of these teams approached monetization, and bringing back knowledge that could help my own team make decisions. I enjoyed doing this — I got to learn about a subject that has ended up driving a large portion of my career, plus my team benefited from the results as well. I made the role work for me by finding something that I really liked about it and putting all my energy there. No matter what your role on a game might be, you can always find joy within the project, if you’re looking for it.</p><p>So the takeaway here is that you need to put your goal of working on a specific game aside when you’re first trying to get a job. You’ll need to be open-minded and willing to apply for any job for which you’re qualified. For example, you may not love mobile match-3 games targeted at the age 45+ audience, but hey, working on that team could be the role that launches your incredibly successful game career. Every shipped game on your resume puts you one step closer to landing that dream job on your favorite game.</p><p><em>This is the first part in a series relating the harsh realities of the game industry, (and trying to find a silver lining, despite the challenges!). These are drawn from my own personal experiences working at companies like Blizzard Entertainment and Electronic Arts, among others. Stay tuned for more!</em></p><p><a href="https://medium.com/@cbrownell/harsh-realities-of-the-game-industry-part-2-101cc09368ee">Read Part 2</a>.</p><p><a href="https://medium.com/@cbrownell/harsh-realities-of-the-game-industry-part-3-e02f2d296382">Read Part 3</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=19088a9573cb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Who is Playing Games on Steam?]]></title>
            <link>https://cbrownell.medium.com/who-is-playing-games-on-steam-e765142cd983?source=rss-607ce55ed14------2</link>
            <guid isPermaLink="false">https://medium.com/p/e765142cd983</guid>
            <category><![CDATA[steam]]></category>
            <category><![CDATA[gaming]]></category>
            <category><![CDATA[game-development]]></category>
            <category><![CDATA[business-strategy]]></category>
            <category><![CDATA[videogames]]></category>
            <dc:creator><![CDATA[Christine Brownell]]></dc:creator>
            <pubDate>Wed, 08 Aug 2018 20:58:25 GMT</pubDate>
            <atom:updated>2021-04-09T07:46:58.020Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*33vwyzqgIe3WNWDZm7j0sA.jpeg" /></figure><p><em>Author’s Note (April 2021): Hey y’all. Even though this article is years old at this point, it still gets a lot of views. Despite it’s age, much of it might still be valid and help you find the data you’re after. If you decide to read it, know that it was written in the world of 2015 and the methods I used then might not be the best ones now. If you spot something that is wrong or misleading, I’d love to hear about it. I’m leaving it up for now but if at a point in the future it is clear that it’s no longer relevant, I’ll pull it down. Happy reading!</em></p><p><em>Author’s Note (August 2018): This article was originally posted in October 2015. While some things have changed since then, there’s still a lot in this article that remains accurate today. So I am posting it in its entirety here on Medium.</em></p><p>According to Valve, there are over <a href="https://www.vg247.com/2015/02/24/steam-has-over-125-million-active-users-8-9m-concurrent-peak/">125 million players on Steam</a>. The platform has been a hit since it began allowing third-party releases in 2005, gaining players at a steady rate over the last 10+ years. 125 million is a lot of players. So who are these players? Which games do they purchase? Which do they play most often? And most importantly, as a game developer, how can you use this information to best inform the games you choose to make?</p><h3><strong>Defining your target audience</strong></h3><p>When you’re making a game, an early step in the development process is defining your target audience, in order to better understand who your product serves. How is your game meeting the needs of that audience and providing what they are looking for in a game?</p><p>Larger companies often pour lots of time and money into defining their audience for each game, using statistics pulled from market data, and observing focus groups. Marketing departments responsible for well-known IPs (the Sims team did loads of this) often produce prolific amounts of presentations and reports on what players of these games like and dislike. Business, business, business, numbers…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/245/1*h-W-gM7IgsNwLJc3M2xkqw.gif" /></figure><p>For an aspiring developer, this kind of work sounds somewhat mind-numbing, I realize. Unless you’re in marketing. Then it probably sounds super fun! Either way, my point is that it’s important to at least spend a short amount of time thinking about who you’re making the game for.</p><p><em>“But I’m making it for me!” </em>exclaimed every first-time game designer ever.</p><p>Cool. If that’s your goal, and you’re fine with the possibility that no one else will like your game, then forge ahead! I’ve actually met a few people like this throughout my career. They create games simply because it’s fun to do and the games are meaningful to them. It’s art — and they don’t really care if anyone else ever plays them.</p><p>(Yes, there’s the possibility that you’ll get lucky and create something massively appealing by just making a game you love. It’s happened. But then again, relying on luck as part of your plan to create the next hit game is sort of like starting your day by saying, “I think I’ll win the lottery today.” It’s not the most realistic goal.)</p><p>The majority of game makers out there are in it because they want to create an experience that other humans enjoy. Potentially LOTS of other humans. So if you’re hoping to find an audience that loves your game, you’re going to want to spend time defining who that audience is.</p><h3>Creating a typical player profile</h3><p>How do you define your target audience? You can do this by creating a profile that describes a single player; the ideal player of your game. This player profile is used throughout the project lifecycle as criteria for making decisions about development — such as which features you prioritize, your art style, or your main playable character. This profile is sometimes called a Persona.</p><p>For example, while working on The Sims Social, our typical player was named “Molly.” Molly was a thirty-something, stay-at-home mom who liked crafts, animals, and romance, and was a moderate spender on casual games. Game features that emphasized collecting, decorating, organizing and socializing were her favorites.</p><p>Your player profile should be a good match for your game type, as well as the platform you release on. We knew players like Molly were numerous on Facebook, so we brought The Sims Social to them. I’d like to say we were largely successful, as the game had 16 million players within the first week of release — a data point that speaks mostly about the popularity of the Sims — but it also had 65 million players over its lifetime, something few Facebook games can claim. The Sims Social was a good fit for the Facebook audience at the time.</p><h3><strong>What does the typical Steam user look like?</strong></h3><p>If you’re planning on launching your game on Steam, you’re going to want to make sure it’s a good fit for the players there. Steam players are a segment of PC gamers, so let’s start with that. What does the PC gaming audience look like?</p><p><strong>Overall</strong></p><ul><li>49% female, 51% male</li><li>Average age is 38</li><li>More than half buy games digitally</li><li>Average household income is $69k</li></ul><p>The PC gaming audience is made up of three distinct segments of players: Casual, Light Core, and Core.</p><p><strong>Casual Segment</strong></p><ul><li>56% of PC gaming audience</li><li>Play non-core games</li><li>Mostly female</li></ul><p><strong>Light Core Segment</strong></p><ul><li>24% of PC gaming audience</li><li>Play core games for less than five hours a week</li><li>Mostly male</li></ul><p><strong>Heavy Core Segment</strong></p><ul><li>20% of PC gaming audience</li><li>Play core games for five or more hours per week</li><li>Mostly male</li><li>Spend twice as much on games as casual segment</li></ul><p><em>Note: Core game genres include Action/Adventure, Fighting, Flight, Massively Multi-Player (MMO), Racing, Real Time Strategy, Role-Playing, Shooter, or Sports</em></p><p>If you’re interested in reading more statistics about PC gamers, see <a href="https://www.npd.com/wps/portal/npd/us/news/press-releases/37-percent-of-us-population-age-9-and-older-currently-plays-pc-games/">this</a>.</p><p>PC gaming stats are helpful, but are really too general to help us develop our target audience description. So what else can we learn about Steam players based on the information freely available on the web? On the Steam &amp; Game Stats site, Valve <a href="http://store.steampowered.com/stats/">freely shares information</a> about concurrent players.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/959/1*mvHcOn3EQiXasbIjjdpOpw.png" /><figcaption>Peak playtime on a Saturday reveals millions of players online.</figcaption></figure><p>Players can also browse a list of the 99 most popular games and how many players are currently playing each one. Browsing this list can tell you a lot about what kind of players are using Steam.</p><p><em>Note: This information was compiled mid-day October 18, 2015 (when this article was written).</em></p><p><strong>Top 10 Steam Games (most players)</strong></p><ul><li>Dota 2</li><li>Counter-Strike: Global Offensive</li><li>Team Fortress 2</li><li>ARK: Survival Evolved</li><li>Sid Meier’s Civilization V</li><li>Garry’s Mod</li><li>Football Manager 2015</li><li>The Elder Scrolls V: Skyrim</li><li>Warframe</li><li>Grand Theft Auto V</li></ul><p><em>I’ve kept an eye on the leaderboard for the past 3 days and the top 10 games have remained consistent. Sometimes they pass each other up in the list but the top 10 has remained the top 10, no matter what order they were in.</em></p><p>So let’s start building our player description. If we just look at the top 3, we can say that a huge percentage of players on Steam enjoy competitive (PVP) experiences. Dota 2, Counter-Strike and Team Fortress are all flavors of the same experience; a highly competitive, fast-paced team arena game.</p><p>ARK: Survival Evolved is slightly different than the first three, although I think it is a near perfect offering for the Steam audience, and that’s why it’s consistently found in the top 10. We’ll come back to that later.</p><p>Based on the top 4 games, I’d say that a large percentage of players on Steam are Core gamers (using the statistics listed above). They are a solid group of gamers that love a challenge, thrive on competition and don’t mind a game being punishing or difficult. Features like achievements, elaborate upgrade systems, or even perma-death can work with this kind of player. They are willing to put the time in to learn complex skills and feel rewarded by attaining mastery within the game, despite the difficulty.</p><p>Now… The outlier here in the #5 slot is Civilization V, a turn-based strategy game. What’s it doing in this list? From my point of view, the popularity of this game is largely in the IP. I could also point out that Civ V has a high replay value; it gives players a lot of autonomy in deciding how they play (such as providing multiple win states). Additionally, the game been regularly updated with expansion and DLC packs over the years since its launch.</p><p>However, I’d say the biggest reason Civ V still successful is largely because it is a great game with an active multiplayer and modding community. A multiplayer game that allows player-created content (modding) is one of the best recipes for building a dedicated community that will stick by your game for years.</p><p><em>Just for fun, I logged into Warcraft III. Over 8000 players are still playing games on the old battle.net, despite the fact that all the games there are well over 10 years old. Multiplayer + modding = dedicated community. Yes, I really have Warcraft III installed on my PC. Don’t judge.</em> ;)</p><p>9 of the top 10 games on Steam are multiplayer games. Looking over the list of 99, you’ll find lots more. And it’s true, making a high quality multiplayer game is the best way for your game to find success and longevity.</p><p>Let’s take a look at the rest of the 99 top games and see what other trends we can find.</p><h3>It’s a mad world</h3><p>Aside from multiplayer, there are many titles that can be described as violent or dark in nature. These games usually rely on things like apocalypse, war, survival, modern-day crime, or darker fantasy themes so that the violence makes sense within that particular world. Games like:</p><ul><li>Payday 2</li><li>H1Z1</li><li>The Witcher 3</li><li>Fallout: New Vegas</li><li>Left 4 Dead 2</li><li>Saints Row IV</li><li>Dead Island</li><li>Arma 2</li></ul><p>And so on…</p><p>So, zombies. ZOMBIES! They’re everywhere!!! Seriously. If there’s something that Steam players are loving right now, it’s zombie apocalypse games. (Hint: Don’t make a zombie apocalypse game right now. We’ve probably hit market saturation on that.)</p><p>While one could argue that a large percentage of all video games are somewhat violent, I still think it’s worth pointing out because violent games are not popular for all audiences. So this means that the Steam top 99 reveals things about gender, specifically — players of games in this list are much more likely to be male.</p><p>And the available stats I’ve found back this up — only between 4–18% of visitors to the Steam homepage are female. Based on this data alone it looks like the Steam audience is generally Core and Light Core players. I doubt this is a surprise to anyone that regularly uses Steam.</p><p>There are a few other general statements that can be made about the top 99:</p><p>— Strategy is a common thread, with several RTS and turn-based games in the list</p><p>— Sports games are numerous</p><p>— Shooters, and lots of ‘em</p><p>— Simulation games are surprisingly popular (Players that enjoy realistic simulation games are typically a small segment of gamers that are notably hardcore in their preferences, so it’s interesting that they seem to be here in larger numbers.)</p><h3><strong>What about top purchases?</strong></h3><p>I realize that using the top 99 current most played games may not be the most effective method to determine the Steam audience simply because it’s not going to be representative of all game types. This list will always be biased towards multiplayer and epic (content-heavy) experiences because those games simply provide the best opportunity for continued play — where a smaller, single player game will not.</p><p>In other words, you could create an awesome, high quality single player game, with only a few hours of gameplay, and it could sell tons of copies on Steam, yet it won’t stay in the top games list simply because it doesn’t have evergreen content. It has a shorter lifecycle — players play it once, then move on.</p><p>For that reason, I think it’s worth taking a look at top purchases on Steam as well, to see how the top played games match up with the top purchased games. This isn’t data that Steam releases, so I’ve dug up an approximate list that was compiled by SteamSpy and posted <a href="http://www.gamerevolution.com/news/the-top-100-bestselling-video-games-in-steam-history-32149">here</a> in April of this year.</p><p><em>If you want more current data, go to SteamSpy, then click on TOP GAMES along the top, and then sort by the OWNERS column. Note that this won’t give you top purchases overall, it only shows data from the last two weeks about owners of the games. This means it’s possible that the numbers shown for owners are vastly different than actual purchases. So keep this in mind if you’re using SteamSpy as a data source.</em></p><p>Comparing our two lists doesn’t actually reveal anything too surprising. The games on each may differ some, but the themes called out above remain constant.</p><p>While there are definitely some smaller games on the list, and even a few indie games (woohoo!), the most important thing to take away here would be that if you want to have a player community actively engaging with your game for years after its release, it needs to be multiplayer, support some form of user-generated content, or both.</p><p>That’s not the only way to find success on Steam, though — there are definitely examples of a standalone, single player game that goes against the general trends and has gone on to do really well. If you haven’t played The Stanley Parable, go play it. Immediately. But then remember that games like this are few and far between on Steam and if you want your game to have this kind of success, it needs to be good, really good, and provide a unique, compelling play experience.</p><h3><strong>Hours played &amp; games owned</strong></h3><p>So the last thing we should take a look at is the total weekly play time of an average Steam player, and how many games they own.</p><p>Steam Spy reports that the typical user on Steam plays games for slightly over 11 hours per week, on average. That puts the Steam audience well into the Core bracket of PC gamers.</p><p>In addition, the average user owns about 10 games. We can’t be sure if these games are free to play or paid, however. So let’s make an estimate that at least half of the games owned were paid for. Paying for even 5 games is significant, and allows us to say that the average user is a moderate spender, since they’ve used Steam enough to validate spending money on games at least 5 times, if not more.</p><p>This information, combined with the popular genres and themes above, can combine to make a useful player profile that defines the Steam target audience.</p><h3><strong>The Steam player profile</strong></h3><p>So after reviewing the top games on Steam, the most purchased games, and finding out how much players tend to play per week, here’s what I’ve got:</p><ul><li>Male</li><li>Core gamer, plays PC games for more than 11 hours per week</li><li>Finds challenges / high difficulty level appealing</li><li>Achiever, enjoys mastery of a skill or system</li><li>Enjoys sandbox/open world, content-rich experiences</li><li>Enjoys realistic or glorified violence (Also, zombies)</li><li>Enjoys competition</li><li>Preferred genres: FPS, Strategy, Action/Adventure, Survival, Competitive Multiplayer</li><li>Moderate spender; will pay for perceived value</li></ul><h3><strong>Now that we have our Steam player profile, what’s next?</strong></h3><p>If you’re planning on making a game and releasing on Steam, you can use the information in the profile to help you make decisions about your game no matter which stage of development you’re currently in. In the beginning, it can help you come up with a targeted theme, or confirm you’re doing the right thing by sticking with a popular genre. Later in development, it can help your team decide which features to prioritize in the schedule.</p><p>For example:</p><p>— Making a farming and cooking game? Steam probably isn’t your ideal platform. Try iOS.</p><p>— Trying to decide which feature is more important: a complicated weapon-crafting system, or a detailed character creation system? Go with the crafting system, no contest.</p><p>— Thinking of developing a zombie apocalypse game? Really. Come up with something else. Anything else.</p><h3><strong>Crafting the Ideal Experience</strong></h3><p>So let’s come back to ARK: Survival Evolved. If I were to sit down to design a game for players on Steam, it would look like ARK. The game is the embodiment of every single point in the Steam player profile. It puts players in a hardcore, challenging environment where they need to fight to survive. It’s an open, multiplayer world with interesting, deep systems to master. You can impact the world around you in a meaningful way, and there’s a thriving PVP community. Plus: dinosaurs you can ride!</p><p>When I first learned about ARK, my first thought was: ARK is what Minecraft wants to be when it grows up.</p><p>Imagine the Minecraft audience. Then imagine them getting older and wanting a more complex, more hardcore experience, yet one that gives them all the fun aspects they loved when they were playing Minecraft: multiplayer, creativity, building, crafting, open world, public/private servers, etc.</p><p>It’s a fantastic audience to tap into, and this game is exactly what they are looking for. The numbers don’t lie: the game <a href="http://www.pcgamer.com/ark-survival-evolved-has-sold-two-million/">sold 2 million copies</a> while still in Early Access!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*DyWMlmUicrHsw_Zu2V1D4w.jpeg" /><figcaption>Live out your Jurassic Park fantasy. RAAAAR!</figcaption></figure><h3><strong>Continue your research</strong></h3><p>If you’re interested in doing more research for yourself about Steam players and which games are most successful, here are a few places you can do that.</p><p><strong>Valve’s Steam Stats — </strong><a href="https://store.steampowered.com/stats/Steam-Game-and-Player-Statistics">Check out</a> how many players are currently online and which games are the most played.</p><p><strong>Steam Charts — </strong>If you want to dig into the stats for a specific game, check out <a href="http://steamcharts.com/">this site</a>, which allows you to see over a year’s worth of data about how many players are playing any particular game.</p><p><strong>SteamSpy </strong>— This is by far my favorite place for checking out what Steam players are doing. <a href="http://steamspy.com/">SteamSpy</a> takes information from the Valve API along with data automatically gathered from Steam profiles and combines it into a great tool for game developers. One of the most useful tools is that you can see and estimate of how many people own a specific game. I also love the integration with Twitch and YouTube statistics.</p><h3>Suggested Reading</h3><p>Ars Technica sampled public data to estimate sales and gameplay info for every Steam game, and <a href="http://arstechnica.com/gaming/2014/04/introducing-steam-gauge-ars-reveals-steams-most-popular-games/1/">shared their results</a>, as well as in the <a href="http://arstechnica.com/gaming/2014/04/steam-gauge-addressing-your-questions-and-concerns/1/">follow-up article</a> that addresses some concerns.</p><p>Read <a href="https://galyonk.in/some-things-you-should-know-about-steam-5eaffcf33218"><em>Some things you should know about Steam</em></a> if you’re interested in looking at some interpretation of the available statistics, including information on players by country and a gender breakdown.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e765142cd983" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I Played Vanilla WoW on Nostalrius… Here’s Why.]]></title>
            <link>https://cbrownell.medium.com/i-played-vanilla-wow-on-nostalrius-heres-why-85e72f45407?source=rss-607ce55ed14------2</link>
            <guid isPermaLink="false">https://medium.com/p/85e72f45407</guid>
            <category><![CDATA[gaming]]></category>
            <category><![CDATA[worldofwarcraft]]></category>
            <category><![CDATA[game-design]]></category>
            <category><![CDATA[accessibility]]></category>
            <dc:creator><![CDATA[Christine Brownell]]></dc:creator>
            <pubDate>Wed, 08 Aug 2018 20:16:50 GMT</pubDate>
            <atom:updated>2018-08-08T20:17:03.229Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9E8Fm3LlqenLTmtPfCIXCA.jpeg" /></figure><p>I still have the <a href="https://en.nostalrius.org/">Nostalrius</a> WoW shortcut on my PC desktop. I just can’t bring myself to delete it, even though the server has been inactive for almost two weeks now. In April 2016, the dedicated team behind Nostalrius complied with a cease and desist order from Blizzard Entertainment to shut down their private WoW server that had amassed 150,000 active players. I was one of those players.</p><p>I can’t log in anymore. But for some reason, I still can’t delete that shortcut.</p><p>I played on the Nostalrius server for about six months. I found the server by chance in a YouTube comment, and it was easy enough to download and install. I’ll just try it for a minute, sure. The first time I started up the game, connected to the Nostalrius server, and woke up in Northshire Valley, it was like embracing an old friend after a very, very long absence. It was happy, and familiar, and wonderfully simple. I was home.</p><p>Fast forward a few months later and it’s gone. While I completely understand and agree with Blizzard Entertainment’s decision to demand the shutdown of this server (it’s well within their rights — and as a company they need to protect their IP in any way required), I still found myself deeply disappointed when I heard the news. As I processed this, I (in true game designer fashion) began to analyze my own response.</p><ul><li>Why did I want to play vanilla in the first place?</li><li>What was I looking for that the current iteration of WoW wasn’t giving me?</li><li>Did I find what I was looking for, playing on Nostalrius?</li></ul><p>I also found myself wondering…</p><ul><li>Should Blizzard pay attention and respond to players that are asking for a classic WoW server?</li></ul><p>In order to answer these questions, we’ll need to dive into some of the changes that were made to World of Warcraft over the years since its launch, and talk about how game design decisions are always trade-offs. When you make a decision, you will always give something up in order to get the benefit of something else. This concept is at the core of the reason that classic WoW realms like Nostalrius have emerged.</p><h3>Why did I want to play vanilla?</h3><p>I admit, vanilla WoW is incredibly special to me. It was the first game I worked on as a game designer, and it was also a game I ended up playing seriously for years after launch. I spent hours, days, months; I’ve gotten to max level on several characters, I’ve bought every expansion, and I have never regretted any of it. To this day I treasure the time I’ve spent in Azeroth adventuring with good friends.</p><p>But slowly, over the years, that game I loved playing was lost to brand new expansion areas (most notably Cataclysm, as it completely destroyed and changed many of the classic zones), altered as entirely new features and wide-sweeping class changes were added.</p><p>When I log into the current version of WoW, sometimes it’s hard for me to recognize that game I once worked on. I know it’s in there somewhere, but it’s wearing 17 sets of epic armor and carrying 86 legendary weapons and is riding shotgun on a two-seater flying mount. I sometimes see it pass by but barely have time to wave before it’s gone again.</p><p>So of course, I’d never deny that it was nostalgia that originally motivated me to play. I know this to be true of so many of the other players on Nostalrius as well. For some of them, WoW is often wrapped up even deeper in their memories; many played WoW as kids or early teens, and it became a part of their childhood.</p><p>It would be so easy to stop here. To say, yeah, it’s just people trying to relive the “good ol’ days” and leave it at that. It would partially be true. But the thing is, this goes much deeper than just nostalgia.</p><h3>What was I looking for that the current iteration of WoW wasn’t giving me?</h3><p>To answer this, let’s talk about accessibility and user experience. From the very beginning, the WoW team was focused on delivering to players the best experience possible. This not only meant fun and engaging content, it meant that the game needed to be accessible — easy to play — and be flexible enough to allow players to play the way they wanted.</p><p>In classic WoW, you can see this reflected in things like:</p><p>— The friendliness of the starting areas — enemies don’t attack unless attacked first, and your character’s health regen is so fast that it’s almost impossible to die in the first 5 levels of the game.</p><p>— The death penalty is minor — just run back and you’re all good to go. In many MMOs prior to WoW, you might lose experience, all of your gear, or both!</p><p>— Players can play solo in WoW and expect to do well. This was markedly different from other MMOs of the time, which required grouping up with others to be successful.</p><p>There are many more examples but you get the idea. Overall, the WoW team had committed to providing a positive, accessible player experience with every aspect of the game. It was well understood that the game needed to be welcoming, fun and rewarding from the start in order to retain the huge audience we were hoping for. Largely, I’d say we were successful.</p><p>So it’s no huge surprise that this effort continued as the game evolved. Friction points in the game were identified and new features were added to make things even easier and more accessible for players. There are two specific examples of this that I want to talk about here, because they made such a huge impact: the dungeon group finder, and the enhanced questing system.</p><h3>LFG</h3><p>The dungeon group finder tool was designed to eliminate those annoying parts of preparing to play through WoWs instanced dungeons. It allows you to choose a dungeon and then enter into a queue, and then the game automatically matches you up with an appropriate group. In addition to finding the group for you, the system also teleports you to the dungeon, saving you the time of travelling there yourself.</p><p>Prior to the dungeon group finder, players needed to do these things themselves. To find a group, they asked in trade chat, they sent private messages to friends, they yelled in the middle of Orgrimmar. Finding five players to do a dungeon was sometimes a difficult task. And then to make it more complicated, once players did find a group, then they had to wait while everyone traveled from various parts of the game world to the dungeon entrance. No teleporting, no shortcuts (unless the warlock got there first).</p><p>So it’s no wonder that doing a dungeon in vanilla was a huge time commitment. Getting a group together and getting to the dungeon usually averaged around an hour, and then the group still had to play through the content, which was usually a few hours just by itself. And sometimes, your group wasn’t skilled enough, wasn’t high enough level, or couldn’t seem to coordinate well enough, so even after all that, you still couldn’t complete the dungeon. With all these friction points, it makes sense that Blizzard would try to solve what they saw as a problem.</p><h3>Where is Mankrik’s Wife?</h3><p>Or take the enhanced quest system and the numerous other changes to the game that have since made questing easier. In vanilla, quests were short (255 characters or less, to be exact), but you still had to read them to understand what to do. While I was a quest designer, it was mandated that every quest include the required information for players — there shouldn’t be any guessing. Questgiver, task, NPC name and location to return the quest were all included in each quest entry. All of the quest team knew the rules, and we followed them. We wanted players to be able to understand what they were being asked to do.</p><p>But now, with the new system, reading a quest is a thing of the past. All you need to do is follow your minimap and you can complete quests like a pro. Enemy targets are marked, the quest giver is always a short distance away, and you’ll almost never find yourself wondering, “Where am I supposed to go? What am I supposed to do?”</p><p>The system has been made so easy, in fact, that you don’t have to read a single word. A couple of months ago, a friend and I played new characters up to around level 10. I never read a quest in that time, yet I accepted and completed tons of them. My friend and I chatted about life over ventrilo as we followed the markers on the minimap, and leveled up.</p><h3>The Ultimate Goal of Accessibility</h3><p>In both of these instances, the systems were made easier to use; in the interest of making the game easier to play; more accessible. And it’s true, as a game gets more accessible, more people will be able to play it. You’ll have fewer players quit out of frustration.</p><p>From a game design perspective, this is where things get tricky. When a task is easy to do, more people can do it. However, when a task is easy to do, a player feels less satisfaction in completing it. It feels less like an achievement; it has less value attached to it.</p><p>So by removing all the barriers to things like dungeons and questing, these activities have become inherently less valuable. There is less satisfaction to be gained by completing them. And that’s because the struggle itself is essential — overcoming a challenge leads to a feeling of satisfaction and achievement. Without the challenge, that doesn’t happen. The easier the challenge is to overcome, the less satisfying it is from a player perspective.</p><p>It may sound like I am arguing against the dungeon group finder and the enhanced quest system right now, and I’m not — to be completely honest, I probably would have made the exact same changes had I been the designer tasked to fixing those problem areas, so I can completely understand the analysis that got Blizzard to where things are now. Accessibility is incredibly important and essential to retaining players and it needs to be a priority.</p><p>But taking a look at the systems now in practice, it’s clear that maximizing accessibility comes at a cost. To make your game as accessible as possible, you must give up something in return. What you most often give up is the powerful moments in a game where a player overcomes a challenge; that challenge that drives players forward and keeps them engaged. It’s up to you as a designer to figure out where the challenge is appropriate, and where it is not — hardly an easy issue to tackle, much more of a gray area when compared to other decisions a designer needs to make.</p><h3>Wanna Join My Guild?</h3><p>Changing both of these systems also had an impact on something very key to the success and longevity of multiplayer games: the quality and quantity of relationships between players. MMOs all strive towards one main goal, to build and maintain an active player base — it’s the only way these games survive. Part of the way that they do this is by cultivating relationships between players inside the game. There are organized ways of doing this; such as guilds, but there are also much more informal ones. Getting a group together for a dungeon falls into this category.</p><p>Sure, it might take an hour to get your group together, but during this time, you’re doing something very crucial to building community: talking. You’re communicating with players who you may have never met before, and in doing that, there is the potential to build relationships. Any MMO designer will tell you that part of good MMO design is to ensure that your players have opportunities to interact with each other, where they can focus on completing a task together (even if that task is simply getting your group together to play). MMOs need player interaction for them to survive long term.</p><p>The dungeon group finder eliminated the challenges involved with getting a group together and getting to the dungeon location, but as a side effect, it also completely eliminated the need to talk to other players to do a dungeon. Players lost the opportunity to build relationships here. The dungeon group finder made dungeons more accessible, but eliminated a place where players had the chance to meet one another. Are there other opportunities? Sure, but my point is simply that this one in particular was lost due to a change made in the interest of accessibility.</p><p>Design decisions are trade-offs. As a designer, problems like these are the toughest to solve, because it’s often less about the “right” answer, and more about clearly defining your goals and understanding the consequences of your decisions. Even if you decide in favor of making something more accessible, it’s good to understand what you’re giving up.</p><h3>Lost in Stormwind… Again</h3><p>In a world where you need to read a quest log, view a map, and ask other players questions in order to complete a quest, you have an opportunity to learn more about the game world that surrounds you. You’re navigating it yourself, you’re remembering landmarks, you’re gaining an intimate understanding of the lay of the land. And again, you’re interacting with the other players around you, who can tell you what to look for, if you’re in the right place, or where that quest giver is hiding. But add a system that marks everything on the minimap, and all of a sudden, you can completely disconnect from the game, yet still play it.</p><p>The closest real world equivalent to this is using Google Maps or Waze to get to a destination. It’s so easy to zone out and just let the app worry about how to get to your destination. Asking for directions? Memorizing landmarks and street names? Backtracking to find your way home on your own? Who cares! There’s no need to learn your surroundings if it’s someone else’s job to tell you how to get to your destination. And in the same way that I still have to use my GPS app to get to locations I’ve been to multiple times, WoW players are not learning their surroundings anymore, either, because the quest system handles it for them. And the world becomes less immersive and interesting.</p><p>The current WoW quest system is incredibly accessible. But that accessibility comes at the cost of immersion. For a game that relies on rich backstory and lore, thoughtful design and breathtakingly beautiful scenery, the enhanced questing system actually becomes a detriment. It helps players figure out where to go next, but it also drives a huge divider between players and the world itself. If I’m too busy watching a marker on my map, I’m not going to pay any attention to the world around me.</p><p>Vanilla WoW, even with its imperfect questing system, ensured that players really learned their way around the game. It’s less accessible in that the player has to do more work in order to find success. However, because of that, completing a quest actually feels more meaningful; it becomes more of an accomplishment. And in simply questing, that player gets to know the world around them.</p><h3>Did I find what I was looking for, playing on Nostalrius?</h3><p>I loved playing on Nostalrius. Not only did I get to indulge my game designer nostalgia, but I also got to relive so many experiences that the current game doesn’t provide anymore. Finding a dungeon group led to making friends; random questing adventures led to joining a guild; which resulted in some late nights and many dungeon wipes. Overall I found the community on Nostalrius to be friendly and helpful. This may have something to do with the audience that finds vanilla WoW appealing, but I think it’s also because the game inspires this by design.</p><p>When players ask for a vanilla WoW server, they are asking for so much more than just nostalgia; what they are really asking for is meaningful experiences. Experiences where they have the opportunity to build relationships, to overcome challenges, and to feel that sweet satisfaction of victory. Vanilla WoW provided a meaningful, memorable experience to millions of players. And that’s what I found playing on Nostalrius. So largely, yes, I did find what I was looking for.</p><h3>Should Blizzard pay attention and respond to players that are asking for a classic WoW server?</h3><p><em>(Author’s Note: Since this article was written, Blizzard has announced and has begun work on </em><a href="https://worldofwarcraft.com/en-us/news/21881587/dev-watercooler-world-of-warcraft-classic"><em>WoW Classic</em></a><em>.)</em></p><p>To me, this question has no clear answer. Running a vanilla WoW server is an undertaking that has a considerable cost attached, even for Blizzard. It means not only the hardware to support the servers and developing a viable vanilla build, but also integration into Battle.net, a community support team, a tech support team, GMs, QA, a minimal dev team to address issues, dealing with gold farmers and hackers. It wouldn’t be free or easy to do this, and it’s questionable whether or not there would be enough players to justify it, even if Blizzard did take this all on.</p><p>All that aside, I was both surprised and happy to see <a href="http://us.battle.net/wow/en/forum/topic/20743584206">J. Allen Brack’s response</a> to the community regarding Nostalrius. To see that the issue has been elevated to this level — that there’s any internal discussion about it at all — it’s clear that no matter how big Blizzard has become, at the core it’s still a company that cares deeply about its players. And that’s a wonderful reassurance in an industry that from the inside often feels so very corporate, decisions driven by stock price and shareholder concerns rather than by what players want.</p><p>Whether or not Blizzard ever decides to run a vanilla server, I’m sure they have learned a lot about the impact of the changes they’ve made to WoW over time. It’s likely that every single person on that team has ideas about what they’d do differently if given the chance to do it over again, and that the lessons they’ve learned will impact all their future titles for the better.</p><p>Did you play on Nostalrius? Let me know what motivated you to play, and if you plan on playing WoW Classic when it launches!</p><p><em>This article was originally posted on </em><a href="http://christinebrownell.com/"><em>christinebrownell.com</em></a><em> on April 28, 2016.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=85e72f45407" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Ace the First Week at your New Job]]></title>
            <link>https://cbrownell.medium.com/how-to-ace-the-first-week-at-your-new-job-d0898076eebf?source=rss-607ce55ed14------2</link>
            <guid isPermaLink="false">https://medium.com/p/d0898076eebf</guid>
            <category><![CDATA[management]]></category>
            <category><![CDATA[careers]]></category>
            <category><![CDATA[jobs]]></category>
            <category><![CDATA[career-advice]]></category>
            <dc:creator><![CDATA[Christine Brownell]]></dc:creator>
            <pubDate>Wed, 08 Aug 2018 19:46:04 GMT</pubDate>
            <atom:updated>2018-10-03T14:33:17.730Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wWHkobIs2JYfNTP-q2eDvA.jpeg" /></figure><p>Last month I met up with a friend who had just finished his first week at a new job. We sampled some craft beers while he filled me in on the company, the product, and how he was feeling about his new role. He sounded very excited as he explained the ins and outs of how the business model worked.</p><p>However, he revealed that his first week hadn’t gone all that well — he was hired in at a lead level, but his team knew more about the brand and product than he did — so he was having a hard time figuring out what he should be focusing on. He struggled to feel productive each day and expressed feeling unqualified to assert his opinion, or to even have one at all.</p><p>“I went to a meeting on my second day, and they asked for my approval of their next UI/UX decision. How would I know if that was the right thing to do?” he said, sounding a bit exasperated.</p><p>I was so surprised to hear this from this particular person — someone I had known for years, a guy who I greatly respect and has a real talent for leading teams. How could one of the smartest and most capable managers I’ve ever known possibly feel this way?</p><p>But… this was a new job. Surely he knew that he couldn’t expect to perform at his full capacity from the first day.</p><p>“That’s normal to feel like that. You know that, right?” I offered.</p><p>“No!” he exclaimed. “I’ve never been in this situation — I’ve always started teams, never joined one midway. At the end of my third day, I was convinced that they were just going to fire me!”</p><p>I admit, his struggle somewhat fascinated me. He was absolutely right — joining a team that is partway through its development cycle can be challenging. It’s like a giant, crazy machine that’s already operating at full speed, and you’re expected to jump in while it’s moving and keep things running at the same pace. It can be really hard to even know where to start.</p><p>What I realized while talking with him is that starting a new job without the knowledge that you aren’t going to be able to contribute much at first can greatly compound the problem. If you don’t know that it’s almost impossible to be productive in a new job from day one, you might become frustrated, anxious and disappointed with yourself, especially if you’re used to being a top contributor.</p><p>As someone that has joined numerous teams over the years, I shared my experience with my friend, pointing out (kindly) that he was causing himself a lot of additional stress by expecting too much, too soon.</p><p>Later on, when I reflected back on the conversation, I realized that it would be a great topic to blog about. I’ve worked primarily at game studios, but most of my suggestions are universal so should be useful to almost anyone working in a business setting. If you’ve just started a new job and want to understand how to meaningfully contribute to your team and project as soon as you possibly can, check out my tips below!</p><h3><strong>Set the stage with your manager</strong></h3><p>As soon as possible, (at some point within your first week) set up a meeting with your manager. Your goal is to get clarity on the following:</p><p><strong>1. The expectations for your role and responsibilities.</strong></p><p>Some of this may be obvious based on your particular role and the amount of discussion that went on prior to your being hired, but getting clarification is always a good thing.</p><p><em>“As a Senior Designer, what should I be spending most of my time on?”</em></p><p>At some companies, the title Senior Designer means you’ll spend your day tweaking tuning values in a game editor, but at others, you might be expected to plan future tasks and review the work of your direct reports. Same title, vastly different job description. So don’t assume that you know the responsibilities just because you’ve done the job somewhere else. Every company has its own interpretation of what a job title means, so it never hurts to ask.</p><p><strong>2. The goals of the team.</strong></p><p>Your team is all working together to produce something. What is it? How well do you understand it and the reasons you’re creating it? Are there any key deadlines coming up that you should be aware of? Are there any dependencies between departments?</p><p>Talking about your team goals can help you get a better understanding of how you fit into the big picture. You’ll also want to get clarification on which areas of the project you “own,” and which are assigned to others on the team.</p><p><strong>3. Management styles.</strong></p><p>Management style is a business-y phrase that simply means the method in which you and your manager can best work together. There are two parts: 1) How your boss manages her direct reports and 2) How you prefer to be managed.</p><p>Is your manager hands-on or off? Does she like regular checkins, or prefer to only hear from you when you need guidance? Is she a “big picture” kind of thinker, or does she want to know every individual detail? This is your opportunity to explain what you need to ensure you are most effective, or that you have a specific strength or weakness you know can impact your job performance.</p><p><em>“During the first couple months, I would appreciate getting your feedback on my reports before I send them to the team.”</em></p><p>or</p><p><em>“I’m great at managing my own time, and part of keeping myself focused includes only checking my email twice a day. Is that going to be ok?”</em></p><p>There’s no one right way to manage someone though there are plenty of wrong ways and I’ve seen my share of both. What you’re aiming for here is a good middle ground that allows you to have the freedom to do your job in the way that works for you and also gets your manager the results she is looking for.</p><p><strong>4. One-on-Ones</strong></p><p>At the end of the meeting, ask your manager if it’s alright to set up a one-on-one meeting at a cadence that makes sense (note: bi-weekly has worked best for me) to allow you both to discuss any issues impacting your role, responsibilities, the team in general, and most importantly, to get feedback on how you’re doing.</p><p>One-on-one meetings can work wonders in building a relationship with your manager, who may be so busy that it’s hard to strike up a casual conversation during the day — I’ve at times worked with managers who were hardly ever at their desks. But having a good working relationship with your manager is super important, so push to claim some of their time. Suggest a regular lunch one-on-one if you’re told “there just isn’t time” during normal work hours.</p><h3>After the “Setting the Stage” Meeting</h3><p>Write up a summary of what was discussed and save it in a place where you can refer to it in the future. Email it to your manager and ask if he agrees with your write-up. Follow up as needed until you’re both on the same page. The goal here is to come across as proactive, engaged, and responsible.</p><p>Taking the time in this first meeting to firmly embed the idea that you are focused and dedicated, that you believe in the product and have the team’s best interests in mind can have a huge impact on your overall relationship with your lead. If you can confidently convey your goals, you’ll win some points with your manager, who honestly just wants to know that the job is going to get done, and it’s going to be done well.</p><h3><strong>Set the stage with your direct reports</strong></h3><p>If you’re coming in as a manager, this can be tricky. Early on, it’s going to be challenging to give your reports direction that is useful, and winning over their hearts simply takes time.</p><p>So, while you should sit down and have a meeting similar to the one above (but with roles reversed) with each report, your focus should be on calming any anxiety that your direct reports may have about you coming in (and ruining everything!). And don’t doubt that they are worried about this — they’ve only just met you, and for all they know, you might be the worst manager in the world.</p><p>So let’s fix that. In your first meeting, your goal is to listen, above everything else. Try to talk as little as possible. Ask questions about the project, how they feel things are going, and how they feel about their own roles. The message you should seek to convey is that you are interested in their thoughts and opinions, that you know that there is a lot you need to learn, and that you’re looking forward to working together.</p><p><em>“Right now, I’m here to learn and to listen. This is your project and I want you to help me understand more about it so that I can join you.”</em></p><h3><strong>Meet your team</strong></h3><p>By this, I mean your entire team, whether that is 6 people or 60 people. If you’re on a large team, say, over 100 people, you may want to do this with the specific part of your team that you’ll be interacting with most often, rather than everyone. Or split it up into multiple days, whatever works for you.</p><p>Ask a coworker to walk you around the team area, or set aside some time to walk around on your own and introduce yourself to everyone personally. Even if you’re the shyest introvert that ever been, this is really important to do — you need to know who is on your team and what they do — so suck it up and just go say hi.</p><p>When do you this, be sure to bring along a notebook with you to write down each coworker’s name and role. No matter how many times I’ve heard someone say you should work really hard to recall all 87 of your coworkers’ names after meeting them a single time, most people can’t do this (nor should they do short-term memory backflips trying to).</p><p>I once worked with a guy that labeled his To-Do list, “Brain,” explaining that he wrote his ideas and tasks down so that they didn’t take up room in his brain, and he didn’t have to worry about forgetting anything important. He had the right idea. Write down the names and save yourself the trouble of trying to remember them all. You’ve got enough to think about!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*eAr80OZvgB-OQ2cwGkltnw.png" /><figcaption>It doesn’t have to be fancy.</figcaption></figure><p>When I was brought in as the creative lead partway through a project, I actually drew a seating chart during this process so that I could keep track of not only names but where each person was sitting as well.</p><h3><strong>Get to know your team</strong></h3><p>A surefire way to learn about the team and company you’ve joined is by “interviewing” your new coworkers. Now that you’ve met everyone on your new team, make a list of key players. This might mean the leads of each department, but it also could mean the person that’s been on the team or at the company the longest, or the person that seems to have the loudest opinions. Once you’ve got your list, set up short, casual meetings or lunches with each person, where you can speak with them one on one.</p><p>If people want to know the purpose of the meeting, just explain that you’re trying to get up to speed as soon as possible and you think that speaking with them would be really informative and helpful for you. Because: truth.</p><p>You can come up with your own set of questions to ask each person, but here’s a list that I’ve used in the past:</p><ul><li>Tell me more about your role on the team. What do you like best about it?</li><li>What are the main goals and/or values of this team/project?</li><li>How does our team fit into the larger company picture?</li><li>What does the brand/company stand for, to you? / Why has it been successful?</li><li>What is the best thing about being on this team?</li><li>Are there any problems I should look out for?</li></ul><p>When I first joined The Sims team, I went through this process and found that it gave me some useful insights, both about the people I would soon be working with and the state of the team and company at the time. I also learned a ton about the brand itself.</p><h3><strong>Go to as many meetings as you can</strong></h3><p>This may sound like odd advice — usually I’m telling people to figure out how to reduce the number of meetings they attend so they can get actual work done. But when you’re new, meetings can be a great place for you to observe and soak in information. Be a sponge!</p><p>So on your first or second day, ask those around you if you can tag along to any meetings they go to. You’ll find that most of the time, people are fine with this. Sometimes they’ll try to explain that you probably don’t need to be there, or that it’s not relevant to your particular role. Just remind them that you’re trying to take in as much as possible and if it’s clear during the meeting that it isn’t helping you with that goal, you’ll politely excuse yourself.</p><p>Going to meetings in the beginning can help you understand more about your team, their working methods, process, and the product overall. You’ll also glean many useful somethings about the different personalities of your coworkers and how they interact.</p><h3><strong>Take notes</strong></h3><p>When I am in a work environment, I am a relentless note-taker. Every meeting, no matter how casual, you can be sure that I will write down anything important that was discussed or decided. The biggest reason I do this is because simply writing something down can increase your retention of that information by up to 20–30%. And when you’re a newbie, you are going to be flooded with new information almost constantly.</p><p>If you’re in a content or production role, you’ll likely be introduced to the tools that the team uses to get work done during your first week. And someone will be assigned the job of walking you through using these tools and how each process works. I can’t tell you how many times I’ve had the experience of sitting down with a new hire and I start explaining things, and then notice that they aren’t writing anything down.</p><p>You’re not going to remember it the first time — so grab a notebook, and write it down! You don’t want to be that annoying person that needs a second (or third!) walk through simply because you didn’t jot down some notes when things were being explained. So if it’s not been clear, whenever you’re talking to someone on your team, write down what they are saying. Because writing it down will help you remember it.</p><h3><strong>Find a “hands-on” task that you can do in your first week</strong></h3><p>Whether it’s a small coding task, writing documentation, or analyzing some player data, find something that you feel comfortable doing, and then do it. It doesn’t even matter if it that task is going to be your main job responsibility eventually, what you’re looking to do here is to choose a task that will get you involved with your team and the project overall, in a measurable way.</p><p>Anything that you involve yourself in will put you in a place where you have the opportunity to learn more about your project, team goals, and how to be better at your job. So find a way to contribute, no matter how small.</p><h3><strong>Accept that there will be a lot you don’t know</strong></h3><p>You’re not going to jump into your role at 100% efficiency, and that’s not only okay, it’s completely expected. There’s no way to rush the transition process — the only solution is to be patient and know that it will happen.</p><p>Whenever I’ve joined a new team, the goal I set for myself is to feel productive by the end of the first three weeks. In my experience, three weeks is really the sweet spot. I’ve had it happen as soon as two, but it’s also taken as long as four for me to truly feel that I am contributing to my team in a way that feels meaningful. If it happens before then, time to celebrate! But if it doesn’t, I remind myself to be patient, set goals, and take it one day at a time.</p><p>I spoke to my friend again after the end of his third week and not surprisingly, he was feeling much more at home and confident at his new company. What helped the most? At the beginning of his second week, he decided to take on something hands-on (actual coding), which helped him really get a much deeper understanding of the product and the direction it needed to go. He felt much more at ease with his team and I have no doubt that he’ll be performing at his usual level of awesome in no time.</p><p>To recap:</p><ul><li>Set the stage with your manager</li><li>Set the stage with your direct reports</li><li>Meet your team</li><li>Get to know your team</li><li>Go to as many meetings as you can</li><li>Take notes</li><li>Find a hands-on task that you can do in your first week</li><li>Accept that there will be a lot you don’t know</li></ul><p>If this sounds like a lot of work, well, you’d be right. But you probably wouldn’t be here reading this particular post unless you’re used to working hard. Kicking ass never comes easy. So from one overachiever to another, I hope this list was helpful, and let me know if you think there’s something missing!</p><p><em>This article was orginally posted on </em><a href="http://christinebrownell.com/"><em>christinebrownell.com</em></a><em> on October 8, 2015.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d0898076eebf" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Dream of Working in the Video Game Industry? Three Things You Should be Doing]]></title>
            <link>https://cbrownell.medium.com/dream-of-working-in-the-video-game-industry-three-things-you-should-be-doing-dd4ed64f06d7?source=rss-607ce55ed14------2</link>
            <guid isPermaLink="false">https://medium.com/p/dd4ed64f06d7</guid>
            <category><![CDATA[videogames]]></category>
            <category><![CDATA[game-development]]></category>
            <category><![CDATA[careers]]></category>
            <category><![CDATA[games]]></category>
            <dc:creator><![CDATA[Christine Brownell]]></dc:creator>
            <pubDate>Wed, 08 Aug 2018 19:14:53 GMT</pubDate>
            <atom:updated>2018-08-08T19:20:03.834Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2F1b9xGxzpA0ScW5j0H5Dg.jpeg" /></figure><p>Without a doubt, the most common question I get about working in the game industry is: “How can I get a job in games?”</p><p>Truthfully, I’ve never found it an easy question to answer because it’s not an industry that has a defined, linear path to follow, and most of the people I’ve worked with have found their way into the industry in vastly different ways.</p><p>I have a degree in a completely unrelated field — graphic design — and I’ve worked with others that have had degrees in history, political science, illustration, and architecture, among others. Many of us got our training by doing, landing our first jobs in the industry with little except our intense determination and lifetime love of games to guide us.</p><p>However, with the rise of game development college programs in the last ten years, and the recent accessibility of game engines like Unity and Unreal, it’s become much easier to get started on the game dev path while you’re in college, or even before! While both of these things have definitely helped kids feel more confident about their goal of becoming a game designer, programmer, or artist, it also means that once you get out in the real world and start looking for a job, there is a much larger pool of qualified candidates out there. And — they are applying for the same entry-level jobs you are.</p><p>So what can you do to give yourself an advantage? Here are three things you can do, right now.</p><h3>Tip 1: Get some experience</h3><p>By that, I mean that you should get some real experience doing the thing that you eventually want to get a job doing. Because, obvious. When I want to hire someone, that’s the first thing I want to know — what experience do you have?</p><p>If you’re a game dev student, you’re probably thinking, “Ok, I’m in school. I’m learning things here about how to make games. Is that experience enough?” And the answer is that it might be. But what if you’re not a game dev student, and you’re getting a degree in a different field, like art or computer science… What should you do then?</p><p><strong>Learn a game toolset</strong></p><p>You can learn a level editor for any game that has one. Super Mario Maker, Starcraft II, Dragon Age: Origins. There are lots out there to choose from. So pick one and learn it. And I mean, really learn it. Build some levels, then release them to the community and get feedback. Polish your levels based on the feedback and make improvements. Keep engaging in that loop of feedback and iteration.</p><p>In other words — don’t just make one level and call it a day. Create one level. And then another. And then another. And have people play your levels — figure out what works and what doesn’t. Learn from your mistakes. Become an expert at making levels in that editor.</p><p><strong>Learn a game engine</strong></p><p>Or you can go even bigger and pick up a full game engine, like <a href="https://www.unrealengine.com/en-US/what-is-unreal-engine-4">Unreal</a> or <a href="https://unity3d.com/">Unity</a>, or one step down like <a href="http://www.yoyogames.com/gamemaker">Game Maker</a>. This is a much bigger time investment, but it’s also a much bigger return — you stand to learn an incredible amount and will be able to use what you learn to build a game on your own time.</p><p>When deciding what to build the first time around, give yourself small goals. I often tell students I’m working with to pick one small event or action in your everyday life and make that your entire game. Make a game about brushing your teeth, using an umbrella to stay out of the rain, teaching a giraffe to roller skate (hey, I don’t know what your everyday life is like), or your morning commute.</p><p>Just pick something simple, and make a game. Have people play your game and give you feedback. Listen to what they say, and what they don’t say. Watch them play and see where they struggle. Use what you learn to make your game better.</p><p><strong>Learn industry software</strong></p><p>If you’re an artist, learn a software package, like Adobe Creative Suite, Maya, Max, or Zbrush. If you are learning one or more of these in school, pick something you’re not learning in school so that you are forced to figure things out yourself.</p><p>Let me specify that learning a new program doesn’t mean opening it, messing around with some of the settings, making something random, and then closing it. Give yourself a real assignment, and try to complete it. Create a 3D model of your pet hamster, redesign the UI for a game you enjoy playing, or create a logo for your future indie game company. Or find a tutorial on YouTube. Then post your projects online — create a portfolio for yourself as you go.</p><p>Having a specific goal in mind will force to learn how to use the application, and posting your projects in an online portfolio will force you to take it to a level of completion where you feel comfortable sharing them with others. You won’t give up at “good enough.”</p><p>No matter what you choose to learn, the goal is to get familiar enough with the program so that you can list it on your resume later as something you’re comfortable using.</p><p><strong>How to choose</strong></p><p>If you’re not sure what to invest time in, the best way to decide is to go to the job site of a company you want to work at one day. Find a job opening for the job you want, and see what the requirements are. Usually, they will include any experience the ideal candidate should have — including specific software you need to know.</p><p><strong>One last thing</strong></p><p>Unconventional experience is useful too! If you love board games or card games, and want to spend your time designing them, then do that! That’s a great, unique type of game design experience that not everyone has, and if you really invest time in it, you will learn things that are applicable to video games as well. Overall, your goal is to make a thing, get feedback on it, and make it better. And then make more.</p><p>There are the two big reasons you should do this. The first is that you’ll learn things about the tools, the process, and you will be on the road to mastery of those things. Mastery is about practice. It’s simple; the more you do something, better you become at that thing. If you work on your own projects consistently over time, you cannot help but become an expert using those tools.</p><p>The second reason is that it shows that you’re willing to work hard on a project, even when it’s not a requirement. When I’m looking to hire for an entry level position, the first thing I want to know is what that person has accomplished outside of school. If I see that you created a mobile game about your grandma, or have an online portfolio of Harry Potter fan art, I’m immediately more intrigued, especially if I go there and that Harry Potter fan art kicks ass. (More Snape, pls.)</p><p>Spending time on your own projects shows that you are passionate, motivated, disciplined, organized, and serious about your goals. If I see that you’ve spent your free time to become a better designer, artist, or programmer, I know that you’re someone I want to work with.</p><h3>Tip 2: Build your network</h3><p>To be successful in the business world, you need to have a network of people that you know and keep contact with. We all have to start somewhere, so at first, your network might be friends you make in school. You might connect with mentors or teachers. You might meet people with the same interests somewhere along the way. Growing your network is something that you can be doing right now, before you’re working in the industry, because it’s a really easy thing to do!</p><p><strong>Join meetups</strong></p><p>You can join game dev meetups on meetup.com. Joining a local meetup can hook you up with game developers and aspiring game developers in your area. Going to these meetups on a regular basis means that you’ll get a chance to talk to other people that are working on their own projects, and that in itself can be really inspiring. Provided that you actually talk to the people at the meetup, that is. So take the time to build relationships, make friends, and expand your network by linking up with others that have similar goals.</p><p><strong>Make an indie game</strong></p><p>There are no barriers when it comes to joining the indie game community. If you’re at home, building a game in your own time, why not join a community where other people are doing the same thing?</p><p>Two good places to start are <a href="https://itch.io/">itch.io</a> and <a href="https://www.tigsource.com/">tigsource.com</a>. Itch.io is a platform that will allow you to post your games and you can customize how you charge for them. TIG Source has an active community and forums where you can post builds and get feedback on what you’re doing as well.</p><p>Also — you can also use social networks to make connections as well. Twitter is a great one for this. If you play an indie game you like, tweet at the developer and tell them you liked their game. Often that’s a great way to open a conversation with another developer!</p><p><strong>Game jams</strong></p><p>You can participate in game jams, where you work with a small group to complete a game in (usually) a 2 day stretch. This is great experience that can teach you things like how to work effectively within a team, how to make decisions quickly, and how to scope an idea so that it’s something your team can accomplish in the time allowed.</p><p><strong>Going to industry conferences</strong></p><p><a href="https://www.e3expo.com/">E3</a>, <a href="https://www.dicesummit.org/">DICE</a>, <a href="http://www.gdconf.com/">GDC</a>, and <a href="http://prime.paxsite.com/">PAX</a> are all great places to meet people in the industry. Given, going to conventions is not cheap, however, most have student rates, so take advantage of that if you’re a student. While you’re there, you’ll meet people, and have a chance to make connections. For example, if you attend GDC and go to a talk you particularly like, go up to the stage afterwards and speak with the person that gave the talk. Think of a question or two you’d like to ask that person. Ask if they’d mind giving you advice on a project you’re working on.</p><p><strong>Using Linkedin</strong></p><p>Last — and the easiest thing on this list — is that you need to create a <a href="https://www.linkedin.com/">Linkedin</a> profile for yourself if you haven’t already. Create a profile, put a professional looking photo on it. If you don’t have a professional looking photo, have a friend take one for you. All it takes is a clean shirt and a neutral background. If you’re a student, add that to your profile. Then post your school and personal projects.</p><p>One note about Linkedin — it is not Facebook. This is what your future employer is going to check first before they decide to interview you — so keep it professional!</p><p>Linkedin is also super useful for making contacts as well. You can join groups on linkedin for game developers, and meet people by simply commenting, asking questions, and posting relevant information. The point here is that you should build real relationships with others in the industry. The more people you know, the more people you can reach out to for help if/when you need it.</p><p><strong>Why your network is important</strong></p><p>Well the most important reason you should build your network right now is because then you know cool people and can go out for beers. This is a picture of some of my past coworkers celebrating the end of the workweek — after hours, of course.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*fJB6IrBrsQfgCTk4X8ijFg.jpeg" /></figure><p>But seriously. Why do people say “It’s all about who you know?” It is because the connections you make will bring you opportunities, once you’re out there in the job market.</p><p>For example, when I got a job at NetDevil, my connection was a designer friend at Blizzard knew a producer at NCSoft. NCSoft was the publisher on Auto Assault, the game that NetDevil was currently working on. My resume was personally sent from my friend at Blizzard, to his friend at NCSoft, to the design director at NetDevil. I basically got pushed to the top of the pile because I came with a personal recommendation. I was interviewed and I was offered the job within a week after applying.</p><p>Before we go any further… I should clarify that whatever job you’re applying for, you still need to be qualified for that job. Having a connection can provide you with a boost, but it can’t override a lack of skills. However, if you are one of two equally qualified candidates, and you have a personal recommendation and the other person does not, it is much more likely that you’ll get the job, simply because people trust personal recommendations. It feels safer than hiring someone they don’t know.</p><p>In some situations, having a connection can even create opportunities where there aren’t any. If someone knows you have the skills they need, they will find a way to get you in.</p><p>In 2006, my friend John was working at a game company called Perpetual Entertainment. He knew they needed a designer with my exact background, so he made a suggestion to his boss, got me an interview and I was eventually hired. There was never a job listing — meaning that I never competed with other people for the job. They wanted someone that had the experience I had, so they created an opening. Connections can create opportunities!</p><p><strong>Utilizing your network</strong></p><p>Once you have your Linkedin profile and you’ve connected with people, you’ll be able to keep track of where they are working. You want to be able to say, “Oh, look, Sarah just started working at Blizzard as a 3D artist.” Or “Justin got that gameplay engineer role he wanted at Riot Games.” Now you’ve got a connection at that company, simply because you decided to keep in touch with people. When you see that, take a moment and tell your buddy, “Congrats!”</p><p>And then when you’re ready to apply for an opening at that particular company, you’re in a better position to talk with your connection and find out if there’s a way to be referred, or have your application fast-tracked.</p><h3>Tip 3: Stand out from the crowd</h3><p>The game industry is relatively small. That means there are fewer jobs than there are people applying for those jobs. So in order to get noticed, you need to stand out. Here are some ways to do that.</p><p><strong>Make games, make art, make something</strong></p><p>First off, you can do things I mentioned above, like creating an online portfolio or making games in Unity. If you just did one of the things on the list from Tip 1, and then posted what you made online, you’d be ahead already.</p><p><strong>Get an internship</strong></p><p>There are lots of game companies now that have formal internship programs. These are usually listed on the company job site, so they are easy to find and apply for. This will be a challenge for those that don’t live in an area of the country where there are game companies nearby, however. But if you can move temporarily and could swing it financially, it’s an excellent option that will help you stand out when you’re looking for a job later on.</p><p>Because game development is such a hot field right now, there is a lot of competition for these roles, even though most internships pay very little to nothing. The upside is that you’d get a chance to work for a real game company, and gain valuable experience — plus if you do a good job, you can even eventually get hired by that company after you complete your internship. I have a friend that did just that and now works on the Hearthstone team.</p><p><strong>Create a blog</strong></p><p>Creating a personal blog is something that you can do, in most cases for free. The subject matter is up to you; but it should be relevant in some way to the job you eventually want to get. As a designer, you could review games you’re playing. You could also create a development blog, where you post your progress, successes and failures with the game you’re working on. If you’re an artist, you could post about techniques you think are useful or discuss art styles in different games.</p><p><strong>Own it</strong></p><p>My overall suggestion to you is this: figure out how to put your own mark on the things you do. If I visit your blog, and you’ve posted 37 insanely well-written game reviews from the point of view of your dog? That’s hilarious. I already want to know more about you. So that thing you’re obsessed over, or that thing that makes you, you, figure out a way to show that to the world. How can you use that to create something unique?</p><p><strong>Make your own opportunities</strong></p><p>Here’s a big one. You need to be proactive and look for opportunities. No one is going to come knocking on your door because they heard a really great game artist lives there and needs a job.</p><p>If you want this, you need to put yourself out there, by making stuff. Because you could be the best artist in the world, but if you sit around waiting for someone else to discover that, it’s not going to happen for you.</p><p>ACTION is the key to almost everything. And I think where a lot of people get caught up is that they want to wait until they feel more confident in their abilities before they take action.</p><p><em>“I don’t feel ready. Maybe in a few months.”</em></p><p>If you always wait until you feel ready, you will pass up a lot of really great experiences where you stand to learn a lot and grow personally and professionally. I’ve seen people decide not to apply for jobs, pass up the chance to meet someone with experience in their industry, or even turn down a promotion simply because they didn’t think they were good enough yet. But if you want to succeed, you need to do things anyway, even if you don’t feel ready.</p><p>Let’s say you’re a beginner at pixel art, and get asked to join a group of friends for a game jam, and they want you to do the pixel art for the game. Even if you don’t exactly know what you’re doing, you should say, “You know what, I don’t know a lot about that yet, but it’s something I want to learn how to be better at and I’m willing to give it 100%. As long as you guys are ok with that, I am totally in.”</p><p>If you see an opportunity to try something, you need to be ready to say YES. And then after you say yes, you need to be ready to work really hard, and give it your all. And sometimes while you’re doing this, you will fail. But that’s totally ok, because failure is essential for success. When you’re learning something, you need to get it wrong a whole bunch of times before you know what it means to get it right, and you will learn something each time you get it wrong.</p><p>Change the way you see failure. It’s not the end of the process, it’s simply a step on the way to learning the skills you need to make it in the industry.</p><p><strong>Go forth, and be awesome</strong></p><p>Everything I’ve suggested here all comes down to making yourself a contender when you’re applying for jobs. There are going to be lots of graduates with game dev degrees. All of them will have school projects under their belts. And all of them want your dream job just as much as you do.</p><p>So:</p><ul><li>Get experience doing the thing you want to do.</li><li>Build your network and connect with people in the industry.</li><li>Stand out from the crowd and look for opportunities.</li></ul><p>As with everything I post, my opinions are based on my own personal experiences and from talking with college &amp; university students looking to get into the industry. Did I leave something out? Let me know!</p><p><em>This article was originally posted on </em><a href="http://christinebrownell.com/"><em>christinebrownell.com</em></a><em> on February 1, 2016.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dd4ed64f06d7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Five Ways to Improve Brainstorm Meetings (for Game Designers!)]]></title>
            <link>https://cbrownell.medium.com/five-ways-to-improve-brainstorm-meetings-for-game-designers-512eedf47c87?source=rss-607ce55ed14------2</link>
            <guid isPermaLink="false">https://medium.com/p/512eedf47c87</guid>
            <category><![CDATA[game-development]]></category>
            <category><![CDATA[creativity]]></category>
            <category><![CDATA[brainstorming]]></category>
            <category><![CDATA[meetings]]></category>
            <category><![CDATA[game-design]]></category>
            <dc:creator><![CDATA[Christine Brownell]]></dc:creator>
            <pubDate>Wed, 08 Aug 2018 18:35:50 GMT</pubDate>
            <atom:updated>2018-08-08T18:47:09.919Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QFXKiNHJWxlpZEc0QuXX_Q.jpeg" /></figure><p>If you’re a game designer, you’ve probably done your fair share of brainstorming. Level design ideas, content design ideas, or even full game concepts often find their beginnings in a brainstorming meeting. You get the design team in a room, give your team sugary drinks and don’t let them out until you’ve got a whiteboard full of kickass ideas, some of which eventually find their way into the game.</p><p>If I’m being honest, I can also say that at one point or another, I’ve sat through a brainstorming meeting that seemed pointless, didn’t yield anything usable, and/or strayed wildly off track. Something that was supposed to encourage creativity had instead become a waste of time.</p><p>Let’s rewind a few years back… To 2012, when I was the design director at Playfish, and The Sims Social was one of the most popular games on Facebook. At that time, we were grinding out content packs at the steady, unrelenting pace of once a week.</p><p>And to keep up with that schedule, we brainstormed once a week, which turned out to be… A lot. It wasn’t that the designers weren’t motivated; in truth, the designers at Playfish were some of the most dedicated and creative I had ever worked with. But I kept feeling that we could be getting more out of the hour we were spending.</p><p>So, like I usually do, I read some, and thought some. I analyzed our current approach. The following week, I decided to make a few key changes to our meetings that led to some really positive results.</p><p>So: here they are! Five simple things that you can do to improve brainstorming meetings for your team.</p><h3><strong>#1: Invite non-designers to participate.</strong></h3><p>Brainstorm meetings are often the very first step in the long process of creating game content. The discussion is usually very high level, where you’re simply collecting ideas rather than evaluating them — an open space where anything goes. This makes it really easy for anyone on the team to join in, regardless of their role.</p><p>Giving everyone a chance to participate is also a great way to gain the support of your team and build confidence in you as a leader. So invite the artists, coders, audio crew or even QA — good ideas can come from anyone. Most people enjoy being creative (even if it’s just for an hour) and jump at the chance to contribute something that ends up in the final game.</p><p>Even better, inviting outsiders into the design process can be beneficial for the designers! The design team is the closest to the game, and can sometimes lose their ability to challenge the constraints they live with, day to day. This can overflow into brainstorming; meaning that the amount of left field, crazy, outside-the-box ideas tend to decrease over time — unless you do something about it. Bringing in non-designers is a great way to keep things exciting in your brainstorming sessions.</p><p>This needs to be done in a somewhat thoughtful way, however. Inviting your whole team into the meeting can be counter productive; too large of a group and things get out of hand, fast. A very large group means people talking on top of one another, side conversations, a general lack of focus. Even the best leader is going to be challenged here (I’ve led some absolutely bonkers brainstorming meetings by inviting the entire art team in at once. It can be incredibly fun, but yeah, not the most productive meeting I’ve ever seen).</p><p>So what I’ve found to work is to periodically send out an email to your team with a simple request:</p><p><em>Are you interested in being a part of the design brainstorming process? If so, reply to this email with a simple ‘Yes’ to be added to the list.</em></p><p>Keep this list somewhere, and keep it current. Then, every time you schedule a brainstorm session, add a few people on the list to your meeting. Work your way through that list, giving everyone a turn.</p><p>I’m not specifying the “right” number of people to invite here because it really has more to do with the size of your design team, and how big of a meeting you feel you’re able to handle. For us, with 6–8 designers, I often invited 3–4 others in addition to that group and found that worked really well for us.</p><p>Varying up the brainstorming group from week to week can really impact the range of ideas that are produced, in a positive way. The key here is to ensure that you have your core participants that are there every week (the design team) that help keep the structure of the meeting constant, but you’ll have fresh, interesting ideas added to the mix from the newcomers. Everyone wins, yay!</p><h3><strong>#2: Write the subject or problem to be solved on a whiteboard (or somewhere prominent).</strong></h3><p>I know what you’re thinking here: “Brilliant! I never would have thought of that!” Yeah, yeah, ok. Stay with me, because here’s the important bit. Underneath your main topic, add 3–6 sub-points that help define that main topic, or in some way help give context to what you’re brainstorming.</p><p>For example, when we brainstormed for The Sims Social, we had several categories of content we had to come up with for each release, like quests, objects for Sims to interact with, and furniture styles. So I’d write the theme up at the top of the board, and then separate the space by defining the different types of content we needed to brainstorm beneath that.</p><p><em>For example:</em></p><p>Theme: Alice in Wonderland</p><p>Objects | Quests | Decorative Items | Etc</p><p>This also works if you’re brainstorming for a particular game area or level. You can set the stage for the level with what you know already:</p><p>Level: Pirate Ship</p><p>Time: night</p><p>Restrictions: The entire experience must take place on the ship</p><p>Level | Enemies | Boss | Etc</p><p>Here’s an example of what this might look like…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*W325-2b27nQz0EYWxCS78A.jpeg" /><figcaption>The whiteboard after one of our Sims Social brainstorming meetings</figcaption></figure><p>Adding details underneath the main topic gives participants a starting point for their thinking and allows them to attack the problem in a more specific and relevant way. Often, giving people the space to “imagine anything” has the opposite effect, yielding fewer ideas, simply because they don’t know where to begin. So add some guidelines or qualifiers to help your participants out, and you’ll get more, and better suggestions.</p><h3><strong>#3: Use the first five minutes of your meeting to allow people to brainstorm individually.</strong></h3><p>The goal here is to allow each person time to come up with their own ideas, before they can be influenced by others in the meeting. Why is this important? Because it’s been proven that brainstorming meetings are ineffective in encouraging a large range of ideas. This occurs because people are, understandably, influenced by the ideas of others in the room. Additional ideas tend to converge rather than become more unique and varied during the course of a meeting.</p><p>Back when I was at Playfish, I figured that we should add some individual brainstorming time, but figured that simply asking people to spend the time brainstorming on their own probably wouldn’t work. So instead, I changed the structure of our brainstorm meetings so that each one started with a 5-minute individual brainstorm.</p><p>Here’s what I did:</p><p>— Prep the meeting room: Have paper/sticky notes and pens waiting on the table before the meeting starts.</p><p>— As people enter the room, remind them that the first five minutes of the meeting is to be used to brainstorm individually on the topic (which you’ve already written on the whiteboard). Tell each person to grab a pen and a sticky note and start writing down ideas.</p><p>— Enforce a strict ‘No talking’ rule during this time.</p><p>As with any new process, this is going to be more work in the beginning, because people need time to learn the routine. When I introduced this idea to my brainstorming group, I first explained what we were going to be doing (come up with ideas on your own first), as well as why we were doing it (it’s been shown that people come up with more ideas when asked to work alone). Luckily, my team at Playfish was totally on board to try this out, and after a couple of meetings, they had the routine down.</p><p>As a bonus, individual brainstorming is a really effective way to kick off a meeting; you’re putting your team into a situation where the meeting topic is ALL they have to think about, in a quiet place sans the typical distractions of IMs, direct reports asking questions, or spammy Outlook notifications. They are in the room, with a solitary task, and they can focus all of their attention on it. Once the discussion begins, you reap the benefits of that focused mindset.</p><p>We found that spending the first five minutes this way was always worthwhile. It took us only one meeting to see the beneficial difference this time made — the range and the quality of ideas increased incredibly. Try it!</p><h3>#4: Everyone that attends the meeting is required to participate.</h3><p>I require participation in brainstorming meetings because they are safe; largely free from any criticism, and a fear of criticism is one of the biggest reasons that people are less likely to speak up in a meeting. So let everyone know ahead of time that they should be prepared to share their ideas, and then calm any anxiety by by reminding your group that just about anything goes, and there’s definitely no “right” answer when brainstorming.</p><p>Requiring everyone to contribute also addresses a problem I used to run into a lot while running meetings: If your group is on the larger side, you’ll soon find that you have 2–3 people that dominate the discussion, while others add absolutely nothing to the meeting because they never speak.</p><p>The solution to this is to structure at least the first 10 minutes of the discussion time so that everyone is required to contribute an idea. And this is actually really easy to do.</p><p>Assuming you spent the first five minutes of your meeting brainstorming individually, each person in the room now has a list of super awesome ideas sitting in front of them. Pick someone to start, and then work your way around the room in order, giving each person a turn to suggest one idea from what they’ve written down. That’s it — one idea — easy.</p><p>During the first rotation, I am fairly strict about this: one idea and then it’s the next person’s turn. But once we make it all around the room, it pretty much becomes a free for all. It’s up to you, though, as the meeting leader, to keep it going or open it up. I usually do whatever I think will keep everyone engaged as well as making sure that my softer-spoken colleagues get a chance to share.</p><p>Requiring all attendees to participate provides the following additional benefits:</p><p>— It discourages lurkers from attending your meetings (people that waste time by attending meetings but never participating). Brainstorming meetings are for brainstorming. If someone doesn’t want to help out with that task, then that person should be somewhere else, doing something else.</p><p>— It supports the team value that good ideas can come from anyone on the team, and it’s everyone’s job to speak up. (Read: increases team investment in the quality of the end product.)</p><p>— It prevents the more outspoken members of the group from completely controlling the meeting (although you’ll have to work a bit to ensure this).</p><h3>#5: Be an active and engaging group leader.</h3><p>By far, this the most challenging item on this list, because it’s hardly a single line item… Being a great leader is actually a lot of smaller tasks rolled into one, so here’s a short list of tips on how to keep your brainstorm meetings on the rails by leading well:</p><p>— Never sit. You’re leading the meeting, and when you’re standing up at the front of the room, you’re a visual reminder of that.</p><p>— Record all the incoming ideas yourself. This seems like an easy job to delegate, but if you aren’t the one at the whiteboard, you’re actually relinquishing some of the control over the meeting. Hang onto that marker, at least for a while. (Eventually, I had all of the designers leading their own brainstorms, but when you’re first getting into a routine, you need to be the constant.)</p><p>— Monitor the conversation to keep things moving. You’re responsible for facilitating the discussion and getting those creative juices flowing. If people are having a hard time getting started, throw a couple ideas out yourself, or ask someone you know usually has great ideas to start.</p><p>— When someone comes up with an idea that’s particularly compelling, ask questions to encourage the group to discuss it further. “How do you see that working?” “What would you expect to happen when…?”</p><p>— If you’re asked a direct question, turn it around and ask the asker that question instead.</p><p><em>Question: “Are there any skills that players should use in this level?”</em></p><p><em>Answer: “Do you have any ideas about that?”</em></p><p>Note that you only want to do this if the question you’ve been asked pertains to the topic at hand. If you do this with every design question you get asked, you may find yourself deep down a rabbit hole, where the discussion is nowhere near the place you started.</p><p>— Police the group as little as possible. Easier said than done. So when is it necessary? Well, here are the times where I usually stop the conversation:</p><ul><li>When designers are getting too far into debating the merits of a particular idea: “There will be time for that outside the meeting, right now we’re all about free expression without criticism. Let’s keep moving.” Don’t be afraid to stop the conversation if it’s not a good use of the time.</li><li>Someone suggests a compelling idea that doesn’t fit at all within the context of the meeting: “Giraffes on roller skates sounds epic, so I’ll write that down for us to discuss later. Now let’s get back to city-building mechanics.”</li><li>Someone suggests something that is wildly off-brand. This may or may not be an issue for your particular game, but it did come up every so often on The Sims, a popular IP that has very specific guidelines as to what is acceptable and what isn’t. So… “A gangster week that includes Sims shooting at one another with guns? Yeah, sorry guys, that isn’t going to fly. Let’s come up with something else.”</li></ul><p>In all of these situations, you should first gauge the impact your interruption is going to have on the meeting. If you determine it’s necessary, then stop the conversation from going too far, but evaluate each instance on its own because sometimes it’s that crazy, in between, seemingly irrelevant conversation that results in something magical.</p><p><em>This article was originally posted on </em><a href="http://christinebrownell.com/"><em>christinebrownell.com</em></a><em> on September 12, 2015.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=512eedf47c87" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Games are Defined by their Players]]></title>
            <link>https://cbrownell.medium.com/games-are-defined-by-their-players-ba45513a42a6?source=rss-607ce55ed14------2</link>
            <guid isPermaLink="false">https://medium.com/p/ba45513a42a6</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[games]]></category>
            <category><![CDATA[game-development]]></category>
            <category><![CDATA[indiedev]]></category>
            <category><![CDATA[videogames]]></category>
            <dc:creator><![CDATA[Christine Brownell]]></dc:creator>
            <pubDate>Wed, 08 Aug 2018 17:29:11 GMT</pubDate>
            <atom:updated>2018-08-08T18:32:19.526Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ySuR_Rl3pXfMWG5qRBSapA.jpeg" /></figure><p>I finally got around to watching the film Indie Game: The Movie over this past weekend. The film focuses on the ups and downs of a few indie game developers as they work towards launching their games. Different personalities, different life circumstances, very different games, but the same end goal: creating a game and finding an audience.</p><p>Most of the film is punctuated by earnest, hopeful, oftentimes emotional displays of the developers as they work to complete their games; nothing surprising about that. Game development can be as fun as it is harrowing, and if you’re not making games because you have a deeply-rooted desire to do so, you won’t last long in the industry, because it’s just really, really hard.</p><p>Indie developers to me are the pinnacle of game-making passion; many of them create simply because it’s what they love to do. I found <a href="https://twitter.com/edmundmcmillen">Edmund McMillen</a> particularly inspiring, especially when he talked about a game he created years ago based heavily on his childhood experience. This is one of my favorite moments in the film.</p><p>But there were also moments that I found myself cringing. About three fourths of the way through the film, one of the developers related that although his game had a huge following, he was troubled that not every player was playing his game in the way he had hoped — that they were not enjoying it in the way he wanted them to. He seemed to be saying: “You’re doing it wrong.”</p><p>Honestly it’s not all that important who said this, because he’s hardly the first person to say it. I’ve seen many designers struggle with this same exact thing on different projects over the years. But as someone that has been immersed in crafting player experience for the entire length of my career, I admit being surprised to hear it. There he was, talking about a game that was ultimately successful, but he expressed what seemed to be genuine disappointment that people did not enjoy it the way he wanted them to.</p><p>“But what about what the players wanted?” I thought.</p><p>This moment was a sudden reminder about the core of the creative process: That thing that you’re making, that you love, the one that you’re pouring your heart into, that you’ve nurtured carefully and grown from a seed of an idea into something wonderful — it’s not actually yours.</p><p>Games are an interactive medium. Part of making a game is the intention to share it outwardly, to give it away and let others find their way through it, creating their own experience, their own understanding of what it is all about. It doesn’t really matter what your intentions were or what your story was originally; all that matters is the end result, and what players do with what you’ve created. You can invite them in, but you don’t get to tell them what their own personal experience should be, what holds meaning for them. Basically, you’re not making the game for you; you’re making it for your players — or rather, you’re sharing it with them. Games are a shared experience between creator and player.</p><p>People come to games for so many reasons: escape, boredom, fantasy, companionship, fun. Games are places to learn, to find friends, to be someone else, to get lost in an epic storyline, to just have something to do for five minutes while you’re waiting for your bus. These reasons are all valid. And what this means is that there just isn’t one “right” way to enjoy the experience.</p><p>So what if they don’t understand your story… Or if they never even read a word of it. Are they still playing your game? Are they having fun? Sweet. You reached that player, in the way that works best for that player. That’s what an interactive medium is about: Making a personal connection with your audience. Because your audience is full of people that love your game, they love it for different reasons, and they may be getting things out of it that you never imagined when you first created it. That should be celebrated! Because: awesome!</p><p>Watching people play your game, listening to people talk about your game; reading what people write about your game, these things become an integral part of what the game actually IS.</p><p>I love origin stories; it’s an absolutely fascinating process to create something and watch it come together piece by piece — but at the end of the day, the real essence of a game is what it becomes when you put it in someone else’s hands and mind. To me, that is what gives a game meaning and life, and it is absolutely the best part.</p><p><em>This article was originally posted on </em><a href="http://christinebrownell.com/"><em>christinebrownell.com</em></a><em> on August 31, 2015.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ba45513a42a6" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>