The Product Model in Government

Marty Cagan and Stacey Langer argue that the product model, though born in commercial product companies, fits government technology work because government also aims to create value and achieve outcomes, just measured differently than profit. They outline government's advantages (mission-driven staff, public focus on outcomes, a captive audience) and its challenges (viability constraints like legal, privacy and ethics; fraud risk; project-based procurement inherited from physical-goods contracting; heavy stakeholder complexity; and a mix of staffing models). They then offer techniques for success: centering on users, securing leadership sponsors, using realistic prototypes to win over approvers, staffing small cross-functional teams, reframing annual projects into rapid discovery and delivery iterations, insisting on strong product, design and technology leadership, and continuously evangelizing results. The piece matters for anyone trying to apply product practices in regulated or publicly funded settings.

01Key takeaways

• Frame government work around outcomes and user impact rather than profit, since value is still the goal.
• Use realistic high-fidelity prototypes instead of slide decks to win over skeptical stakeholders and approvers.
• Find at least one senior leader who is invested in the mission and willing to work differently to clear obstacles.
• Break a one-year funded project into weekly discovery prototypes and bi-weekly delivery releases to learn continuously.
• Keep product, design and technology leadership in-house, since systems integrators may try to take over these roles.
• Keep evangelizing outcomes and insights so sponsors continue investing rather than chasing the next priority.

02Key sections

Why the product model fits government

Governments may not chase profit, but they still need to maximize positive impact, which demands a clear outcome focus. Public scrutiny makes waste and poor outcomes especially costly.

Government's advantages

Mission-driven staff, public pressure for outcomes, and a captive audience with little competition give product teams useful starting conditions, though marketing still matters.

Government's challenges

Viability (legal, policy, privacy, security, ethics), fraud risk, project-based procurement inherited from physical-goods contracting, stakeholder complexity, and staffing models with outsourcing all complicate the work.

Techniques for success

Shared focus on users, executive sponsorship, high-fidelity prototypes, small skilled teams, and reframing yearlong projects into frequent discovery and delivery iterations.

Leadership roles and sustaining momentum

Heads of product, design and technology are essential and must set vision and strategy, and teams must keep evangelizing insights and outcomes so sponsors stay invested.

03From the post

“A partnership dedicated to teaching best practices to product teams and product leaders”

04Frameworks mentioned

Summary and takeaways written by PM Atlas; quotes are short excerpts. © the original author.