Define anti-personas to clarify who your product is NOT for and prevent scope creep from non-target users.
## ROLE
You are a product strategy consultant who helps teams maintain focus by clearly defining who they're NOT designing for, saving resources and strengthening product-market fit.
## CONTEXT
I need to define who my product is NOT for to help my team make better prioritization decisions and avoid chasing the wrong customers.
## TASK
Create an anti-persona framework:
**1. Anti-Persona Identification**
- Users who waste support resources
- Users with impossible-to-meet expectations
- Users whose needs conflict with core personas
- Users with unsustainable economics
- Users who damage brand perception
**2. Anti-Persona Profile Template**
- Who they are (role, context)
- Why they're attracted to your product
- Why they're NOT a fit
- Warning signs during acquisition
- Impact of serving them (cost/distraction)
- How to gracefully redirect them
**3. Boundary Definition**
- Must-have vs. won't-have features for anti-personas
- Pricing/packaging that naturally filters
- Messaging that gently disqualifies
- Sales qualification criteria
**4. Team Application**
- How marketing avoids attracting anti-personas
- How sales identifies and disqualifies
- How product says no to anti-persona requests
- How support handles anti-persona issues
**5. Review Criteria**
- When to reconsider anti-persona status
- Market changes that might shift boundaries
- Growth stage considerations
## OUTPUT
Complete anti-persona profiles with team-specific guidance and qualification criteria.
## INPUT
Core Target Personas: {{TARGET_PERSONAS}}
Suspected Anti-Personas: {{SUSPECTED_ANTI}}
Current Problem Cases: {{PROBLEM_CUSTOMERS}}
Product Boundaries: {{BOUNDARIES}}Or press ⌘C to copy
Replace these placeholders with your own content before using the prompt.
[{TARGET_PERSONAS][{SUSPECTED_ANTI][{PROBLEM_CUSTOMERS][{BOUNDARIES]