Project Management

Project Risk Aversion or MItigation?

From the Strategic Project Management Blog
by
As an "accidental" project manager, it's very satisfying to contribute to the project management community online with anecdotes and stories I've picked up from my own experience. I hope you enjoy our daily conversation.

About this Blog

RSS

Recent Posts

Tell Me You're Going to Get This Done

Quiting Isn't Easy if You Never Do It

Getting in the Way of Peak Performance

The Agony of Defeat?

Nobody Likes Being the Heavy

Categories

decision-making, empowering team members, project leadership, project management, project management fundamentals, project success, project teams, struggling projects, work management

Date

linkedin twitter facebook Request to reuse this  


I think most of us agree that projects are inherently risky endeavors. We don't normally talk about them that way but let's face it, if they weren't  risky we would treat them like business as usual. Projects are usually associated with something new, something we haven't done before or some kind of change—making them risky.

Flying home from San Francisco on Friday night I finished a new book I'd picked up a couple of weeks ago. First published in 1900, Sailing Alone Around the World Alone by Joshua Slocum may not have the most captivating title, but it describes in detail Slocum's solo circumnavigation around the globe in a derelict 36 foot sloop, Spray, he rebuild himself. He may not have been the first to do it, but he was the first to do it alone.

Setting sail from Boston in April of 1895, at the age of 51, Slocum set out on what many thought was a "fool's errand." There were many who didn't think he would make it back alive. He recognized the risks associated with such an endeavor, but he had a couple of things going for him that the average guy in a 36 fool sailboat might not. As it turned out, his skills didn't eliminate the risks of his journey, but they helped him mitigate what might have otherwise been disaster. Do you and the members of your project team share some of these skills/behaviors?

  1. Preparation and Experience: This wasn't Slocum's first experience on the high seas. He'd been a sea captain on a number of ships over the course of his career, running away from home at a young age to begin a life at sea. He'd even been shipwrecked and forced to build his own boat to return home. He was no stranger to the sea and the challenges associated with traveling both the Atlantic and Pacific Oceans. Challenging projects require preparation and some experience to ensure success.
  2. Flexibility and the Ability to Adapt to Difficult Circumstances: Chased by pirates, pursued by hostile natives, illness, rough seas and horrible weather sometimes made Slocum's circumnavigation a challenge. Nevertheless, the ability to adjust expectations and adapt to challenging situations made it possible for Slocum to keep going when others might have abandoned hope and given up. Sometimes "stuff" happens and project leaders need to adjust their plans to accommodate. Being flexible is a critical part of achieving project success.
  3. A Willingness to Accept Help From Others: It didn't seem to matter where he stopped. Alone on the sea, people were always willing to help him make repairs to the Spray and offer provisions to help him along the way. As news of his adventure spread around the world, more and more people became aware of what he was doing and were willing to help. However, even strangers who knew nothing of what he was about were amazed that he was sailing alone and offered help along the way. Are you and your team willing to look outside the team for help when needed?

Risk aversion would have kept Slocum safe at home, while a willingness to accept the potential for risk and devise a way to mitigate expected problems made Joshua Slocum a pioneer; and allowed him to successfully do what no man had done before.

Although we might not ever face hostile natives, pirates or the depths of the sea, we need the same skills and behaviors that helped Slocum along his journey.

If you'd like to read more about dealing with risks, you might find these recent posts interesting: Sometimes the Smart Plan is to Regroup, Rethink and Retreat or Risk Management: Don't Become a Casualty.


Posted on: May 21, 2012 10:11 AM | Permalink

Comments (1)

Please login or join to subscribe to this item
avatar
David Hillson The Risk Doctor| The Risk Doctor Partnership Petersfield, Hampshire, United Kingdom
Hi Ty. You say "I think most of us agree that projects are inherently risky endeavors. We don't normally talk about them that way but let's face it, if they weren't risky we would treat them like business as usual. Projects are usually associated with something new, something we haven't done before or some kind of change—making them risky."

I agree. All projects share a range of features which make them inherently risky including:

* Uniqueness. Every project involves at least some elements that have not been done before, and naturally there is uncertainty associated with these elements.

* Complexity. Projects are complex in a variety of ways, and are more than a simple list of tasks to be performed. There are various kinds of complexity in projects, including technical, commercial, interfaces or relational, each of which brings risk into the project.

* Assumptions and constraints. Project scoping involves making a range of guesses about the future, which usually include both assumptions (things we think will or will not happen) and constraints (things we are told to do or not do). Assumptions and constraints may turn out to be wrong, and it is also likely that some will remain hidden or undisclosed, so they are a source of uncertainty in most projects.

* People. All projects are performed by people, including project team members and management, clients and customers, suppliers and subcontractors. All of these individuals and groups are unpredictable to some extent, and introduce uncertainty into the projects on which they work.

* Stakeholders. These are a particular group of people who impose requirements, expectations and objectives on the project. Stakeholder requirements can be varying, overlapping and sometimes conflicting, leading to risks in project execution and acceptance.

* Change. Every project is a change agent, moving from the known present into an unknown future, with all the uncertainty associated with such movement.

These risky characteristics are built into the nature of all projects and cannot be removed without changing the project. For example, a “project” which was not unique, had no constraints, involved no people and did not introduce change would in fact not be a project at all. Trying to remove the risky elements from a project would turn it into something else, but it would not be a project.


Please Login/Register to leave a comment.

ADVERTISEMENTS

"Technology is a gift of God. After the gift of life it is perhaps the greatest of God's gifts. It is the mother of civilizations, of arts and of sciences."

- Freeman Dyson

ADVERTISEMENT

Sponsors