Neoseeker : News : IGDA members upset with leadership's stance on 60+ hr. work weeks

IGDA members upset with leadership's stance on 60+ hr. work weeks
Kevin Spiess - Friday, April 3rd, 2009 | 2:57PM (PT) 0 Like


Long hours are a game industry tradition, some argue

IGDA members upset with leadership's stance on 60+ hr. work weeks Image 1

Many members of the IGDA -- the International Game Developers Association, a leading game industry professional society -- have been upset with their organization's arguably soft stance on working long hours in the game industry.

The issue was re-ignited recently, when Mike Capps, head of Epic and former board of directors member for the IDGA controversially stated that working 60 or more hours a week was standard practice at Epic, and that he would not hire staff not willing to commit this much of their lives to working on the game at hand. The comments were made at a IGDA Leadership Forum at end of 2008, in a panel called "Studio Heads on the Hot Seat."

While being the head of Epic, Mike Capps is certainly justified in running his own company as he sees fit, but the comment irked many members of the IDGA who argue that his position does not jive well with the organization's mission statement, which is to "advance the careers and enhance the lives of game developers."

Many members of the IGDA have consequently called for a clarification of the organization's position on the topic of the long, industry-common work weeks. IDGA Chair Emeritus Jen MacLean responded in press release today on the matter. She said the IGDA "believes unequivocally that enabling your employees to create for themselves a high quality of life is a good business practice, and there are direct, negative consequences to ignoring your employees' quality of life. But work/life balance also goes far beyond the number of hours worked. Quality of life also varies significantly according to the individual."

Judging from comments read in the IGDA's forum, it seems that many members feel that while the IGDA has made progress on the amount of transparency game employers use to describe their studio's work expectations, many members think that the group should take a stronger stance against excessive, and unhealthy, work schedules.

The extensive hours often worked in the game industry has been a contentious issue -- perhaps most notably so when the "EA_Spouse" letters were released, which caused EA some measure of embarrassment and litigious trouble. Programmers working 20hr shifts are not unheard of, and can lead many to question the efficacy of planning 'crunch' times, as if they are a requirement of development.

One particular example that stood out in the forum linked above was from David Weinstein, who worked on Ubisoft's Rainbow Six. He said the final stretch ("crunch" time) working on that game was "extreme" -- so much so that he was twice pulled over when driving home from work, on suspicion of drunk driving, when in fact, he was just extraordinarily -- and unsafely -- exhausted.

Update:  IGDA board member Tom Buscaglia says that Jen MacLean "mishandled the issue", and that the IGDA will work on clarifying their position on the matter, but right now, it is not a priotory on a massive to-do list that they have. He further went on to say, perhaps whimisically,  that the situation would not benefit from IGDA members "bitch slapping Mike Capps for being a **cktard" (source.) 

Source: IGDA forums

Section: Console Games

  • 0 thumbs!
    anacreon since Oct 2005 | Apr 3, 09
    this isnt really surprising since programming eats a huge chunk of people's days without them even realizing it.
  • 1 thumbs!
    chautemoc since Mar 2008 | Apr 3, 09
    I have absolutely no problem with longer development cycles becoming standard so game developers work reasonable hours. Most other industries aren't like this, I don't see why ours should be any different. Suddenly I don't like Epic so much.
    Last edited by chautemoc :: Apr 3, 09
  • 2 thumbs!
    kspiess since Jun 2007 | Apr 3, 09
    I haven't done any hardcore programming, but perhaps it is like working in film where you don't really get the ball rolling until 4 hours into your work day.

    But yeah I can't say that I'm a big fan of working more than 70 hours a week myself -- which I've done, in the film industry. I think it is unnecessary and people work better if they have more balance in their lives. Of course, this is an outsider's perspective I suppose.

    But when a game like Gears of War 2 is set to make many millions of dollars profit, planning to work your employees 65+ hour week doesn't make sense to me. If I was a programmer doing that, I would just wonder why they wouldn't hire more people -- the game's budget can obviously accommodate that. I don't see how a mandatory crunch time is necessary in that situation, but I'm no Mike Capps.
    Last edited by kspiess :: Apr 3, 09
  • 0 thumbs!
    | Apr 3, 09
    kspiess is in porn?
  • 0 thumbs!
    OmegaFury since Jan 2008 | Apr 4, 09
    @fatbird

    I don't think people would spend 70 hours a week *bleep*ing -_-

    Back to the article:
    "Damn Mike... Gawd! You can't tell them directly that we condone slave labor. Geez, what's your problem?
    Last edited by OmegaFury :: Apr 4, 09
  • 0 thumbs!
    THM since Jan 2008 | Apr 6, 09
    quote fatbird
    kspiess is in porn?
    Hee Hee!!!!!
  • 1 thumbs!
    | Apr 5, 09
    @kspiess: Just to clarify -- Mike Capps original statement is that they purposely don't hire more developers because they share the wealth with everyone on staff. Fewer people working longer hours means each person gets a larger bonus. At least, that's his theory (which is entirely against all research into human productivity on multi-month work cycles). But that's the reasoning officially behind it.

    Realistically, long periods of longer hours results in less actual productive work being done. The 40-hour work week, divided as 5 days of 8 hours, was initially developed by Ford. It is longest he found he could work his employees while still actually gaining production. Any longer, and the number of defects ruining a given item, general fatigue slowing people down, and accidents causing work halts actually caused a net loss in productivity despite more man-hours being put in. I have a feeling Epic could produce better games with fewer people if they cut hours, but hey, I'm just a guy who's resting on every single bit of research ever done on the field, I'm not a Company President who never had any proper training in project management...
  • 0 thumbs!
    kspiess since Jun 2007 | Apr 6, 09
    fatbird-=> No, I wasn't in porn. But feel free to spread that rumor if you'd like.

    Karl-=> Thanks for your comments.
- This news story is archived and is closed to new comments now -

Hardware Newsletter:
Email:



Compare Prices

Motherboards
Abit
ASUS
Gigabyte
MSI
eVGA
Intel
Tyan
More...

Processors
AMD
Intel
More...

Memory
DDR
DDR2
DDR3
More...

Video Cards
ATI
eVGA
XFX
BFG
Sapphire
More...

search for lowest prices
(0.1228/d/nova)