Problem x Customer

🎯 Problems

Most teams reach pain points and stop. Real problems have three dimensions — Goals, Obstacles, and Needs. Miss one and you're building something people understand but don't fight to keep.

1. Write Your Current Problem StatementCommit your current hypothesis to paper before analyzing it — you can't diagnose what you haven't made explicit.
   • Write one sentence describing the problem, exactly as you'd say it in a pitch — don't edit it
   • Identify which dimension it reaches: Goal (what they're achieving), Obstacle (what's in the way), or Need (why it deeply matters)
   • Most first drafts are obstacle-level — that's one dimension of three
   • Name inaction and the status quo explicitly — "do nothing" is always a competitor
2. Map All Three DimensionsStop at obstacles and you'll build a feature — get to needs and you'll build something people fight to keep.
   • Goals: What is the customer ultimately trying to achieve? The evergreen version, not just the immediate ask (e.g., belonging, certainty, competitive edge)
   • Obstacles: What's in the way right now? This is what most founders call "the problem" — but it's only the middle layer
   • Needs: Why does this deeply matter? Ask "why does this matter?" three times — stop when you hit something emotional, social, or functional that feels unavoidable
   • Draft a full problem statement: "Our customer is a [role] who is trying to [goal] but struggles with [obstacle] and will still try/switch because [why it matters]"
3. Test Your Insight — What / So What / Now WhatA useful insight has all three layers — if the So What doesn't surprise you, it won't surprise anyone else.
   • What? The main finding — what you heard or observed
   • So What? Why is this surprising? What assumption does it challenge? This is the most-often-missing layer
   • Now What? What decision does this change? If the answer is "nothing," it's a report — not an insight
   • If So What doesn't challenge an assumption, keep digging — surface-level insights produce surface-level products
4. Prioritize Across Four LensesIf you have multiple problems to choose from, score each one rather than defaulting to the most familiar.
   • Desirability: Is the problem urgent, frequent, and painful enough that people will change behavior?
   • Team Fit: Does your team have an irrational drive and decade-long fuel to solve this?
   • Feasibility: Do you have a unique insight or capability others don't?
   • The problem that scores highest across all four lenses — not just one — is where to start

• My problem statement reaches all three layers: Goals, Obstacles, and Needs
• The needs layer names something emotional, social, or functional — not just "inconvenient"
• My So What challenges an assumption — if it doesn't surprise me, it won't surprise anyone
• I've named inaction and the status quo as real competitors
• If I have multiple problems, I've scored them and have a principled basis for my choice

👤 Customers

Most founders describe their customer using demographics — job title, company size, industry. That tells you who they are on paper. It doesn't tell you why they'd switch. A strong ICP starts with mindset and use case, then works backward to who fits that profile.

1. Run a Bright Spot AnalysisYour three best existing customers contain more signal than 100 brainstormed hypotheses — start there.
   • Pick your 3 best customers: most value delivered, longest retained, most enthusiastic
   • For each, map: what triggered them, what pain they had, what they were doing before, why they stay
   • Spot the patterns — what do they share in terms of trigger, pain, and before-state?
   • Note what surprised you — unexpected patterns are often the most valuable signal
2. Draft Your ICP Hypothesis — Psychographics FirstDemographics describe; psychographics explain — start from use case and you build something excellent, start from demographics and you get the diluted middle.
   • Define what your ideal customer believes, wants, and fears before naming their job title or company size
   • Map: their goals, the obstacles in their way, why it deeply matters, and what they're doing instead of using you
   • Identify the trigger moment — the event, frustration, or inflection point that prompts them to act
   • This is v1 — meant to be tested, not defended; revisit it after every customer sprint
3. Pressure-Test with ExclusionA good ICP excludes someone — if it doesn't, it's not specific enough.
   • Name who your ICP explicitly excludes — if the answer is "no one," it's too broad
   • The narrower wedge is not the limit of your vision — it's how you earn the right to expand
   • For marketplaces: decide which side to serve first — serve two masters and you'll serve neither
   • A smart outsider reading your ICP should be able to name exactly who you're building for — and who you're not

