Project managers are often left wondering whether ambiguity should be lessened, accepted, or both. is acceptance of ambiguity necessary to project success? Saving Changes...
I think it depends on the outcome / the product of the project as well as the stage/phase of the project. Certain outcomes can and should accept ambiguity (e.g. cutting edge technology products being design to fit emerging market) whereas certain outcomes cannot accept ambiguity (e.g. life saving medical equipment) Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
First of all, ambiguity about what? But in general, if you accpet ambiguity, then you wil fail. I really surprised if some project manager in this world accept ambiguity, mainly in project requirements. But, I could agree, if and only if you translate ambiguity into risks and those risk are recorded and visualized into each project item they impact. Saving Changes...
Bala S DuvvuriProject Manager| ShellBangalore, Karnataka, India
I agree with Sergio.
We will have assumptions in any project but they should be recorded and carefully tracked as risks instead of just accepting them. Saving Changes...
Thank you Sergio. Allow me to put clarity to my question earlier. lets take for example we are dealing with a project concerned with improving health services e.g. Male circumcision in a selected community. Due to funding agency restrictions vis a vis Implementation regulations the project has a high ambiguity in the service delivery component; e.g. other infections like cholera or dysentery disease breaks out during implementation of the male circumcision. Saving Changes...
