After reading No Sure Victory: Measuring U.S. Army Effectiveness and Progress in the Vietnam War I could not help but think about the consequences failed data reporting by MACV can serve a historical lesson for re-implementing or adjusting campus data reporting systems.
Key stakeholders on campus should easily state their reasons for data collection and reporting. No Sure Victory benefits campus units by revealing an early, dare I say Big Data approach to unstructured data reporting and delivering actionable data.
Today we immediately understand Google’s Compute Engine or an Amazon Elastic MapReduce cloud for this demand.
Universities can thrive with diverse reporting teams. Working with Institutional Research and striving to improve enrollment and retention efforts are key goals. Yet important roles are filled with student workers. Here unstructured data often fragments over mismanagement. Many ad hoc Microsoft Excel documents are created without data governance and become silo’d from the campus data warehouse. Key stakeholders on any campus including CIOs, IR Directors, Research staff, Program Directors, campus data reporter writers and student workers. Even seasoned campus data report writers are not leveraged to streamline actionable data insights.
No Sure Victory brings to light a tragic failed data reporting implementation by Secretary of Defense Robert McNamara in addressing a war in Vietnam. The was his reputation as one of The Wiz Kids, the World War II Statistical Control unit that analyzed operational and logistical data to manage war.
My interest in revisiting is remembering Chapter 4: Predicting Trends. This touches two important factors today: cloud and procurement.
It seemed like an eternity that analytics are now realized as a critical business strategy for universities. 