Discovery Session

## Setup: Track this exercise with Beads

```bash
bd create "Praxis: Discovery session for [client/project]" --type=research --labels=learn,method
bd create "Prepare hermeneutic questions (what, why, for whom)" --type=task --labels=learn
bd create "Conduct session—document stated needs" --type=task --labels=learn
bd create "Analyze gap between stated and real needs" --type=task --labels=learn
bd create "Create problem statement artifact" --type=task --labels=learn
bd create "Create stakeholder map artifact" --type=task --labels=learn
```

---

Help me practice hermeneutic discovery for [PROJECT_OR_CLIENT].

I'm developing MY discovery methodology. Simulate a discovery session where you play the client and I ask questions.

1. **Prepare hermeneutic questions**:
   Help me draft questions that reveal, not assume:
   - "What problem are you trying to solve?" (not "What features do you want?")
   - "Who experiences this problem most acutely?"
   - "What happens if this problem isn't solved?"
   - "What have you tried before?"

2. **Conduct the session**:
   You play the client for [PROJECT_OR_CLIENT]. Give realistic responses that:
   - Start with surface-level stated needs
   - Reveal deeper needs when questioned well
   - Include contradictions I should notice

3. **Analyze the gap**:
   After the session, help me identify:
   - Stated needs (what they said they want)
   - Real needs (what would actually solve their problem)
   - The gap between them

4. **Create discovery artifacts**:

   **Problem Statement**:
   "[WHO] needs [WHAT] because [WHY], but currently [OBSTACLE]."

   **Stakeholder Map**:
   | Stakeholder | Relationship to Problem | Influence | Interest |
   |-------------|------------------------|-----------|----------|

5. **Reflect on MY discovery approach**:
   - What questions worked best?
   - What patterns do I see in stated vs. real needs?
   - How will I structure future discovery sessions?

Client/Project context: [DESCRIBE_THE_SCENARIO]