Shows & Panels
- The 2014 Big Picture on Cyber Security
- AFCEA Answers
- Ask the CIO
- Building the Hybrid Cloud
- Connected Government: How to Build and Procure Network Services for the Future
- Continuing Diagnostics and Mitigation: Discussion of Progress and Next Steps
- Federal Executive Forum
- Federal Tech Talk
- The Intersection: Where Technology Meets Transformation
- Maximizing ROI Through Data Center Consolidation
- Moving to the Cloud. What's the best approach for me
- Navigating Tough Choices in Government Cloud Computing
- The New Generation of Database
- Satellite Communications: Acquiring SATCOM in Tight Times
- Targeting Advanced Threats: Proven Methods from Detection through Remediation
- Transformative Technology: Desktop Virtualization in Government
- The Truth About IT Opex and Software Defined Networking
- Value of Health IT
Shows & Panels
Should the federal workforce spread out?
Tuesday - 7/27/2010, 5:44pm EDT
The Washington Post's Alec MacGillis thinks so. But this isn't the first time this sentiment has been expressed.
"It's just one of those things that seems to come up every few years, and the case never seems all that entirely strong to me," Tom Shoop, editor in chief at Government Executive said. "So put me in the category of not being convinced! "
MacGillis' opinion was that if Washington, due to the high government presence, is under such heat from the rest of the nation for remaining relatively unscathed during the economic downturn affecting the rest of the country, why not break it up and spread the wealth?
Well, Shoop says, there's a few caveats to the argument. First up, the government isn't all that Washington-centric.
"The government is not exactly as concentrated as people tend to think it is in Washington," Shoop said. "Eighty-three percent of the government is actually outside the Washington area."
Also, Shoop says, MacGillis excluded Defense and Veterans Affairs employees based around the country in his statistics.
"I think it's a little curious to take Defense and VA out of the calculations, apparently purely on the grounds that they have a lot of employees who aren't in Washington" "It's sort of like saying 'if you look at Walmart, and take out all of people who actually work at Walmart, well they'd be very heavily concentrated in Bentonville, Arkansas.' Well, yea, that's where their headquarters are. But doesn't tell you that much about the situation."
And taking out Defense and Veterans affairs on results in a 25 percent concentration of the government in and around Washington, Shoop writes in his rebuttal, which means 75 percent is still outside the area, not exactly an outrageous imbalance.
While there's one school of thought that says that the government should be moved out of Washington and brought closer to the people, Shoop says the result might not be what they expect.
"These agencies would then become entirely captive of their locality. If you move the Department of Agriculture to Des Moines, think how important it would be to the economy of Des Moines." Shoop said. "If you think pork-barrel spending is a problem now, imagine what it would be like if those people had huge agency headquarters in their districts."
Shoop believes that the idea to "break-up" Washington gets floated around every time the anti-Washington sentiment around the country increases, and hopes people realize that while it's not to counter-act the concentration in Washington, there's already more geographic diversification taking place.
"If you want government to be more and more outside Washington, you're gradually getting what you wish for already," Shoop said, citing federal agency hubs around the country in places like Kansas City, Huntsville, Ala., and Denver, Colo. "This sort of thing is already going on."
Email the author of this post at firstname.lastname@example.org