Technology Transformation Services: Mission and Programs
The federal government, for most of its history, did not have a place you could call to ask, in earnest, whether the website you were building should use a particular login system. It had many places, none of them quite the right one. The Technology Transformation Services exists, in part, because someone eventually decided that this was a problem worth solving from inside the building rather than outside it.
TTS is a relatively young organization stitched together from older ones. It lives inside the Federal Acquisition Service at the General Services Administration, which is itself a slightly unexpected home for a group of designers and engineers, given that FAS is better known for buying office chairs and negotiating airfare contracts. The arrangement is less strange than it sounds, and the reasons are worth explaining.
What TTS Is, Formally
According to GSA's organizational materials, the Technology Transformation Services is a component of the Federal Acquisition Service, the same FAS that runs the Multiple Award Schedule and the government's charge card program. Within FAS, TTS operates as a distinct directorate with its own programs, leadership, and funding model.
The mission, in plain terms, is to help federal agencies build, buy, and share technology that works for the public. That phrasing covers a great deal of ground — everything from operating a shared sign-in service used by tens of millions of people to embedding a small team of engineers inside an agency that has decided its grant-application portal needs reconsidering. The unifying idea is that certain digital problems recur across the government, and that solving them once, well, is generally cheaper and better than solving them eighty-seven times, badly.
TTS was assembled in roughly its current shape in 2016, consolidating several earlier digital efforts that had grown up in different corners of GSA and the Office of Management and Budget. The most prominent of those efforts, 18F, had launched in 2014; the Presidential Innovation Fellows program had been running since 2012; and a handful of consumer-facing properties such as USA.gov had existed for years under various stewards. Bundling them produced something with a coherent reporting line, if not always a coherent public identity.
The Funding Arrangement, Which Matters More Than It Sounds
Most federal organizations are funded through annual appropriations: Congress provides money, the agency spends it, the cycle repeats. TTS is funded differently. It operates largely on a cost-recoverable basis, meaning its programs are paid for by the agencies that use them, generally through interagency agreements. An agency that wants 18F to spend six months helping rebuild a permitting system pays 18F for those six months. An agency that integrates Login.gov pays a per-authentication fee.
This model has consequences that ripple through everything else. It means TTS programs must demonstrably be useful, because nobody is required to buy from them. It means the catalog of services shifts as demand shifts. And it means that TTS, somewhat unusually for a government organization, has to think about pricing.
The cost-recoverable structure is part of why TTS sits inside the Federal Acquisition Service at all. FAS is the part of GSA that already runs cost-recoverable programs — the Schedules, SmartPay, the City Pair airfare program — and it had the financial machinery to absorb a digital-services organization without inventing a new one.
The Programs
The TTS portfolio is best understood as a set of distinct programs that share a parent organization but solve different problems. They are not products in a corporate-portfolio sense; they are more like adjacent civic utilities.
18F
18F is a consultancy of designers, engineers, product managers, and content specialists who work with other federal agencies on a project basis. The name comes from the address of GSA headquarters at 18th and F Streets in Washington, which is the kind of detail that endears an organization to certain people and bewilders others.
The model is straightforward: an agency identifies a problem — typically a software system that is failing in some interesting way — and 18F sends a team to work alongside agency staff for a defined engagement. Engagements emphasize user research, modern development practices, and, importantly, transferring knowledge so the agency can maintain what gets built. 18F does not, as a rule, take over systems permanently. The work is scoped to leave the agency more capable than it found them.
Login.gov
Login.gov is the federal government's shared sign-in service. A member of the public who creates a Login.gov account can use it across participating agencies, rather than maintaining separate credentials at each one. The program handles identity verification at varying levels of assurance, depending on what the partnering agency requires.
The premise is that identity is a horizontal problem. Every agency that puts a service online needs some way for the public to prove who they are; building that capability eighty-seven times, again, produces eighty-seven slightly different answers, none of them quite as secure or as well-tested as one shared answer. Login.gov is the shared answer. Adoption has spread across agencies including the Office of Personnel Management, the Small Business Administration, and the Social Security Administration, among others.
Cloud.gov
Cloud.gov is a Platform-as-a-Service offering aimed at federal agencies and their contractors. It runs on top of commercial infrastructure but adds a layer of compliance and configuration tuned for federal use, including a FedRAMP authorization that agencies can inherit rather than pursuing independently.
The value, for an agency, is that deploying an application to Cloud.gov shortcuts a substantial amount of compliance paperwork. The tradeoff is the usual tradeoff of any platform: less flexibility than running raw infrastructure, more speed for the common case. For teams building straightforward web applications under a tight timeline, the bargain is often a good one.
USA.gov
USA.gov is the public front door to the federal government — a directory and information portal that helps people find the agency, form, or program they need. It is one of the older properties in the TTS portfolio, predating TTS itself by some years, and it operates in both English and Spanish. The site does not, generally, deliver services directly; it points to the agencies that do.
Search.gov
Search.gov provides search infrastructure for federal websites. An agency that needs a search box on its site can use Search.gov rather than building its own indexing and ranking pipeline. The service is shared across hundreds of federal sites, which produces both economies of scale and a consistent search experience for the public.
Vote.gov
Vote.gov is a small site with a narrow purpose: helping people register to vote, by directing them to the correct state or territorial registration system. Voter registration in the United States is administered at the state level, with rules that vary considerably, and Vote.gov functions as a routing layer rather than a registration system itself. The simplicity is the point.
Centers of Excellence
The Centers of Excellence, or CoE, are a different kind of TTS engagement. Where 18F tends to embed teams to build things, CoE works at a higher altitude — partnering with an agency's leadership on broader IT modernization, cloud adoption, contact-center improvement, data analytics, and infrastructure optimization. CoE engagements are typically longer and more strategic, and they often coordinate the work of multiple contractors and internal teams rather than producing software directly.
The model originated at the Department of Agriculture in 2017 and has since extended to the Department of Defense, the Office of Personnel Management, and others.
Office of Solutions and Office of Acquisition
The remaining components are less public-facing but structurally important. The Office of Solutions develops and operates several of the shared platforms — including, depending on the year and the org chart, pieces of Login.gov, Cloud.gov, and Search.gov. The Office of Acquisition handles contracting and procurement specific to TTS programs, including initiatives related to emerging technology and to making federal acquisition itself work better for digital services. Both offices exist because running a portfolio of cost-recoverable programs requires real operational machinery underneath.
Why This Lives at GSA
A reasonable question, on encountering TTS for the first time, is why a digital services organization is housed inside the agency that manages federal buildings and buys office supplies. The answer is partly historical and partly structural.
GSA's role, since its creation in 1949 under the authorities now codified in 40 U.S.C., has been to provide shared services to the rest of the federal government — buildings, vehicles, contracting vehicles, travel programs. Digital infrastructure is, in this framing, another kind of shared service. Login.gov is to authentication roughly what the City Pair Program is to airfare: a centrally negotiated, centrally operated capability that individual agencies can use rather than building their own.
There is also the matter of authorities. GSA has the legal and financial mechanisms — interagency agreements, working-capital funds, governmentwide contracts — that a cost-recoverable digital services organization needs in order to function. Standing TTS up inside an agency without those mechanisms would have required inventing them, which tends to take longer than reorganizing.
What TTS Does Not Do
It is worth saying clearly what TTS is not. It is not a regulator. It does not set policy that other agencies must follow, in the way that the Office of Management and Budget does. Standards such as those issued under the Federal Acquisition Regulation, available at acquisition.gov, come from elsewhere. TTS produces reference implementations, shared services, and consulting engagements, but agencies are generally free to use them or not.
TTS also does not replace agency IT departments. An engagement with 18F or CoE supplements an agency's own staff for a defined period; it does not absorb the agency's technology function. When the engagement ends, the agency owns what was built and is responsible for running it.
And TTS, despite the name, is not the government's only digital services organization. The U.S. Digital Service operates out of the Executive Office of the President, with a different mandate and a different reporting line. The two organizations have collaborated on various efforts over the years, and their alumni networks overlap considerably, but they are distinct entities with distinct authorities.
A Note on Stability
Organizations like TTS exist in a somewhat unusual position. The cost-recoverable model means programs survive by being useful, which is healthy, but it also means that priorities shift with the priorities of partner agencies, which can make long-range planning difficult. Programs have been added, restructured, and occasionally wound down over the years. The current shape of TTS, as described in GSA's published organizational materials, reflects the state of things at this writing; it has changed before and will change again.
That instability, if it is instability, is also a feature of the work. The problems TTS was assembled to address — fragmented identity, redundant infrastructure, brittle public-facing systems — are themselves moving targets. An organization built to address them should probably expect to keep moving as well.