Persona alignment

# Persona alignment

Use when you want to confirm that the features you are planning serve the personas you defined.

## Definitions

Use these meanings consistently in every step.

- **Feature:** A feature record from the provided list report or the single feature the user specified
- **Personas:** Persona records in **Strategy** for the current workspace, unless the user names a different workspace or a specific persona record
- **Persona criteria:** The persona's needs, goals, and pain points
- **Linked records:** Ideas, requirements, goals, initiatives, and dependencies connected to the feature, including everything on the **Related** tab

## Workflow

1. Understand the personas. Read each persona record and extract its needs, goals, and pain points.
2. Understand the features. Read the description and requirements on each feature, then follow linked records for customer evidence and dependencies.
3. Analyze alignment for each feature:
   - Assess whether the feature addresses the persona criteria for each persona
   - Name the specific elements that align and the specific elements that do not
   - Note when a feature is already linked to a persona record, and whether that link matches your assessment
4. Analyze the gaps. Explain why a feature does not fully support the persona, and propose concrete changes such as a requirement to add or a use case to cover.
5. Summarize and recommend. State which features are well aligned, which need work, and which personas nothing in the list serves. An unserved persona is a roadmap gap.

## Rules

- If the features or the personas are not specified, ask short follow-up questions first. Do not infer a persona from a feature name.
- Write for a product management, UX, and marketing audience
- Always report both strengths and gaps. A review that lists only problems is incomplete.
- Keep suggestions constructive and actionable
- Reference every record by reference number and name
- Do not modify any record. Present recommendations and let the user apply them.
- Headers use sentence case. No em dashes, en dashes, or curly quotes.

## Output

```
## <Feature reference number and name>  
- \*\*Persona:\*\* <every persona it applies to>  
- \*\*Alignment assessment:\*\* Yes | No | Partial. <one line of justification>  
- \*\*What aligns:\*\* <specific elements>  
- \*\*Gaps:\*\* <why it falls short, and how to close it>  
  
## Summary  
<which features are aligned, which are not, and which personas are underserved>  
  
## Prioritized next steps  
1. <highest value action>
```

Use a table when comparing more than four features against the same personas. Save the analysis as an artifact so the team reviews it together.

## Quality checks

- Every feature in the input set receives an alignment assessment
- Every gap names a concrete change, not just a shortfall
- Every persona in scope is accounted for, including any that nothing serves