As an appetizer for an upcoming Work Better article on collaboration techniques, I’m pleased to present these team work worst practices from Ester Derby’s Software Managemet Process Improvement weblog:
A clear strategy to stifle teamwork
Establish two classes of membership on the team [WP NOTE: i.e. developers and testers, employees and contractors, or people with technical focus and people with business focus] , then follow these steps to ensure that all are aware of the distinction
3) Hold meetings to discuss project business, and exclude the 2nd class team members. If they ask to attend, tell them the meetings are to discuss topics they don’t need to know about… or say “This is meeting is only for 1st class team members.”?
4) Swap in new 2nd class staff frequently (2nd class team member are fungible, afterall, unlike more important 1st class team members). This is a double-header strategy – it slows down progress, too!
8) Blame the 2nd class when the so-called team fails to work together effectively…“They just don’t understand how to work as part of a team.”?
For all 8 helpful hints, visit A clear strategy to stifle teamwork.
As illustrated by this article, teams are about quality interpersonal relationships. If the office culture doesn’t support building collaborative relationships – failure is imminent. For the project, the team, and the organization.
Comments are closed.