Contents
Building a Great Team: Communication
 
 
Printer-Friendly VersionPrinter-Friendly Version
 
Latest News
spacer View All spacer
 
November 22, 2009
 
Video Game Watchdog National Institute On Media And The Family Shutting Down [11]
 
Modern Warfare 2 Infinity Ward's 'Most Successful PC Version' Yet [12]
 
New Tech, Design Details Of Project Natal To Emerge At Gamefest In February
spacer
Latest Jobs
spacer View All     Post a Job     RSS spacer
 
November 22, 2009
 
Sucker Punch Productions
Character Artist
 
Sucker Punch Productions
3D Environment Artist
 
Sucker Punch Productions
Network Programmer
 
Sucker Punch Productions
Texture Artist
 
Sony Online Entertainment
Brand Manager
 
Monolith Productions
Sr. Software Engineer, Engine - Monolith Productions - #113767
 
Crystal Dynamics
Sr. Level Designer
 
Gargantuan Studios
Lead World Designer
spacer
Latest Features
spacer View All spacer
 
November 22, 2009
 
arrow Upping The Craft: Susan O'Connor On Games Writing [6]
 
arrow Small Developers: Minimizing Risks in Large Productions - Part II [6]
 
arrow iPhone Piracy: The Inside Story [48]
 
arrow And Yet It Grows: Analyzing the Size and Growth of the European Game Market [5]
 
arrow NPD: Behind the Numbers, October 2009 [13]
 
arrow Reflecting On Uncharted 2: How They Did It [5]
 
arrow Sponsored Feature: Rasterization on Larrabee -- Adaptive Rasterization Helps Boost Efficiency
 
arrow Postmortem: Wadjet Eye's The Blackwell Convergence [2]
spacer
Latest Blogs
spacer View All     Post     RSS spacer
 
November 22, 2009
 
Accepting the Inherent Value of Games
 
Planckogenesis, Part II: Song Structure & Gravy Train [1]
 
Designing Games Is About Matching Personalities [1]
spacer
About
spacer News Director:
Leigh Alexander
Features Director:
Christian Nutt
Editor At Large:
Chris Remo
Advertising:
John 'Malik' Watson
Recruitment/Education:
Gina Gross
 
Features
  Building a Great Team: Communication
by Marc Mencher
3 comments
Share RSS
 
 
September 17, 2008 Article Start Previous Page 5 of 5
 

Use a Problem Log

Work-related problems can actually be opportunities for team improvement. Use a problem log and give all team members access to it to share lessons learned. You may want to appoint a team member to resolve the problem but be careful -- no matter how adult people appear to be, most of them probably have not forgotten the heady power of the hall monitor!

Advertisement

Some relevant questions either you or the designated problem-solver wants to ask include:

  • What event(s) led up to the problem?
  • What is the apparent cause of the problem? Is it internal (within the team) or external (within the company)? Is it personal or professional?
  • Where do things stand?
  • What are potential positive solutions? More training? Better communication?

Talk it Out

Ever burn a boss down to very little health, only for him to do something unexpected and wipe out the whole group? Well, you are not the first, and won't be the last. When this happens, nobody runs back and tries the same strategy again. It is important to take a few minutes, regroup, and recompose.

Talk it out with the group and figure out how to tweak the strategy in order to do the good parts correctly, and prepare for the part that went wrong. Making changes cannot be done by an individual in a group instance, but rather the whole team has to be on the same page. It is important for each person to know what they need to do, and more important for them to know why they do what they need to do. Once everyone is on the same page, and the strategy is reworked, it's time to try again.

Once a problem is identified, discuss it with the people involved. This is basically a listening task -- let them tell you how they see things. Assess attitudes and preconceptions. What they say, what they do, and what they feel may be different. Are there hidden agendas? Are they withholding information and/or holding back deep-seated emotions and grudges? If an individual blames others to justify personal actions, confront and question the defensive reaction. Track all rumors to the source as best you can. People's reactions will show you the strength of their commitment to the team.

DO

DON'T

Try to identify weaknesses in the team

Go on a witch hunt that turns the team on itself

If subgroups are part of the team, be sure they are all working efficiently

Lay blame indiscriminately on the entire team

Analyze all the information

Ignore the evidence and proceed without change

Offer training as a solution

Ignore the possibility that reorganizing the team might solve the problem

Review the team/subgroup leader's abilities

Leave the team or subgroup without a leader

Ensure that everyone on the team agrees to the solution

