the 'not my job' / 'tossing over the wall' political positioning. basically a team not being a team but a group of individuals working to their own benefit instead of the focusing on the project's goals. when people are separated physically (different offices/locations) each co-located grouping sees themselves as special and all others as incompetent. the father the group is apart the harder the PM has to work on personalizing each person and ensuring effective communication is taking place. regular get togethers, video or on-going live chat, focus on team accomplishments instead of individual, etc. will help. Know where the breakdowns are, visualize what they should be and works towards those goals and always search out accomplishments that can be rewarded that move the team toward those goals

PM should create an environment where in all the team members feel the ownership of the project. Team need to be motivated from time to time by celebrating even on small successes in the project. There should be a get together on a regular basis so that everyone can share their grivences and get them sorted before they become problems or hindrance to the project eg. team going for weekly lunch.

In a software development context, PM's need to keep their own political agenda out of the technical decision-making.

PM's often play the "management trump card" where they intervene to make a technical pronouncement.

Any time a PM begins a sentence with "it seems to me that it would be simpler if..." and dictates a technical solution, they're playing a political game with the developers.

It's very difficult to make objective technical decisions. So difficult that the good PM's rely on an architect who has the final word on technical decisions. A good PM will challenge the architect, but the point is to avoid endless wrangling among team members. The PM is (often) unqualified to make a final technical determination.