LESSON UP


Cost impact: If this lesson had a positive or nega- tive effect on your program in terms of cost, please try to quantify it and provide the base year used to derive cost savings.


Schedule impact: If this lesson had a positive or negative effect on your program in terms of schedule, please try to quantify it.


Performance impact: If this lesson had a positive or negative effect on your program in terms of perfor- mance, please try to quantify it.


Additional comments: Please add any additional comments.


Category: Please choose one or more categories that apply to this lesson. Please refer to the Category worksheet for valid choices. Multiple categories should be separated by a semicolon.


Keywords: Please choose one or more keywords that apply to this lesson. Please refer to the Keywords worksheet for valid choices. Multiple keywords should be separated by a semicolon.


Phase: Please indicate the appropriate phases to which this lesson applies (otherwise choose “Not


Applicable”). Please refer to the Phase worksheet for valid choices. Multiple phases should be separated by a semicolon.


Milestone or event: Please indicate the appro- priate milestones or acquisition events to which this lesson applies (otherwise choose “Not Applicable”). Please refer to the Milestone worksheet for valid choices. Multiple milestones should be separated by a semicolon.


ACAT: Please indicate the appropriate ACAT level to which this lesson applies. Please refer to the ACAT worksheet for valid choices. Multiple ACATs should be separated by a semicolon.


System: If this lesson was learned within a particu- lar system/program, provide the name of the system (e.g., JLTV, AMPV).


Time of occurrence: If this lesson is linked to a spe- cific time period, please indicate when it occurred.


No specific format is required.


–CENTER FOR ARMY ACQUISITION LESSONS LEARNED


Writing up a lesson learned follows common rules for gram- mar, syntax, spelling and usage that you’d encounter in any sort of writing. Tere are, however, a few rules of the road that the ALL portal staff enforces vigorously. A lesson learned is not the place to air grievances, make accusations or show disrespect to other organizations or to contractors, according to Janet O’May, an operations research analyst on the acquisition lessons learned team.


“Sometimes we get a lesson, and it’s pristine. Tere’s not a whole lot [to do]. We always check grammar and make sure it reads well and that there’s nothing there that shouldn’t be there— you’re not slamming an organization, you’re trying to be helpful. We always check that sort of thing. Last week I got a couple [of] lessons in from PEO Soldier. I had very little to do on those. Tere was no back-and-forth. Everything was filled out; I had


54 Army AL&T Magazine January-March 2017


to do a couple of acronym checks, but other than that, they were great.


“Others just have a skeleton of information, so we may be going back and forth four and five times. It depends on how much effort [the organization] puts into it, and whether it provides enough information to be valuable to somebody else.” O’May guessed that she and her team have to go back and forth with a lesson’s author an average of about three times to get the lesson ready for posting on the portal.


What that means for most portal users is that the team does its best to make sure that providing a lesson learned is as simple as possible. Perfect or imperfect, the team will help make it useful.


—MR. STEVE STARK


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