President Obama has quietly recruited top tech talent from the likes of Google and Facebook. Their mission: to reboot how government works.
For Eric Maland, the whole thing goes back to that San Francisco wedding. Mikey wasn’t there—well, wait, actually, Mikey was there. But Eric didn’t meet him at that point. Eric met some other folks at the wedding who told him they were doing some fix-it stuff in Washington, and it sounded kind of interesting.
And now we’re chatting about it in front of the White House security gate, where we’re waiting to talk with the leaders inside about why guys like Eric are now wandering around this neighborhood with MacBooks in their shoulder bags and code in their heads. These are the “new techies,” as longtime Washingtonians tend to say, but that’s somewhat imprecise. These are people whose pedigree in Silicon Valley gives them the whispered reputations of gods and goddesses. I look at Eric. He’s wearing a faded T-shirt; his sparse hair is seriously matted down. Did he sleep lately? Exercise? Shave? All debatable. “Ever wonder what you’re doing here?” I ask him. He was the 13th engineer hired at Amazon, the first operations director at Twitter. Like everyone else on the stealth team that President Barack Obama is amassing and deploying inside the government, he never imagined he would live and work in D.C. “I guess I just like to fix things that are broken,” he says, shrugging.
Then there’s Lisa Gelobter. “Oh, you’ve gotta hear my story,” she says. It’s later that day, and we’re walking near the Washington Monument under a searing midday sun. There was this call she got out of the blue last summer in New York, inviting her to some kind of roundtable discussion in Washington for tech leaders. Lisa had just spent time on the upper management teams at Hulu and BET. She decides, reluctantly, that she’ll go take the meeting, which includes this guy named Mikey as well as this other guy named Todd, and turns out to be in the Roosevelt Room in the West Wing. Then President Obama opens the door and surprises everyone, and over the course of 45 minutes gives the sales pitch to beat all sales pitches. They need to come work for him. They will need to take a pay cut, the president announces. But he doesn’t care what it takes—he will personally call their bosses, their spouses, their kids to convince them. The crowd laughs. But he gravely responds: I am completely serious. He needs them to overhaul the government’s digital infrastructure now. “What are you going to say to that?” asks Lisa.
Lisa Gelobter, Chief digital service officer, U.S. Dept. of Education; Previously: Hulu, BET
Oh, and the stories about Weaver. “First name is Matthew,” Weaver says, sitting on a cheap couch in a makeshift office near the White House. But no one calls him Matthew, he explains, since there are too many Matthews in any given room at any given moment. Even among D.C.’s new technorati, people view Weaver as someone separate from the fray. Maybe it’s because he once lived in a camper in the Google parking lot without going home for an entire year. Maybe it’s because he was the one guy who, if he didn’t answer an emergency call, the whole search engine might go down. Or maybe it’s because in a group of brilliant engineers, Weaver, as one of his new colleagues puts it, stands out as “someone who is, like, superhero-fucking-brilliant.” Recruited from California last year by these guys Mikey and Todd to work on the broken Healthcare.gov website, Weaver decided this year to stay in D.C. and leave behind the comfort of Google and a big pile of stock options. He recalls it in terms that suggest the transfixing power of a holy pilgrimage. “That”—he says, meaning the Healthcare.gov fix-it work—”changed my life in a profound way. It made it feel like all my accomplishments in my professional life meant very little compared to getting millions of people through the hospital doors for the first time. And that made me see that I could never do any other work without a public impact.” Weaver now spends his days in the guts of the Veterans Administration, helping the agency’s digital team upgrade their systems and website—and trying to reboot the way government works. As an early test to see if he could challenge the VA’s protocol, he insisted, successfully, that his official government title be Rogue Leader. And so he is: Rogue Leader Weaver.
Todd and Mikey—the ones who helped bring people like Eric Maland, Lisa Gelobter, and Weaver down here—are, respectively, Todd Park, the former chief technology officer of the United States, and Mikey Dickerson, who led a team of 60 engineers at Google and supervised the crew that fixed the Healthcare.gov website last year. Since that time, Park and Dickerson have been steadily recruiting an elite digital corps—a startup team, essentially, built mainly from the ranks of top private-sector companies—and embedding them within the U.S. government. Their purpose is to remake the digital systems by which government operates, to implement the kind of efficiency and agility and effectiveness that define Silicon Valley’s biggest successes, across everything from the IRS to Immigration Services. “We’ve got about 140 people in the network right now,” Park says of the digital team. “The goal is to get it to about 500 by the end of 2016.” Whether Park and Dickerson can find enough superstar techies to take a flyer on this risky project is just one of many concerns. There are bigger questions, too, such as whether a small number of technologists can actually bring about vast changes within the most massive, powerful, bureaucratic regime on earth.
Todd Park has just 18 months—until the Obama administration ends—to recruit a tech corps of 500.
It helps that the two men have substantial “air cover,” as President Obama describes it in an exclusive, in-person interview with Fast Company. For the past year, the president explains, he has personally helped Park and his team hire talent and implement their ideas across a host of government agencies. While the reasons behind this initiative and its scope have not been made clear before, in the president’s view, the idea of building a “pipeline” of tech talent in Washington starts with practical appeal: Better digital tools could upgrade the websites of, say, the Veterans Administration, so users get crucial services that save time, money, and (for veterans in need of medical help) lives. “But what we realized was, this could be a recipe for something larger,” the president explains. “You will have a more user-friendly government, a more responsive government. A government that can work with individuals on individual problems in a more tailored way, because the technology facilitates that the same way it increasingly does for private-sector companies.” In other words, if Obama’s tech team can successfully rebuild the digital infrastructure of Washington—an outcome that is by no means certain yet—you might not only change its functionality. You might transform Americans’ attitudes about government too. And you might even boost their waning feelings of empowerment in an ideologically riven country of 320 million people.
In the meantime, do you also end up with a dedicated group of Rogue Leader Weavers where none existed before? Tech geniuses who embrace public service as an essential element of their careers? The president is betting on that outcome as well. Get the country’s technologists to change Washington, the theory goes, and maybe—just maybe—you end up changing the country’s culture of technology, too.
The new hub of Washington’s tech insurgency is something known as the U.S. Digital Service, which is headquartered in a stately brick townhouse half a block from the White House. USDS employees tend to congregate with their laptops at a long table at the back half of the parlor floor. If there’s no room, they retreat downstairs to a low-ceilinged basement, sprawling on cushioned chairs. Apart from an air-hockey table, there aren’t many physical reminders of West Coast startup culture—a lot of the new techies are issued BlackBerrys, which seems to cause them near-physical pain. Nevertheless, the corps at USDS tends to rely on the same jargon you hear around Silicon Valley these days. They’ll say they’re here to “iterate,” or to “deliver product,” or to “JFDI” (that is, just fucking do it). When I wander downstairs one morning in late April, Ben Maurer, a young engineer on sabbatical from Facebook, is huddling with a few colleagues on a project for the Department of Defense. “I’m not just fixing bugs here,” he informs me, looking up from his laptop for about a nanosecond before going back to his coding. He seems tired but pleased to work on something big—in this case, to map out a broad digital structure for an upcoming project at the mammoth agency.
“”What we realized was, this could be a recipe for something larger,” the president explains. If the tech team succeeds, it could transform Americans’ attitudes about government.”
To a certain extent, the Obama administration has always been a comfortable place for techies like Maurer; the president—whose 2008 campaign was arguably the most convincing demonstration at the time of social media potential—was the first chief executive to appoint a chief technology officer and, more recently, a chief data officer. “Government has done technology and IT terribly over the last 30 years and fallen very much behind the private sector,” Obama says. “And when I came into government, what surprised me most was that gap.” But creating high-level positions like the CTO was a route to better government technology policy, not necessarily better operations. Besides, the immediate priority was addressing the economic crisis and resolving military entanglements.
Tech moved up on the punch list in 2013 due to a new crisis: the Healthcare.gov fiasco. When the president’s key legislative achievement was mortally threatened by a nonfunctioning website, Todd Park, as CTO, was among those asked to help rescue the endeavor. Before his stint in government, Park had started two medical IT companies now valued at over a billion dollars each, and it was that experience, not policy or politics, that he called upon. Park recruited Dickerson from Google, as well as a half-dozen other engineers. This small team, working around the clock in Maryland, fixed the site in seven hectic weeks. Not only did the effort “save the president’s baby,” as one former White House staffer puts it, it crystallized within the administration the impact that just a handful of deeply talented techies could have on our government’s functionality. And it prompted Obama, Park, and their colleagues to wonder: Could an infusion of West Coast tech talent become permanent? What might that achieve?
As it turned out, there was a model to follow. The British government had demonstrated that the best digital practices from the private sector could be applied to the public realm with transformative results, through an initiative known as the Government Digital Service. (A columnist at the Guardian newspaper lamented that he couldn’t invest in the GDS, even though it seemed like the best tech startup in Europe.) Park, meanwhile, had already put some pieces in place: a program known as the Presidential Innovation Fellows, begun in 2012, which brought bright young technologists into government for 12-month stints; and a group called 18F, within the government’s General Services Administration, that deployed graduates of the fellows program to other government agencies on a project basis.
“”We need both kinds of people,” says Park. “People who can hack the technology and people who can hack the bureaucracy.””
With the backing of the president, Park scaled up his recruiting efforts. His outward-facing policy job became focused on building an internal tech team. Dickerson had returned to the West Coast after Healthcare.gov—his goal was to sleep as much as possible for several weeks straight. But in May 2014, he came back to Washington for a meeting with Park, who harangued him late into the evening at the Shake Shack in DuPont Circle, the favored hangout of the West Coast techies. Park wanted Dickerson to pick up where he left off at Healthcare.gov and lead a new and more ambitious project. The two were gently kicked out of the restaurant by a manager locking up for the night. But by that point, Dickerson had decided to commit to running a new central technology bureau. The USDS opened for business a few months later.
One morning in late April I sat down at USDS headquarters for several hours with Park, Dickerson, and Haley Van Dyck, who, with Dickerson, helps run the USDS. If the president is effectively the CEO of the White House’s tech startup, Park would be its chief strategist. He is excitable and charming, with a cyclonic energy that helps explain why he’s been so successful as a talent recruiter. When he talks about two ideas, or two people, that he very much likes, he blurts out, “This is a total double-helix of awesomeness!” In describing the level of difficulty the new tech team in D.C. faces, he exhorts, “This is DARPA meets the Peace Corps meets SEAL Team Six!” (“Todd is the most enthusiastic person I know,” says Obama.) Dickerson, by contrast, does not emote. In fact, Dickerson comes off at first glance as grumpy and rumpled—someone who, in a not-too-distant era, might have made an excellent clerk in a video-rental store. Then you talk with him and wish to take your first impression back. Dickerson is an uncommonly skilled engineer with a deadpan wit and an unflappable nature. When I ask how he feels about the tech surge scaling up, he says, “Yeah, I’m losing all that free time I had.” His business card carries no title but reads, Don’t panic. Park calls him Buddha.
Haley Van Dyck: Deputy Administrator, U.S. Digital Service; Previously: Obama 2008 campaign, FCC, USAID
Outsiders often make the mistake of perceiving Washington’s technical problems as the result of a dearth of engineering talent. This makes it tempting to frame the current wave of hires from Google and elsewhere as a wartime tactical team moving in to save us from the city’s existing coding barbarians. But this is not quite correct. For one thing, the people Park and Dickerson are luring here aren’t just software engineers; they’re data scientists, user-experience gurus, product managers, and design savants. For another, these people are being matched with government insiders who can advise them on how to deploy private-sector tools like Amazon Web Services, for instance, that have long been considered forbidden within the Beltway, or how the procurement of contractors can be improved. Usually this involves cutting a jungle path through thousands of pages of overgrown government regulations. As Park says, “We need both kinds: people who can hack the technology, as well as people who can hack the bureaucracy.”
The complexity is formidable. If you put your engineer’s hat on, Dickerson says, you can look at government’s approach to tech and decide that it’s pretty much insane. But if you consider it as an anthropologist might (“If you’re studying this alien culture,” he says, “and you ask, Why do they behave so strangely?”), you see that D.C. has developed its dysfunctions for deep, structural reasons. For instance, Washington has plenty of smart people, Dickerson says. But they have been removed from the extraordinary growth—only occurring during the past decade, really—of the handful of West Coast companies that can now manage “planet-scale websites,” as Dickerson puts it.
Above all, there is the inertia of the past. One of the first lessons Dickerson learned about D.C. when he arrived was that the city traditionally conflates the importance of a task with its cost. Healthcare.gov ultimately became an $800 million project, with 55 contracting companies involved. “And of course it didn’t work,” he says. “They set aside hundreds of millions of dollars to build a website because it was a big, important website. But compare that to Twitter, which took three rounds of funding before it got to about the same number of users as Healthcare.gov—8 million to 10 million users. In those three rounds of funding, the whole thing added up to about $60 million.” Dickerson believes that the Healthcare.gov project could have been done with a similar size budget. But there wasn’t anyone to insist that the now-well-established Silicon Valley practice of building “agile” software—rolling out a digital product in stages; testing it; improving it; and repeating the process for continuous improvement—would be vastly superior to (and much, much cheaper than) a patchwork of contractors building out a complete and monolithic website. In his Fast Company interview, President Obama remarks that he made a significant mistake in thinking that government could use traditional methods to build something—Healthcare.gov—that had never been built before. “When you’re dealing with IT and software and program design,” the president explains, “it’s a creative process that can’t be treated the same way as a bulk purchase of pencils.”
Which is not to say that replacing Washington’s culture with that of Silicon Valley should be the goal. Some hybrid of tech people who can innovate with patience rather than aggression may be more effective. Dickerson notes that government tech contractors, even the most skillful ones, face the arduous challenge of trying to repair an aging digital system without compromising any essential services. The method for issuing Social Security checks, for instance, relies upon old mainframe servers running on the dying COBOL computer language. “That’s fine, and it’s lasted them a long time,” Dickerson says. But the people who can maintain and operate that generation of technology are not going to live forever; indeed, many of them are past retirement age already. In this case, the West Coast mentality could be counterproductive. “There’s an attitude in the entrepreneurial private sector where we don’t care what came before us: We’re going to disrupt it,” Dickerson explains. “But we are not going to disrupt Social Security. That’s a big reason why it’s so hard to make these changes, because you can’t interrupt the flow of operations.”
Dickerson adds, “It will not work, and you will not go far, if you come here with a big attitude, saying, ‘You people are stupid, get out of the way and we’ll show you how it’s done.’ ”
Are there really people like that in the Valley? I ask.
Dickerson laughs. The people he’s directing, he says, tend to be the more humble types. And the folks interested in curated meals and big equity packages and uncompromising disruption didn’t come east to help him. This is not the place for them anyway, he says. They just wouldn’t get it.
We’re not choosing these types of people when we recruit, Van Dyck, the USDS deputy, adds. “And they’re not choosing us, either.”
The White House chief of staff, Denis McDonough, enjoys walking meetings, so one morning he guides me through the corridors of the West Wing and out onto the South Lawn, where we spend 25 minutes doing brisk laps around a circular driveway flanked by green grass and blooming gardens. McDonough points out the Rose Garden and relates a few historical tidbits about the White House grounds. But mostly we talk about the larger goals of the tech insurgency. As he sees it, the web and technology tools “flatten everything” by allowing Americans to engage with government more directly. So the notion that better tech will yield better democratic engagement is to both him and the president an aspirational—and logical—pursuit. But McDonough also believes there will be other immediate benefits. The transparency that technology enables (consider, for instance, how health insurance plans can now be easily compared online) will not only yield tremendous efficiencies. It can allow Americans to have better control over their own decisions—to interact with government in the same glitch-free way we do with iTunes or Amazon. “Why should we be immune?” he says. “Everything else is getting done faster. Why should this institution be different?” McDonough tells me that he admires how the tech insurgents have brought to D.C. their skills and collaborative habits, as well as what he calls a “hunger” for increasing performance. He stops walking and turns to me to say, “They are in an industry that has constantly reinvented itself and become more efficient. And that’s because at the heart of that industry is the belief that you’re going to get twice as good every two years, and that’s held for 50 years.”
“”Everything else is getting done faster,” says chief of staff McDonough. “Why should this institution be different?””
There is no Moore’s Law for government—at least not yet. And another thing that McDonough, Park, and Dickerson must confront is that this government startup will never have the same lean, concentrated focus of a private-sector company. Indeed, the tech insurgency is not even being built all in one place. Dickerson’s USDS currently employs 37 people, but it is only one aspect of an endeavor that has grown organically and sprawls all over Washington. It doesn’t even have a proper name. Park tends to describe the new tech corps as a “three-layer cake.” USDS is the first layer—a group of technologists who strategize about what projects should become government priorities and which people should work on them. The second layer is 18F—a group of 90 technologists and designers who work within the General Services Administration a few blocks away. 18F takes its name from its address (the GSA building is at 18th and F Streets) and has informal ties to USDS, but it is essentially a service agency. The group can take on jobs from anywhere within government that’s in need of digital help. Unlike USDS, it doesn’t necessarily follow the president’s political priorities.
And the third layer? That would be the tech teams, ranging in size from five people to 50, that will be installed within 25 government agencies over the course of the next 18 months. These teams will consult regularly with USDS for guidance and may utilize 18F for its services. The first wave is being led by people like Lisa Gelobter, who was given the hard sell by the president in the Roosevelt Room and who now works in the Department of Education. Matthew Weaver, formerly of Google, leads another group at the Veterans Administration.
Matthew Weaver: Rogue Leader, Digital Services, U.S. Dept. of Veterans Affairs; Previously: Google
The “tech cake” is only a metaphor, of course. And while visiting the different layers of the cake over the course of a week, I began to wonder if it’s the wrong one. What the designers of this effort actually want to create is something more dynamic—in effect, a technology ecosystem that long outlasts their stints in government. In that regard, you might consider Washington’s tech landscape, as it currently exists, as a kind of brown and barren field. And on that field, consider each agency as having a fenced-in plot of land. The USDS works now as landscape architects—the ones who design what kind of trees and plantings will go in each plot, and who will do the work. The people at 18F function like a nursery and contractors—they’ll provide the healthiest trees and do the plantings, either on their own or via someone they trust. They’ll even teach you how to be a good gardener. Meanwhile, the tech teams at agencies like Education and Veterans will take what USDS and 18F advise to make their plot flourish.
The overarching goal here is to get everything to grow together—very tall, very fast, inevitably joining up into a forest canopy so as to create a functional and interconnected system.
“If we’re trying to build new services that serve the public good, then the mechanism by which we do that is by combined services talking to each and getting you what you want,” says DJ Patil, another Silicon Valley recruit of Park’s, who works closely with USDS and serves as U.S. chief data officer. Plus, he adds, “If we combine systems, what kind of cool, amazing things will we find? What happens when we bring together climate data with health information—can we understand how the changing environment is impacting our health?”
If it’s still too early to say whether this technology ecosystem will flourish, it is nonetheless true that the tech surge has moved beyond its conceptual stages. Various teams are now engaged in rolling out projects. One day in Washington I spend the afternoon at 18F, a large, bright, open space, where teams of two or three work at white tables. The group has 15 contracted projects under way. “Our two primary areas are delivery and consulting,” says Hillary Hartley, who leads 18F. Delivery, she explains, “is where we would build the thing for an agency—the website, the service, the online transaction, whatever.” That’s what most of the teams in front of us are up to. “Consulting is where we’re helping the client do some of the design thinking, or problem scoping,” so they can figure out what to buy from a vendor.
Hillary Hartley: Co-founder and Deputy Executive Director, 18F; Previously: Presidential Innovation Fellow
We sit down with a team trying to revamp the Peace Corps website, then we walk over to chat with another team that recently created a user-friendly analytics web page, analytics.usa.gov, that tracks which government websites are trending (a National Weather Service page usually tops the list). The goal here is to reveal how U.S. citizens use government websites, and to spark healthy competition among agencies to create more popular services. In keeping with the tech corps’ guiding principles, everything is open source, so outsiders are free to adapt the program. And they do: A few weeks after the analytics website went live, Philadelphia used the program for its own analytics website, which the 18F team considered a measure of success. Thanks to their open-source code, they had improved government without doing any extra work.
We visit another team at a nearby table. At this point, probably the most important work at 18F, done in conjunction with USDS, involves overhauling the Immigration Services website. 18F is helping to redesign the site to drastically improve the user experience—for instance, by simplifying searches to aid those whose facility with English may be limited. Meanwhile, USDS is laboring deep beneath the surface. One of the initial goals is to rebuild the technology for a form known as the I-90. It’s how legal immigrants whose green cards are lost or stolen apply for a replacement, and the current process—paper-based and slow—can take as long as eight months. In creating a digital tracking form and a better online application, the designers think they can reduce the time to a fraction of that.
And that’s only one bureaucratic improvement at one agency. There are dozens of other forms on the Immigration Services website alone, which hints at the scale for improvement. “This is a $75 billion technology market,” Andrew McMahon, a cofounder of 18F along with Hartley, says of the annual government IT budget. “So if you wonder, How far can we reach? Well, I think it’s kind of limitless.” Hartley, for her part, notes that 18F couldn’t actually capture all of that IT work. “Our underlying goal is to make better clients, and to make the agencies understand a new way of doing things,” she says. “We’re never going to be big enough to take on the $75 billion market. But we will be big enough to help people out there make better decisions on how to build, or buy, their digital services.”
The paradox here is that when the tech teams succeed with a project like the I-90 form, or with any retooled government website, users likely won’t think much about it. It will be fast and intuitive. It will not crash when you use it. And you will then get on with your life. When I ask Dickerson what USDS’s biggest win has been since its start, he points to the open-enrollment season for Healthcare.gov, which went smoothly this year as compared to last year’s debacle. “That’s a big accomplishment,” he says, “but we don’t have any coverage of it because there’s nothing to say. The train wreck didn’t happen. We’re proud of that.”
The biggest problem with assessing tech startups is that most of them sound pretty good at the start. And even if you know the odds going in—that by some estimates, nine out of 10 will fail within a few years—it doesn’t necessarily dim the shine of a new idea. Without question, a tech startup of 100-plus people, backed by the president and working deep within government, differs from a startup involving three guys in a Palo Alto crash pad cluttered with fast-food wrappers. As Park perceives the government mission: “This may be more like what some large corporations have done to basically disrupt themselves.” Still, if you were a VC trying to game out the odds of success here, you might go through the risk factors facing the U.S. Digital Service, 18F, and the tech teams now growing within various agencies. As a risky and ambitious startup, how do they measure up?
First, there’s what we might think of as “talent risk”—as they scale, are these the right people for the right job? Tech managers like Dickerson and Weaver already proved their mettle during the Healthcare.gov rescue, and the folks now being lured to D.C. by Park’s team are arguably among the industry’s best. They are screened not only for IQ, but for EQ (that is, emotional intelligence). So they seem to pass that test. And that means we might next consider the risks of the tech corps’ resources: Do they have the wherewithal and organizational structure to make this take root within government?
There are a number of reasons, some highly technical, to think the corps have a reasonable chance. One should never underestimate the difficulty of getting Washington to move forward quickly—or logically. What’s more, budgets can always be vulnerable to political fights in congress. But the architects of the USDS—especially Park, Dickerson, and Van Dyck—made sure that their bureau was ensconced within the Office of Management and Budget, which gives the techies muscle within various agencies and an ability to influence various IT budgets and lines of command. What’s more, with the solid backing of the president and his chief of staff, the USDS has enough of what Dickerson calls “hard power” to fix important problems around town. Quite simply, the president can (and does) ask his cabinet secretaries to take seriously any USDS overtures to work on projects within their agencies.
What about the market risk? Will there be enough business in D.C. for the tech teams? If you’ve ever been on, say, the U.S. Department of Education’s site, it’s a question that answers itself. Van Dyck tells me “there are now lines around the block” to tap the USDS’s services. McDonough, the chief of staff, says, “Those guys”—the USDS—”went over to brief the secretary of defense and he said, ‘I’m sold. Give me 10 teams.’ ” The techies’ market demand is further buttressed by a lack of competition. The USDS is helping agencies find the best contractors, not competing with contractors or agencies. So, arguably, they pass this test too.
Mikey Dickerson: Administrator, U.S. Digital Service; Previously: Google
An unresolvable risk nevertheless hangs over the whole endeavor: the risk of running out of time. Many of those working with USDS talk about getting to “escape velocity,” which means getting the speed and momentum necessary, much like a rocket at liftoff, before Obama’s second term ends. “We have 630 more days,” Dickerson tells me in late April. “We have booster rockets for those 630 days to get us into orbit. If [USDS] achieves a stable orbit in that time, then it will be here for a generation, or maybe longer.” And what if the next U.S. president has a different agenda? In a number of conversations, I came away with the impression that improving government technology is less politically fraught, and less partisan, than other Obama initiatives—yet it still might be the case that a future administration dismantles what Dickerson and Park are building, or even eliminates the office of chief technology officer. “I don’t personally worry about it a ton,” Dickerson says with a shrug. “Because the things we set out for ourselves just for the next two years—I mean, if we accomplish just those things, it will be worth all the effort, even if it all goes up in smoke just after.”
The people at USDS and 18F don’t seem to doubt that they’ll have an impact. Indeed, they believe it is obvious already. By constantly testing their software with users, they can gauge improvements in real time. Some of those upgrades may seem minor now, but they should, in time and in sum, add up to something significant—and perhaps something very big. Even if you never go onto the improved Veterans or Immigration websites, you may soon find that, say, the Federal Student Loan pages (a forthcoming project of Dickerson’s) are improved so that better information and clearer navigation increases participation and reduces defaults. And it doesn’t seem to matter, in this case or others, that USDS teams as small as five or 10 people will be working inside agencies that are much larger than Google, Apple, or even General Motors. As the Healthcare.gov rescue effort demonstrated—or, indeed, any successful startup in Silicon Valley can prove—a very small number of tech people can have a disproportionate effect.
There is another side to the impact question as well: What about the effects on the recruits themselves? In terms of looking for meaningful work, the tech industry may not be what it was; one running joke on HBO’s Silicon Valley is that everyone has been led to believe that they’re changing the world with their app or algorithm, even when they obviously aren’t. Meanwhile, at the actual Silicon Valley companies that have genuinely changed global culture and business—Google, Apple, Facebook, Twitter—there may be a different dynamic. As those companies grow ever larger, the contributions of individual engineers may seem proportionately ever smaller. At least so far, these factors have created a pool of top-tier candidates open to taking on other kinds of work with depth and import. And the point for Obama is not to sell these candidates on a career in government, but rather to enlist them in a stint of a year or two at USDS, or even a few months. For decades, accomplished lawyers and economists have worked in the capital between private-sector jobs, so why not technologists? “What I think this does,” says Megan Smith, the current U.S. chief technology officer, who spent much of her career at Google, “is really provide a third option. In addition to joining a friend’s startup or a big company, there’s now Washington.”
Megan Smith: U.S. Chief Technology Officer; Previously: Google
This idea appeals greatly to the president—in fact, it was built into the USDS design from the start. “I’m having personal conversations with folks, meeting with them, or groups of them, and pitching them,” Obama says. “And my pitch is that the tech community is more creative, more innovative, more collaborative and open to new ideas than any sector on earth. But sometimes what’s missing is purpose. To what end are we doing this?” As the president explains, he asks potential recruits, “Is there a way for us to harness this incredible set of tools you’re developing for more than just cooler games or a quicker way for my teenage daughters to send pictures to each other?” For the time being, at least, there seems to be. HBO might want to consider an on-location shoot.
[Photos: Daniel Shea for Fast Company, President Obama photographed in Washington, D.C., on April 30, 2015.]
A version of this article appeared in the July/August 2015 issue of Fast Company magazine.
http://www.fastcompany.com/3046756/obama-and-his-geeks
