Applicants to federal aid programs face numerous barriers in accessing benefits they are eligible for. The Centers for Medicaid and Medicare conducted an extensive qualitative user research study to better understand applicant experience in enrolling in public assistance programs. Based on the results, the study emphasizes the need for simplified, streamlined and less burdensome application processes.
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.
Executive order by President Biden mandating that governments deliver services more equitably and effectively through simple, accessible, and transparent design.
Government solicitations to procure custom software are often long, complicated, and take months. By using 18F’s agile contract format, agencies can hire an agile software contractor with a quickly-written dozen-page solicitation, allowing for immense savings in time and money.
This brief describes the current state of SNAP benefit delivery through the electronic benefits transfer (EBT) card, identifies the features necessary for SNAP benefit delivery to ensure consistency with principles of equity and inclusion, and explores how future SNAP benefit delivery can keep up with rapid changes in commercial payment infrastructure.
18F describes journey mapping: a visualization of the major interactions shaping a user’s experience of a product or service. This allows design teams to view a service through the perspective of the user and incorporate their learnings throughout the development process.
