This guide is for people at 18F who are wondering what to expect from a product manager on their team, as well as for product managers and those filling that role to understand what their team expects from them. This guide also serves as a resource for product management best practices at 18F (generalized to apply to any of the specific types of product work we do, like Custom Partner Solutions (CPS) projects, product or platform work, Acquisition projects, consulting, etc.)
Product Management at 18F
As a product manager at 18F, you may be put in a client-facing role to help a government partner build a mission critical product. You may also be working on one of TTS’s flagship products, like eRegs, Federalist, cloud.gov or login.gov. In all cases, you will create or steward the product vision and strategy, and drive a cross-functional team to deliver the right product to the right audience. We will talk more about this in the “Defining the Future State” section.
You will also focus on sustainability: Anything we build should empower our partner agencies to better meet their mission, be relatively easy for them to adopt and support, and be easy for end users to use. If we are building something with a partner, the product needs to be constructed and hosted in a way that the partner can manage, and the partner should be empowered to take over after we leave. We will talk more about this in the “We help our partners do Product by themselves” section.