search.noResults

search.searching

saml.title
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
COMMENTARY


Finally, the right effort—and right amount of it—should be up to other experienced KOs to analyze. Commissioned officers who serve in this role should concern themselves primarily with becoming experts who can perform and critique these aspects of contracting, to ensure that the workforce remains focused on the Soldier and capability overmatch.


OBSERVATIONS ON THE WORKFORCE AND IMPROVING OUTCOMES 1. Implementing new systems will stymie the workforce in the short term. Atul Gawande, a surgeon and public-health researcher, wrote a 2018 article for Te New Yorker titled “Why Doctors Hate Teir Computers,” in which he described the “revenge of the ancil- laries.” Te struggle is the result of the system design choices being more political than technical: Tose doing medical billing have different concerns than doctors do, but the recommendations of the administrators become part of the software the doctors must use (to their irritation).


Tis is a useful analogy for the burden of new enterprise resource planning software on the workforce. We should better forecast updates of the software and enable the average worker to provide suggestions on improving systems. A solution might be to form a single U.S. Army Contracting Command office that seeks input when creating Army systems and consolidates Army workforce input for other DOD systems.


2. Te Army contracting community should consider identifying members of the workforce who focus primarily on the repeti- tive “labor-hour” type tasks associated with contracting, possibly designating them as purchasing agents or procurement techni- cians. Tat way, if those numbers go down, the Army should either assign more technicians or provide more training. Tis could help alleviate the tension between the dual demands for contracting speed and more data input.


3. Leaders should distinguish tasks as either routine or requiring expertise. Te Financial Times in 2019 ran the article “Law Firms’ Love Affair With the Billable Hour Is Fading,” in which they rated different firms on their ability to get away from the billable-hour model to other methods of pricing (i.e., quantifying) the expert services they provide. Te winner? Te Financial Times found that Accenture’s legal department was able to cut its costs by 70 percent by creating two workflows: the “complex” contract work- flow, handled by senior attorneys, and the “transaction” workflow handled by offshore junior attorneys using automation. While government employees can’t be “offshored,” we should realize that we have some expensive, highly trained employees doing some very repetitive tasks. Tat’s not acquisition on a war footing.


4. All discussion about the workforce is ultimately about resources. Te dollars-and-actions method of allocating resources has seri- ous flaws. It measures the wrong things, fails to measure the right things and doesn’t account for novel situations requiring expertise.


We could build a proposal difficulty score that rates how hard it is for vendors to participate in federal contracts, reflecting proposal sizes and evaluation sub-factors.


THE SO-WHAT Increasing performance metrics in contracting is a worthwhile goal, but the application of expert abstract knowledge to diag- nose and resolve novel problems is inherently difficult to measure. To change the culture of Army contracting, we should improve the metrics we have, reduce our deference to the flawed ones and facilitate data gathering. Ultimately, however, expertise is what will truly improve outcomes.


For more information, contact the author at brian.j.burton.mil@ mail.mil.


MAJ. BRIAN J. BURTON is a warranted contracting officer at Army Contracting Command – Rock Island, Illinois. He received his J.D. from the George Washington University Law School in 2014 and is an associate member of the Virginia State Bar. He received a B.A. in philosophy from Arizona State University. He is a member of the Army Acquisition Corps and holds Level III certification in contracting as well as Level I certification in program management.


https://asc.ar my.mil


151


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