The last few months, I've had to really bite my tongue over government waste. I've been contracting with a Small Business Programs office at the Pentagon, and on Friday, they terminated our contract after a series of rifts between the company and the office.
This office was like an elementary school playground. It had bullies, kids who picked their noses and slept through class, and crossing guards and hall monitors who had basically no real authority.
Except these weren't rowdy kids with nothing better to do. These were GS-12s and GS-15s, getting paid six-figures, doing practically nothing, traveling to meaningless conferences and events, and taking every Friday off. Sometimes taking several weeks at a time off.
Just letting you know, your tax dollars pay for that office. A hamster's cage of pathetic creatures who want to shake things up just to advance their careers. Tasteless, really.
They forced us to hire at least four staff who we would not have normally hired, and then terminated without warning, so those staff, plus half a dozen others are out of a job, as of today. These are people that this office insisted on hiring, because they were the best for the job, and they didn't even give them the consideration of a warning shot.
We are a small company, so firing 10 people is about HALF of our normal staff. And this is the model for treating small businesses at the DoD - from a Small Business Programs office? Chew on that for a minute.
I'd love to quantify all the ways they waste, and oh, I do have that information.
For those of you who are interested in Government Contracting Waste, feel free to use the following resource:
Make a public access username and password. The only difference is that there is a 90 day delay for DoD data, for security purposes.
you can download free training resources at www.fpdsng.com
I suggest the Data Dictionary, which will help you sort abbreviations and codes out.
Whatever you find, make public. Some of us have our hands tied, but the government is responsible to its constituents, right?
- ▼ June (3)