Plea Bargain Converts Multiple False Claims Into A Single False Statement
Article removed by request.
Are You Letting HR Kill Your Company?
 We’ve recently posted a couple of articles about employee development and workforce management in times of budgetary pressure. We’ve tried—perhaps too subtly—to nudge readers towards thinking about their employees and about strategies for ensuring that their organizations are positioned to survive the looming budget cuts, and perhaps even thrive.
Have we been too subtle? Heck, we came right out and begged you to take action on these issues, back in February.
While the idealist hopes you’ve invested time thinking deep thoughts about these issues, the cynic is pretty sure you’ve blown them off. We’re sure you had good reasons: focusing on program execution is always a good rationale for ignoring more long-term needs. If other excuses were needed, we expect budget planning or mid-year forecast efforts were trotted out like show horses. In other words, we bet you’ve been ignoring your workforce issues and will continue to ignore them … and then of course you’ll complain when your operations start to become negatively impacted.
We figure you need another swift kick to the keister.
So here’s yet another article on the boring, yet critical, topic of workforce management. Print it out; show it to you co-workers. Post it on the bulletin board. Send a copy anonymously to HR. We don’t care (just make sure you note it came from www.apogeeconsulting.biz). But do something about this, will you please?
Our first point is brought to you by DefenseNews, who reported that defense contractors “are struggling to keep talent” in the budgetary downturn. The DefenseNews article stated—
Cutting employees is easy. Keeping the right ones is difficult. While U.S. defense companies will likely continue to reduce staffing as part of the defense downturn already in progress, the process of sorting the critical from the expendable is a concern for many senior executives. Much of their fear stems from a glance at history: The aerospace and defense industry didn’t handle the last downturn well. Not only did a loss of critical knowledge affect efficiency, but in many cases companies were ill-prepared to support government needs when greater spending returned.
The article quoted Steve Grundman as saying—
‘In general, I think reductions in the last downturn were focused on ‘capacity’ and capital investments, not people, and what they learned was that the focus should have been on ‘capabilities’ and skills instead,’ Grundman said. ‘Compared to finding a good systems engineer, it’s comparatively easy to build a factory, an insight I’m not sure was so widely shared 20 years ago as it is today.’
One of the time-honored tactics for managing workforce cuts is to “stack rank” (sometimes called “rack and stack”) employees. Employees in each organization are ranked in comparison to each other. Often this is an annual process; but when workforce cuts are being contemplated, it is traditionally one of the first steps that management takes. We understand why. Generally speaking, you want to lay-off your low performers and retain your high performers. Thus, you first need to identify who is who. Makes sense, right?
Well, maybe not.
Recently, we have come across articles and discussions which assert that “stack ranking” is a fairly terrible approach to workforce management—especially when implemented on a routine basis and especially when a pre-selected “grading curve” is issued by upper management. The pre-selected approach was made famous by Jack Welch and the General Electric Company, where the lower 10% of the workforce is identified annually—and then fired—came in for special criticism.
The first salvo came from an article about why Microsoft is no longer the leading-edge of technology innovation. One of the primary reasons for Microsoft’s lagging performance in innovation and development, according to the author, is its preoccupation with forced rank stacking. A summary of the article stated—
Analyzing one of American corporate history’s greatest mysteries—the lost decade of Microsoft—two-time George Polk Award winner (and V.F.’s newest contributing editor) Kurt Eichenwald traces the ‘astonishingly foolish management decisions’ at the company that ‘could serve as a business-school case study on the pitfalls of success.’ Relying on dozens of interviews and internal corporate records—including e-mails between executives at the company’s highest ranks—Eichenwald offers an unprecedented view of life inside Microsoft during the reign of its current chief executive, Steve Ballmer, in the August issue. Today, a single Apple product—the iPhone—generates more revenue than all of Microsoft’s wares combined. Eichenwald’s conversations reveal that a management system known as ‘stack ranking’—a program that forces every unit to declare a certain percentage of employees as top performers, good performers, average, and poor—effectively crippled Microsoft’s ability to innovate. ‘Every current and former Microsoft employee I interviewed—every one—cited stack ranking as the most destructive process inside of Microsoft, something that drove out untold numbers of employees,’ Eichenwald writes. ‘If you were on a team of 10 people, you walked in the first day knowing that, no matter how good everyone was, 2 people were going to get a great review, 7 were going to get mediocre reviews, and 1 was going to get a terrible review,’ says a former software developer. ‘It leads to employees focusing on competing with each other rather than competing with other companies.’
Teresa Nielsen-Hayden had this opinion to offer about forced rank stacking, at her website’s blog (“Making Light”)—
[Rank stacking] strikes me as magical thinking: you make your company more competitive by making its internal departments and individual employees compete with each other. Wherever it comes from, IMO it’s profoundly dysfunctional. Business is about getting work done — unless you’re in a line of business where that work consists of figuring out who’s a star and rewarding them, which is rare. Companies and departments are by nature internally cooperative clusters of people who are working on the same projects and/or issues. Turning employee evaluations into a game of winners and losers and stars, and employees into competing gameplayers, is not a good way to get work done. … Stack ranking also fails to take into account what kind of work is being done. Sometimes fast-moving highly profitable achievements rest on an earlier foundation of slow incremental work on less-than-tractable problems. It’s not unusual for a department to do both sorts of work. Which kind gets rewarded for being productive? Which gets the bad reviews and firings? I’ll absolutely question the use of stack ranking as a motivational device. Doing good work, looking ahead, helping to create a strong, smart organization, and refraining from doing evil should be enough to get any employee a good annual review. If what it gets them is a note in their permanent record saying it wasn’t enough, and they should have done more, they might feel motivated to try harder next year, and in a few cases may try harder the year after that; but mostly not, and sooner or later they’re all going to lose heart. People want to care about their work. If you break their faith in their job, it’s hard to win it back. It’s a miserable system for managers, too. Say you’ve put together a great department — competent, well assorted, good work proprioception, with high productivity and high morale. Now impose a rating system that tells you that your department manages its people neither better nor worse than any other department. Be forced to label 20% of your people winners, without reference to the rest of the department’s work that makes theirs possible. Label 70% of them as timeservers and underachievers, no better than they should be. Label 10% of them failures, or even fire them, when you’ve spent all year trying to help them be good at their jobs.
One of the commenters on her site offered this observation—
I'll not knock evolution: blind competitive pressure has created some pretty amazing things over the past billion years. One of things it has consistently produced, however, is cooperation. Time and again, it's turned out that in a cutthroat take-no-prisoners dog-eat-dog existential battle of all against all, the most winningest strategy is working together. What these competition-inducing schemes to improve upon the inefficiency of group production constantly miss is that group production originates in the first instance by out-competing everything else. Cooperation is where competition leads. Trying to use blind evolution to improve upon cooperative systems is like noticing that great square wheel you made is getting rounded on the corners from wear and setting about sharpening them back up.
This is more than simply the opinion of one (or two) individuals. If you visit Nielsen-Hayden blog post (link above) you’ll find links to several academic and business magazine articles on the topic that share this point of view. The consensus seems to be that forced rank stacking is bad for employee morale, hurts productivity and project execution, and stifles innovation. And it’s more than simply one or two or seven peoples’ opinions—it’s also questionable on a statistical level: it’s bad math.
As Ms. Nielsen-Hayden wrote—
The ‘grading on the curve’ aspect of it is also defective. Basic management theory limits the number of employees that can report directly to a single boss. Any department that’s small enough for everyone in it to be reporting to the same boss is too small a sample for that boss to be grading them on a rigid 20-70-10 curve. Besides, as any kid who got curve-graded in school can tell you, it’s no guarantee of high-quality work. If all the students in a curve-graded class slack off, they don’t all get a D or F. Instead, it gets easier to get a B. If all but a few students slack off, it’s a good bet that the ones who don’t will get an A. Now translate that into the essentially cooperative workplace. Is it really a good idea to reward employees when their co-workers fail?
Let’s posit for a moment that the “rack and stack” practice is bad. So why do you let your HR Department make you do it? And that is the critical question, isn’t it? Why do you let your HR folks and senior leadership perpetuate a practice that hurts your company?
We might speculate that the reason for the perpetuation of the practice is that it’s “traditional”—i.e., it’s the way it’s always been done. Nobody who makes the decisions in this area knows any other way.
But we all know that the worst reason to do anything is “because it’s always been done that way.” (The second worst reason is “because we don’t have enough budget to do it any other way.”) If that’s all they’ve got for a rationale, then they’ve got nothing at all. And we think you should call them on it.
One more point apropos to this issue, again offered by Ms. Nielsen-Hayden—
If you know in advance that 10% of the employees in your department are going to get fired, one logical answer is to always keep a few redshirts around. This frees up the rest of you to stop worrying, and work on the stuff you were hired to do. Any good work you get out of the redshirts is pure profit.
Perhaps that’s a bit cynical, but it’s also the logical answer to the problem of forced rank stacking.
So as you ponder the current and future budgetary pressures imposed on your organization by customers and the general marketplace, we ask you to remember that you need to plan for survival. You need to plan for the long-term future. And that means managing your current workforce, developing employees to become the next generation of leaders, and keeping your HR Department from getting in the way.
|
Another Voice in the Wilderness
“He said, I am the voice of one crying in the wilderness, Make straight the way of the Lord, as said the prophet Isaiah.” – John 1:23, King James 2000 Translation
Well, we were lucky enough to make the acquaintance of the owner of a small business who not only has had significant “lessons learned” about dealing with DCAA and DCMA, but has blogged about the company’s travails. The blog is called “Small Business Government Contracting: Adventures in Dealing with DCMA, DCAA, and Other Government Bureaucrats.” From the first post, we were hooked: it’s a must-read.
We had never heard of Quimba Software before we received an e-mail from a company executive, but maybe we should have—these Quimba folks are no strangers to disputes with the Department of Defense. This ASBCA decision sheds some light on why the Quimba folks are so passionate in their contempt for the DOD bureaucracy that, in their view, has wronged them.
It’s a short and to-the-point decision. Quimba received a Contracting Officer’s Final Decision (CoFD) disallowing certain deferred executive compensation costs. Quimba filed an appeal, but did so on the 91st day after receipt of the CoFD. Unfortunately for Quimba, the ASBCA Judges strictly enforced its 90-day appeal period, and dismissed Quimba’s appeal without hearing any arguments on the merits. End of discussion.
It may sound harsh, but that’s the way the government contracting game is played. What seems unfair to one party (Quimba) seems perfectly fair to the other party (the United States). The United States, the Sovereign, consents to be sued, but only within strictly enforced circumstances. If you fail to follow the playbook, you lose the game.
Now, we could take off on a rant here ourselves. We could rail that treating the US Federal government as “sovereign” is a hold-over from English jurisprudence. The English had a Sovereign, but we fought a revolution in order to rid ourselves of that concept of governance. Treating the Federal government as a “sovereign” perpetuates an anachronistic system that has no place in freedom-loving America. But that kind of ranting does no good in this context, since Quimba (and all other government contractors) consent to this treatment when they execute their contracts and accept the government’s money.
Sure the game is rigged, but if you don’t bet you can’t win.
So with that background, let’s start quoting some of Quimba’s “lessons learned”—clearly published with the intent of warning other small businesses about the landmines that Quimba tripped in its dealings with the Department of Defense.
About DCAA:
-
The biggest mistake many entrepreneurs new to the government contracting game make is to think DCAA has, or under any miraculous set of circumstances, will have even an iota of interest in your success.
-
I promise you, however, that a DCAA auditor that consistently does not find “something wrong” with contractor cost calculations will probably be banished to the children’s table at their annual agency picnic! Same is true, though with a twist, of DCMA staff, particularly the Administrative Contracting Officers or the ACOs. An ACO who fails to perform as a de facto employee of DCAA and follow the auditor “recommendations” will probably not be invited to DCMA’s holiday party.
About DCMA:
-
In my direct experience, however, most ACOs simply do not care enough about small businesses to do anything but try to get them off their “to do” list as fast as possible. … In my direct experience, DCMA also intentionally fosters a defective management structure that promotes lackadaisical and inconsistent enforcement that breeds a contemptible lack of supervisory sophistication. … In short, in my direct experience, DCMA has intentionally structured a management environment that promotes and rewards incompetence by its staff, particularly the ACOs.
-
I would in fact venture as far as to say that you are NEVER done negotiating terms and pricing on any contract until it is closed. Up until then you should absolutely expect the government, through its duly authorized employees in DCAA and DCMA to focus on reducing your contract’s value – or the total amount you will ultimately receive on your contract regardless of what they themselves agreed to, either explicitly or implicitly. This is cheating.
-
Simply stated, just because DCMA and DCAA represent the US flag, it does not mean their policies, or their employees, will either be fair or reasonable. The bureaucrats you will be dealing with care only about what any bureaucrat cares about – stay under the radar, get the paycheck, and build the pension. These bureaucrats also do know that any contract dispute is likely to spend several years in the agency’s internal administrative processes before starting on a long and windy legal road. Given that it could take a decade or more before a dispute is resolved, most bureaucrats simply push it off on to the next guy. At least this has been our experience. And the guy who is stuck with you at the end of this musical ACO game is sure going to let you know just how unhappy s/he is that you do not simply submit to the bureaucrat’s will.
-
Throughout this ordeal, it has been my personal experience that DCMA staff are intentionally hostile and abusive – and they like it that way. It has also been my experience that there are absolutely no management controls in DCMA to rein in the type of abuse we have been subject to over the past FIVE , yes F-I-V-E years. How hard is it, we have continually wondered, to verify that ACO [Named Withheld] made an error and correct it?
Well, we here at Apogee Consulting, Inc. feel Quimba’s pain. The Quimba folks are expressing the frustration that many of us feel, all too often. Let’s keep in mind that Quimba was awarded an SBIR Phase 2 contract, so it (theoretically) had something that the DOD was interested in obtaining. But no that’s not going to be happening.
So in this story, there are no winners—only losers. Quimba is (quite possibly) out lots of money—and, even if the company ultimately prevails at the Court of Federal Claims, they are out quite a lot of attorney fees. The Defense Department loses out on some promising software. And we, the taxpayers, lose out because our taxes are going to a contract dispute that should be easily solved—if anybody cared to negotiate.
Problems with the T&M Contract Type – Part 3
Previously we discussed problems with the T&M (and Labor Hour) contract type at the Prime Contract level. In this article, we want to discuss problems at the subcontract level—i.e., why in the world would you ever issue a T&M type subcontract?
Well, we know one answer to that semi-rhetorical question. You issue a T&M subcontract when you have a T&M prime contract, and you need separate subcontractor billing rates. Prior to 2007, prime contractors could plausibly argue that, if a subcontractor was performing the same work as the prime contractor, the subcontractor’s labor hours could be billed at the same fixed hourly rates as the prime contractor. (There was even a somewhat-on-point legal precedent that stood for the proposition that it was the work that counted, and not who performed it.) But in 2007, everything changed. Federal Acquisition Circular 2005-15 and DFARS Change Notice 2006-1212 amended the regulations applicable to T&M (and Labor Hour) type contracts in several areas, and thus most contracts subsequently were required to have three sets of billing rates: (1) for the prime’s employees, (2) for each subcontractor’s employees, and (3) for any work performed by a subsidiary or separate division of the prime contractor. (Note that competitively awarded non-DOD contracts are subject to different, more lenient, requirements.) Subcontractor efforts that don’t qualify as required labor hour work (i.e., subcontract efforts that don’t constitute delivered labor hours) cannot be billed under the “T” portion of the contract, and must be billed under the “M” portion at actual costs paid (plus applicable indirect costs, less fee).
So if you have a T&M contract that requires separate billing rates, you would want to put your subcontractor under a T&M contract. If you didn’t, then you would have to bill the subcontractor’s efforts at actual costs with no profit component. So that’s one answer to the question we posed; but now we are running out of answers.
If you intend to award a T&M subcontract, you are entering into a world of hurt. First, you may be dealing with a small business entity that may not have an “adequate” accounting system, as defined by the SF 1408 or DCAA. That’s fine from a technical standpoint—there is no requirement in the FAR or DFARS that T&M contractors must have an “adequate” accounting system, as there is for cost-reimbursement contractors. But the problem there (as we saw in Part 2) is that too many Government people think that a T&M contract is “flexibly priced”—and hence cost-reimbursement—and so an “adequate” accounting system must be required to be in place before contract award. They’re wrong, of course. But setting them straight will be a challenge.
Similarly, there is no requirement to find that “no other contract type is suitable” with respect to entering into a subcontract; yet Contracting Officers may think that the requirement should apply to a prime’s subcontracting. If the prime contractor is submitting a proposed T&M subcontract package for consent, it may prove problematic to convince the CO that consent should be given, absent such a document in the file.
If you enter into a T&M subcontract, and the subcontractor applies indirect costs to the reimbursable “M” portion of the subcontract, then the requirements of the Allowable Cost & Payment clause (52.216-7) apply. That clause requires, among other things, that the parties need to establish a reasonable provisional billing rate, which will be finalized after the subcontractor (a) submits its annual final indirect cost rate proposal, (b) that proposal is audited by a government audit agency, and (c) the rates are negotiated and finalized. That’s going to take years—and your subcontract will remain open during that timeframe.
We should also note that the billed labor hours under the “T” part of the subcontract are to be billed in accordance with the T&M Payment clause 52.232-7. This will require (among other things) that the subcontractor must submit documents supporting its monthly billing, including individual daily job timekeeping records and records that substantiate the employee’s billing rate category qualifications. That’s going to be a bit burdensome, especially if your subcontractor is a small business that lacks a sophisticated timekeeping system. (We see no regulatory reason that “individual daily job timekeeping records” can’t consist of several 3x5 cards, but still.)
Is there any way around these bureaucratic and burdensome billing requirements?
Well for one thing you can think about using quick-closeout rates if the subcontract qualifies. Revisions made to the FAR in June 2011 made it much more difficult to use quick-closeout procedures, but smaller value subcontracts may still qualify. (See FAR 42.708.)
Another possible approach may be to avoid the protracted indirect cost rate settlement issue by agreeing, upfront, to a firm, fixed-price for allocated indirect rates. That creates a risk for the contracting parties: if the actual (audited) rates are lower than the rates used to negotiate the FFP value, then the subcontractor will earn additional margin; but if the actual (audited) rates are higher, then the subcontractor will experience margin erosion. (Creating a FP-EPA or FP with reopener clause defeats the purpose, since the parties will still have to wait for the indirect rates to be audited and finalized.) And, in any case, the “M” portion of the contract will still be based on actual costs incurred, so those costs will need to be audited and finalized as part of contract close-out activities (if for no other reason).
What if you negotiate an FFP price for both the (otherwise reimbursable) “M” portion, as well as any indirect costs allocated to that portion? Will that avoid the flexible price issue? Well, yes. And in that case, you can probably throw-out all requirements associated with the 52.216-7 clause, as well. But you might notice that the contract you have ended up negotiating looks very much like a FFP (or perhaps FFP-LOE) contract type, where everything is firm, fixed-price and the only variable is the actual number of labor hours delivered by the subcontractor. At that point, maybe you might want to consider moving toward an honest-to-goodness FFP (or FFP-LOE) contract, and in that manner simply avoid all the hassle and problems associated with the T&M subcontract?
|