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
“We talked about the aspects of acquisition: Do you use multiple capability development documents? Where in the timeline did you have pitfalls? What were your biggest cost drivers and delays in your schedule? How did it make your product more effective? And how do you continue to do it in the future? Sharing those kind of lessons was very helpful. We now have developed our schedule to avoid those kinds of pitfalls in the future,” Price said.


Price’s experience is just one of many success stories of acqui- sition professionals coming together and finding solutions to challenges encountered on the job by sharing lessons learned on the ALLP. “Te whole idea is for programs going through their milestone reviews to not keep making the same mistakes,” said Guite. “Tey [program managers] should be learning from each other and applying lessons that already have been learned.”


FLAGGING SUPPORT Since its inception in 2012, ALLP showed a steady growth of published lessons learned, with usage peaking in 2014 with 304 lessons submitted. However, usage waned after that, dropping to 155 and 49 for 2015 and 2016, respectively.


Tat decline corresponds to Shyu’s departure as assistant sec- retary of the Army for acquisition, logistics and technology (ASA(ALT)). “I think we lost a champion down in ASA(ALT) headquarters,” Guite said. “Prior to that, they were pushing for people to make sure they were conducting AARs and collect- ing lessons learned and pushing them to us. We were sending figures [to ASA(ALT)] to let them know how many accounts we had and lessons coming, and we had slides put into program status reviews and ACAT II program reviews.”


Guite said that with Shyu’s retirement and the change in opera- tional


tempo at ASA(ALT) headquarters, ALLP apparently


became less of a concern. “Given that they are busy and have a lot of other things to do,” he said, “I think it [ALLP] was low on the priority list.”


REDEFINED VISION Tat is going to change, thanks to a concentrated effort led by Lt. Gen. Michael E. Williamson, principal military deputy to the ASA(ALT) and Army director, acquisition career management.


Williamson has said many times that lessons learned aren’t valu- able unless they’re lessons applied. To capture what worked or didn’t work, pitfalls and success stories, and keep them in one repository to share with the acquisition community is a simple and effective concept. But if they’re not applied, they’re just


words. “We need to share knowledge through a common data- base that is both user-friendly and useful,” Williamson said.


Senior leadership, including Williamson, recently noted an


increase in project managers asking for guidance on challenges that they were facing—and many of those challenges had already been solved by someone else in the community and, in some cases, documented on the ALLP. “It was important to address the situation immediately by identifying the problems and finding a workable solution,” Williamson said.


An analysis found that the ALLP had become low-profile: Most of the acquisition community was not aware of the portal, return users were scarce, and lessons learned input had plummeted. To address those problems, ASA(ALT) formed a task force to rein- vigorate, re-emphasize and reintroduce the portal to all levels of the acquisition community as well as individual users.


“We had our initial brainstorming session, and everyone [agreed that] we have a lessons-applied problem. Te site is there; there- fore, the site must not be good and nobody’s using it. Terefore, we were not having our lessons applied,” said Maj. Shannon Tompson, 51A proponency officer for the U.S. Army Acqui- sition Support Center (USAASC) and team facilitator on the project.


After speaking at length with the site owners, Tompson found they’d been noting deficiencies in usage of the portal for a while. Te acquisition community was either not prioritizing submit- ting lessons or the lessons learned process “was not deemed to be useful, because not enough people were starting the ‘movement,’ indicating a cultural problem.”


“Tey had collected a lot of data and done surveys,” Tompson continued, “and it turns out that the root of the problem isn’t so much that the site is not useful. Te root of the problem is they can’t get folks to feed the system with lessons learned; that then would draw other users to pull those lessons learned and apply them to their particular situation.”


Tompson suggested that raising awareness of the lessons learned portal throughout an acquisition officer’s career progres- sion would increase its recognition and usage. “If we were to get them at the basic course as captains and junior majors and say,


‘Here’s this tool [ALLP] out there, and by the way, we’re going to do a small module and a practical exercise on how to use this tool,’ [we could] make it a part of the community culture.”


ASC.ARMY.MIL


51


ACQUISITION


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  |  Page 157  |  Page 158  |  Page 159  |  Page 160  |  Page 161  |  Page 162  |  Page 163  |  Page 164  |  Page 165  |  Page 166  |  Page 167  |  Page 168  |  Page 169  |  Page 170  |  Page 171  |  Page 172  |  Page 173  |  Page 174  |  Page 175  |  Page 176