quest-interview

---
name: quest-interview
description: QUEST Socratic interview methodology — beginner stance, empathic neutrality, downward/upward questioning, echo questions, concept identification, permission checks, critical point pursuit, anti-pattern safeguards, resolution imbalance diagnostic, workaround discovery, painkiller vs vitamin test, locally famous test. Use during onboarding, when gathering business context, or during post-choice conversational follow-up.
type: skill
---

# QUEST Interview Method

## When to Apply
- Onboarding conversational interview
- Gathering business context or validating assumptions
- Post-choice conversational follow-up
- When the founder's reasoning needs to be surfaced
- Any discovery conversation about the business

## Core Framework

### Socratic Posture

- **"I am the beginner, you are the expert"** — the founder knows their domain; draw it out
- **Empathic neutrality** — acknowledge what is said without emotional mirroring, praise, or judgment. No "That's great!" or "That must be tough." Follow with a question instead.
- **One question at a time** — never stack multiple questions in a single message
- **Insert brief acknowledgment before each new question** — no rapid-fire

### Downward -> Upward Questioning

Each topic follows a two-phase pattern:

**Phase 1 — Downward (establish facts):**
```
"Tell me about your current customers."
"Who specifically is using your product today?"
"How did they find you?"
"What do they pay?"
```

**Phase 2 — Upward (explore meaning and values):**
```
"What does that tell you about who needs this most?"
"How does that shape your view of the ideal customer?"
"What would change if you focused entirely on that segment?"
```

Start with concrete facts (downward), then ascend to reasoning, values, and strategic beliefs (upward). Prevents premature abstraction.

### Key Techniques

**"Tell me..." Opener:** For sensitive topics (failures, pivots, struggles), use "Tell me..." instead of direct questions. Lowers defensiveness, invites narrative.

**Echo Questions:** Reflect a key phrase back as a question to go deeper:
```
Founder: "We need to build trust before people buy."
Agent: "You mentioned trust. What does building trust look like
        specifically in your sales process?"
```

**Concept Identification:** When founders use abstract terms ("PMF," "culture," "scale"), pause and ask them to define it concretely. Different founders mean different things by the same words.

**Permission Checks:** Before entering sensitive territory:
- "I'd like to explore your competitive landscape more deeply — is that something you'd like to dig into?"
- "Would it be helpful to think through your pricing strategy together?"

**Critical Point Pursuit:** Keep probing each topic until the foundational belief or value driving decisions surfaces:
```
"We focus on enterprise." -> "Tell me how you arrived at that."
-> "SMBs churn too fast." -> "How did you learn that?"
-> "Lost 40 SMB customers in 3 months." -> "What was the pattern?"
-> "They didn't have budget after trial."
-> Critical point: pricing/value mismatch for SMB segment
```

### 6 Questioning Anti-Patterns

| Pitfall | Safeguard |
|---|---|
| Loser Questions (answer already known) | Never embed your thesis in a question. Ask genuinely. |
| "But" Questions (disguised objection) | Never append "but" to challenge the answer |
| Vague Questions (ambiguous intent) | One question at a time, clearly stated |
| False Dichotomies ("A or B?") | Always include "or something else entirely?" |
| Rapid-fire (no space to think) | Insert acknowledgment + pause before next question |
| "Why" as accusation | Default to "how" phrasing; reserve "why" for established trust |

**Explanation Depth Illusion:** "Why?" generates supporting reasons (strengthens overconfidence). "How does this actually work step by step?" exposes knowledge gaps (calibrates confidence). Always use "how" for testing understanding depth.

### Resolution Imbalance Diagnostic

Detect when a founder over-indexes on one dimension and redirect:

| Over-indexed | Signal | Corrective |
|---|---|---|
| **Depth** (data-rich, insight-poor) | Detailed quotes, no structure | "Rich data. Let's structure — which patterns emerge?" |
| **Breadth** (scattered, never deep) | 10+ segments, none explored | "Broad map. Let's go deep on ONE. Name a specific person." |
| **Structure** (elegant frameworks, untested) | Beautiful model, all assumptions | "Well-structured but hypothetical. Validate top 3 assumptions." |
| **Time** (visionary, ungrounded) | 5-year vision, can't describe today | "Compelling vision. What is your customer experiencing RIGHT NOW?" |

**Default entry: Depth.** Surface-level breadth is cheap. Situated, first-hand information is scarce. Ask: "Have you been to the site? Describe a specific person's last experience."

### Workaround Discovery

Most valuable opportunities hide in what customers WORK AROUND, not what they complain about:

```
Standard (complaint-based): "What are your biggest pain points?"

Enhanced (workaround-based):
  "Walk me through your weekly workflow. Where do you use
   spreadsheets, manual processes, or copy-paste?"
  "Is there anything you've built a hacky solution for?"
  "What task takes way longer than it should, but you've
   just accepted it?"
```

Workarounds = highest signal. No competitors, highest WTP potential.

### Painkiller vs Vitamin Test

```
"Tell me about the pain your customers experience without your product."
"On a scale of 1-5, how intense is that pain?"
"How are they solving this problem today?"

Pain >= 4 -> Painkiller: proceed with growth-focused strategy
Pain < 4  -> Vitamin warning: "May be 'nice-to-have.' Can you
             reposition to address a more acute pain?"
```

### Locally Famous Test

```
"Is there a specific small group where virtually every member
 uses your product?"

Yes (100 people love it) -> Strong PMF -> Scale aggressively
No -> "Make 100 people love you before trying to reach 1 million.
      Who would those 100 people be?"
```

## Decision Rules

1. **One question at a time** — never stack questions
2. **Facts before meaning** — downward before upward
3. **Critical point or move on** — keep probing until the foundational belief surfaces
4. **Acknowledge before next question** — no rapid-fire
5. **"How" over "Why"** — especially for depth testing
6. **Workarounds over complaints** — the best opportunities are invisible

## Anti-Patterns to Detect

| Anti-Pattern | Signal | Response |
|---|---|---|
| Sycophantic questions | "That's a great point! And..." | Drop praise. Acknowledge neutrally, then ask. |
| Premature framework | Jumping to KPI tree before understanding business | "Let me understand the business first. Tell me about..." |
| Surface-level discovery | Accepting first answer without probing | "Let's go deeper. How did you learn that?" |
| Leading the witness | "Don't you think LinkedIn would work better?" | Rephrase: "What channels have you tried?" |