23 February 2005
While we are in the business of putting a team together, borrowing this picture seemed irresistible. And here are some of the words which go with it:
It’s not teams that are the problem, it’s the rabid insistence on teamwork. Group think. Committee decisions.
Most truly remarkable ideas did not come from teamwork. Most truly
brave decisions were not made through teamwork. The team’s role should
be to act as a supportive environment for a collection of individuals.
People with their own unique voice, ideas, thoughts, perspectives. A
team should be there to encourage one another to pursue the wild ass
ideas, not get in lock step to keep everything cheery and pleasant.
This comes from, of all unlikely places, the blog of an author of textbooks on Java. But the more important clue is in the title – Creating Passionate Users.
I am not sure how much I agree with this characterisation of the individual/team balance – the argument is a little too sepia and white for my taste. But I strongly support the idea that part of the role of the team is to support individual creativity. The question is how best to do it. Over to you…