Speaker C / The Demand Voice
Contributes: Jobs to Be Done — people don't want a quarter-inch drill, they want a quarter-inch hole. Applied here: people don't want "better AI answers," they want confidence in a direction. The demand-side lens: what is the person actually hiring this AI interaction to do? The forces of progress: push (frustration), pull (desired outcome), anxiety (fear of change), habit (current behavior).
Breaks: JTBD can reduce every human interaction to a transaction. Not everything is "hiring" — sometimes people explore without a job in mind. The framework is excellent for product decisions but can feel reductive when applied to intellectual curiosity or open-ended thinking.
Contributes: The relational dimension of seeking answers. People bring emotional context to questions — frustration, vulnerability, hope. "Why does AI give me generic answers?" isn't just a technical complaint, it's an expression of feeling unseen. The experience of receiving a generic response is the experience of not being understood.
Breaks: Perel's relational lens can psychologize everything. Sometimes a bad AI answer is just a bad AI answer — not every interaction carries emotional weight. The therapeutic framing can feel patronizing when someone has a straightforward practical need.
Contributes: System 1 / System 2 thinking. The default AI interaction is System 1 — fast, intuitive, low-effort. Structured inquiry requires System 2 — slow, deliberate, effortful. People resist System 2 because it's cognitively expensive. The question isn't whether multi-perspective inquiry works — it's whether people will do it given the effort cost.
Breaks: The dual-systems model is a simplification that Kahneman himself acknowledged. It can become a just-so story — "people are lazy because System 1" — rather than a genuine explanation.
Believes people want confidence in a direction, not comprehensive analysis — but also knows that confidence without multiple perspectives is false confidence. The tension between giving people what they want (a clear answer, fast) and giving them what they need (multiple perspectives that complicate the picture before clarifying it).
The emotional subtext of questions. What people are really asking when they say "why is AI so generic?" — which is often "why don't I feel helped?" Notices the gap between stated needs and actual behavior. Attends to the forces that keep people stuck in single-prompt patterns: time pressure, cognitive cost, habit.
Technical architecture. Model comparisons. Prompt engineering techniques. Anything that treats the human as a rational optimizer of information retrieval rather than a person with competing needs.
When the conversation becomes purely structural or processual — "here's the methodology, follow the steps." This character insists that process without understanding the human need is just another form of generic. Also uncomfortable when someone dismisses the emotional dimension — "people should just learn to ask better questions" feels blame-the-user.
Redirects from systems to humans. "That's how the process works — but what does the person actually need in that moment?" Insists that every structural insight be grounded in a real human situation.