To execute their projects, project champions must secure resources from their organizations. Whether proposing new ideas, or seeking additional resources to continue work on existing efforts, they're in the role of "sellers." They must seek approval for resources from decision makers — "buyers" in this situation. Risk creep happens when the decisions of buyers and sellers introduce unrecognized risk into the projects they pursue together. Here are three sources of risk creep. For more examples, see Part I.
- Organizational blind spots
- By applying to new efforts the patterns we used for past efforts, we often leave unaddressed whatever risks the past efforts didn't encounter. Most organizations have risk blind spots. The risks that are overlooked or underestimated tend to be correlated across similar efforts, because of knowledge and experience sharing, and because management tends to hire and promote people of similar strengths and abilities. In some cases, people with unique experiences or unusual knowledge might encounter resistance upon offering those experiences or knowledge, or upon incorporating their insights into plans and proposals. Thus, organizations not only have blind spots, but also harbor mechanisms that tend to maintain those blind spots.
- Sellers exploit the biases of buyers
- Intentionally By applying to new efforts the
patterns we used for past efforts,
we often leave unaddressed whatever
risks the past efforts didn't encounteror inadvertently, buyers disclose their personal preferences to sellers, who then use that information in the selling process, to make their proposals more appealing to buyers. In some cases, this tailoring requires biased assessments of risks of the proposed project. Risk then creeps into the project, even when neither buyer nor seller is aware of the bias. These biases affect sellers not only in how they position their proposals, but also in their choices of what to propose. Some perfectly sound ideas are never even proposed, because the sellers mistakenly believe the buyers wouldn't be interested. - Both buyers and sellers exploit urgency
- When we regard pursuing an idea as urgent, we're more likely to accept risks, more likely to underestimate risks, and more likely to overlook risks. Both buyers and sellers contribute. Some buyers have preconceived ideas about what's important. Whether or not they're correct, they communicate their preconceptions to sellers to encourage them to propose the kinds of ideas they favor. At times buyers add a dash of urgency to these communications to attract the most capable sellers. This biases the portfolio of proposals they receive by replacing importance with urgency. As an element of their "sales pitch," some sellers assert, "…we must do this now or miss the opportunity." This replaces the question of the importance of the proposed objective, with a question of timing. When this happens, both buyer and seller may be mistaking urgency for importance. Whether buyers or sellers exploit urgency, risk creeps in.
Risk is a fact of life. Risk creep need not be. Use open conversations to mitigate risk creep risk. First issue in this series Top Next Issue
Are your projects always (or almost always) late and over budget? Are your project teams plagued by turnover, burnout, and high defect rates? Turn your culture around. Read 52 Tips for Leaders of Project-Oriented Organizations, filled with tips and techniques for organizational leaders. Order Now!
Your comments are welcome
Would you like to see your comments posted here? rbrenjTnUayrCbSnnEcYfner@ChacdcYpBKAaMJgMalFXoCanyon.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.
This article in its entirety was written by a human being. No machine intelligence was involved in any way.
Point Lookout is a free weekly email newsletter. Browse the archive of past issues. Subscribe for free.
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.
Related articles
More articles on Project Management:
- Status Risk and Risk Status
- One often-neglected project risk is the risk of inaccurately reported status. That shouldn't be surprising,
because we often fail to report the status of the project's risks, as well. What can we do to better
manage status risk and risk status?
- 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.
- The Retrospective Funding Problem
- If your organization regularly conducts project retrospectives, you're among the very fortunate. Many
organizations don't. But even among those that do, retrospectives are often underfunded, conducted by
amateurs, or too short. Often, key people "couldn't make it." We can do better than this.
What's stopping us?
- Why Scope Expands: II
- The scope of an effort underway tends to expand over time. Why do scopes not contract just as often?
One cause might be cognitive biases that make us more receptive to expansion than contraction.
- 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.
See also Project Management and Project Management for more related articles.
Forthcoming issues of Point Lookout
- Coming January 22: Storming: Obstacle or Pathway?
- The Storming stage of Tuckman's model of small group development is widely misunderstood. Fighting the storms, denying they exist, or bypassing them doesn't work. Letting them blow themselves out in a somewhat-controlled manner is the path to Norming and Performing. Available here and by RSS on January 22.
- And on January 29: A Framework for Safe Storming
- The Storming stage of Tuckman's development sequence for small groups is when the group explores its frustrations and degrees of disagreement about both structure and task. Only by understanding these misalignments is reaching alignment possible. Here is a framework for this exploration. Available here and by RSS on January 29.
Coaching services
I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenjTnUayrCbSnnEcYfner@ChacdcYpBKAaMJgMalFXoCanyon.com or (650) 787-6475, 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, )
- Get 2003-4 in Why Dogs Wag (PDF, )
- Get 2005-6 in Loopy Things We Do (PDF, )
- Get 2007-8 in Things We Believe That Maybe Aren't So True (PDF, )
- Get 2009-10 in The Questions Not Asked (PDF, )
- Get all of the first twelve years (2001-2012) in The Collected Issues of Point Lookout (PDF, )
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-1000 words in your inbox in one hour. License any article from this Web site. More info
Follow Rick
Recommend this issue to a friend
Send an email message to a friend
rbrenjTnUayrCbSnnEcYfner@ChacdcYpBKAaMJgMalFXoCanyon.comSend a message to Rick
A Tip A Day feed
Point Lookout weekly feed