Forget to follow-up on the team's progress after problem resolution

Other Kinds of Problems

Naturals are few and far between. Very few people can be inserted into a situation and automatically excel. In the game world, people can pick things up rather quickly, but that does not mean you know the ins and outs of the game. Many times, it is easiest to find someone who has been in your shoes, and use them as a model for your own gameplay. Sometimes, you need a guide to walk you through levels, instances, or just general skills that your character has gained.

An experienced hand could have all sorts of tricks, tips, and advice that can help you through some of your difficulties. Use this person as a resource, as they have undoubtedly done the same with someone else when they were in your place. This is a great way to build allies, compare strategies, and continue your character's growth. When you take on a mentor or a guide, be respectful and help them with what they need as well, cause you never know what lessons you may learn from strictly watching, listening or helping.

In real life, sometimes you need to hire consultants. This can be a great way to provide instant training for the team -- or it can create a management nightmare. Whenever possible, make consultants feel like they are part of the team but don't give them responsibilities regular employees can or should handle. Keep a watchful eye on contract or temp employees who are angling to oust a regular employee and take over the job.

Cross-functional multi-disciplinary and/or interdepartmental teams are becoming more common in today's business world. In some cases, there may not appear to be many differences between a team in Los Angeles and a team in London, other than time zones and accents. However, there are some significant cultural differences, especially between American and Asian business practices, so it's a good idea to do your research and brief your team to reduce potential conflict or potentially offensive behaviors.

One of the most difficult situations companies encounter in the workplace is sexual harassment. Most companies have a training program that all employees must complete but that doesn't always prevent inappropriate behavior. Be sensitive to conversational overtones and innuendos.

Points to Remember

  • Handle personal problems between team members constructively
  • Don't react until you have the facts
  • Avoid creating a "blame culture"
  • Treat everyone equally
  • Praise team members publicly whenever you can
  • Don't play favorites -- and don't be forced to by nepotism
  • Be alert for sexual harassment in either direction and be sure every member of your team has completed the company's mandated training in this area.

---

Conflict photo by Kevin Simpson, used under Creative Commons license.

 
Article Start Previous Page 5 of 5
 
Comments

Sergey Lobko-Lobanovsky
profile image
Actually quite a good article, thanks! Written from the middle management perspective, it correctly describes what should & shouldn't be done to foster team work. Kudos!

Jacek Wesołowski
profile image
I like this article, too. It's a pity that people who need this kind of advice most are the same people who never read articles about improving one's management skills.

People keep writing about how to manage a team better, but since I'm not a manager myself, I could really use an article on how to be managed. Especially: how to deal with my personal perception of my managers doing a poor job. The most important question is, in my opinion: how do I tell whether I'm a reformer or a troublemaker?

Assume I'm right in a given situation -- how do I make my boss listen to me at all, let alone agree with me? How do I deal with "false agreement", when manager agrees to introduce certain solution, but then sabotages the actual implementation thereof, either by inaction or contradictory decisions?

What do I do when my boss complains about overall quality of my work but refuses to give actual qualification (e.g. he keeps saying "your concept art is ugly", but never says "there's too much red in this picture")?

How do I confront a boss who's clearly doing a bad job? I used to have a boss who would come to the office at 2pm. There was a weekly meeting scheduled for 12:30pm, but it was never held, because the boss was never present. Clearly, someone should have talked to him about it, but how do you do that without getting fired?

How do I deal with coworkers who complain about their superiors in private, but refuse to speak openly about their issues, because they "don't want to lose their jobs"? How do I make my coworkers more active without appearing to be trying to take over?

What do I do when there's a genuinely good idea that requires every single person on the team to change their habits just a little? What if I'm tasked with making sure the idea works as intended, but I'm not allowed to require anyone to do their part?

How do I get around my superior's quirks? I mean, managers are just people, and people are never perfect. I used to have a boss who was some 190cm tall, with low, loud voice and intimidating personality. He almost never answered e-mail. And he was perfectly capable of mocking his employees publicly when they failed to meet his expectations. How do you deal with issues like this in a civilized manner that doesn't turn the team into a powder keg?

Most people I've worked with so far have a simple solution: they just don't care about their work. At least that's what they say. I would send them a link to some good article on the matter, but I don't have any.

Jose Eduardo Teran
profile image
Undoubtedly, an important factor for having an efficient and effective development team is the constant communication between everyone.

Excellent article.


none
 
Comment:
 


Submit Comment