What should you do when presented with a highly ambiguous project?

My answer is option (2) Progress in small and short iterations with several phases of trial and error.

 

This will be the best way to avoid ambiguity problems.

 

From my point of view, progress in small and short iterations with several phases of trial and error and create a road map instead of a plan are the best ways to avoid ambiguity problems on a project.

2 and3 points should be carried out 

From my experience working in a most high risk environment with lots of variables and lots of ambiguity. I can say: Depending on where is the ambiguity? Is it in the requirements, deliverables or in the implementation environment? In general:1- You need to agree with the project sponsor that it is an ambiguous project; this is to facilitate the reasons of building additional backup plans.2- So many interviews should be done with all stake holders.3- The project plan should be built based on the information available at that time.4- You should have some tolerance in your Risk plan.5- Contingency plans should be put into place, based on "what if" scenarios and should be approved and agreed when to be initiated.6- The actual situation should be reviewed instantly for any new findings and to be evaluated to see if there is any impact on the plan, based on this amendment to the plan can be done.7- Trial and error method is your last option in critical projects and should be to the minimum.

Answer2.

However having the strength and diligence to request clarification of the vision or higher plan and result would be my approach.

For the projects that contain high ambiguity, we should manage & learn to deal with uncertainty, listen to yourself and be confident in your abilities. We should realize there is not a defined plan that you need to follow, be flexible and most importantly, learn to deal with our stress.

Option no2 is correct: Progress in small and short iterations with several phases of trial and error 

 

Reason: 

When you adopt the method of trial and error, you should get out of the uncertainties as fast as you can. The ideal duration is60 days. It is important to roughly test the ideas that you have in your mind to avoid the uncertainties as fast as you can.  Rapid testing is always recommended, so that you can get the best idea from trail and error method. 

 The best way to  proceed with a highly ambiguous project is creating a road map and progressing in small and short iterations.

Tips for dealing with ambiguous projects

Here are some starter tips for running projects that contain high ambiguity.

1. Manage uncertainty – not time-lines.  Start by recognizing that these kind of projects are different than the norm.  It’s much more about mapping the uncertainties and learning about them than it is about managing time-lines and milestones.  When you don’t know what you don’t know, well articulated and detailed project plans are not going to help (too many critical assumptions factored in).  Creating a reasonable starting point of what you know and don’t know, and then running low cost experiments to learn about the uncertainties (what you don’t know) is how to get started.
2. Embrace diversity.  Learning accelerates when people with diverse opinions and experiences are brought to play.  In the example above, the company could and should include existing consumers as part of their team.  They will provide insights about what they, as consumers, would want to experience.  Diversity keeps you from spending too much time going down false trails.
3. Go fast and slow at the same time.  When running experiments to uncover the answers to critical uncertainties get out there as fast as you can.  A good rule of thumb is60 days.  Test roughed-out ideas with real people very fast.  Counteract that with the expectation that overall, the project will likely run slow.  It can take many months and iterations before the real answers surface.  Hence the need to test rapidly.
4. Review learning.  Finally, keep the momentum high by running regular (weekly) learning reviews. Sharing the learning on a regular basis keeps team members focused and makes each individual’s contribution that much more robust.

Questions business owners and executive team leaders can ask

Here are some question you can ask of yourself and your team.

1. How comfortable are we in discussing ideas that fall outside the norm of our experience?  How quick are we to judge?  Is our judgement focused too heavily on the risks?
2. How well do we as a  team or company deal with ambiguous ideas?  Do we devote sufficient time in exploring the uncertainties that arise from it?
3. What is our capacity to develop and execute low cost experiments?  Do we have procedures in place?
4. When dealing with uncertainty how well do we embrace diversity?
5. How well do our habits in selecting team help us in creating a wide range of potential solutions?
6. How well do we balance between aggressive targets for completion with sufficient allowance for learning and prototyping?
7. How well do we create and maintain momentum?   What is our capacity for tracking and sustaining project implementation?
8. How well do our reviews focus on learning?  Are we too focused on time-lines at the expense of managing risks through learning?

I go with answer of Mr .Ayoub Tartir >>>>>>>>>>>> Thanks

I will go for option number2 and option number4