This update highlights progress in improving federal customer experience (CX) following Executive Order 14058, showcasing service enhancements across agencies.
The U.S. Web Design System (USWDS) is makes it easier to build accessible, mobile-friendly government websites. USWDS is an active open source community of government engineers, content specialists, and designers. Its contributors both in and out of government support dozens of agencies and nearly 200 sites.
Handbook by 18F designed for executives, budget specialists, legislators, and other “non-technical” decision-makers who fund or oversee state government technology projects that receive federal funding and implement the necessary technology to support federal programs. It aids in setting projects up for success by asking the right questions, identifying the right outcomes, and equally important, empowering decision-makers with a basic knowledge of the fundamental principles of modern software design.
The US General Services Administration announces that it is seeking a limited number of state and local government partners to take advantage of login.gov to administer their federally funded programs.
Described as the “public’s one account for government,” this U.S. government website allows users to use one account and password for secure, private access to participating government agencies.
The Administration for Children and Families’ Office of Family Assistance (OFA) worked with 18F to replace its legacy data reporting system through product management training, user research, and an assisted acquisition.
Policy changes are often dynamic and occur quickly, but they can only create impact once implemented. The Eligibility APIs Initiative at 18F shares an example from their work that shows the potential for rapid, accurate policy implementation as code.
18F describes modular contracting, the process of breaking up large, custom software procurements into a small constellation of smaller contracts. Modular procurement requires agile, product thinking, user-centered design, DevSecOps, and loosely-coupled architecture.
It is frequently assumed that when rules are implemented as code, a rules engine is necessary. However, it is possible for policy people and engineers to effectively work together to code logic that drives technological system without needing a mediating rules engine at all.
Few large government software projects are successful, as current ecosystems in place at agencies do not support agile development practices. This guide provides instructions to federal agencies on how to effectively budget for, procure, and oversee software development projects.
Programs like Medicaid and SNAP are managed at the federal level, administered at the state level, and often executed at the local level. Because there are so many in-betweens, there is significant duplicated effort, demonstrating the need to simplify eligibility rules to facilitate easier implementation.
