The Public Sector Product Canvas

Clear thinking for product teams in the public sector

The Public Sector Product Canvas is a purpose-built strategic thinking tool for teams building digital products and services in the public sector. It's designed for the reality of delivery in government: political constraints, legacy systems, and a complex stakeholder landscape.

Who is this for?

  • You're building digital products in central government, local authorities, or public agencies

  • You need to navigate political reality, legacy systems, and stakeholder veto power

  • You're fed up of frameworks built for startups or private companies focused on adoption / revenue and competition

  • You want your whole team aligned on strategy, visible on a page

Why existing frameworks don't fit

The Business Model Canvas asks about revenue streams when you're effectively building a monopoly funded by the Treasury (there aren't competitor products when applying for a passport, submitting planning permission or paying your taxes).It assumes you can pivot, when you're bound by legislation or legacy systems.Government products have legacy integration problems, stakeholder veto problems, and ministerial change problems - not revenue generation or customer acquisition problems.

The Public Sector Product Canvas is an evolution of the Business Model Canvas - it's a tool built for the world we're actually working in.

HOW IT'S STRUCTURED

Nine boxes across three layers: your product strategy broken down on a single page.

STRATEGY LAYER: BUILD THE RIGHT THING

  • Context: What reality are you working within?

  • Problem: What's broken, how do you know it's broken, and which bits are you tackling?

  • Vision and value: What does the future look like, and why does it matter?

PRODUCT LAYER: BUILD THE THING RIGHT

  • Users: Who are you building for? What changes for them?

  • Design and tech stack: What's the shape of your solution? What are the major technical components and tech choices?

  • Coherence: How will a new thing replace or work alongside what's currently happening?

DELIVERY LAYER: NAVIGATE THE REALITY

  • Stakeholders and org landscape: Who has influence / veto power? Why do they care?

  • Risks and constraints: What could kill this? What non-negotiable constraints exist? (laws, budget, contracts, legacy)

  • Milestones: What are the key delivery dates and decision points?

Use it for

  • Struggling to get budget approval? Use for business cases

  • New team members lost? Use for onboarding

  • Stakeholders asking "what's the plan"? Use for governance reviews

  • Joined a new project? Use it to build context and get up to speed

  • Team not aligned? Use for strategy workshops

  • Need to communicate with senior leaders? Use for stakeholder communication

NEED MORE HELP?

The field guide explains each box in more detail - what to fill in, questions to ask, and mistakes to avoid. It includes examples, workshop tips, and the thinking behind each layer.Use it as a reference when you're stuck or want to go deeper on specific sections.

About

This emerged from years watching government product teams wrestle with frameworks that just don't fit. Government digital work needs tools built for its messy reality: complex stakeholder politics, heaps of legacy infrastructure, and products that must survive scrutiny, meet user needs - and cohere with what exists right now.Created by Joe Hart. I'm a product manager who builds digital products and services across the UK public sector.This is v1.0 as of Jan 2026 - I'll continue to iterate based on feedback over time.

CONTACT

Using this with your team? I'm collecting examples and feedback for the next version. I'd love to hear what's working and what needs improving. Please get in touch.

Created by Joe Hart in 2026. Licensed under Creative Commons 4.0. Free to use, adapt and share with attribution.