One of the more interesting challenges of my MBA classes during the first year is working with group members on projects. In undergrad, working on a group project for a CS class generally meant working on some software project and handing in a working program (and perhaps some user documentation or design documents) at the end. Projects generally required work done individually by the group members and then putting it together at status meetings. It was important to have clean code, of course, but the primary goal was to have a working program at the end of the project and if someone was having trouble or a feature didn’t work quite right it was pretty easy to see. We could make changes and e-mail the rest of the group letting them know what we did.
In these business classes, though, it is a real challenge to keep everyone on the same page. When working as a group to turn in a paper or to prepare and give a presentation, the group members need to come up with some sort of thesis or conclusion that the paper/presentation will reach. Of course, as graduate students, most of us have jobs and significant others and some of us have kids, so it is extremely tempting to have an hour meeting where we split up sections of the paper/presentation and agree to get back together at a later time. At that time, we go over what we have discussed, start putting the pieces together, and decide who will present or write the introduction and conclusions of the paper/presentation. This leads to all sorts of organizational issues with the project:
1.) The paper/presentation is disjointed. One section does not lead to another or does not make sense. The supporting information of the paper/presentation does not actually support the thesis. Two group members may not have agreed on something that is important to the conclusions that the group reached and they don’t even know it until one person is speaking at the presentation.
2.) The paper/presentation is not consistent. One section of the presentation has 5 slides with 10 words on each slide. The next section has 1 slide with 60 words on it. The paper really sounds like it was written by 6 different people (even though there were only 4 people in the group).
3.) The paper/presentation goes extremely long. Everyone wants to get their 5 minutes in, even though their section of the presentation just isn’t that important.
4.) The person that writes/presents the introduction, conclusion, or main themes of the paper/presentation gets it wrong or misses a key point.
The groups that have been the most successful are the groups that keep things organized and cohesive in an efficient manner that doesn’t piss people off. You aren’t going to be able to keep the entire group together in a room for hours while you go over every detail; there must be some delegation. Moreover, when people do go off and do things on their own, the other group members have to be diplomatic when they come back with stuff that doesn’t fit with the rest of the paper/presentation. At the end of the day, though, each group member has to rely on other people that they just don’t know very well to be prepared and do good work. Good leaders must be able to trust their team and accept the consequences.
Filed under: management, School | Leave a Comment »