codymaster 4.1.4 → 4.3.0

package/skills/mom-test/references/finding-conversations.md

@@ -0,0 +1,251 @@
+# Finding Conversations
+
+The hardest part of customer development isn't knowing what to ask -- it's finding people to ask. This reference covers where to find your target customers, how to approach them, and how to keep conversations casual enough to produce honest answers.
+
+## The Framing Problem
+
+How you frame a conversation determines the quality of data you receive. Compare:
+
+| Framing | Effect |
+|---------|--------|
+| "Can I interview you for my startup?" | They put on armor. Answers become polished and guarded. |
+| "I'm doing customer research for a new product" | Slightly better, but they still perform for the researcher. |
+| "I'm trying to understand how your industry works" | Good -- positions them as the expert. |
+| "I'm thinking about getting into [space] and I don't want to be an idiot" | Great -- triggers their desire to help and teach. |
+| (Casual conversation at an event about their work) | Best -- no framing needed, pure honesty. |
+
+**Key insight:** The less formal the conversation, the more honest the data. The best customer conversations don't feel like interviews at all.
+
+## Seven Channels for Finding Conversations
+
+### 1. Warm Introductions
+
+The highest-quality channel. A warm intro from a mutual contact starts the conversation with trust already established.
+
+**How to build an intro network:**
+- Tell everyone you know what you're exploring (not what you're building)
+- Ask: "Do you know anyone who deals with [problem area]? I'd love to learn from them."
+- Be specific: "I'm looking for [role] at [company type] who [relevant behavior]"
+- Make it easy: offer to write the intro email for them
+
+**The intro email formula:**
+
+```
+Subject: Intro -- [Your Name] <> [Their Name] re: [topic]
+
+[Contact Name] -- meet [Your Name], who's researching how
+[industry/role] handles [problem area]. I thought you'd be a
+great person for them to learn from.
+
+[Your Name] -- [Contact Name] is [one sentence on their expertise].
+
+I'll let you two take it from here!
+```
+
+**Volume target:** Ask 10 people for intros. Expect 3-5 to follow through. Each intro should produce 1-2 additional referrals, creating a snowball effect.
+
+### 2. Industry Events and Conferences
+
+Go where your customers already gather. The conversations happen naturally.
+
+**Types of events:**
+- Industry conferences (large, diverse, good for initial exploration)
+- Local meetups (smaller, more intimate, better for deeper conversations)
+- Trade shows (good for B2B, especially supply-side conversations)
+- Workshops and seminars (people come to learn, which means they're aware of problems)
+- Online communities with meetups (Reddit, Discord, Slack groups)
+
+**How to approach people at events:**
+- Don't pitch. Don't hand out business cards unprompted.
+- Open with genuine curiosity: "What brings you to this event?"
+- Ask about their work: "What's the biggest challenge you're facing in [area]?"
+- Share your interest: "I've been exploring [space] -- what should I know?"
+- Follow up within 24 hours with a specific reference to your conversation
+
+**Event preparation checklist:**
+- [ ] Identify 5-10 people you'd like to meet (check speaker list, attendee list)
+- [ ] Prepare 3 open-ended questions about their work
+- [ ] Bring a notebook, not business cards
+- [ ] Set a goal: have 5 substantive conversations
+- [ ] Plan follow-up within 24 hours
+
+### 3. Cold Outreach
+
+Cold emails and messages work if you lead with their expertise, not your needs.
+
+**The cold outreach formula:**
+
+**Subject:** Quick question about [specific thing they know about]
+
+```
+Hi [Name],
+
+I saw your [talk/post/article] about [specific topic].
+I'm exploring [problem area] and trying to understand
+how [their role/industry] handles it.
+
+Would you have 15 minutes for a quick call this week?
+I'm not selling anything -- just trying to learn from
+people who know this space.
+
+Best,
+[Name]
+```
+
+**Key principles for cold outreach:**
+- Keep it under 5 sentences
+- Reference something specific about them (not a generic template)
+- Be transparent: you're learning, not selling
+- Ask for 15 minutes, not 30 or 60
+- Provide a clear reason why you're reaching out to them specifically
+- Follow up once after 3-5 days, then stop
+
+**Response rates by channel:**
+
+| Channel | Typical Response Rate | Best For |
+|---------|----------------------|----------|
+| LinkedIn DM | 5-15% | B2B professionals |
+| Cold email | 3-10% | Anyone with a public email |
+| Twitter/X DM | 10-25% | Thought leaders, indie makers |
+| Community forum post | 15-30% | Niche communities |
+| Reddit comment/DM | 5-20% | Consumer insights |
+
+### 4. Landing Pages and Signups
+
+Create a simple page that describes the problem (not the solution) and collect emails from people who resonate.
+
+**How to use landing pages for conversations:**
+1. Describe the problem in your target customer's language
+2. Add a signup: "We're exploring solutions -- want to help shape what we build?"
+3. When someone signs up, email them within 24 hours: "Thanks for signing up. I'd love to learn more about how you handle [problem]. Do you have 15 minutes this week?"
+4. These are your warmest leads -- they self-selected by caring about the problem
+
+**Landing page copy principles:**
+- Lead with the problem, not the solution
+- Use language from your initial conversations (mirror their words)
+- Don't promise a product -- promise involvement in shaping one
+- Include a short survey (3-5 questions) to pre-qualify
+
+### 5. Online Communities
+
+Participate genuinely in communities where your target customers hang out.
+
+**Where to look:**
+- Reddit subreddits related to the problem space
+- Industry-specific Slack groups
+- Discord servers
+- Facebook groups (especially for consumer products)
+- Hacker News (for developer/startup audiences)
+- Specialized forums (e.g., Indie Hackers, Product Hunt discussions)
+
+**How to participate without being slimy:**
+- Join 4-6 weeks before you start asking questions
+- Contribute value first: answer questions, share relevant resources
+- When you do ask, be transparent: "I'm exploring [problem area] and would love to hear how people here handle it"
+- Never pitch in a community. Ever. Even if someone asks you to.
+- DM people who post about relevant problems: "I saw your post about [problem]. I'm researching this area -- would you mind telling me more?"
+
+### 6. Advisors as a Channel
+
+Formalize relationships with well-connected people who can open doors at scale.
+
+**What makes a good advisor for conversations:**
+- They know 50+ people in your target customer segment
+- They're respected in the community (their intro carries weight)
+- They understand what you're trying to learn (so they can make relevant intros)
+- They have a genuine interest in your success
+
+**How to structure an advisor relationship for conversations:**
+- Be explicit: "I don't need strategy advice. I need introductions to [specific type of person]."
+- Set expectations: "Would you be able to make 3-5 introductions over the next month?"
+- Make it easy: provide them with a one-sentence description of who you want to meet and a template intro email
+- Give them credit: "Sarah introduced us, and she mentioned you're the expert on [thing]"
+
+**The advisor pipeline:**
+1. Identify 5-10 well-connected people in your space
+2. Approach them honestly: "I'm trying to learn about [problem]. You know everyone in this space. Can I buy you coffee?"
+3. If the coffee goes well: "Would you be open to being an informal advisor? Mainly, I'd love your help making introductions."
+4. Formalize if appropriate (advisory shares, compensation)
+
+### 7. Customer-Adjacent Roles
+
+When you can't easily reach end customers, talk to people who serve them.
+
+**Who to talk to:**
+- Consultants who advise your target customers
+- Sales reps who sell to your target segment
+- Customer support agents who hear complaints daily
+- Industry analysts who study the market
+- Journalists who cover the space
+
+**Why this works:**
+These people talk to hundreds of your potential customers. They have pattern-matched the common problems, objections, and buying behaviors. One conversation with a consultant can compress what would take 20 customer interviews.
+
+**How to approach customer-adjacent roles:**
+- "You work with dozens of [type of company]. What's the most common problem you see them struggling with?"
+- "When companies in [industry] buy new tools, what's the typical process?"
+- "What are the top 3 complaints you hear from your clients?"
+
+## Keeping Conversations Casual
+
+### The Vision/Framing/Weakness/Pedestal/Ask Framework
+
+A five-part structure for getting meetings that produce honest conversations:
+
+**1. Vision (one sentence)**
+"I'm exploring how small businesses handle their bookkeeping."
+
+**2. Framing (set expectations)**
+"I'm not selling anything. I'm just talking to people who deal with this to understand the space."
+
+**3. Weakness (show vulnerability)**
+"I'm an engineer, so I don't know much about the accounting side. I'm trying not to build something stupid."
+
+**4. Pedestal (elevate them)**
+"You've been doing this for 10 years, so you'd know better than anyone."
+
+**5. Ask (specific and small)**
+"Would you have 15 minutes for a quick chat? Coffee's on me."
+
+### Rules for Keeping It Casual
+
+1. **Never use a clipboard or formal survey.** Use a small notebook or your phone's notes app.
+2. **Don't record without permission.** And know that recording changes behavior.
+3. **Meet in their territory.** Their office, their favorite coffee shop, their coworking space.
+4. **Start with rapport.** Talk about something other than your topic for the first 2-3 minutes.
+5. **Don't ask all your questions.** Ask 3-5 important ones, not a 20-question script.
+6. **Let the conversation flow.** Follow interesting tangents. Your best insights will come from unexpected directions.
+7. **End naturally.** Don't abruptly end at exactly 15 minutes. Let the conversation wind down organically (but respect their time).
+8. **Follow up with value.** Send them an article, a connection, or a thank-you note. Not a pitch deck.
+
+## How Many Conversations Do You Need?
+
+### Convergence Theory
+
+You don't need hundreds of conversations. You need enough to see patterns.
+
+| Signal | Number of Conversations |
+|--------|------------------------|
+| Hearing brand-new information in every conversation | You need more. Keep going. |
+| Starting to hear similar themes from 3-4 people | Getting close. Focus your questions. |
+| Conversations are repeating -- nothing surprises you | You've reached saturation. Time to act. |
+
+**Rule of thumb by stage:**
+
+| Stage | Conversations Needed | Goal |
+|-------|---------------------|------|
+| Problem exploration | 10-15 | Understand if the problem is real and who has it |
+| Customer segment validation | 5-10 per segment | Identify which segment cares most |
+| Solution validation | 5-10 with prototype | Test whether your approach works |
+| Pre-launch | 3-5 commitment conversations | Collect real commitments (time, money, reputation) |
+
+### When to Stop and Build
+
+Stop talking when:
+- You can predict what the next person will say
+- Multiple people describe the same problem in the same way
+- You've received concrete commitments (not just compliments)
+- You have a clear picture of the problem, the customer, and the existing alternatives
+- You're procrastinating on building by scheduling more conversations
+
+**Warning:** "Just one more conversation" can become a form of procrastination. If you're past saturation and still not building, you might be using conversations to avoid the risk of building something real.

package/skills/mom-test/references/processing-learning.md

@@ -0,0 +1,256 @@
+# Processing and Learning
+
+Customer conversations generate raw material. Without a system for processing that material, you'll unconsciously cherry-pick the data that confirms your existing beliefs and ignore the signals that challenge them. This reference covers note-taking, team sharing, belief updating, and knowing when to stop talking.
+
+## Note-Taking During Conversations
+
+### What to Capture
+
+Take notes on facts and commitments, not opinions and feelings. Your notes should be useful to someone who wasn't in the room.
+
+**Capture these:**
+
+| Category | Examples | Why It Matters |
+|----------|----------|----------------|
+| Exact quotes | "I spend 3 hours every Friday on this" | Customer language reveals real pain points |
+| Specific behaviors | "She uses a spreadsheet + Slack + email to coordinate" | Reveals current workflow and workarounds |
+| Numbers | "$2,000/month on the current tool" | Quantifies willingness to pay |
+| Emotions | "He got visibly frustrated describing the process" | Emotional weight = real pain |
+| Commitments | "Agreed to a 15-min demo next Tuesday" | Separates real interest from politeness |
+| Surprises | "Nobody has mentioned the feature we thought was key" | Challenges assumptions |
+
+**Don't waste space on these:**
+
+| Category | Example | Why It's Noise |
+|----------|---------|----------------|
+| Compliments | "They said they loved the idea" | Zero predictive value |
+| Generics | "He usually handles it quickly" | No specific instance = fluff |
+| Your interpretations | "I think she'd definitely buy" | Your opinion, not a fact |
+| Feature requests (raw) | "They want a mobile app" | Record the underlying problem instead |
+
+### Note-Taking Systems
+
+#### The Two-Column Method
+
+Divide your notebook page (or document) into two columns:
+
+| Left Column: Raw Data (Facts) | Right Column: Interpretation (Your Thoughts) |
+|-------------------------------|----------------------------------------------|
+| "We tried Asana but quit after 2 months" | Asana might be too complex for small teams |
+| "Our CEO checks the dashboard every morning at 8am" | Dashboard is part of the CEO's daily routine |
+| "We pay $500/month for HubSpot but only use email" | Significant overpaying for what they actually use |
+| "She pulled up a spreadsheet with 47 tabs" | They've built a complex workaround (strong signal) |
+
+This separation is critical because it prevents you from conflating what you observed with what you think it means. Raw data is permanent; interpretations are hypotheses that should be tested.
+
+#### The Shorthand System
+
+During fast conversations, use shorthand symbols to tag important moments:
+
+| Symbol | Meaning |
+|--------|---------|
+| :) | Emotional moment (positive) |
+| :( | Emotional moment (pain point) |
+| $ | Money mentioned (budget, spending, willingness to pay) |
+| ! | Surprising or unexpected information |
+| -> | Commitment or next step |
+| ? | Something to follow up on |
+| X | Contradicts your current belief |
+| "" | Direct quote (write it verbatim) |
+
+**Example note with shorthand:**
+
+```
+Sara, VP Ops at Acme Corp, Jan 15
+
+"" "I spend my entire Friday doing reports that nobody reads" :(
+! She didn't know her company paid for Tableau ($1,200/mo) $
+"" "If someone could just email me the 3 numbers that matter, I'd be so happy"
+X She doesn't want a dashboard (contradicts our assumption)
+-> Agreed to 20-min demo next Wed 2pm
+? Who else on her team does reports? Ask next time
+```
+
+### When to Take Notes
+
+**During the conversation:**
+- Jot quick keywords and quotes
+- Don't let note-taking disrupt the flow
+- Say "That's really interesting, let me write that down" if you need a moment
+- A small notebook is less intimidating than a laptop
+
+**Immediately after the conversation (within 5 minutes):**
+- Expand your shorthand into full sentences
+- Add context you remember but didn't write down
+- Separate facts from interpretations (two-column method)
+- Rate the conversation quality: did you learn new facts or just collect compliments?
+
+**Never rely on memory alone.** After 24 hours, you'll have lost or distorted most of the details. After a week, you'll remember only what confirms your existing beliefs.
+
+## Processing with Your Team
+
+### The Weekly Customer Learning Session
+
+Set aside 30-60 minutes per week to review conversations as a team. This is the single most important ritual in customer development.
+
+**Agenda:**
+
+**1. Raw Data Review (20 minutes)**
+- Each team member shares their conversation notes (facts and quotes only)
+- No interpretation yet -- just the raw data
+- Other team members ask clarifying questions
+
+**2. Pattern Identification (15 minutes)**
+- What themes are repeating across conversations?
+- What problems come up most frequently?
+- What surprised us?
+- What contradicted our assumptions?
+
+**3. Belief Update (15 minutes)**
+- Review and update the team's three core beliefs (see below)
+- Document what evidence supports or challenges each belief
+- Decide whether any beliefs need to change
+
+**4. Next Actions (10 minutes)**
+- Who do we need to talk to next?
+- What questions should we add or remove?
+- Are we ready to stop talking and start building?
+
+### Why Team Processing Matters
+
+Individual processing is biased. Every person unconsciously filters information through their own lens:
+- Engineers focus on technical feasibility, not customer pain
+- Designers remember the UX complaints, not the business model signals
+- Founders remember the validation, not the contradictions
+- Salespeople remember the "yeses," not the hesitation
+
+When the whole team processes raw data together, these biases partially cancel out. The group sees patterns that individuals miss.
+
+### Rules for Team Processing
+
+1. **Share raw notes, not filtered summaries.** Saying "I talked to Sara and she liked the idea" is useless. Sharing Sara's exact quotes is useful.
+2. **No hierarchy in interpretation.** The founder's interpretation isn't more valid than the intern's. Evidence decides.
+3. **Celebrate surprising data.** When someone brings a conversation that challenges the team's beliefs, that's the most valuable contribution. Don't shoot the messenger.
+4. **Distinguish between "interesting" and "actionable."** Some facts are fascinating but don't change what you should build. Focus on data that has decision-making power.
+
+## The Three Core Beliefs
+
+At any point in customer development, your team should be able to articulate three beliefs:
+
+### Belief 1: The Problem
+"We believe that [customer segment] struggles with [specific problem] because [root cause]."
+
+**Example:** "We believe that freelance designers struggle with invoicing because they use generic tools that don't account for project-based billing and revision cycles."
+
+### Belief 2: The Customer Segment
+"We believe that the people who care most about this problem are [specific description] who [observable characteristic]."
+
+**Example:** "We believe that the people who care most are solo freelance designers earning $50-150K who manage 5-15 clients simultaneously."
+
+### Belief 3: The Solution Direction
+"We believe that the right solution [approach] because [evidence from conversations]."
+
+**Example:** "We believe the right solution integrates invoicing with project milestones because 7 of 10 designers told us their biggest pain is tracking which revision rounds are billable."
+
+### Updating Beliefs
+
+After each batch of conversations, review each belief:
+
+| Question | Interpretation |
+|----------|---------------|
+| How many conversations support this belief? | Track the count explicitly |
+| How many conversations contradict this belief? | Track this too -- don't ignore it |
+| Has new evidence strengthened or weakened this belief? | Be honest |
+| Should we update, narrow, or abandon this belief? | Make a decision |
+
+**When to update a belief:**
+- 3+ conversations provide contradictory evidence
+- A new pattern emerges that your current belief can't explain
+- You discover that a different customer segment cares more than your current target
+
+**When to abandon a belief:**
+- Majority of conversations contradict it
+- You can't find anyone who exhibits the problem
+- Everyone who has the problem already has a satisfactory solution
+
+## Organizing Customer Data
+
+### The Conversation Spreadsheet
+
+Maintain a central spreadsheet (or Notion database, or Airtable) with one row per conversation:
+
+| Column | Content |
+|--------|---------|
+| Date | When the conversation happened |
+| Name | Who you spoke with |
+| Company/Context | Where they work or their relevant context |
+| Segment | Which customer segment they represent |
+| Key quotes (3-5) | Exact words, not your paraphrase |
+| Problems mentioned | What pain points came up (unprompted only) |
+| Current solutions | What they're using now |
+| Money signals | What they pay, what they'd pay, budget context |
+| Commitment given | What they agreed to do next |
+| Commitment fulfilled? | Did they follow through? |
+| Belief impact | Did this change any of our three core beliefs? |
+| Surprise | What was unexpected? |
+
+### Tagging and Filtering
+
+As your conversation count grows, you'll need to filter by:
+- **Customer segment:** Which type of person said this?
+- **Problem area:** Which problem does this relate to?
+- **Signal strength:** How strong was the evidence? (fact/commitment > opinion/fluff)
+- **Recency:** When was this collected? Old data may be stale.
+
+### Quantifying Qualitative Data
+
+While customer conversations are qualitative, you can and should count patterns:
+
+| Metric | How to Track | Threshold |
+|--------|-------------|-----------|
+| Problem mention rate | N people who mentioned problem X unprompted out of M total conversations | >50% = strong signal |
+| Willingness to pay | N people who are currently paying for a solution | >30% = real market |
+| Commitment rate | N people who gave a concrete commitment out of M conversations | >20% = real interest |
+| Segment concentration | Which segment produces the strongest signals? | If one segment dominates, focus there |
+
+## Knowing When to Stop Talking
+
+### Signs You've Talked Enough
+
+1. **Convergence:** The last 3-5 conversations didn't teach you anything new. You can predict what the next person will say.
+2. **Clear problem:** You can describe the problem in the customer's own words, and multiple customers have confirmed it.
+3. **Clear segment:** You know exactly who has this problem most acutely and can describe them specifically.
+4. **Existing spending:** You've confirmed that people are already spending time or money on this problem.
+5. **Commitments collected:** You have concrete commitments (time, reputation, or money) from real potential customers.
+
+### Signs You Haven't Talked Enough
+
+1. **Every conversation surprises you:** You're still discovering the problem space.
+2. **Segment unclear:** You can't describe your ideal customer specifically.
+3. **No commitments:** Nobody has invested time, reputation, or money -- only compliments.
+4. **Contradictory data:** Different conversations point in completely different directions.
+5. **You're guessing:** Your three core beliefs are assumptions, not evidence-based conclusions.
+
+### The Conversation-to-Action Transition
+
+When you've hit convergence, make the transition explicit:
+
+**Team exercise: The "Stop Talking" Decision**
+1. Review all conversations from the last 2-4 weeks.
+2. For each of your three core beliefs, count supporting vs contradicting evidence.
+3. Ask: "If we build based on what we know now, what's our biggest remaining risk?"
+4. If the risk can be addressed by more conversations, keep talking.
+5. If the risk can only be addressed by building something, stop talking and build.
+
+**The dangerous middle ground:** Teams often get stuck in an infinite loop of conversations because talking is less scary than building. If your conversations are no longer producing new insights, you're procrastinating. Ship something and learn from real usage.
+
+## Anti-Patterns in Processing
+
+| Anti-Pattern | What It Looks Like | Fix |
+|-------------|--------------------|----|
+| Cherry-picking | Only sharing quotes that support your thesis | Share all raw notes, including contradictions |
+| Founder filtering | One person summarizes conversations and filters the data | Everyone reads raw notes independently before discussion |
+| Recency bias | Over-weighting the most recent conversation | Review all conversations together, not just the latest |
+| Confirmation bias | "9 people love it!" (ignoring the 3 who didn't) | Track and report both supporting and contradicting evidence |
+| Analysis paralysis | Endless analysis without action | Set a hard deadline: after N conversations, we build |
+| Sunk cost | "We've done 50 conversations, we can't pivot now" | Conversations are cheap; building the wrong thing is expensive |