User Persona

Create a User Persona tailored to your inputs.

Share:XWhatsAppLinkedIn
You are a senior UX researcher who creates empathy-driven, realistic user personas.

Create a detailed user persona for the following product:

Product Name: {{product_name}}
Target Audience: {{target_audience}}
Use Case: {{use_case}}

Generate a comprehensive user persona in Markdown format. Include:
1. Overview (name, age, occupation, location)
2. Bio (2-3 sentences describing this person)
3. Goals (3-5 specific goals related to the product)
4. Pain Points (3-5 frustrations or challenges)
5. Behaviors (3-5 behavioral patterns)
6. Motivations (what drives this person)
7. A memorable first-person quote
8. Preferred channels (where they spend time online)

Make the persona realistic, specific, and directly relevant to the product and use case provided.

Fill the 3 fields below to customize.

Customize before copy

Fill these — your prompt updates live.

Stays in your browser. Nothing sent anywhere — we don't run a server for this.

Using Gemini, Llama, Mistral or local LLMs? Copy the prompt and paste — no deep-link supported.

Sample

Example output

What the prompt produced when KLI ran it for a real case. Yours will vary by model and inputs.

# User Persona: Priya Sharma

## Overview
**Name:** Priya Sharma
**Age:** 32
**Occupation:** Product Manager
**Location:** Bangalore, India

## Bio
Priya is a product manager at a mid-sized SaaS company. She leads a cross-functional team and is constantly juggling stakeholder requests with engineering capacity. She values clarity and efficiency above all else, and is always on the lookout for tools that reduce friction without adding complexity.

## Goals
- Ship features that move key business metrics
- Align engineering and design teams around a shared roadmap
- Reduce time spent in status meetings and sync overhead
- Build a product her users genuinely love

## Pain Points
- Difficulty prioritizing competing feature requests from multiple stakeholders
- Lack of visibility into actual customer pain points without heavy research cycles
- Too many disconnected tools that don't share data with each other
- Hard to get engineering buy-in on product decisions without solid data

## Behaviors
- Starts every morning reviewing analytics dashboards and user feedback queues
- Runs weekly syncs with engineering and design teams
- Uses async video updates to replace recurring status meetings
- Documents decisions in Notion to keep the team aligned asynchronously
- Spends Friday afternoons reviewing customer support tickets for product insights

## Motivations
Priya is driven by impact. She wants to see her work translate into measurable improvements for both users and the business. Reco
Related

You might also like

Made with KLI — extracted from real tools, shared free. krakelabsindia.com