rampstackco/claude-skills / skills/brand-discovery
brand-discovery
VerifiedRun upstream brand discovery covering audience research, competitive landscape, category dynamics, problem space, and positioning territory exploration. Use this skill at the very start of a brand or website project when the user needs to understand who they're for, who they compete with, what the audience actually needs, and where the brand could plausibly stand. Triggers on brand discovery, audience research, market research, competitive scan, category research, customer research, who is this for, who are we, positioning research, intake, kickoff. Also triggers when a creative brief is requested but the upstream inputs (audience, competitors, problem space) are not yet clear.
| File | Kind | Size |
|---|---|---|
| README.md | markdown | 356 B |
| SKILL.md | skill md | 9.5 KB |
| references/discovery-report-template.md | markdown | 4.5 KB |
| references/interview-guide.md | markdown | 6.8 KB |
references/interview-guide.md
View on GitHub# Audience Interview Guide
A guide for conducting 30 to 45 minute interviews with current customers, prospects, or audience members during brand discovery.
The goal of interviews is not to validate assumptions. It is to find surprises. Plan to be wrong about most of what you think you know.
---
## Before the interview
### Who to interview
For a typical brand discovery, talk to 5 to 8 people across these segments:
- **Active customers** who have been using the product for 3+ months (deep understanding)
- **Recent customers** who joined in the last 30 days (still remember the buying journey)
- **Lapsed customers** who churned (the most informative; understand why people leave)
- **Prospects who didn't buy** (understand objections)
- **Power users** in adjacent categories (understand alternatives and substitutes)
If the project is for a new brand with no customers yet, interview members of the target audience using competitive products or substitutes.
### Recruiting
Recruit through:
- Customer email list with a thank-you incentive
- Sales team referrals
- LinkedIn outreach to titles matching the audience profile
- Existing user research panels
- Niche communities (Reddit, niche Slack groups, professional forums)
Compensate participants. $50 to $100 in cash or product credit is reasonable for 30 minutes.
### Logistics
- 30 to 45 minutes is the right length. Longer fatigues both sides.
- Record (with consent). Take notes too in case the recording fails.
- Use a video tool that creates transcripts automatically.
- Send a calendar invite with a clear agenda.
- Confirm the day before.
---
## Question framework
Structure interviews in three sections: their world, the problem, and how they currently solve it.
### Opening (3 to 5 minutes)
Get them talking. Build rapport. Establish that there are no wrong answers.
- "Tell me a bit about yourself and what you do."
- "Walk me through a typical day. What does work look like?"
- "How long have you been doing this kind of work?"
These warm-up questions also surface context you'll need later.
### Section 1: Their world (10 minutes)
Understand the context the brand fits into.
- "When you think about [the problem area or category], what comes to mind?"
- "What's the part of your work or life this connects to?"
- "How important is [the problem area] in the bigger picture of what you do?"
- "Who else is involved in [the problem area]? Coworkers? Family? Clients?"
- "What's the goal you're trying to hit in this area?"
Listen for: priorities, stakeholders, vocabulary, time pressure.
### Section 2: The problem (10 to 15 minutes)
Surface the actual problem, not the surface symptom.
- "Tell me about the last time you ran into [the problem]. Walk me through what happened."
- "What was frustrating about that?"
- "What did you try to do about it?"
- "What did you wish had happened instead?"
- "What's the cost of this problem? Time? Money? Stress? Relationships?"
- "Have you ever just decided to live with it instead of solving it? Why?"
Listen for: emotional weight, the real cost, the workarounds people invent, the resignation.
The key follow-up: **"Tell me more about that."** Use it relentlessly. Most insight is one or two layers below the first answer.
### Section 3: How they solve it now (10 to 15 minutes)
Understand the current toolkit and the alternatives considered.
- "What do you currently use to address [the problem]?"
- "How did you start using [their current solution]? What were you using before?"
- "What did you consider but not pick? Why not?"
- "What do you wish [your current solution] did better?"
- "If you could wave a magic wand and have [the problem] solved perfectly, what would that look like?"
- "Imagine a tool came along that promised to solve [the problem]. What would it have to be true for you to switch?"
Listen for: the switching cost, the unmet needs, the specific moments where current solutions fail.
### Closing (3 to 5 minutes)
- "Is there anything I should have asked but didn't?"
- "Is there anyone else you think I should talk to about this?"
- "Would you be open to a follow-up if questions come up later?"
---
## Common interview pitfalls
### Leading questions
**Bad:** "Do you find it frustrating when [your assumption]?"
**Better:** "Tell me about your last experience with [the activity]."
The first question telegraphs the answer you want. The second lets them tell you what was actually frustrating, including things you didn't predict.
### Asking for solutions
**Bad:** "What features would you want in [the product]?"
**Better:** "What's frustrating about how this works today?"
Users are not product designers. They are the world's leading experts on their own frustrations. Mine the frustrations; you'll design the solutions.
### Validating instead of investigating
**Bad:** "Would you use [feature description]?"
**Better:** "When was the last time you needed something like that? What did you do?"
Hypothetical answers are useless. Past behavior is informative.
### Closed questions
**Bad:** "Was that frustrating?"
**Better:** "How did you feel about that?"
Yes/no questions kill the conversation. Open questions keep it going.
### Talking too much
If you're talking more than 20 percent of the time, you're talking too much. Your job is to listen, follow up, and get out of the way.
---
## Synthesis
After all interviews, synthesize across them.
### Step 1: Tag the transcripts
Read every transcript. Tag passages by theme:
- Pain points
- Workarounds
- Aspirations
- Vocabulary they use
- Emotional moments
- Surprising statements
### Step 2: Identify recurring patterns
A theme that appears in 3+ interviews is signal. A theme in 1 interview is interesting but anecdotal.
### Step 3: Look for surprises
The most valuable findings are things you didn't expect. List them explicitly. These often become the basis for distinctive positioning.
### Step 4: Identify quotes
The right quote captures more than a paragraph of synthesis. Pull 5 to 10 quotes that capture the core insights.
### Step 5: Write the audience section of the discovery report
For each segment:
- Who they are (with the specificity you've earned)
- What they're trying to do
- What's getting in the way
- How they currently solve it
- What they wish were different
- Anchor quote (one strong verbatim quote)
---
## What to avoid
- Treating the interview as a sales pitch
- Asking about your specific product or feature ideas (validation theater)
- Skipping interviews because "we already know our customer" (you don't)
- Interviewing only happy customers (lapsed customers are more informative)
- Doing 1 or 2 interviews and declaring "we did research"
- Skipping synthesis and going straight to "here's what we learned" without rigor
5 interviews is the minimum to find patterns. 8 is comfortable. 12+ has diminishing returns for most projects.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |