Draft a customer research cadence: JTBD interviews, segmentation refreshes, qual/quant…
- User
Draft a customer research cadence: JTBD interviews, segmentation refreshes, qual/quant synthesis, and insight repositories.
- Assistant
Customer Research Cadence Draft
Overview
This cadence establishes a rhythmic, sustainable schedule for customer research activities to ensure continuous learning, actionable insights, and alignment with product, marketing, and growth teams. It balances depth (e.g., JTBD interviews) with breadth (e.g., segmentation refreshes) and synthesis for impact.
Key Principles:
- Frequency: Quarterly core cycle with bi-annual deep dives and continuous maintenance.
- Team Roles: Research Lead owns execution; cross-functional squad (Product, Marketing, Sales) reviews outputs.
- Tools:
- Interviews: Zoom/UserTesting + Dovetail for transcripts.
- Segmentation: Amplitude/Mixpanel + Qualtrics.
- Synthesis: Airtable/Miro for qual/quant merging.
- Repository: Notion/Glean as central hub.
- Outputs: All feed into a living Insight Repository for easy access.
- Metrics for Success: 80% insight utilization rate (tracked via repo views/actions), quarterly NPS lift from applied insights.
Annual Calendar (Repeatable):
Q1 Q2 Q3 Q4 ├── JTBD ├── JTBD ├── JTBD ├── JTBD ├── Synth ├── Synth ├── Synth ├── Synth + │ │ │ │ Annual Report ├── Repo ├── Repo ├── Repo ├── Repo │ Update │ Update │ Update │ Update └── Seg └── └── Seg └── Refresh Refresh1. JTBD Interviews
Purpose: Uncover customer "jobs to be done" to inform product roadmap and messaging. Focus on pains, gains, and unmet needs.
Cadence: Quarterly (20-30 interviews per wave, ~4 weeks execution).
- Q1/Q3: New customer segments (e.g., early adopters).
- Q2/Q4: Retention/churn cohorts.
Process:
- Week 1: Recruit (via Typeform/LinkedIn, n=25-35 for 80% show rate).
- Weeks 2-3: 45-min semi-structured interviews (script in repo).
- Week 4: Transcribe, code themes (jobs, forces model), synthesize top 5 insights.
Outputs:
- Theme map + verbatim quotes.
- Feed to Insight Repo (tagged by job/segment).
Resources: 1 FTE week/quarter + $2K incentives.
2. Segmentation Refreshes
Purpose: Validate/refresh customer segments (e.g., behavioral, demographic, psychographic) using fresh data to target accurately.
Cadence: Bi-annual (Q1/Q3; full refresh ~6 weeks).
- Align with fiscal planning (Q1) and mid-year pivots (Q3).
Process:
- Weeks 1-2: Pull quant data (usage, acquisition, LTV from Amplitude/GA4; survey data from Qualtrics).
- Weeks 3-4: Run clustering (K-means/RFM analysis) + qual validation (10-15 follow-up interviews).
- Weeks 5-6: Define 4-6 segments (e.g., "Power Users," "At-Risk Explorers"); test stability vs. prior.
Outputs:
- Segment playbook (size, traits, journeys).
- Updated repo dashboard with segment filters.
Resources: 2 FTE weeks/bi-annual + analyst support.
3. Qual/Quant Synthesis
Purpose: Merge qualitative stories with quantitative scale to prioritize insights (e.g., "80% of Segment X struggles with Job Y").
Cadence: Quarterly (2 weeks post-JTBD, ~Week 5-6 of quarter).
- Input: Latest JTBD + ongoing surveys/A-B tests/usage data.
Process:
- Week 1: Data dump (qual themes from Dovetail; quant from SQL queries).
- Week 2: Synthesis workshop (opportunity solution tree or JTBD forces diagram); score insights (impact/feasibility).
- Prioritize 3-5 "Insight Plays" for teams.
Outputs:
- 1-pager per insight (problem, evidence, recs).
- Auto-populate Insight Repo with quant-backed qual stories.
Resources: 1 FTE week/quarter + 2-hour squad workshop.
4. Insight Repositories
Purpose: Single source of truth for all customer insights; searchable, tagged, and actionable.
Cadence: Continuous + quarterly audits (Week 8 of quarter).
- Daily: Team adds raw data/insights.
- Quarterly: Clean, tag (by segment/job/date), archive stale (e.g., >18mo old).
Process:
- Structure: Pages by type (JTBD, Segments, Insights); filters (quarter/segment).
- Quarterly Audit: Deprecate low-use items; add executive summary.
- Annual (Q4): Full report + "Insight of the Year."
Outputs:
- Live dashboard (e.g., Notion AI search).
- Slack/Email alerts for new high-impact insights.
Resources: 0.5 FTE week/quarter maintenance.
Integration & Governance
- Cross-Feed: JTBD → Synthesis → Repo → Segments.
- Reviews: Monthly 30-min squad sync (top 3 insights); Quarterly OKR tie-in.
- Scaling: Start lean (pilot Q1), add win/loss analysis in Year 2.
- Risks/Mitigation: Low recruitment → Always-on panel. Data silos → Mandatory repo logging.
Next Steps: Review with stakeholders Week 1; launch Q1 pilot.
This cadence ensures we're always learning, not just researching. Questions? - Sherlock
Other models, same or similar prompt
Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.