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


I learned two lessons from this experience. First was an appreciation of the impor- tance of program leadership teams. Sure, I knew this from the Army, but this time it hit hard with consequences. Te second lesson was to make sure I communicated with my leadership team and insisted on the importance of collaboration. Te systems approach proposed here not only would foster familiarity; it would also provide insight into the ways each team member thinks.


Te Army is the world leader in estab- lishing, educating and employing teams, but we are not taking advantage of that expertise and training knowledge, partic- ularly in experiential learning, by using it to educate the Acquisition Corps.


EXPERIENTIAL LEARNING Today we educate and train PMs, systems engineers, contracting officers and budget specialists separately. Tis approach is logical because each discipline has its own knowledge and educational princi- ples. However, no educational or training environment exists to take these talented specialists and mold them into a func- tioning team. Te emphasis is still on preparing the individuals.


As a seasoned Navy captain once told me during a conversation about the qualifica- tions of a particular officer nominated for a job in our command, “Te Navy assigns officers to a role because they know they will be successful.” No surprise there, nor is the observation unique to the Navy. However, this line of thinking begs the question of whether simply assigning officers or senior civilians to acquisi- tion leadership roles is enough to ensure project success. Training for the sake of training is not in anyone’s interest, but neither is simply assigning competent individuals, putting them together and expecting them to excel as a unit. Tis


118 Army AL&T Magazine Fall 2019


FIGURE 2


BOXED IN


The rework cycle illustrated here is a basic component of system development. Rework is common in a development project, either because a task was done incorrectly or something changed in the larger system that necessitated redoing it. Understanding the dynamics makes it possible to trace the actions and decisions that caused the problem. (Graphic courtesy of the author and USAASC)


is where experiential learning can be so valuable.


Experiential learning is ambiguous and at times uncomfortable. It places us in situations where we must make decisions with significant uncertainty. Experien- tial learning also provides the ability to stop, to think about what you did or said and how you responded—an important part of learning. Tis kind of learning also affords the participants the ability to unlearn skills, decision-making processes and ultimately the way one sees the world


and the way it operates. And the best part is that the decisions made, and their conse- quences, won’t cost time or money.


COLLABORATIVE ANALYSIS No tactical commander would deploy teams without first giving them the oppor- tunity to train together. And while no one would directly compare fighting a brigade or division with managing a complex weapon system development program, there are some similarities. Both require information and coordination, resulting in decisions, while performing effectively as a


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