Application of Antifragility in Project Management

From apppm
Revision as of 13:50, 21 September 2015 by Lassehoier87 (Talk | contribs)

Jump to: navigation, search

“To see how large things can be fragile, consider the difference between an elephant and a mouse: The former breaks a leg at the slightest fall, while the latter is unharmed by a drop several multiples of its height. This explains why we have so many mice than elephants”

Organizations established on the idea that any volatility is poison to the system, is not in balance with the laws of nature. Such organizations is fragile and will properly suffer from times with high volatility. Exposed to high volatility has the ability to show vulnerability or weakness of an organization. As the immune systems thrives with viruses in order to keep being intact, the antifragility organization thrives with volatility in order to improve and grow. In this sense, nature gives the answer to high volatility in organizations.

The projects of our time are designed for stability and can be defined as highly complex, pursuit of effectivity and interdependency.

In order understand this; imagine how a project would look like in the past century. The projects were less complex, simply because projects had a lower technical level. Things such as the globalization also add to the complexity. While the parts for a building usually was build or assembled nearby in the past, things are usually shipped to the construction site from the other side of the world today. A lot of the processing of high complexity within an organization is divided into the various academic disciplines. This can be a great challenge to the project management and demands a high level of communication from each discipline. In order for the project manager to make the best planning, risk analysis etc., the complexity has to have more focus in the project management. High complexity has the tendency of surprising, because no one “saw it coming”.

Second, the efficiency is a huge driver to failure in projects. In the pursuit of efficiency, fewer and fewer things are controlling more and more.

“The stock exchanges have converted from “open outcry” where wild traders face each other, yelling and screaming as in a souk, then go drink together. Traders were replaced by computers, for very small visible benefits and massively large risks. While errors made by traders are confined and distributed those made by computerized systems go wild”

For the past 2-3 decades, we have continued the pursuit of efficiency, but the risk is neglected. In projects were communication between each discipline is a key word, the high computerization can be a big challenge to handle. Within this computerization lies a high risk to the project schedule. This argues for more understanding of the computer systems in order to reduce the complexity. The term “Black Swan” defines a rare and unpredictable event, highly difficult to prepare for. “Black Swan” is a typical phenomenon in a fragile system. What we should do, is build a system that is not fragile to these events.

Example.jpg


Content list

  • Benefits of implementing antifragility in project management
    • Instead of seeking to eliminate any kind of stress or volatility in the project management, the idea is to have an organization that seeks to grow and prosper from volatility. “Vaccines introduce a little of what is harmful to build resistance to disease” (Taleb, N.N. Antifragility: How to Live in a World We Don’t Understand, The Guardian)
  • Simulate failure scenarios in project management
    • Typically, the project has a clear definition of success and failure from the early start. The possibility of failure is great and can have a substantial impact on the organization. In order to reduce the impact of a failure - simulating possible failure scenarios stand as a strong tool.
  • “Upside risk” and “downside risk”
    • Taking risk has two outcomes – either you fail or succeed. A successful project manager is rewarded if the project succeed beyond expected, but if it fails the project manager must have something at stake.
Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox