Comments on: Embrace Uncertainty…Why Would I Do That? http://www.reformingprojectmanagement.com/2004/02/15/323/ The magazine for the project age Sun, 07 Sep 2008 23:28:17 +0000 http://wordpress.org/?v=2.0.5 by: Paulo Napolitano http://www.reformingprojectmanagement.com/2004/02/15/323/#comment-188 Wed, 31 Dec 1969 16:00:00 +0000 http://www.reformingprojectmanagement.com/2004/02/15/323/#comment-188 I was looking at the dictionary the meaning of embrace and uncertainty. According to Longman’s dictionary I found: Embrace: 1. to put your arms around someone and hold them in a friendly or loving way; 2. to eagerly accept a new idea, opinion, religion etc; 3. to include something as a part of a subject, discussion etc. Uncertainty: 1. when you feel doubt about what will happen; 2. a situation which you are not sure about because you don’t know what will happen Embrace uncertainty under my perception is in a sequence 3 and 1 or: “To include something as a part of the subject when you feel doubt about what will happen.” In projects we need always to question ourselves about the directions we are taking and if we are speaking the same language. More we need to share our point of view among the team members to put under the lights the real issues. Most of the time uncertainty becomes from our inability to perceive what is going on around us and measurements cannot helps us to do that if we are not able to perceive the environment in which these measurements occurred. Even being measures they have their subjective meaning according to the different moods and backgrounds of the team members. Hal wrote on his weblog: “Someone wrote me last week wondering if embracing uncertainty was an all-or-nothing position.” I would like to write something that Bart Kozko , in his book Fuzzy Thinking, wrote based on Bertrand Russell thoughts: PARADOX AT ENDPOINTS, RESOLUTION AT MIDPOINTS “Embracing uncertainty was an all-or-nothing position.” They both assert and deny themselves and my opinion is that we must be aware of uncertainty all the time we are in process and the blindness of uncertainty will increase breakdowns. I was looking at the dictionary the meaning of embrace and uncertainty.
According to Longman’s dictionary I found:
Embrace:
1. to put your arms around someone and hold them in a friendly or loving way;
2. to eagerly accept a new idea, opinion, religion etc;
3. to include something as a part of a subject, discussion etc.

Uncertainty:
1. when you feel doubt about what will happen;
2. a situation which you are not sure about because you don’t know what will happen

Embrace uncertainty under my perception is in a sequence 3 and 1 or:

“To include something as a part of the subject when you feel doubt about what will happen.”

In projects we need always to question ourselves about the directions we are taking and if we are speaking the same language. More we need to share our point of view among the team members to put under the lights the real issues.
Most of the time uncertainty becomes from our inability to perceive what is going on around us and measurements cannot helps us to do that if we are not able to perceive the environment in which these measurements occurred.
Even being measures they have their subjective meaning according to the different moods and backgrounds of the team members.

Hal wrote on his weblog:
“Someone wrote me last week wondering if embracing uncertainty was an all-or-nothing position.”

I would like to write something that Bart Kozko , in his book Fuzzy Thinking, wrote based on Bertrand Russell thoughts:

PARADOX AT ENDPOINTS, RESOLUTION AT MIDPOINTS
“Embracing uncertainty was an all-or-nothing position.”

They both assert and deny themselves and my opinion is that we must be aware of uncertainty all the time we are in process and the blindness of uncertainty will increase breakdowns.

]]>