• My ICP starts with psychographics — what they believe, want, and fear — not just who they are on paper
• My ICP excludes someone — I can name who it's not for
• I've named what they're doing instead of using me, including inaction as a competitor
• If I have multiple candidate segments, I've picked one to lead with

🔁 Behavior

Knowing a problem exists isn't enough. You need to understand why the behavior is hard to change before you can design something that actually sticks. The Fogg model (B=MAP) gives you three diagnostic levers.

1. Name the Real CompetitorInaction is always a competitor — "do nothing" is free, familiar, and requires no learning curve.
   • Name every real alternative: workarounds, incumbents, adjacent tools, and inaction
   • Identify what the status quo does well — you need to understand why it's "good enough" before you can beat it
   • Your product needs to be ~9–10x better than the status quo in your customer's estimation, not yours
   • If "do nothing" beats you, either the problem isn't urgent enough or your solution isn't differentiated enough
2. Build Your Customer's MAP ProfileBehavior happens when Motivation, Ability, and Prompt converge at the same moment — miss one leg and the behavior doesn't happen, no matter how good the product.
   • Motivation (why): Anticipation (hopes/fears), sensation (pleasure/pain), belonging (acceptance/rejection) — most products over-invest here; it's rarely the bottleneck
   • Ability (how): Time, money, physical effort, mental effort, routine disruption — the real leverage is almost always here; mental effort and routine disruption are most underestimated
   • Prompt (when/where): External (notifications, word of mouth) or internal (recurring frustration, scheduled moment)
   • When something isn't working — not converting, not coming back — ask which leg of MAP is missing; that's the fix, not another feature
3. Apply the 10x TestAbstract behavioral understanding becomes concrete product and GTM decisions when you map it to specific moments.
   • Pick the 3–5 moments that matter most: awareness, first use, ongoing use
   • Overlay MAP on each moment — which element is weakest? What would maximize it?
   • Ask: is your solution genuinely 9–10x better than the status quo at each critical moment, from the customer's perspective?
   • If you can't articulate where specifically, that gap in your answer is a product gap

• I've named the real competitor — including inaction
• I know which 1–2 ability barriers are highest for my customer
• I've identified at least one external and one internal prompt
• I can articulate where my solution is 9–10x better — in their terms, not mine

📢 Positioning

Positioning is the work of translating your ICP into language. Most positioning fails because it's written from the inside out — for the board, not for the person with the problem. What you can't say clearly, you don't yet know.

1. Confirm Your Inputs Are ReadyGaps in positioning almost always trace back upstream — check your ICP and problem statement first.
   • You have a prioritized ICP — one specific customer type, psychographics first
   • You have a problem statement with all three dimensions: Goals, Obstacles, and Why it matters
   • You have at least one real customer quote or language from actual conversations
   • You have a clear answer to: what were they doing before you?
2. Draft the Five-Component Positioning StatementGood positioning excludes — if your statement could describe three other companies, it's a category description, not a position.
   • For [target customer — specific situation, not just demographics]
   • Who [problem in their words — use the language your best customers use]
   • [Product] is a [simple, honest product category — not a vision statement]
   • That [key benefit — functional first, then emotional; earn the emotional claim]
   • Unlike [the real alternative — what they were doing before you, often a workaround or inaction, not a named competitor]
3. Write the 25-Word VersionIf it sounds like a press release, it's not positioning yet — it's a category description.
   • No buzzwords — should sound like something a real customer would say to a friend
   • Read it out loud; if it sounds unnatural, rewrite it
   • Start from what your best customers say when they describe you to someone else — that language is your positioning draft
   • Positioning reveals gaps: if you can't fill in the "unlike" line, you don't yet know your real competitor
4. Run the Three Sanity ChecksAll three should pass before you ship the language downstream to hiring, sales, or marketing.
   • Referral test: Would a happy customer actually say this to a friend?
   • Exclusion test: Does this statement exclude someone? Name who it's not for
   • 'I need that' test: When you pitch this, what parts make people lean in vs. glaze over?
   • Fuzzy positioning creates fuzzy everything downstream — misaligned hires, reactive roadmaps, messaging that resonates with no one

