Project Management

Project Management Central

Please login or join to subscribe to this thread

Topics: Risk Management, Using PMI Standards
Examples of
In PMBOK Guide 7 in Uncertainty Performance Domain there is a section: "2.8.3.2. Reframing". In this section the following approach to deal with complexity is mentioned: "Balancing the type of data used...".
Could anyone explain what it means? I'm not a newbe both in Risk Management, and in Theory of systems, but I don't get it.
Maybe some examples would help.
Sort By:
The reframing section is about looking at things from different views/perspectives to understand a complex situation. Balance is looking at multiple data sources to gain a broader perspective.

Example: You need to purchase a new product for your team. If you only look for the products with the highest reviews, you may not see limitations to some products which don't meet your needs. By looking at both the positive and negative reviews, you may gain a more balanced understanding of user experiences to select the right product for your team, than just looking for the highest satisfaction score.
Aleksei,

let me start that I am not yet convinced about the wisdom in PMBoK ed7, and in particular not about what is said about risks and complexity. PMBok ed6 was much cleared for me in the respect (e.g. saying complexity is in the eye of the beholder/observer), even if it did not mention changing perspectives as a T&T related to complexity.

There is some literature about it, for example this, and maybe the PMBoK team looked at this.
https://dandoerksen.me/reframingleadership/
Google yourself.

Changing perspectives is an important human capability, useful in many respects, also with ambiguity, uncertainty and maybe less with volatility.

I gave you a small example in my first paragraph: look at complexity using the perspectives of PMBoK ed6 and ed7 respectively and you will see different concepts. Which is good since it provides choices and bad as it may create feelings of confusion.

Thomas
While I think this type of things inside the PMBOK has no sense, the intention is trying to pointed out that you have lot of data that that you have to convert into information to take decisions and to take data to convert into information you have to consider all type of data, not forecast or past indicators (like lessons learned for example) only. This is not new. When you start working on a project the key activity to do is to elicit about all related to similar projects/product done in similar organizations and about the environment by making PESTLE analysis or Porter Five Force analysis for example.
Many thanks to all who replied!
Your examples are great.
And dear Thomas, thank you for the link. Really interesting!
I will continue to search for the clearest explanation, since it seems to me that some specific tool or principle from new frameworks is mentioned here.

Please login or join to reply

Content ID:
ADVERTISEMENTS

"Once, during prohibition, I was forced to live for days on nothing but food and water."

- W. C. Fields

ADVERTISEMENT

Sponsors