the EA spouse

I'm sure most of you have seen this already, but I thought I'd post it here, in case anyone hadn't yet.

Shame it's written anonymously, the author did a good job.

---------
EA: The Human Story
My significant other works for Electronic Arts, and I'm what you might call a disgruntled spouse.

EA's bright and shiny new corporate trademark is "Challenge Everything." Where this applies is not exactly clear. Churning out one licensed football game after another doesn't sound like challenging much of anything to me; it sounds like a money farm. To any EA executive that happens to read this, I have a good challenge for you: how about safe and sane labor practices for the people on whose backs you walk for your millions?

I am retaining some anonymity here because I have no illusions about what the consequences would be for my family if I was explicit. However, I also feel no impetus to shy away from sharing our story, because I know that it is too common to stick out among those of the thousands of engineers, artists, and designers that EA employs.

Our adventures with Electronic Arts began less than a year ago. The small game studio that my partner worked for collapsed as a result of foul play on the part of a big publisher -- another common story. Electronic Arts offered a job, the salary was right and the benefits were good, so my SO took it. I remember that they asked him in one of the interviews: "how do you feel about working long hours?" It's just a part of the game industry -- few studios can avoid a crunch as deadlines loom, so we thought nothing of it. When asked for specifics about what "working long hours" meant, the interviewers coughed and glossed on to the next question; now we know why.

Within weeks production had accelerated into a 'mild' crunch: eight hours six days a week. Not bad. Months remained until any real crunch would start, and the team was told that this "pre-crunch" was to prevent a big crunch toward the end; at this point any other need for a crunch seemed unlikely, as the project was dead on schedule. I don't know how many of the developers bought EA's explanation for the extended hours; we were new and naive so we did. The producers even set a deadline; they gave a specific date for the end of the crunch, which was still months away from the title's shipping date, so it seemed safe. That date came and went. And went, and went. When the next news came it was not about a reprieve; it was another acceleration: twelve hours six days a week, 9am to 10pm.

Weeks passed. Again the producers had given a termination date on this crunch that again they failed. Throughout this period the project remained on schedule. The long hours started to take its toll on the team; people grew irritable and some started to get ill. People dropped out in droves for a couple of days at a time, but then the team seemed to reach equilibrium again and they plowed ahead. The managers stopped even talking about a day when the hours would go back to normal.

Now, it seems, is the "real" crunch, the one that the producers of this title so wisely prepared their team for by running them into the ground ahead of time. The current mandatory hours are 9am to 10pm -- seven days a week -- with the occasional Saturday evening off for good behavior (at 6:30pm). This averages out to an eighty-five hour work week. Complaints that these once more extended hours combined with the team's existing fatigue would result in a greater number of mistakes made and an even greater amount of wasted energy were ignored.

The stress is taking its toll. After a certain number of hours spent working the eyes start to lose focus; after a certain number of weeks with only one day off fatigue starts to accrue and accumulate exponentially. There is a reason why there are two days in a weekend -- bad things happen to one's physical, emotional, and mental health if these days are cut short. The team is rapidly beginning to introduce as many flaws as they are removing.

(continued in next post)