Need States and Awareness

People do not arrive at your product in general; they arrive in a state—a circumstance, an emotional charge, and a level of awareness about their problem and its solutions. Diagnosing that state is what lets the first surface meet them where they are.

What it is

A need state is the combination of circumstance and motivation that activates a job: not “users need expense tracking” but “it is the last day of the quarter, the receipts pile has become unbearable, and I feel behind.” The same person cycles through different need states; the same need state recurs across very different people. Need states carry emotion by definition—urgency, dread, hope, embarrassment—which is why they, not demographics, are the natural unit for emotional design.

Awareness is the second axis: how far the person has already travelled toward a solution. Eugene Schwartz’s five stages of awareness (from Breakthrough Advertising, 1966) remain the standard vocabulary:

flowchart LR
  U[Unaware] --> P[Problem-aware]
  P --> S[Solution-aware]
  S --> Pr[Product-aware]
  Pr --> M[Most aware]

1. Unaware — does not yet recognise the problem.
2. Problem-aware — feels the pain, does not know solutions exist.
3. Solution-aware — knows the category exists, not your product.
4. Product-aware — knows your product, is comparing and doubting.
5. Most aware — convinced, needs only a fair final step.

Design moves people one stage at a time. Jumping from problem-aware to paying is where pressure tactics breed.

Why it works

Mismatch between a surface and the arriving state is one of the most common emotional failures in product design. A feature tour is welcome to a solution-aware evaluator and noise to a problem-aware arrival who needs their pain named first. A discount feels helpful at most-aware and cheapens the product at problem-aware. “Why don’t users get it?” is usually a diagnosis error: the surface was written for a state its visitors are not in.

The forces of progress (from the Jobs-to-be-Done tradition) complete the diagnosis:

flowchart LR
  Push[Push of the struggle] --> Switch{Switch?}
  Pull[Pull of a better way] --> Switch
  Anxiety[Anxiety about change] -.->|holds| Switch
  Habit[Habit of the present] -.->|holds| Switch
  Switch -->|yes| New[Hire your product]
  Switch -->|no| Stay[Stay with current alternative]

Push and pull supply motivation; anxiety and habit are the emotional friction discovery must surface—because your product, not your marketing, is what has to defuse them (Sandbox Experience, Fail Safe, Effort Moat). The habit force is the physics of the present alternative (Habit Formation); pressure that jumps someone from problem-aware to paying fails User Agency.

Going deeper

Diagnosing need states in discovery interviews:

1. Reconstruct real episodes, not opinions. “Walk me through the last time this became urgent” recovers the circumstance, the trigger, and the emotion; “how important is this problem to you?” recovers politeness. The trigger event—what made that day the day they went looking—is the single highest-value fact in the interview.
2. Capture the emotional vocabulary verbatim. The words people use for their state (“drowning,” “flying blind,” “babysitting the spreadsheet”) are both diagnostic data and future copy (see How Customers Talk, Search, and Buy).
3. Map states to entry points. Different need states arrive through different doors: a problem-aware reader lands on a blog post; a product-aware evaluator lands on pricing; a most-aware buyer arrives from a referral and just wants signup to not fumble the handoff. Each entrance deserves a surface tuned to its state.
4. Design the state transition, not just the conversion. A surface’s job is to move a person one stage—problem-aware to solution-aware, product-aware to convinced—by teaching, demonstrating, or de-risking (Spark Curiosity, Sandbox Experience). Trying to jump someone from problem-aware to paying in one screen is where pressure tactics breed.

For builders and agents

Need states are routing logic: entry point, referrer, campaign, and first-session behaviour are the observable proxies for the arriving state. Landing every source on the same generic homepage is a decision to serve one state and disappoint the rest (Deep-link). Instrument the trigger, not just the visit: the events preceding signup tell you which state your acquisition actually attracts—often not the state the product was designed for, which explains many “activation problems.”

Onboarding questions are state diagnosis when they change what happens next (“what brings you here today?” → different first-run paths) and are friction when they do not (Commitment, Intent Mirroring). For agents reviewing a surface: identify which awareness stage the copy assumes, then check which stage actually arrives there. Flag mismatches—the fix is usually rewriting for the real state or re-routing the traffic, not more persuasion.

When to use it

• Choosing first-run, landing, or campaign surfaces
• Diagnosing “users don’t get it” (often wrong state, not wrong IQ)
• Designing state transitions (Sandbox Experience, Spark Curiosity)
• Instrumenting acquisition: which state does traffic actually bring?

Do

• Reconstruct real episodes; capture trigger, circumstance, and emotion
• Capture emotional vocabulary verbatim for later copy
• Map states to entry points (blog ≠ pricing ≠ referral signup)
• Move one awareness stage per surface; de-risk rather than leap to payment
• Use onboarding questions only when answers change the path

Don’t

• Write one generic homepage for every arrival state
• Jump problem-aware users straight to pay with pressure tactics
• Ask “how important is this?” instead of reconstructing the last episode
• Ignore anxiety and habit forces when diagnosing switch resistance

Founder Tip

The trigger event—what made that day the day they went looking—is usually the highest-value fact in the interview.

Make It Yours

1. List entry doors — search, referral, comparison, cold homepage—and the state each implies.
2. Name the trigger — for your ICP’s last real episode.
3. One-stage job — for each key surface: from which stage to which next stage?
4. Check traffic — do referrers and campaigns match the state your copy assumes?

Insights & Metrics

1. Trigger capture rate — Interviews with a concrete trigger event ÷ Total discovery interviews.
2. State mismatch — Sessions where assumed awareness ≠ inferred arrival.
3. Stage-appropriate conversion — Conversion by entry state; watch for pressure spikes on problem-aware traffic.

Behind the Data

• Which awareness stage does your highest-volume channel actually deliver?
• Where do you ask people to skip a stage?
• Do activation “problems” track a state mismatch more than a feature gap?

Related concepts

• Jobs-to-be-Done, Friction, User Agency, Habit Formation
• Consumed by: Onboarding, Conversion Optimisation, Intent Shaping, Sandbox Experience, Deep-link

Further reading

• Eugene Schwartz (Wikipedia) — Breakthrough Advertising and five stages of awareness.
• The Ultimate Guide to JTBD with Bob Moesta (Lenny’s Newsletter) — Forces of progress; switch interviews.
• Know Your Customers’ “Jobs to Be Done” (HBR) — Circumstance-first demand.
• Empathy Mapping (NN/g) — Say / think / do / feel in a state.

Agent skill

• Primary command: /productfeeling jobs — before/during/after emotional jobs tied to the arriving state
• Related commands: /productfeeling persona, /productfeeling map, /productfeeling sequence (Customer discovery)
• When the agent should load this page: “need state”, “awareness stage”, “why now”, “trigger”, “arrival state”
• Companion handoff: DocSlime — entry states and journey notes in docs/experience/. Impeccable after synthesis. RedTeam if locking a funnel that jumps stages. No external discovery skill.
• Feeling north star this practice serves: meet people in the state they are in
• Anti-goals: stage-jumping pressure, one surface for every arrival, hypothetical “importance” instead of episodes
• Reference path: skill/reference/jobs.md
• Durable DocSlime targets: docs/experience/ (need states, entry doors, journey stages)