Joshua Foust – Joshua Foust is a fellow at the American Security Project and the author of Afghanistan Journal: Selections from Registan.net.
The Atlantic, 20 September 2011
This morning I testified at the Senate Committee on Homeland Security and Government Affairs’ Subcommittee on Oversight of Government Management, the Federal Workforce, and the District of Columbia (a mouthful, I know) about how we can better manage and administer contractors within the intelligence community. I’m pasting a brief excerpt of my written testimony below, followed by a link to the full text of my remarks.
Every contract the government issues for a company to perform work is defined by the Statement of Work (SOW). This is a document that defines the parameters of the work the contractor will perform, including a description of the project, expected duties the contractor must fulfill, and the outputs and metrics by which performance will be measured. These are often poorly written, kept intentionally vague, and wind up not actually addressing the stated intent of the contracts.
As one example, every SOW I’ve had to either administer, edit, review, or write has stated as a basic metric of performance the number of employees the contractor should hire. That is, the basic means by which the government measures the contractor’s performance is based first and foremost on the number of people hired to work on the contract. This has two serious consequences that affect the contracting environment: it removes the distinction between employees that would make work products better, and it confuses the number of employees with contract performance.
The frankly bizarre system of hiring intelligence contractors is born from several interdependent processes: getting a security clearance, getting hired, and getting “read on” to work at a government site. The system of getting a clearance is structured such that those with clearances are given preference above those without clearance, regardless of the relevant experience of either employee. In other words, if two candidates are competing for a job with a contractor, and one has deep relevant experience but no clearance, she will most likely lose to a candidate with less relevant experience but a current and active security clearance.
There is a great deal more to this, and I would suggest anyone interested in this topic to download both my own testimony (At SCRIBD, or PDF here), and checking out the Hearing page, which includes written remarks from Daniel Gordon from the Office of Management and Budget, DHS Chief of Intelligence Charles E. Allen, Scott Amey from the Project on Government Oversight, and Dr. Mark Lowenthal.