Why Is Operation Anaconda An Ill-Structured Problem

Operation Anaconda an Ill Structured Problem
An ill structured problem is a situation or dilemma that does not have a clear concise objective or solution, or a clear process to solve it. Operation “Anaconda”, which took place in March 2, 2002 would prove to be one of those problems. The three major reason reasons why Operation Anaconda fit this definition so well is due to failures in several areas. The first area of failure was the Command element, even though there were many joint force commands in the area. The area of conception would be the next area of failure, information is critical. Lastly the area of execution would be the final area of failure, there should never be guess work involved. The US found itself learning many brutal lessons regarding ill structured problems during Operation Anaconda.
Command
According to Wikiversity.org. (2018) ill-structured problems(ISPs) have no initial clear or spelled out goals, set of
Considering all of the other mistakes that were being made, it is a certainty the historic value of the area was down played greatly. Identified by Fleri, al et (2003) the Shahi Kot valley was one of the places that the Afghanis were able to hold off the Soviets in 1980. When dealing with a people of faith, knowing that at one time they were able to hold off such a formidable opponent would motivate them to fight harder. As stated by Military (2010) the enemy had learned well from previous engagements, and proved adept at exploiting the rocky and mountainous terrain. In addition Military (2010) stated, the Central Intelligence Agency (CIA) had picked up intelligence that not only might enemy forces be higher in the mountains instead of in targeted villages in the valley, but also might be three times as numerous as the attacking forces suspected. Unfortunately, due to organizational stovepipes, that information never got to the 10th Mountain