Risk plans are rarely perfect. For complex projects, unanticipated risk will almost certainly materialize. We can deal with this risk — I'll call it risk management risk — if we adopt some simple practices. Let's begin with some examples of organizational and political risks.
- Organizational blind spots
- Organizational risk management asset bases usually consist of previously developed risk plans and risk plan elements, documented risk plan development procedures, and personal experiences.
- Although referring to these assets might uncover risks that any particular risk manager might not otherwise consider, relying on the asset base probably won't uncover risks not included there. Since continuous organizational change almost certainly exposes the organization to risks never before seen, these asset bases have blind spots.
- To limit these blind spots, analyze the results of retrospectives to determine what risks were unanticipated. They provide clues to the location of the organization's blind spots.
- Organizational political correctness
- In general discourse, political correctness requires that we shape our statements and behavior — if not our opinions — to conform to a generally accepted ideological standard. Organizational political correctness provides an analogous constraint relative to the ideology and views of the organization.
- Organizational Organizational political correctness
can limit the ability of risk managers
to address significant riskspolitical correctness can limit the ability of risk managers to address significant risks, when even discussing such risks calls into question organizational beliefs, or the beliefs of those who have internal political power.
- If a common theme appears among unanticipated risks, if those risks are evident to many, and if the same risks materialize across many projects, organizational political correctness could be a cause. Organizational culture change is required to address this risk.
- Political risk
- The organizational value of any project is determined, in part, by the political clout of its advocates. How an organization values a project can present risks to it through resource allocation, schedule, and budget.
- Although these risks are widely understood, talking about them openly and planning for them in writing is often difficult, for reasons far beyond organizational political correctness. For the politically weak project, committing to writing and review any plan to deal with political risks simply provides a roadmap to rival projects if they are politically stronger. Such a risk plan is often effectively countered before it can be implemented. In some cases, it might even be forbidden. This effect is especially pronounced if a state of toxic conflict persists between the departments, leaders, or champions of the two projects.
- Two factors suggest the presence of political risk. First is the absence of any explicit mention of political risk from the risk plans of politically weak projects. A second indicator can be changes in the execution plan of politically stronger projects, especially following publication of the risk plan of a politically weaker project.
Is every other day a tense, anxious, angry misery as you watch people around you, who couldn't even think their way through a game of Jacks, win at workplace politics and steal the credit and glory for just about everyone's best work including yours? Read 303 Secrets of Workplace Politics, filled with tips and techniques for succeeding in workplace politics. More info
Your comments are welcomeWould you like to see your comments posted here? rbrenoDnGWXZbeCcsWqwPner@ChacSArZiFyrHcERaDJeoCanyon.comSend me your comments by email, or by Web form.
About Point Lookout
Thank you for reading this article. I hope you enjoyed it and found it useful, and that you'll consider recommending it to a friend.
Support Point Lookout by joining the Friends of Point Lookout, as an individual or as an organization.
Do you face a complex interpersonal situation? Send it in, anonymously if you like, and I'll give you my two cents.
More articles on Project Management:
- Nepotism, Patronage, Vendettas, and Workplace Espionage
- Normally, you terminate or reassign team members who actually inhibit progress. Here are some
helpful insights and tactics to use when termination or reassignment is impossible.
- Managing Risk Revision
- Prudent risk management begins by accepting the possibility that unpleasant events might actually happen.
But when organizations try to achieve goals that are a bit out of reach, they're often tempted to stretch
resources by revising or denying risks. Here's a tactic for managing risk revision.
- Long-Loop Conversations: Clearing the Fog
- In virtual or global teams, conversations can be long, painful affairs. Settling issues and clearing
misunderstandings can take weeks instead of days, or days instead of hours. Here are some techniques
that ease the way to mutual agreement and understanding.
- Seven Ways to Get Nowhere
- Ever have the feeling that you're getting nowhere? You have the sense of movement, but you're making
no real progress towards the goal. How does this happen? What can you do about it?
- Ten Approaches to Managing Project Risks: I
- Risk management usually entails coping with losses if they do occur. Here's Part I of a concise summary
of the options for managing risk.
Forthcoming issues of Point Lookout
- Coming May 31: Unresponsive Suppliers: III
- When suppliers have a customer orientation, we can usually depend on them. But government suppliers are a special case. Available here and by RSS on May 31.
- And on June 7: The Knowledge One-Upmanship Game
- The Knowledge One-Upmanship Game is a pattern of group behavior in the form of a contest to determine which player knows the most arcane fact. It can seem like innocent fun, but it can disrupt a team's ability to collaborate. Available here and by RSS on June 7.
I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenSRLKWIUJTCfKWXxmner@ChacqIAZvKtTFnNGpsxGoCanyon.com or (617) 491-6289, or toll-free in the continental US at (866) 378-5470.
Get the ebook!
Past issues of Point Lookout are available in six ebooks:
- Get 2001-2 in Geese Don't Land on Twigs (PDF, USD 11.95)
- Get 2003-4 in Why Dogs Wag (PDF, USD 11.95)
- Get 2005-6 in Loopy Things We Do (PDF, USD 11.95)
- Get 2007-8 in Things We Believe That Maybe Aren't So True (PDF, USD 11.95)
- Get 2009-10 in The Questions Not Asked (PDF, USD 11.95)
- Get all of the first twelve years (2001-2012) in The Collected Issues of Point Lookout (PDF, USD 28.99)
Are you a writer, editor or publisher on deadline? Are you looking for an article that will get people talking and get compliments flying your way? You can have 500 words in your inbox in one hour. License any article from this Web site. More info
- Creating High Performance Virtual Teams
- Many people experience virtual teams as awkward, slow, and sometimes
frustrating. Even when most team members hail from the same nation or culture, and even when they all
speak the same language, geographic dispersion or the presence of employees from multiple enterprises
is often enough to exclude all possibility of high performance. The problem is that we lead, manage,
and support virtual teams in ways that are too much like the way we lead, manage, and support co-located
teams. In this program, Rick Brenner shows you how to change your approach to leading, managing, and
supporting virtual teams to achieve high performance using Simons' Four Spans model of high performance.
Read more about this program. Here's an upcoming date
for this program:
- Baci Grill, 134 Berlin
Road, Berlin, CT 06416: September 19,
Monthly Meeting, Southern New England Chapter of the Project Management Institute. Register now.
- Baci Grill, 134 Berlin Road, Berlin, CT 06416: September 19, Monthly Meeting, Southern New England Chapter of the Project Management Institute. Register now.
- The Race to the South Pole: Ten Lessons for Project Managers
- On 14 December 1911, four men led by Roald
Amundsen reached the South Pole. Thirty-five days later, Robert F. Scott and four others followed. Amundsen
had won the race to the pole. Amundsen's party returned to base on 26 January 1912. Scott's party perished.
As historical drama, why this happened is interesting enough, but to organizational leaders, business
analysts, project sponsors, and project managers, the story is fascinating. Lessons abound. Read
more about this program. Here's an upcoming date for this program:
- CTCPA, 716 Brook Street,
Rocky Hill, CT 06067: September 20,
Full-day Workshop, Southern New England Chapter of the Project Management Institute. Register now.
- CTCPA, 716 Brook Street, Rocky Hill, CT 06067: September 20, Full-day Workshop, Southern New England Chapter of the Project Management Institute. Register now.