The Objective Force Unit of Action operates in a significantly different command environment. It is called "execution-centric command" and it relies on information superiority. The commander uses superior situational understanding and the "quality of firsts" to see first, understand first, and act first upon the enemy. The commander uses a "tactical infosphere" or networked information management system to gain and maintain information superiority. He uses sensor systems within his battlespace and is networked to joint and space-based intelligence assets. Additionally, the network allows the commander to leverage information from any information system or subject matter expert connected to the network. Within the tactical infosphere, he uses collaborative planning and automated decision aids. Lastly, the commander uses the tactical infosphere and experience to intuitively make decisions based on pattern recognition. In current doctrine, the battle staff completes the tasks of information management, staff decision-making, and providing the commander's visualization. If the tactical infosphere provides the commander his visualization, manages information, and can assist in his decision-making, does the Unit of Action need a battle staff? This is the research question answered in this monograph. The command environment is comprised of organizations, procedures, and technical means. This monograph uses the changes in the Objective Force Command environment and the battle staff tasks (information management, staff decision-making, and providing visualization) to answer the research question. It is answered by deciding if these three tasks are necessary in the Objective Force execution-centric command environment. The Legacy Force Commander and battle staff use the analytical MDMP to create detailed plans and matrix's. This is an attempt to eliminate uncertainty. The Legacy Force battle staff uses radio networks, in three command posts, and a hierarchical system of info
