The backwards way I analyze markets
Your stakeholders want market analysis. You want to design products people love. These goals should align, but most market research frameworks were built for MBAs, not designers.
I’m a product designer who spent years treating market analysis as homework to rush through before “real work” started. Then I discovered that market analysis, done right, is design research with better data.
Here’s the framework I use to conduct market analysis that actually improves design decisions.
Start with a sharp question
Market analysis without a specific objective produces generic insights nobody uses. I define exactly what decision this research will inform.
Entering a new market? I need broad landscape understanding and competitive positioning.
Launching a new feature? I need tight focus on specific user segments and their current workarounds.
Benchmarking competitors? I need behavioral data on why users switch between products.
The objective shapes everything downstream. Nail this first.
Collect data like a designer
Market research has two halves: numbers and stories. I need both.
Quantitative data comes from surveys, market reports, product analytics, and industry databases. This tells me how many people exist in each segment, growth rates, and behavioral patterns at scale.
Qualitative data comes from user interviews, support conversations, online forums, and competitive product teardowns. This tells me why patterns exist and what needs go unmet.
Most designers are comfortable with qualitative research but skimp on quantitative analysis. Most business analysts do the opposite. I force myself to gather both in equal measure.
Segment by problems, not profiles
This is where traditional market analysis loses designers. Segmenting by age, income, or geography produces categories that don’t help design decisions.
