18F Blog

At 18F, we have employees across the U.S. Over time, we’ve cultivated our best practices for distributed teams and design methods. Yet, doing research as a remote team is still really hard. Here are some things that we’ve found make it easier.

Often when developing open source software, and especially software that relies on outside services, you’ll find that you have to manage sensitive information. While there are a large number of things that can be considered sensitive, open source developers often deal with sensitive items such as API tokens, passwords, and private keys that are required for the system to function. Here's how we approached keeping this information safe.

Recently, 18F released a new version of the Method Cards, a collection of tools that offer simple, “how-to” descriptions of research and design methods with a special emphasis on the use of those methods in government work. With this new release, the Method Cards have become easier to read and understand, as well as easier to print and circulate.

As custom software development becomes integral to accomplishing any program’s mission, many managers in government find themselves faced with handling the unfamiliar: overseeing the design and implementation of a digital product that is functional and user-friendly.

The Technology Transformation Services (TTS) has been working with the Forest Service in an effort to move their permitting process online. We’ve previously written about how doing this work in the open can benefit other agencies with permit systems. In this post, we’ll focus on why it’s important to have a product owner, what that looks like from the Forest Service’s perspective, and why a product owner is critical to successful projects.