Go Inside the Mission That’s Bringing the Federal Government into the Digital Age

Eight years after President Barack Obama promised to change the way Washington does business, there’s not much evidence of a new era of bipartisanship on Capitol Hill. His administration, however, has brought an antiquated, disjointed and inflexible bureaucratic system into the tech age. With a team of 153 people working across agencies, the U.S. Digital Service (USDS) retooled and modernized online applications for student loans, veteran’s healthcare and immigration visas. NationSwell spoke with Haley Van Dyck, a San Francisco native who co-founded the initiative, about running the federal government’s in-house startup.

The President asked you personally to change the government’s online systems. Why did you say yes?
Well, the president is a pretty hard guy to say no to! Honestly, why I’m here is because I couldn’t imagine doing anything else right now. Government is, I think, an overlooked platform for creating change in people’s lives. When you take a platform the size and scale of the United States government and you combine it with the transformative power of technology to create change, it can be a force multiplier for good.

What specifically are you integrating into government operations?
Our team is focused on how we can bring in the best technology talent across the country and pair it with the innovators in government to focus more on the underlying systems. There are services that government provides every single day that are utterly life changing for Americans, and whatever we can do to bring what Silicon Valley has learned about providing planetary-scale digital services that work into services that are in desperate need of upgrades is an incredibly appealing mission.

The federal government currently spends $86 billion on IT projects, but nearly all these projects go over budget or miss deadlines. Two out of every five are shut down. What’s getting in the way?
There are a lot of factors that go into it, so there’s no easy answer. Government still builds software the same way it builds battleships: very expensive, long planning cycles. That is simply not the way that Silicon Valley and the tech industry writ large has become one of the most innovative sectors, because it’s found ways to take very, very large projects and break them up into smaller pieces where they’re more approachable and [easier to] deliver results on a much faster, much less risky surface area. I think that is one of the big problems of government — it’s structured to do these large projects, and that’s what it continues to do.

Another problem we run into is just outdated technology. You will still find COBOL [a 1959 computer programming language] alive and well in parts of the United States government, because doing these kinds of technology upgrades are hard and complicated and challenging, and it takes a lot of work. So those two — the mentality as well as the existing technology — combine together make a very, very hard problem to solve. That’s basically what our team is targeting, right?

The rollout of healthcare.gov, by anyone’s assessment, was a logistical disaster and a political nightmare. Did that failure mark a turning point in how the government does its business?
There was obviously a ton of work underway long before healthcare.gov happened to solve this problem. But absolutely, I do think healthcare.gov was an incredibly critical turning point in two big ways. The first and most important one is that the rescue effort of healthcare.gov was one of the first times that many people with technology and engineering backgrounds were able to see how their skill-sets could truly help benefit a large number of their fellow Americans. It really shone a light onto the pathway for public service. The second way in which it was a defining moment was internally across government (for everyone from the White House down) it showed that the status quo right now is the riskiest option. The way the government goes about building software today is not successful and needed to change. That was a critical piece of energy and momentum that we needed to break the inertia and look at the problem from a different perspective.

Tell us a little bit about your first project with “boots on the ground,” where a team streamlined the transfer of health records from the Department of Defense to the Veterans Administration. Why start with such a huge bureaucracy?
If we were filtering for where the easy problems were, we wouldn’t have a ton of business. We ended up very excited and eager to work with the VA because we believe that veterans deserve a world-class experience when applying for the benefits after all they’ve done in service of their country. So it was an incredibly motivating mission.

Where does that project stand now?
We’re really excited because the team is making a ton of traction even in one of the largest, most entrenched bureaucracies in government. We’ve found incredible partners and supporters inside the VA who are really doing the heavy lifting and the hard work of creating culture change inside the agency, as they’re looking at how to improve services for veterans from all angles. The team is focused on two areas. First, how do we improve the experience for the veterans? Right now there are hundreds of websites, all intending to help veterans get access to their benefits. The work being done is streamlining all those service offerings and websites into a single place, where veterans can get better information and access to the benefits. Vets.gov is the new website that we’re building. It’s in beta and it’s launched for education and health benefits, and we continue to add services to it regularly.

The second big areas we spend a lot of time working is on the tools for the dedicated civil servants inside the VA to make it as easy as possible for them to complete their job of providing services to the vets. We just launched a product we’re excited about called Caseflow, which was designed with adjudicators inside the VA. It’s focused on streamlining and improving application processing. We realize that by helping upgrade the outdated systems that a lot of employees were using, we’re able to help the vets themselves.

In what ways is USDS similar to your run-of-the-mill Silicon Valley tech startup? And in what ways would you notice a difference?
We’re in incredible scrappy, bootstrap office spaces, with people running around in jeans, Post-It notes everywhere, tons of white boards and big discussions happening left and right. In many ways it looks and feels very, very similar to many of the startups you see across the country. But a couple of ways that it’s different, we’re actually quite proud of. For example, we have a very diverse team and are over 50 percent women, which I think makes different from a lot of companies in the Valley.

You’ve mentioned that USDS is easing arduous applications and centralizing contact information in one website. How does that work actually benefit the most vulnerable Americans?
I don’t want to pontificate too much on the status of our tech industry, but as you see various tech companies create change across the industry, they’re simplifying and improving the lives of Americans and really taking out a lot of the biggest inconveniences that we have. It is absolutely imperative that our government makes that same jump to providing services the same way that the rest of the industry does. The internet is obviously a huge conduit for that. In order to make sure that divide doesn’t become larger, between the people who are benefiting from the tech revolution and those who aren’t, government should make sure that we are also modernizing our services for the primary platform where people are looking to do business and communicate.

