When does it happen, who does it hurt, how badly, and what do they do today instead? Get these four right and the solution often writes itself.
Layout
Problem Statement Canvas
7 blocks · 3-row grid
What it is
Seven sharp questions about a problem worth solving. The top row sets the scene (Context, Problem, Alternatives). The bottom row makes it specific (Customers, Emotional Impact, Quantifiable Impact, Alternative Shortcomings). The canvas is "done" when you could brief an outsider in two minutes and they'd know what to build.
Origin
A problem-statement canvas in the lineage of the product-discovery brief, mental-model interview research, and the design-thinking "How Might We" rubric. The shape is open-source — most product teams adapt it to fit their own discovery rituals, but the seven cells here cover the questions worth answering before any build commits.
When to reach for it
You're about to commit engineering time to a new feature or product and want to write down the brief.
A stakeholder hands you a "we need X" request and you suspect X is the symptom, not the cause.
You're writing the first slide of an investor or board update and need the problem framed precisely.
The blocks
Worked example uses Airbnb's founding problem (the IDSA design conference, San Francisco).
What good looks like
The situation in which the problem occurs. When, where, under what conditions — set the scene before describing the wound.
Example — Airbnb's founding problem (the IDSA design conference, San Francisco)
A major industry conference is happening in a city. Hotels within walking distance are sold out months in advance. Out-of-town attendees are paying $300+/night for hotels an hour away, or skipping the conference entirely.
What good looks like
The specific pain in one sentence. Plain language, no jargon. "Wait, that's their problem?" should be the reaction.
Example — Airbnb's founding problem (the IDSA design conference, San Francisco)
Conference attendees can't find affordable, central lodging — and locals with a spare bedroom or couch have no safe, paid way to host them.
What good looks like
What the customer uses today — even if it's a Google Doc, a spreadsheet, or doing nothing. Each alternative is a competitor.
Example — Airbnb's founding problem (the IDSA design conference, San Francisco)
Sold-out central hotels, distant hotels with a long commute, Craigslist sublets (no identity, no reviews, no escrow), Couchsurfing (free, awkward, no payment), or staying home and skipping the trip.
What good looks like
Who hurts when the problem happens. Named segments, ideally with a count or a representative profile.
Example — Airbnb's founding problem (the IDSA design conference, San Francisco)
Industry-event attendees — designers, developers, conference-goers — travelling to major cities. On the supply side: urban residents with a spare room they're not using during peak event weeks.
What good looks like
How the problem makes the customer feel. Frustration, embarrassment, fear, fatigue — emotions sell, but they also reveal severity.
Example — Airbnb's founding problem (the IDSA design conference, San Francisco)
Frustration at the cost and the commute, social FOMO at missing the after-hours conference networking, anxiety about the safety of Craigslist, and resignation when the only option is to stay home.
What good looks like
Numbers. Hours lost, dollars wasted, accounts churned, deals missed. Without a number, the problem isn't prioritised.
Example — Airbnb's founding problem (the IDSA design conference, San Francisco)
$300–$500 per night for distant hotels. 1+ hour daily commute lost to travel. Roughly 30% of would-be attendees skipping the conference because they cannot afford lodging.
What good looks like
Why the alternatives fail. Each shortcoming is a hook for your value proposition.
Example — Airbnb's founding problem (the IDSA design conference, San Francisco)
Hotels are sold out or far away. Craigslist has no identity, no reviews, no payment escrow. Couchsurfing has no payment guarantee, so hosts who would happily rent out a room won't list. "Stay home" loses the entire conference.
How to use it
Fill Context and Problem together — neither makes sense without the other.
Then jump to Customers and Quantifiable Impact. Severity without specificity is hand-waving.
Inventory Alternatives explicitly — and the Shortcomings of each. The shortcoming is where your wedge lives.
Read the canvas as a brief. If you can't hand it to a designer and have them sketch the solution, the canvas isn't done.
Common mistakes
Stating the problem as the absence of your solution. "They don't use AI" is not a problem statement.
Skipping Quantifiable Impact. If you can't put a number on it, you can't prioritise it.
Treating "alternatives" as only competitor products — ignoring spreadsheets, manual work, and "doing nothing".
Spin up the canvas in one click. Copilot will score every cell against the same rubric this guide describes.
Keep reading