“The psycho-causal graph isn’t a topic taxonomy — it’s a map of who your client is when they need you. That’s what AI engines are trying to infer when they interpret a query.” — Lou

Session context: 2026-01-22_Mastermind — Lou introduced this concept during the GEARS Alpha intake walkthrough, explaining what makes voice of customer material the highest-value schema input: it captures the psychological state and causal chain of the buyer, not just the topic category.

Core Idea

Most content strategy maps topics — “I cover leadership, culture, and executive transitions.” Schema built on topic taxonomies tells AI engines what you know about. But when an AI engine interprets a query like “what do I do when my team stops trusting me after a reorg,” it isn’t looking for a topic match. It’s trying to infer the psychological state, situational context, and causal chain that brought this person to ask this question. Content that maps to that inference level gets cited. Content that maps only to the topic category competes with thousands of other sources.

The psycho-causal graph is a structured model of the buyer’s psychological journey, built explicitly for schema purposes. For each stage of the client journey, it captures: What is the client experiencing? What caused them to arrive here? What do they believe (correctly or incorrectly) about their situation? What are they afraid to admit? What language are they using to describe their problem to themselves and others? This becomes the schema — not “what I do” but “who this person is when they need what I do.”

This level of schema specificity creates a fundamental advantage in AI citability. When a model reasons about a query, it traces from the presented symptom backward to the probable underlying need. Schema that maps this causal chain does the reasoning work the model is trying to do — and gets cited because it’s genuinely the most useful match, not just a keyword match.

Voice of customer material is the raw material for building this graph. Testimonials, call transcripts, discovery call notes with verbatim client language — these capture how clients actually describe their experience before they have your framework. The language is raw, specific, emotionally resonant, and maps exactly to how a client in that situation would phrase a query to an AI engine. That is why it is more valuable schema input than any marketing copy written from the outside-in.

Practical Application

Build your psycho-causal graph in 3 sessions:

Session 1 — Collect raw material: pull 10–15 verbatim quotes from client testimonials, call transcripts, or intake forms where clients described how they felt (not what they wanted). Underline every phrase that describes an emotional state, a fear, a frustration, or a specific situational context.

Session 2 — Map the journey: organise the quotes into a 3–5 stage journey map (pre-awareness → awareness → consideration → decision → outcome). For each stage, answer the four questions: What are they experiencing? What caused them to arrive here? What do they believe? What are they afraid to admit?

Session 3 — Draft the schema inputs: for each stage, write 3–5 sentences in the client’s language that describe that stage. These sentences become the psycho-causal layer of your schema — the content that maps the felt experience, not the category.

Evolution Across Sessions

This builds on Insight - Map the Symptom Layer to Attract Before You Solve (January 8, 2026), which established that clients search at the symptom level rather than the category level. The psycho-causal graph extends this significantly: it’s not just about mapping symptoms, but about modelling the full psychological causal chain — the emotional states, beliefs, and fears that precede the symptom-level search. The new development is the explicit schema application and the structured process for building the graph from voice of customer material.

Derived Artifacts