A review copy of this case is available free of charge to educators and trainers. Please
create an account
or sign in
to gain access to this material.
Permission to Reprint
Each purchase of this product entitles the buyer to one digital file and use.
If you intend to distribute, teach, or share this item, you must purchase
permission for each individual who will be given access.
Learn more about
purchasing permission to reprint.
Abstract: Accurate information about troop positions and other conditions are crucial for battlefield commanders. But when the US Army moves to develop a software program which will make such information more easily and widely available, complications develop. How should designers decide what kind of information to include? This case tells the story of the development of the Maneuver Control System, Version 2 (MCS2) and conflicts which arise between various potential users of the system--specifically, commanding officers and staff officers. Implicitly, the case allows for discussion of the organizational politics of new information technologies. In the development of MCS2, designers must deal with the potentially conflicting demands for a simple program and for one which includes work from a wide variety of the Army's organizations. The case highlights the decision-making process as it dealt with one specific feature and the demand that it be added to the MCS2 system.