• My positioning has all five components filled in
• The "unlike" line names the real alternative — not a named competitor if the real answer is a workaround or inaction
• My 25-word version sounds like something a real customer would say to a friend
• My positioning excludes someone — I can name who it's not for

🎤 Pitch Prep

A pitch that's accurate but doesn't generate urgency has a structure problem, not a content problem. The What / So What / Now What framework turns your customer research into a narrative arc that makes your audience feel the problem before they hear the solution.

1. Orient Your Audience — WhatMost pitches skip So What and go straight from What to Now What — that's why audiences nod but don't lean in.
   • Set the world today: one tight paragraph orienting a smart outsider to the space
   • Introduce your customer with psychographics first — goals, obstacles, why it matters — then demographic sketch
   • Include a real customer quote or moment in their language, not yours — one real voice beats three summarizing sentences
   • Show the trigger moment: what event or frustration prompts them to look for a solution?
2. Make Them Feel It — So WhatThe emotional case — the cost of not solving this — is what makes the ask feel inevitable, not just logical.
   • Name the cost of inaction — keep asking "why does this matter?" until you hit something unavoidable
   • Show the status quo and why it's not good enough — how are they coping today, and at what cost?
   • Paint the hope: what does their world look like if this problem is actually solved?
   • Answer Why Now with something specific — "AI is moving fast" doesn't count; name the structural shift
3. Earn the Ask — Now WhatYour solution should feel like the only logical conclusion to the problem you've built — not a pivot from it.
   • State your vision in 1–2 sentences — ambitious, but earned by everything that came before
   • Explain your solution in terms of the specific obstacles named in the What section
   • Answer Why You — the insight, access, or capability that makes you the right person to build this
   • Make the ask concrete: what you need and what you'll do with it

• My problem slide shows the cost of not solving it — it doesn't just name the pain point
• I have at least one real customer quote or story in the What section
• My So What has a clear cost of inaction — emotional, functional, or financial
• My Why Now is specific, not generic
• Every major claim has a show + tell version — not just a statement

🧱 Product Pillars

Pillars are the 3–5 named customer needs that anchor your product decisions. They live one level above features and one level below vision. When your roadmap feels reactive — or when your team uses different language for what you're building — pillars are what's missing.

1. Surface Raw Needs from ResearchFeatures without pillars create a roadmap that grows sideways — every reasonable request gets added and the product gets wider and shallower.
   • List everything customers fundamentally need from you — from interviews, support tickets, sales calls, and churn feedback
   • Quantity first, don't filter — aim for 15–20 raw needs before clustering
   • Ask: what do your best customers praise most? What do churned customers say they were missing?
   • Pick your most-requested feature from the last quarter, then ask "why" three times — the underlying need is probably a pillar
2. Cluster and Name Into 3–5 PillarsPillars are named customer needs — not features, not values, not vision statements.
   • Group related raw needs and find the underlying need behind each cluster
   • Name each cluster as a noun from the customer's perspective (e.g., Demand, Efficiency, Quality, Partnership)
   • Write the pillar definition: "Our customers need [pillar name] — which means [what success looks like for them on this dimension]"
   • Aim for 3–5 pillars — not 7, not 2; if you can't explain each in one sentence, keep clustering
3. Map Your Roadmap to Pillars and Pressure-TestEach pillar should help you say no to at least one feature request — that's the mechanism for keeping the product deep.
   • Map your current roadmap to pillars — which features belong where?
   • Anything that doesn't map to a pillar is a candidate for cutting or deferring
   • Ask: which pillar is most important right now — and which is most at risk?
   • Test team alignment: can everyone independently name the pillars from memory? If not, keep refining

• Each pillar represents a customer need — not a feature, a value, or an internal goal
• I can explain each pillar in one sentence from the customer's perspective
• I have 3–5 pillars — not 7, not 2
• Each pillar helps me say no to at least one feature request
• My team can independently name the pillars from memory

Resources