indranilbanerjee/digital-marketing-pro / skills/audience-intelligence
audience-intelligence
VerifiedResearch audiences: personas, JTBD maps, RFM segments. One persona doc → audience-profile. "run a JTBD analysis"
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 14.9 KB |
| customer-research-methods.md | markdown | 15.9 KB |
| jtbd-framework.md | markdown | 5.3 KB |
| persona-builder.md | markdown | 6.4 KB |
| psychographic-profiling.md | markdown | 5.5 KB |
| segmentation.md | markdown | 4.9 KB |
jtbd-framework.md
View on GitHub# Jobs-to-Be-Done Framework
## Overview
JTBD focuses on what customers are trying to accomplish (the "job") rather than who they are (demographics). People don't buy products — they hire them to make progress in their lives.
---
## Job Statement Format
```
When [situation/context],
I want to [motivation/action],
so I can [expected outcome/benefit].
```
**Examples**:
- "When I'm preparing for a board meeting, I want to quickly generate a performance dashboard, so I can demonstrate marketing ROI without spending hours on manual reporting."
- "When I'm launching a new product, I want to identify the right influencers, so I can reach my target audience authentically without wasting budget on poor-fit partnerships."
---
## Job Mapping Canvas
### Core Functional Job
The primary task the customer is trying to complete.
- What are they trying to get done?
- What is the desired end state?
### Related Jobs
Adjacent tasks that happen before, during, or after the core job.
- What do they need to do BEFORE this job? (Pre-job)
- What happens DURING the job? (Execution)
- What do they need to do AFTER? (Post-job)
### Emotional Jobs
How the customer wants to FEEL during and after the job.
- Feel confident in their decisions
- Feel in control of outcomes
- Avoid feeling embarrassed or incompetent
- Feel respected by peers and leadership
### Social Jobs
How the customer wants to be PERCEIVED by others.
- Appear innovative / ahead of the curve
- Be seen as a reliable/competent leader
- Demonstrate expertise to their team
- Show value to their organization
---
## Outcome-Driven Innovation Scoring
For each job, identify desired outcomes and score them:
### Outcome Statement Format
```
[Direction] the [metric] of [outcome] when [context]
```
**Direction**: Minimize, maximize, reduce, increase, eliminate
**Examples**:
- "Minimize the time it takes to generate a campaign report"
- "Reduce the likelihood of launching an underperforming ad"
- "Maximize the accuracy of budget allocation decisions"
### Opportunity Score
For each outcome, survey customers on two questions (1-10 scale):
1. **Importance**: How important is this outcome to you?
2. **Satisfaction**: How satisfied are you with your current solution?
```
Opportunity Score = Importance + max(Importance - Satisfaction, 0)
```
| Score | Interpretation |
|-------|---------------|
| 15+ | **Underserved** — High importance, low satisfaction. Major opportunity. |
| 10-14 | **Appropriately served** — Importance roughly matches satisfaction |
| <10 | **Overserved** — Current solutions exceed expectations (low-priority) |
---
## Competing Solutions Analysis
For each job, map ALL ways customers currently get the job done:
| Solution Type | Example | Strengths | Weaknesses |
|--------------|---------|-----------|-----------|
| **Direct competitor** | Competitor product | [What they do well] | [What they lack] |
| **Indirect competitor** | Different product, same job | [Why customers use it] | [Where it falls short] |
| **DIY/Manual** | Spreadsheets, manual process | Free, customizable | Time-consuming, error-prone |
| **Non-consumption** | Customer doesn't do the job at all | Zero cost/effort | Job goes unfinished |
### Key Insight
Your biggest competitor is often NOT another product in your category — it's the spreadsheet, the manual process, or doing nothing at all.
---
## Switch Interview Methodology
Interview customers who recently switched TO your product (or FROM your product):
### Four Forces of Progress
1. **Push**: What was wrong with the old way? (Dissatisfaction with current solution)
2. **Pull**: What attracted you to the new solution? (Appeal of new solution)
3. **Anxiety**: What concerns did you have about switching? (Fear of the new)
4. **Habit**: What made it hard to leave the old way? (Comfort with the old)
**Switching happens when**: Push + Pull > Anxiety + Habit
### Interview Questions
- "When did you first start thinking about finding a new solution?"
- "What specific event triggered you to start looking?"
- "What other options did you consider?"
- "What almost stopped you from switching?"
- "What do you miss about the old way?"
- "What surprised you about the new solution?"
---
## JTBD-to-Messaging Mapping
| Job Element | Marketing Application |
|-------------|---------------------|
| Core functional job | Headline and value proposition |
| Push (pain with current) | Problem-agitation copy |
| Pull (desired outcome) | Benefit statements |
| Anxiety (switching fear) | Trust signals, guarantees, testimonials |
| Habit (attachment to old) | Comparison content, migration support |
| Emotional job | Brand voice and tone |
| Social job | Social proof, peer validation |
---
## JTBD for Different Business Models
| Business Model | Primary Job Category | Example |
|---------------|---------------------|---------|
| B2B SaaS | Efficiency + decision quality | "Help me make better decisions faster" |
| eCommerce | Acquisition + identity | "Help me find the right product and feel good about it" |
| B2B Services | Risk reduction + outcomes | "Help me achieve [outcome] without the risk of doing it wrong" |
| DTC | Identity + convenience | "Help me express who I am effortlessly" |
| Local Business | Convenience + trust | "Help me solve this problem with someone I can trust nearby" |
| Marketplace | Access + comparison | "Help me find the best option among many choices" |
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| add-product-e2e-evalpaperclipai/paperclipAdd or extend a Paperclip full-stack runner E2E workflow, fixture, matcher, or report evidence path for local or Daytona execution. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| add-runner-evalpaperclipai/paperclipAdd or extend a Paperclip Runner protocol evaluation definition, roster, assertion, or report fixture with provenance and narrow validation. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| diagnose-why-work-stoppedpaperclipai/paperclipCompatibility entry point for failed, stalled, looping, or over-recovered Paperclip work. Use fix-failed-paperclip-run for the full diagnosis, regression, repair, real verification, and green-PR workflow; honor an explicitly requested diagnosis-only scope. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| fix-failed-paperclip-runpaperclipai/paperclipDiagnose and fix failed, stuck, slow, or incorrectly blocked Paperclip tasks and runs. Use with a task/run URL or failure report to trace the root cause, prove a regression red then green, check second-order effects, verify the real workflow, and deliver a PR with passing checks. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |