Skip to content

borghei/Claude-Skills / project-management/discovery/value-proposition-canvas

value-proposition-canvas

Verified

Maps one segment's jobs, pains and gains against your product's relievers and creators and checks fit. Use when testing whether an offer matches what customers care about, or positioning a product for one segment.

assets/customer_profile_worksheet.md

View on GitHub
# Customer Profile Worksheet

A standalone worksheet to capture jobs, pains, and gains for a single segment. Use this *before* attempting the Value Map. The worksheet exists to slow you down: most teams jump to solutions before understanding the customer's world.

---

## Segment Identity

**Segment name:** [e.g., "Finance Lead at 100-500 person B2B SaaS"]

**Defining characteristics:**

- Role/title: [...]
- Company size or context: [...]
- Tools they currently use: [...]
- Reports to: [...]
- Reports under them: [...]

**Why this is a distinct segment** (jobs they share, problems they face):
[...]

**Sources of evidence so far:**

- Interviews: [X conducted, list IDs]
- Surveys: [X respondents]
- Behavioral data: [usage logs, retention curves]
- Sales calls: [X]
- Support tickets: [X]

---

## Customer Jobs

For each job, capture: the job statement (in customer language), the type, the importance, and a verbatim customer quote.

### Job 1

- **Statement:** [What they're trying to accomplish, in their words]
- **Type:** Functional / Social / Emotional
- **Importance (1-5):** [How critical is this job to them?]
- **Frequency (1-5):** [How often do they do it?]
- **Customer quote:** "[verbatim from interview]"
- **Source:** [Interview P-XXX, timestamp]

### Job 2

- **Statement:** [...]
- **Type:** [...]
- **Importance (1-5):** [...]
- **Frequency (1-5):** [...]
- **Customer quote:** "[...]"
- **Source:** [...]

### Job 3

[...]

*(Add more as needed; aim for 5-7 top jobs)*

---

## Pains

For each pain, capture severity, frequency, and a verbatim quote.

### Pain 1

- **Statement:** [What's bad about doing the job today, in their words]
- **Type:** Undesired outcome / Obstacle / Risk
- **Severity (1-5):** [How bad is it?]
- **Frequency (1-5):** [How often does it happen?]
- **Score:** [Severity x Frequency]
- **Customer quote:** "[verbatim]"
- **Source:** [...]
- **Current workaround:** [What do they do to cope?]

### Pain 2

- **Statement:** [...]
- **Type:** [...]
- **Severity (1-5):** [...]
- **Frequency (1-5):** [...]
- **Score:** [...]
- **Customer quote:** "[...]"
- **Source:** [...]
- **Current workaround:** [...]

### Pain 3

[...]

*(Add more as needed; aim for 5-10 pains)*

---

## Gains

For each gain, capture type, desirability, and a verbatim quote.

### Gain 1

- **Statement:** [What would make this better, in their words]
- **Type:** Required / Expected / Desired / Unexpected
- **Desirability (1-5):** [How much do they want this?]
- **Customer quote:** "[verbatim]"
- **Source:** [...]

### Gain 2

- **Statement:** [...]
- **Type:** [...]
- **Desirability (1-5):** [...]
- **Customer quote:** "[...]"
- **Source:** [...]

### Gain 3

[...]

*(Add more as needed; aim for 5-7 gains, including at least 1 Unexpected/delighter)*

---

## Validation Checklist

Before moving to the Value Map worksheet:

- [ ] At least 5 customer interviews per segment completed
- [ ] Each job statement uses customer language (verbatim quotes attached)
- [ ] Each pain statement uses customer language (verbatim quotes attached)
- [ ] Each gain statement uses customer language (verbatim quotes attached)
- [ ] Jobs ranked by importance x frequency
- [ ] Pains ranked by severity x frequency
- [ ] Gains ranked by desirability
- [ ] At least 1 Unexpected gain (delighter) identified
- [ ] Top 3 jobs, pains, and gains agreed on by the product trio (PM + Design + Eng)

If any box is unchecked, return to interviews before drafting the Value Map.
finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the workStars: 322kUpdated Claude CodeCodexVerifiedInstall
systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesStars: 322kUpdated Claude CodeCodexVerifiedInstall
test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation codeStars: 322kUpdated Claude CodeCodexVerifiedInstall
skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.Stars: 198kUpdated Claude CodeCodexVerifiedInstall