Testing (and re-testing) your designs with users will help you build the best possible product. Our Validate Methods cover varied testing scenarios and potential user groups.
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.
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.
This blog describes how 18F adopted a new illustration library (“18F Folks”) based on Open Peeps, to better represent diversity, context, and human experiences in their visual communications.
The Decide Methods help you derive insights from the information gathered during the Discovery phase. You’ll validate initial assumptions, develop a deeper understanding of workflows and processes, and develop design hypotheses.
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.
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.
