Search This Blog

Showing posts with label Withdrawing. Show all posts
Showing posts with label Withdrawing. Show all posts

24 March 2013

Project Management and Open Communications

Project Managers need to guard against setting up an environment where bad news never reaches them. They need to praise and encourage those who communicate risks before they become issues, issues before they become problems, and problems before they become project failures.

Some managers remind me of the Clinton trial in the Senate, following his impeachment in the House.

The Senate set up a rule requiring Ken Starr to keep all the records and evidence in another building. Bringing it to their offices without an invitation would have violated protocol.

Then the majority of senators refused to go view the evidence. A few who did view it said they came away weeping, and the rest (having refused to view the evidence) said that they lacked evidence sufficient to convict.

Does your comfort zone tempt you to maintain willful ignorance? Does your character allow reliance on plausible deniability? The PM has accountability for project success, which any lack of awareness may bring about; but that accountability extends to achieving success ethically.
 
I wonder:  Do PMs ever include ethical lapses as project risks?

08 March 2013

Forcing versus Withdrawal for Conflict Resolution

Is it true that the Forcing conflict resolution technique is worse than Withdrawal?

Withdrawal can have negative or positive consequences. On the negative side, left to themselves, people may escalate the conflict to the point that the PM loses control. While time passes, risks may evolve into issues, or issues into problems.

On the other hand, people may calm down and consider each others' needs and opinions. In time, they may voluntarily find ways to meet all needs, or at least reach a compromise. They might also find a new solution. So the problem may solve itself. It's important for the PM to respect the team's ability to solve problems and allow them "space" to do so.

Forcing always has losers and creates the risk of driving a less-than-optimal solution. People don't disagree about issues unless somebody sees an aspect that the others do not see. Odds are, if you force a solution, you've missed an opportunity to find a better solution.

Forcing also implies showing disrespect for the "losers," so it demotivates them. Their decrease in performace can becomes a drag to the team. The negative feelings and the drag, in turn, affects the whole team's performance.

You may not have time to find better solutions. Although forcing ranks as the worst technique, circumstances may force you to use it. If you force a solution, you need to follow up with the "losers" to identify the negative consequences. This shows respect for their needs and their perceptions. It also allows you to find ways to mitigate any shortcomings in the forced solution.