Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.getcore.me/llms.txt

Use this file to discover all available pages before exploring further.

Goal: Create 3 research-backed user personas from empirical data, incorporating jobs-to-be-done, pain points, gains, and behavioral insights to inform product strategy.

​
Tools Required

This skill runs using CORE memory only. No integrations required.

​
Step 1: Gather Research Data

Ask the user to provide or describe:
  • Customer interviews (or summaries)
  • Surveys or user research
  • Analytics data or usage patterns
  • Feedback or support tickets
  • Any existing user segmentation
“What research do you have about your users? Interviews, surveys, usage data?”
If they have none, ask: “Can you describe 3-5 customers you know well?” and work from those stories.

​
Step 2: Identify User Patterns

Review the data and look for:
  • Recurring motivations or goals (Jobs to Be Done)
  • Common pain points
  • Shared use cases or workflows
  • Behavioral similarities
  • Demographic clusters
Ask: “What are 3 distinct user groups or segments in this data?”

​
Step 3: Develop Three Personas

For each distinct user segment, create a persona with: Demographics:
  • Name, role, company/context
  • Seniority, experience level
  • Goals and priorities
Jobs to Be Done:
  • Primary task or goal they’re trying to accomplish (1-2 sentences)
Pain Points:
  • 3 main frustrations or challenges
  • Current workarounds
Desired Gains:
  • 3 outcomes they want to achieve
  • Improvements they’d value
Counterintuitive Insight:
  • 1 surprising behavior, preference, or assumption that contradicts stereotypes
  • Must be grounded in research data
Product Fit:
  • How well this product/solution fits their needs
  • Likelihood to adopt

​
Step 4: Ground Everything in Data

For each insight, verify:
  • Is this supported by the research?
  • Can I cite a quote or data point?
  • Am I making an assumption, or is this observed behavior?
Flag gaps: “I don’t have data on this yet—should we interview more users to confirm?”

​
Step 5: Present the Personas

User Personas Persona 1: [Name, Role] Context [Company, industry, seniority, 2-3 sentences describing their role] Primary Job to Be Done [1-2 sentences describing what they’re trying to accomplish] Pain Points 🚨
  • [Pain point 1]: [Current workaround or impact]
  • [Pain point 2]: [Current workaround or impact]
  • [Pain point 3]: [Current workaround or impact]
Desired Gains ✨
  • [Gain 1]: [Why it matters]
  • [Gain 2]: [Why it matters]
  • [Gain 3]: [Why it matters]
Counterintuitive Insight 💡 [One surprising behavior or preference, grounded in quote or observation] Product Fit [How well does this product solve their needs? Likelihood to adopt? 1-2 sentences]
Persona 2: [Name, Role] [Same format] Persona 3: [Name, Role] [Same format]

​
Edge Cases

  • Too few research data points: Work with what you have, but note: “We have limited data on [segment]. We should interview more to validate.” Continue with 2-3 personas instead of forcing 3.
  • Similar personas: Ask: “How are these two different? What distinct need or behavior separates them?” Merge if they’re too similar.
  • No counterintuitive insight: Don’t force it. Leave blank or note: “Insufficient data to identify.”
  • Assumptions vs. data: Call out when you’re guessing. Ask the team: “Have you seen this behavior, or is this assumption?”