Customer Learning Notes
Use this skill after customer conversations to turn raw notes into team-readable
evidence. Good notes make it harder to misremember, overfit, or let one founder
become the sole source of customer truth.
Source Traceability
Primary source: The Mom Test by Rob Fitzpatrick, especially chapter 8 and the
conclusion. Guidance is paraphrased for this MIT repo; authoring notes used
converted EPUB lines 3613-4445.
Signal Taxonomy
Use these labels when synthesizing notes:
| Label |
Meaning |
| Pain |
Problem, obstacle, annoyance, risk, or cost |
| Goal |
Desired outcome, job to be done, or priority |
| Workaround |
Current manual process, tool stack, hack, or substitute |
| Money |
Budget, cost, value, purchase process, or decision owner |
| Person |
Specific stakeholder, competitor, team, buyer, or intro lead |
| Feature |
Request, buying criterion, integration need, or implementation clue |
| Emotion |
Strong excitement, anger, embarrassment, fear, or skepticism |
| Follow-up |
Promise, task, intro, research item, or next step |
Synthesis Workflow
- Preserve concrete facts separately from interpretation.
- Pull out short, useful quotes only when they are needed for traceability,
positioning, or internal alignment.
- Tag signals using the taxonomy above.
- Group evidence by segment, problem, workaround, budget, and commitment.
- Identify contradictions and mixed-segment noise.
- Update beliefs, risks, and the next three questions.
- Recommend whether to continue, narrow the segment, ask for commitments, or
move to building/testing.
Confidence Levels
| Level |
Use When |
| High |
Repeated behavior from a focused segment, with concrete cost or commitment. |
| Medium |
Specific evidence from a few good-fit conversations. |
| Low |
One-off quotes, mixed segments, opinions, or weakly anchored claims. |
Output Format
# Customer Learning Synthesis
## Source Notes
- Conversations:
- Segment:
- Date range:
## Evidence
| Signal | Evidence | Segment | Confidence | Implication |
|--------|----------|---------|------------|-------------|
## Belief Updates
- Stronger / weaker / new / rejected:
## Decisions
- Product, segment, positioning, sales or access:
## Next 3 Questions
1. [Question]
2. [Question]
3. [Question]
Workflow
Use workflows/synthesize-conversation-notes.md when the user provides raw
notes, transcripts, call summaries, or interview excerpts.
Quality Bar
- Do not summarize notes into vibes.
- Do not let one loud quote outweigh repeated behavior from a focused segment.
- Do not mix segments without labeling them.
- Do not treat notes as useful until they have been reviewed and turned into
updated beliefs or decisions.
1---2name: customer-learning-notes3description: Turn customer conversation notes, interview transcripts, call summaries, CRM snippets, or research notes into shared team learning and next questions. Use when synthesizing raw customer notes, avoiding founder interpretation bottlenecks, extracting quotes and signals, updating beliefs, or deciding what to ask next.4license: MIT5---67# Customer Learning Notes89Use this skill after customer conversations to turn raw notes into team-readable10evidence. Good notes make it harder to misremember, overfit, or let one founder11become the sole source of customer truth.1213## Source Traceability1415Primary source: The Mom Test by Rob Fitzpatrick, especially chapter 8 and the16conclusion. Guidance is paraphrased for this MIT repo; authoring notes used17converted EPUB lines 3613-4445.1819## Signal Taxonomy2021Use these labels when synthesizing notes:2223| Label | Meaning |24|-------|---------|25| Pain | Problem, obstacle, annoyance, risk, or cost |26| Goal | Desired outcome, job to be done, or priority |27| Workaround | Current manual process, tool stack, hack, or substitute |28| Money | Budget, cost, value, purchase process, or decision owner |29| Person | Specific stakeholder, competitor, team, buyer, or intro lead |30| Feature | Request, buying criterion, integration need, or implementation clue |31| Emotion | Strong excitement, anger, embarrassment, fear, or skepticism |32| Follow-up | Promise, task, intro, research item, or next step |3334## Synthesis Workflow35361. Preserve concrete facts separately from interpretation.372. Pull out short, useful quotes only when they are needed for traceability,38 positioning, or internal alignment.393. Tag signals using the taxonomy above.404. Group evidence by segment, problem, workaround, budget, and commitment.415. Identify contradictions and mixed-segment noise.426. Update beliefs, risks, and the next three questions.437. Recommend whether to continue, narrow the segment, ask for commitments, or44 move to building/testing.4546## Confidence Levels4748| Level | Use When |49|-------|----------|50| High | Repeated behavior from a focused segment, with concrete cost or commitment. |51| Medium | Specific evidence from a few good-fit conversations. |52| Low | One-off quotes, mixed segments, opinions, or weakly anchored claims. |5354## Output Format5556```markdown57# Customer Learning Synthesis5859## Source Notes60- Conversations:61- Segment:62- Date range:6364## Evidence65| Signal | Evidence | Segment | Confidence | Implication |66|--------|----------|---------|------------|-------------|6768## Belief Updates69- Stronger / weaker / new / rejected:7071## Decisions72- Product, segment, positioning, sales or access:7374## Next 3 Questions751. [Question]762. [Question]773. [Question]78```7980## Workflow8182Use `workflows/synthesize-conversation-notes.md` when the user provides raw83notes, transcripts, call summaries, or interview excerpts.8485## Quality Bar8687- Do not summarize notes into vibes.88- Do not let one loud quote outweigh repeated behavior from a focused segment.89- Do not mix segments without labeling them.90- Do not treat notes as useful until they have been reviewed and turned into91 updated beliefs or decisions.
ConcertoNotes