Write to the Symptom, Not the Solution

Topic

Why content that addresses clients’ symptoms (what they’re experiencing) outperforms content that addresses their solutions (what you offer) — especially for AI discoverability.

Target Reader

A coach or consultant creating content that describes their methodology and transformation but isn’t attracting people at the early awareness stage. They know their work is valuable but can’t figure out why it doesn’t generate inbound interest from people who need it most.

The Fear / Frustration / Want / Aspiration

“I keep writing about what I do, but the people who need me most never find me. They’re out there struggling with the exact problems I solve, but somehow my content doesn’t reach them.”

Before State

The reader creates content from the expert’s perspective — describing the transformation, the methodology, the framework. This speaks to people who already know what they need. It misses the larger audience: people experiencing symptoms they haven’t yet connected to the reader’s domain.

After State

The reader maps the symptom layer — the fears, behaviors, emotions, and language clients use before they know what category of help they need — and creates content that meets people where they actually are, not where the reader wishes they were.

Narrative Arc

Your content solves problems for people who’ve already found you — but the biggest audience is the one that doesn’t know you exist yet. The tension: people don’t search for the answer to a problem they haven’t named. They search for the symptoms they’re experiencing. The turn: writing to symptoms instead of solutions reaches people earlier in their journey, when trust is most easily built. The resolution: a practical symptom-mapping exercise that generates a year’s worth of content ideas in an afternoon.

Core Argument

People don’t search for solutions to problems they haven’t named — they search for symptoms they’re experiencing, and content that speaks to symptoms reaches them six months earlier than content that describes solutions.

Key Evidence / Examples

• “People don’t search for the answer to the problem when they don’t even understand what the problem is. So what they perceive, and they’re grappling with, are the symptoms.” — Don Back
• Insight - Ontology Reveals What SEO Hides - The Beneath-the-Surface Client Map — the ontological framework underneath symptom mapping

Proposed Structure (5–7 beats)

1. The content blind spot — writing about what you offer vs. what they’re feeling
2. The symptom-solution gap — how far apart your language is from your client’s experience
3. The search behavior shift — what people actually type at 3 AM
4. The symptom mapping exercise — listing experiences, emotions, and behaviors that precede finding you
5. The language capture — collecting exact phrases from clients, not paraphrased into expert terms
6. The content calendar — turning symptom maps into a systematic publishing plan
7. The GEO multiplier — why symptom-layer content gets retrieved by AI engines more often

Related Insights

• Insight - Ontology Reveals What SEO Hides - The Beneath-the-Surface Client Map
• Insight - The Psychographic FAQ as Authority Infrastructure
• Insight - You Are Becoming an Answer Provider, Not Just a Website

Editorial Notes

Strong overlap with the “Clients Are Googling Their Confusion” brief — this is the tactical companion. Could be published together as a two-part series: Part 1 (ontology/strategy) and Part 2 (symptom mapping/tactics). The Don Back quote is the hook.

Next Step

• Approved for drafting
• Needs revision
• Deprioritised