>> Tuesday, August 4, 2009
I talked about collaboration yesterday, specifically the odd one my husband and I have regarding writing (which is different than the strange collaborations we have for everything else).
Teamwork is somewhat related to the topic of partnerships, only the dynamics tend to be much more complex. Now, I'm not going to tell you the right teams or what is always good or always bad. However, I can tell you some of my experiences and what I think helps (and doesn't help) make a good team. For those of you who do a lot of interactive and team work, I expect I won't be telling you anything new.
One thing about working for the government, I have seen a lot of the features that DON'T make for a good team - though they are not restricted to government and contractor organizations (and, yes, I have seen teams that work here, too):
Too many chiefs, not enough Indians. There are many organizations out there where the management structure dwarfs the working segment. It's a recipe for waste, inertia, and making poor decisions.
- In such an environment, decisions are often amorphous and preliminary much longer than they should be because it's under constant review - middle management has nothing else to do so they do meetings, reviews, reevaluations.
- Poor decisions stay in place far longer than they should because no one can reach concensus on the alternatives or, because those "making the decisions" don't really understand it so they're afraid to change it.
- Decisions are made more on the slickness of the presentation rather than because it makes sense because someone who isn't knowledgable is most influenced by good advertising.
- Meanwhile, while the management isn't accomplishing even what they are supposed to be providing (meaningful direction), they are sucking away resources (salaries), leaving the small cadre of real workers not only overworked, but often performing more work than necessary because they have to keep redoing things to try to get a reasonable product. That, of course, also reduces feedback so that management doesn't find out what's wrong until far too late.
Not enough experts. Too many folks with not enough actual expertise makes a meeting an exercise in action items with everyone going to "find out." If people don't have the understanding and knowledge to resolve the situation when decisions are to be made, decisions won't be made. If a team requires expertise outside (and doesn't have it IN the team), the team is poorly designed.
Too many experts. Expertise is great and definitely something to include in a team, but if everyone's an expert (particularly if you have experts in the same field), there is a definite risk of egos getting in the way of solutions. Experts can compete (and torpedo each other), can get distracted by by inconsequential trivialities instead of addressing the whole problem. Experts are important, but an effective team usually needs people to (a) provide a fresh perspective and (b) to put the story all together find the "answer".
Not enough (or ineffective) communication. Teams cannot work effectively in isolation. Anything that blocks communication, blocks progress, leads to misunderstandings, tasks or considerations falling through the cracks, doing work more than once, or pieces that work fine independently but not together. And that anything can be distance, poor communication skills, unnecessary bureaucracy, language, unit systems, personality, technology, whatever.
Too much communication. If everyone's statusing, meeting, discussing, brainstorming, caucusing, reviewing, reporting, etc., no one's doing anything. If it takes longer to explain what you did than to do it (to everyone you need to explain it to), you're not exactly working efficiently.
Tomorrow, the kind of things I think make a team effective...