search.noResults

search.searching

dataCollection.invalidEmail
note.createNoteMessage

search.noResults

search.searching

orderForm.title

orderForm.productCode
orderForm.description
orderForm.quantity
orderForm.itemPrice
orderForm.price
orderForm.totalPrice
orderForm.deliveryDetails.billingAddress
orderForm.deliveryDetails.deliveryAddress
orderForm.noItems
AN EXERCISE TO EXPERIENCE


Te Army Acquisition Workforce spends significant time learning its trade, whether in the classroom or online, training or pursu- ing formal degrees. Firsthand experience from opportunities like Training with Industry notwithstanding, the workforce learns through passive methods, for the most part. It is no exaggeration to say that passive learning is like listening to someone read from PowerPoint slides; it has limited utility in preparing acquisition officers to deal with the challenges of today’s complex weapon system acquisition programs.


Dealing with complexity, whether it means contracts with thousands of pages, congressional staffers’ questions on budget details or the technological detail of our systems, simply cannot be taught in a classroom. In the Army, we tend to teach Soldiers to deal with complexity using the sink-or-swim method known as OJT—on-the-job training. OJT works, but it isn’t the most effective way to learn, is rarely effi- cient and almost always has hidden costs. In a realistic environment, experiential learning is effective and efficient, offer- ing an immediate payoff.


rotation. Such an exercise would be cross-functional, focused on providing Army program managers and staffs—acquisition leadership teams—with the executive, managerial, teaming and technical skills necessary for success in managing complex acquisitions.


Acquisition program management is a series of decisions connected in


something that will one day become a fielded weapon system.


Te Army trains division and corps staffs through the Mission Command Train- ing Program. Tis isn’t a physical center like the National Training Center, although the command posts do deploy to the field. Instead, commanders and staffs do battle in a simulated environment on a virtual battlefield located in a simu- lation center. Shortly after graduating from the U.S. Army School of Advanced Military Studies at Fort Leavenworth, Kansas, I was assigned to the 1st Cavalry Division as a plans officer. 1st Cav was scheduled for a warfighter exercise the year I arrived. As the plans officer, I engaged with the operations staff and commanders and reacted to enemy and friendly fire and maneuver. It was an eye- opening opportunity to experience how a division commander and staff interact, make decisions and win. No plan survives first contact, but experiencing the execution of a plan, even simulated, builds confidence and, above all, learning.


THE BENEFITS OF HANDS-ON LEARNING Experiential learning can make a difference in the education and training of our acquisition warriors. An Army acquisition exer- cise using the Army’s proven “learning by doing” approach would provide an experience similar to a National Training Center


116 Army AL&T Magazine Fall 2019


Tink of this as taking a systems approach to acquisition educa- tion, the same approach the Army has been using for training since World War II. A system in this case is a set of interrelated and inter- dependent events, with inputs that lead to outputs through processes. Te system operates under constraints and rules that are applied by a mech- anism, usually people. A systems approach recognizes the causes and effects, or feedback loops, of our interactions with our environment.


Te three core pieces of this proposed systems approach to acquisition education are acquisition leadership, which represents the system mecha- nism; experiential learning, providing the system process; and a third factor, collaborative analysis, a kind of war- gaming, which provides the inputs and captures the outputs. Te foun- dation of this approach is a simulated


but realistic environment where acquisition leaders can experience and learn from both success and failure before actually manag- ing a weapon system development. (See Figure 1.)


DEVELOPING LEADERS Te complexity of technology and project management forces people to specialize. Te benefit of specialization is that we have dedicated experts in management, systems engineering, contract- ing, finance and other fields. Te downside is that we have fewer people with broader backgrounds who can make sense of the bigger picture. Given the technical and managerial scope of acquisition programs today, no one person, the program manager (PM) included, has all the knowledge and information to make effective decisions on their own.


Te Army embraces teams because it is built on teams—infan- try, armor, artillery, etc.—that fight together, from fire team to corps. So it is with the teams that manage weapon system programs. Teams are central to the successful execution of Army


Page 1  |  Page 2  |  Page 3  |  Page 4  |  Page 5  |  Page 6  |  Page 7  |  Page 8  |  Page 9  |  Page 10  |  Page 11  |  Page 12  |  Page 13  |  Page 14  |  Page 15  |  Page 16  |  Page 17  |  Page 18  |  Page 19  |  Page 20  |  Page 21  |  Page 22  |  Page 23  |  Page 24  |  Page 25  |  Page 26  |  Page 27  |  Page 28  |  Page 29  |  Page 30  |  Page 31  |  Page 32  |  Page 33  |  Page 34  |  Page 35  |  Page 36  |  Page 37  |  Page 38  |  Page 39  |  Page 40  |  Page 41  |  Page 42  |  Page 43  |  Page 44  |  Page 45  |  Page 46  |  Page 47  |  Page 48  |  Page 49  |  Page 50  |  Page 51  |  Page 52  |  Page 53  |  Page 54  |  Page 55  |  Page 56  |  Page 57  |  Page 58  |  Page 59  |  Page 60  |  Page 61  |  Page 62  |  Page 63  |  Page 64  |  Page 65  |  Page 66  |  Page 67  |  Page 68  |  Page 69  |  Page 70  |  Page 71  |  Page 72  |  Page 73  |  Page 74  |  Page 75  |  Page 76  |  Page 77  |  Page 78  |  Page 79  |  Page 80  |  Page 81  |  Page 82  |  Page 83  |  Page 84  |  Page 85  |  Page 86  |  Page 87  |  Page 88  |  Page 89  |  Page 90  |  Page 91  |  Page 92  |  Page 93  |  Page 94  |  Page 95  |  Page 96  |  Page 97  |  Page 98  |  Page 99  |  Page 100  |  Page 101  |  Page 102  |  Page 103  |  Page 104  |  Page 105  |  Page 106  |  Page 107  |  Page 108  |  Page 109  |  Page 110  |  Page 111  |  Page 112  |  Page 113  |  Page 114  |  Page 115  |  Page 116  |  Page 117  |  Page 118  |  Page 119  |  Page 120  |  Page 121  |  Page 122  |  Page 123  |  Page 124  |  Page 125  |  Page 126  |  Page 127  |  Page 128  |  Page 129  |  Page 130  |  Page 131  |  Page 132  |  Page 133  |  Page 134  |  Page 135  |  Page 136  |  Page 137  |  Page 138  |  Page 139  |  Page 140  |  Page 141  |  Page 142  |  Page 143  |  Page 144  |  Page 145  |  Page 146  |  Page 147  |  Page 148  |  Page 149  |  Page 150  |  Page 151  |  Page 152  |  Page 153  |  Page 154  |  Page 155  |  Page 156