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
 
Trion Redwood City
Sr. Environment Artist
 
Trion Redwood City
Sr. Evnironment Modeler
 
Sucker Punch Productions
3D Environment Artist
 
Sucker Punch Productions
Network Programmer
 
Sucker Punch Productions
Texture Artist
 
Sucker Punch Productions
Character Artist
 
Crystal Dynamics
Sr. Level Designer
 
Monolith Productions
Sr. Software Engineer, Engine - Monolith Productions - #113767
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 [7]
 
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
 
Time Fcuk [1]
 
Accepting the Inherent Value of Games
 
Planckogenesis, Part II: Song Structure & Gravy Train [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 3 of 5 Next
 

Networking

In the MMO world, this is extremely prevalent. People join guilds or clans, which open up a myriad of opportunities to explore game content with like minded individuals. Unfortunately, your group is not always going to be available when you want to do various tasks, quests, or XP grinding. For this reason, it is important to expand your network of in-game friends and allies. It is always a good idea to have a few tanks, minstrels, and crowd control in your friends list, just in case you need them.

Advertisement

In the workplace environment, certain people (senior management and/or your client) have considerable influence over your team. Make full use of formal and informal connections inside and outside your organization to provide valuable support. Teams can always use "friends in high places". Identify these people and seek their support and approval, preferably without sacrificing the integrity of team or the project.

A team sponsor is usually a well-placed, well-disposed individual who works outside your team. Team life is much tougher without these mentors, they offer guidance, help find creative solutions to problems as well as keep you on track so cultivate any relationships that may be useful.

A basic network can include a decision maker (maybe an executive or member of senior management), a liaison who may have the ear of senior managers (this might be you) and an approver, usually an individual whose official consent is required for key decision and milestone completion. Work the network in and out of the organization to find the support your team needs to be successful.

Every team needs to maintain three key relationships: within itself, with upper management and with the client. The lines of communication should be strong and amicable. This becomes even more important if your team is based away from headquarters, for example in a factory or separate office building. In some cases, upper management may also be the client or the sponsor. Be flexible and work within the structure.

Confidentiality

Before you decide what is confidential, ask, "Who else needs to know this?" and "Would openness be damaging?" If the answers are "everybody" and "no," circulate the information. However, if there is a real need for secrecy or if confidentiality is mandated by company policies and NDAs (non-disclosure agreements), be sure that there is no margin for error. Establish a procedure for dealing with information leaks and stick to it.

Teamwork and secrecy can be mutually exclusive, so a leader who isn't open with team members won't get the team's best work. Try to give your team full access (where appropriate) to information relevant to their overall project responsibilities, but remember there will be times when you may have to maintain confidentiality.

By sharing the overall vision with your team, you provide them a sense of individual ownership in their focus and can generate real team synergy by showing how all the pieces fit together in the puzzle. The more direct you are, the more accepting the team will be when you have to withhold information based on the "need to know".

Points to consider before passing along information:

  • Is the information accurate?
  • Who really needs to know?
  • What's the best way to relay it?
  • Who's the best person to relay it?
  • Will there be any negative fallout from disseminating it?
  • What kind of follow-up might be needed, positive or negative?
  • What will be the effect if this information is leaked to the marketplace?

Points to remember

  • Your job as team leader is to keep stakeholders (investors, publishers, senior management) informed of team progress. Avoid the temptation to sugar-coat bad news or promise more than your team can reasonably deliver.
  • You and the team may not agree with senior decision makers but it's wise to treat them with respect.
  • Be sure news (good or bad) is told to the whole team at the same time to ensure that everyone hears the message the same way -- but don't publically embarrass team members with bad news about their performance or employment in front of their peers or colleagues.
 
Article Start Previous Page 3 of 5 Next
 
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