---
title: "About this guide"
source: 18F Guides
source_url: https://github.com/18F/guides
licence: CC0-1.0
domain: engineering
subdomain: 18f-guides
date_added: 2026-04-25
---

18F product managers lead cross-functional teams of researchers, designers, and engineers to help government agencies develop a product vision, craft a product strategy, and successfully deliver software using user-centered and agile approaches.

The 18F Product Guide is primarily written for consulting product managers at 18F, offering resources for product management best practices across multiple phases and types of consulting work. This guide also communicates what a team might expect from a product manager. As such, we hope it will be a useful reference for anyone new to product management in government or new to working with a product manager.

## How to use this guide

As a product manager at 18F, you may find yourself in a partner-facing consulting role to help a government agency build or buy a mission-critical product. As we work across the entire federal government and can now support state and local governments, you may encounter subject matter that is entirely new to you. Or, you may be working on one of TTS’ flagship products, like [cloud.gov Pages](https://cloud.gov/pages), [cloud.gov](https://cloud.gov/) or [login.gov](https://login.gov/).

In all cases, you will develop and steward a product vision and strategy, and drive a cross-functional team to deliver the right product to the right audience. This involves different activities and priorities at different phases of the work. Whether you're in discovery or implementation mode, you are creating the space and opportunity for your team to deliver on intended outcomes, rooted in empathy and evidence, that benefit members of the public and the government employees who serve them.

We created this guide for your reference. It’s here for a refresher on writing compelling vision statements, or for quick access to roadmap templates, skill building workshops, presentations, etc. You’re also welcome to read it from start to finish, of course.

This guide is divided into 4 sections:

- [**Discover the current state**]({{ './discover/' | url }}) describes key elements of our discovery work, where we seek to understand [users and their needs]({{'./discover/users/' | url }}), [stakeholders and their priorities]({{'./discover/stakeholders/' | url }}), their [technical landscape and requirements]({{'./discover/technical/' | url }}), and their [regulatory landscape and obligations]({{'./discover/compliance/' | url }}) so that we can help our partners make informed decisions about the path forward.

- [**Define the future state**]({{ './define/' | url }}) describes our processes for translating discovery to implementation by defining the [problem we’re solving]({{ './define/problem/' | url }}), creating an aspirational [vision for the future]({{ './define/vision/' | url }}), developing a [strategy]({{ './define/strategy/' | url }}) to achieve those outcomes, and crafting a [roadmap]({{ './define/roadmap/' | url }}) to get there. This strategic work, focused on goals rather than a specific destination, is essential for ensuring the success of government technology projects in environments where people, priorities, and policies regularly shift.

- [**Deliver incremental value**]({{ './deliver/' | url }}) describes how we [build products]({{ './deliver/build/' | url }}) iteratively following agile principles, [collaborate and communicate]({{ './deliver/collaborate/' | url }}) transparently, and [measure success]({{ './deliver/measure/' | url }}) as we go so that we can reduce risk and uncertainty, adjust or pivot as we learn, and develop solutions with impact.

- [**Enable partners**]({{ './partners/' | url }}) describes our unique approach to ensuring our agency partners build or buy sustainably and to creating a culture of long-term, government-led product ownership so that they can maintain their digital products after we leave. This is accomplished through helping our partners [develop product leadership capacity]({{ './partners/capacity/' | url }}), [coaching on product ownership]({{ './partners/coach/' | url }}), preparing them to [manage an agile vendor]({{ './partners/vendor/' | url }}), and planning from the beginning for that [transition]({{ './partners/transition/' | url }}) so that partner agencies can successfully practice product ownership in government on their own.

This guide and our approach to product management are informed by several frameworks that years of experience have shown to be effective in driving low-risk, successful technology projects in government:

- **[Agile delivery](https://guides.18f.gov/agile/)**: iteratively develop functional software, deploying and testing continuously.

- **[User-centered design](https://guides.18f.gov/ux-guide/)**: design with, not for the users of a system or government service.

- **[Build and communicate in the open](https://18f.gsa.gov/2016/03/07/the-need-for-transparency-in-government/)**: build trust through transparency.

- **[Low-risk technology acquisition](https://derisking-guide.18f.gov/federal-field-guide/basic-principles/#modular-contracting)**: ensure that purchasing software services or off the shelf products is low risk and contracts are structured modularly.

If you have any suggestions for improving this guide or want to get involved, read our [contributing page](https://github.com/18F/guides/blob/main/CONTRIBUTING.md); find us on Slack in #product; or [create an issue in GitHub](https://github.com/18F/guides/issues).

## Reusing this guide in other organizations

As a work of the federal government, this project is in the public domain within the United States. Additionally, we waive copyright and related rights in the work worldwide through the [CC0 1.0 Universal public domain dedication](https://creativecommons.org/publicdomain/zero/1.0/legalcode).

This guide is written for internal use and is shared in the spirit of open source. We encourage you to make a copy of this guide and adapt it to your organizational needs. This guide is just that: a guide. It’s not meant to provide the final opinion on any of the topics discussed. If a certain section isn’t relevant to you and your team, delete it. And if you feel the guide is missing a section, by all means, add it. This guide is yours to use, and we trust you’ll update it in the ways that best suit you.