Now, that doesn’t mean it’s the only channel. We, as the government, do not have the luxury of segmenting our audiences the way that most companies do. We can’t just care about people on the internet. We have to care about those who don’t have access. But by the work we’re doing through actual user-centered design and modern technology stacks, we are able to do things like design for mobile, which is also addressing a huge percentage of Americans who now have access to internet only through smartphones and not through broadband. So I think that it’s an incredibly important part of the conversation, but it’s also not the entire conversation.

MORE: This Is a Smart, Nonpartisan Way to Improve Local Government

How a Former Google Engineer Plans to Change the Government for Good

Last fall, when the government stumbled launching the HealthCare.gov website last fall, Google engineer Mikey Dickerson stepped in to save the day.
Now, the White House is once again reaching out to Silicon Valley and carving out a permanent position for Dickerson, appointing him deputy chief information officer of the federal government and the administrator of the United States Digital Services Team.
Dickerson will helm a small team of digital experts aimed at repairing other government websites and computer systems, signaling a shift toward using technology to improve government efficiency. The goal is make these sites more accessible, user-friendly and as enjoyable as logging on to Facebook or Amazon, Dickerson told the New York Times.
Dickerson recalls walking into the storm that was the headquarters of of HealthCare.gov in Columbia, Md., in the winter of 2013.

“It was a very life-changing experience,” he says, adding his dismay over the lack of modern tools present to track data or better understand why the site was crashing.

“It’s easy just to order a bunch of machines and install them, and we’re doing all that stuff,” he says. “But you have to find exactly where is the choke point, and it’s a very compacted system.”

Dickerson likens his job to a traffic engineer, identifying where back-ups and bottlenecks exist. When the White House asked him to leave his job at Google for the new position, “there was really not any way I could say no to that,” he says.

In tandem with Dickerson’s hire, the White House also released a draft “playbook” to assist technology officers across federal agencies, using some of processes and tools enlisted in fixing the health care site last year.

The Digital Services Team plans to act as a sort of emergency responder to federal websites and systems temporarily stalled, but Dickerson also hopes to preemptively help agencies and anticipate potential problems on the horizon.

For now, the team will operate on a small scale, with only $3 million in the government’s technology budget. But the government has requested $13 million for next year and has plans to expand the team to as many as 25 people to help Dickerson revolutionize the next generation of government.

To us, that sounds like a goal that is certainly worth the cost.

MORE: Governmental Technology Difficulties Abound, Yet the Future Looks Bright

Governmental Technology Difficulties Abound, Yet the Future Looks Bright

With a $12 billion budget for 200 major IT programs and a total of $82 billion to spend on IT projects this year, it’s really hard to understand why the government just can’t get it right with digital initiatives. After all, innovations like Facebook have taken off, whereas Healthcare.gov, well, not so much.
According to Fast Company, “the government doesn’t take the same approach to software development that startups do,” explains Matthew McCall, a health technologist who started a well-known petition urging the government to open-source Healthcare.gov when it became obvious that its problems were copious. The government has tens of billions of dollars to ensure success, yet can’t achieve it — while startups with no money often manage to create popular products.
Why does the government have such a problem with technology? Startups are focused on creating a popular product as quickly as possible and once users provide feedback, it can be changed to better suit their needs. The government does the complete opposite of this.
McCall states, “government development focuses more on gathering comprehensive requirements up front, issuing a contract for the work, and managing the contractor during the build out. This ‘big bang’ approach typically means longer development time with little to no customer validation.” Changes are only made if a requirement is no longer valid, which causes developers to no longer focus on the products usefulness.
There are a number of policies in place that make the government different from a startup, like The Paperwork Reduction Act, which prevents developers from asking the public questions about products quickly. In general, many of the governmental policies in place slow down the process of production.
Of course, the government is also more risk-averse, simply by nature because if they get hacked, it is more of a big deal than if a startup was to be hacked.
Fortunately, there’s seems to be a solution this problem. (And no surprise, it’s a start-up.)
OpenGov, a company founded by Zac Bookman and Mike Rosengarten, is helping state and local governments shed their 30-year-old spreadsheets and visualize all data simply with just a few clicks.
MORE: Can a Children’s Book Persuade Girls That Coding Is Cool?
Need more money to control fires? Cities using OpenGov can immediately see how much money has been spent on fire and safety and where they can reallocate money from to help reduce wildfires.
Bookman explains, “there is an epidemic in governments of all shapes and sizes across the country. If you are the mayor of a city and I ask you a basic question about your data like, How much have you spent on police hours over the last five years?’ you probably don’t know of the answer.” With OpenGov, this answer can be found easily.
Major cities like Los Angeles and Palo Alto are already using this to help with city government, as are residents, as OpenGov isn’t just for city officials. Cole explains, “it’s to our benefit as public servants to demystify budget data to rebuild trust through transparency and accountability.”
So, why didn’t the government create this solution earlier?
Often, the problem stems from the lack available talent. The best engineers want to work for companies like Google or Facebook, not the government. Those big companies have better recruitment tactics than the government does, and according to Rosengarten, “if more students understood the problems or that the potential opportunity to solve real hard challenges with the local governments, they would get more excited.”
Although governmental work will never be as sexy as, say, working for Twitter or Square, the government does offer coders with the opportunity to code for a better world.
McCall notes, “if government can attract and retain people who want to make a difference and are given that opportunity, I think it will go a long way.”