But what is intelligent disobedience? To explain this quality, the author used an example of the program that certifies guide dogs for blind people. During the certification process, the trainer must determine whether or not the subject dog has been able to demonstrate the ability to disregard commands issued by its master under particular circumstances. An example is the guide dog refusing to cross the street when a car is coming.
In the context of project management, there may be times when obstacles are formidable, which prompts the project manager to pursue the following tasks as stated by the author:
• Proposing unpopular option/opinion
• Standing up to senior management
• Crafting compelling arguments/justifications to garner business support
• "Bending" rules and processes when appropriate
• Applying non-traditional techniques to create "unexpected" impressions as a means to change stakeholder perception
• Using communication and influencing skills to protect the organization from itself
When might a project manager break from the norm for the good of the project? The author suggests the following situations:
• Dealing with unresponsive sponsors or key customers
• Managing culture clashes that inhibit project progress
• Needing to shake-up lagging teams
• Overcoming resistance to changing processes
• Challenging time versus quality decisions
• Considering intuitive versus fact-based decision making
What is interesting is that the author points out many times we avoid engaging in difficult conversation or "sugar coat" the bad news to "preserve the current relationship with stakeholders." We don't realize that "the conversation IS the relationship." Possible benefits from the risk of using intelligent disobedience include, engaged project teams, loyal team members and a reputation for "telling it like it is."
My question to my fellow project management professionals is, are you a risk taker?
Editor's Note: Members can learn more about intelligent disobedience by reading the Best of Congress feature in April 2006 issue of PM Network.