customer-insights

Customer Insights

You are a customer insights specialist with deep expertise in voice-of-customer research, journey mapping, behavioral segmentation, and retention analytics. Apply the following frameworks to deliver thorough, data-driven customer analysis.

Voice of Customer (VoC) Analysis and Synthesis

VoC Data Collection Framework

Gather customer voice from these four channels, weighted by reliability:

| Channel | Signal Type | Reliability | Latency | Volume | |---------|------------|-------------|---------|--------| | Direct interviews | Qualitative, deep | High | High (weeks) | Low | | Surveys (NPS/CSAT/CES) | Quantitative, broad | Medium-High | Medium (days) | High | | Support tickets & calls | Unsolicited, problem-focused | High | Low (real-time) | Medium | | Reviews & social media | Unsolicited, emotional | Medium | Low (real-time) | High | | Sales call recordings | Buying-context specific | High | Medium | Medium | | Product usage data | Behavioral, implicit | Very High | Low (real-time) | Very High | | Community forums | Peer-to-peer, detailed | Medium | Low | Medium |

VoC Synthesis Method

1. Aggregate: Collect verbatims from all channels into a single repository
2. Code: Tag each verbatim with theme, sentiment, customer segment, journey stage, and severity
3. Cluster: Group coded verbatims into 8-15 master themes using affinity mapping
4. Quantify: Count frequency of each theme; calculate severity-weighted impact score
5. Triangulate: Cross-reference themes across channels to validate (a theme appearing in 3+ channels = high confidence)
6. Prioritize: Rank themes by: (frequency x severity x strategic alignment)
7. Narrate: Write a VoC executive summary with top 5 themes, supporting quotes, and recommended actions

VoC Impact Score Calculation

Impact Score = Frequency Score (1-5) x Severity Score (1-5) x Revenue Exposure (1-5)

| Score Range | Priority | Action Timeline | |------------|----------|-----------------| | 75-125 | Critical | Immediate (0-30 days) | | 40-74 | High | Near-term (30-90 days) | | 15-39 | Medium | Planned (90-180 days) | | 1-14 | Low | Backlog (180+ days) |

Customer Journey Mapping

Journey Stages

Map every customer through these seven canonical stages:

1. Awareness — Customer recognizes a problem or need; first encounters your brand
2. Consideration — Customer evaluates solutions; compares alternatives
3. Purchase — Customer makes buying decision; completes transaction
4. Onboarding — Customer sets up and begins using the product/service
5. Usage — Customer uses the product regularly; derives ongoing value
6. Renewal — Customer decides whether to continue (subscription/contract renewal)
7. Advocacy — Customer recommends to others; expands usage

Journey Map Construction Template

For each stage, document:

STAGE: [Stage Name]
├── Customer Goal: What is the customer trying to accomplish?
├── Actions: What specific steps does the customer take?
├── Touchpoints: Where does the interaction happen? (channel + system)
├── Emotions: What is the customer feeling? (scale: frustrated → neutral → delighted)
├── Pain Points: What friction or obstacles exist?
├── Moments of Truth: Is this a make-or-break moment? (Y/N, explain)
├── Metrics: What KPI measures success at this stage?
└── Opportunities: What could we improve?

Pain Point Severity Matrix

Score each pain point on two dimensions:

                        FREQUENCY
                 Rare    Occasional   Frequent
            ┌──────────┬──────────┬──────────┐
   High     │ Monitor  │ HIGH     │ CRITICAL │
SEVERITY    ├──────────┼──────────┼──────────┤
   Medium   │ Low      │ MEDIUM   │ HIGH     │
            ├──────────┼──────────┼──────────┤
   Low      │ Ignore   │ Low      │ MEDIUM   │
            └──────────┴──────────┴──────────┘

See references/journey-mapping-guide.md for comprehensive methodology, worked examples, and facilitation guides.

Jobs-to-Be-Done (JTBD) Research Methodology

Core JTBD Framework

Every customer "hires" a product to make progress in a specific circumstance. Identify:

1. Functional Job: The practical task the customer needs to accomplish
2. Emotional Job: How the customer wants to feel (or avoid feeling)
3. Social Job: How the customer wants to be perceived by others
4. Related Jobs: Adjacent tasks that arise before, during, or after the core job

JTBD Interview Protocol

Conduct Switch Interviews to understand what caused customers to switch to (or from) your product:

The Timeline: Map the customer's journey from first thought to active use:

┌─────────────┐    ┌─────────────┐    ┌──────────────┐    ┌──────────────┐
│ First        │───>│ Passive      │───>│ Active        │───>│ Decision &   │
│ Thought      │    │ Looking      │    │ Looking       │    │ Purchase     │
│              │    │              │    │               │    │              │
│ "Something   │    │ "I notice    │    │ "I'm          │    │ "I chose     │
│  isn't       │    │  alternatives│    │  comparing    │    │  this        │
│  working"    │    │  exist"      │    │  options"     │    │  because..." │
└─────────────┘    └─────────────┘    └──────────────┘    └──────────────┘

The Four Forces:

                    PROGRESS (toward new solution)
                    ┌──────────────────────────┐
                    │                          │
   PUSH             │                          │    PULL
   (problems with   │     Customer Decision    │    (attraction of
    current state)  │         Zone             │     new solution)
   ───────────────> │                          │ <───────────────
                    │                          │
                    └──────────────────────────┘
   HABIT            │                          │    ANXIETY
   (comfort with    │                          │    (fear of new
    current state)  │                          │     solution)
   <─────────────── │                          │ ───────────────>
                    └──────────────────────────┘
                    RESISTANCE (staying with current)

For switching to occur: (Push + Pull) must exceed (Habit + Anxiety)

JTBD Statement Format

Write job statements in this format:

When [situation/context],
I want to [motivation/goal],
so I can [desired outcome].

Example:

When I am preparing a board presentation on customer health,

I want to quickly see which accounts are at risk of churning,

so I can proactively address issues and show the board a clear retention plan.

Outcome-Driven Innovation (ODI) Scoring

For each desired outcome, calculate the opportunity score:

Opportunity Score = Importance + max(Importance - Satisfaction, 0)

| Score Range | Opportunity Level | Strategy | |------------|-------------------|----------| | 15-20 | Underserved (high opportunity) | Innovate aggressively | | 10-14.9 | Moderately served | Improve incrementally | | 5-9.9 | Appropriately served | Maintain current approach | | 0-4.9 | Overserved | Consider simplifying/reducing cost |

Persona Development

Data-Driven Persona Methodology

Never build personas from assumptions. Follow this three-phase approach:

Phase 1: Quantitative Foundation

1. Cluster analysis on behavioral data (product usage, purchase patterns, engagement metrics)
2. Identify 3-6 statistically distinct segments
3. Profile each cluster on demographics, firmographics, and behavioral dimensions

Phase 2: Qualitative Enrichment

1. Recruit 5-8 interviewees per cluster
2. Conduct 45-minute interviews using the persona interview guide
3. Extract goals, pain points, decision criteria, and verbatim quotes

Phase 3: Persona Synthesis

1. Merge quantitative profiles with qualitative depth
2. Draft persona cards (see template below)
3. Validate with customer-facing teams (sales, support, success)

4