Shows & Panels
- The 2014 Big Picture on Cyber Security
- AFCEA Answers
- Ask the CIO
- Connected Government
- Consolidating Mission-critical Systems
- Constituent Servicing
- Continuous Monitoring: Tools and Techniques for Trustworthy Government IT
- The Data Privacy Imperative: Safeguarding Sensitive Data
- Eliminating the Pitfalls: Steps to Virtualization in Government
- Federal Executive Forum
- Federal Tech Talk
- Government Cloud Brokerage: Who, What, When, Where, Why?
- Government Mobility
- Mission-critical Apps in the Cloud
- Mobile Device Management
- The Modern Federal Threat Landscape
- The Path from Legacy Systems
- Understanding the Intersection of Customer Service and Security in the Cloud
Shows & Panels
E-government's promise partially fulfilled
Wednesday - 12/17/2008, 2:44pm EST
By Jason Miller
As part of his government reform plans, then candidate for president George Bush promised to ask for $100 million for e-government, way back in June 2000.
This pledge became one of the most talked about and watched parts of this administration's management agenda.
Time and again, the administration asked for tens of millions of dollars, and Congress came back with $3 million to $5 million. Additionally, each year lawmakers placed more severe restrictions on how the administration spent money on e-government.
The Hill wasn't the only place the administration encountered roadblocks. Agencies were not always willing partners, especially early on.
Despite several obstacles, current and former federal officials all agreed that e-government's impact was significant and changed the government for the better.
"The focus has been on getting the foundational types of activities done," says Karen Evans, the Office of Management and Budget's E-Government and Information Technology administrator. "Initially agencies were looking at the enterprise as an agency or component. Now they look at the enterprise as the entire government. The promise of a citizen-centered government has been realized."
Mark Forman, the first e-government administrator and now a partner with KPMG, says the number of technology and program management problems when he took office in 2001 were great.
Forman remembers there were a lot of redundant buys, few agencies were using enterprise architectures to plan and manage their technology investments, agencies were implementing systems independently of each other and cybersecurity barely registered on many chief information officers' radars.
"Agencies were automating management problems and not fixing them," Forman says. "I am surprised that we've had so much success. It's almost like we did it on a shoe string budget. We had to do a lot of governance work and set up processes to make this work."
Forman says most of the problem areas now are in much better shape. He rates most areas an 8 or 9 on a scale of 10.
"We were living in a decades old organizational structure that no longer matched the way information is managed," he says. "The administration spent the last eight years busting down these silos. And the next administration will continue to do this."
Evans says some of the most successful e-government projects were in the government-to-citizen portfolio and government-to-business portfolios. Evans says projects such as Grants.gov, Recreation One Stop and USA Services really changed the way the government connects with citizens.
"We had a lot to achieve and a lot to realize," Evans says. "We went from adoption to usage to measuring customer satisfaction. We are moving beyond the satisfaction rates of many commercial sites."
Under the government-to-business portfolio, Evans says projects such as E-rulemaking and Business Gateway are among the most successful and have showed value to the business community.
Evans says the other two portfolios-government-to-government and internal efficiencies and effectiveness-were less successful for a host of reasons.
She points to the challenges of coordinating between levels of governments, and the culture change inside the federal government as some of the biggest obstacles.
"What really had to happen with internal efficiencies and effectiveness projects was to clearly demonstrate their value to people who know their business," Evans says. "Payroll was pretty easy from concept, but then there are a lot of variations of the pay scale themselves. People agree with you, but they don't want their mission encumbered, so you have to be clear about value and really clear about how it affects each and every agency."
Evans says OMB's experience with the consolidation of payroll providers provided important lessons learned for future human resources and financial management consolidation initiatives.
"I think the next team will look at where we are and what foundational things are in place and it will morph again," she says. "The platform is there and is ready to move to the next generation services and technology."
But the next administration also has to be careful not to fall into the same potholes that this one did, especially with Congress.
Evans and Forman both pointed to the limited support from the Hill, especially from the appropriators, as one major reason why e-government did not achieve more.
"There was no problem with communications with people interested in government reform," Forman says. "In the E-Government Act, we got everything we wanted. But the problems that existed on the Hill were related to the funding processes. They fund in islands of automation. It took us too long to figure out how to deal with that structure. There were things we could have done with the Budget committee that we didn't do."