Design decisions don't happen in a vacuum — a feature that's great for the user but breaks how the product actually makes money won't survive contact with a real business, no matter how well-designed it is. Understanding the business model isn't a detour from design work; it's context that makes design decisions defensible.
A one-page framework (Alexander Osterwalder) breaking a business into 9 building blocks: Customer Segments (who it's for), Value Proposition (what problem it solves), Channels (how it reaches customers), Customer Relationships (how it interacts with them), Revenue Streams (how it makes money), Key Resources, Key Activities, Key Partnerships, and Cost Structure. Filling this in for an existing product, even roughly, quickly surfaces which design decisions actually matter to the business and which are purely cosmetic preference.
Ash Maurya's adaptation swaps a few blocks for ones more relevant to an early, unproven product: Problem (the top 1-3 problems worth solving), Solution, Key Metrics, an Unfair Advantage (something competitors can't easily copy), replacing Key Resources/Activities/Partnerships from the original canvas. It's built for a product that doesn't have paying customers or proven revenue yet.
| Question a designer should be able to answer | Canvas block it maps to |
|---|---|
| Who is this actually for? | Customer Segments |
| What problem does this solve that a competitor doesn't? | Value Proposition / Unfair Advantage |
| How does this product actually make money? | Revenue Streams |
| What number does this feature need to move to matter? | Key Metrics |
Why this is worth 20 minutes
A designer who can answer these four questions about a product they're working on can defend a design decision in business terms, not just aesthetic ones — a genuinely useful skill in any real product conversation.