user-personas

Build research-backed customer and user personas from interviews, surveys, and feedback data.

Updated Jul 1, 2026
One-click install
npx skills add https://github.com/MilUX-Ltd/footing --skill user-personas-milux-ltd
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: user-personas
Source: https://github.com/MilUX-Ltd/footing/tree/main/footing/template/Skills/pm-skills/user-personas
Command: npx skills add https://github.com/MilUX-Ltd/footing --skill user-personas-milux-ltd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Persona work often collapses into demographic stereotypes or generic profiles that cannot guide real product decisions. This Skill builds personas grounded in actual research evidence, separating the customer who buys from the user who operates, so segmentation and value-proposition work connect without translation. ## Core Features & Use Cases - Two persona types: Distinguishes the customer persona (who selects and pays, judging on cost, risk, and procurement) from the user persona (who operates daily, judging on real working experience). - Evidence-grounded method: Extracts recurring purposes, pains, gains, and behaviours from interview transcripts, survey responses, support data, and win/loss notes, with quotes and flagged gaps. - Purpose-based clustering: Groups people by job to be done and selection criteria rather than demographics, then validates that personas are distinct and non-overlapping. - Use Case: After ten customer interviews for a B2B service, use this Skill to produce one customer persona (the budget holder) and two user personas (the frontline operators), each with a primary purpose, top pains, top gains, and explicit selection criteria. ## Quick Start Build customer and user personas from the attached interview transcripts and survey responses, capturing each persona's purpose, pains, gains, and what they judge on.

Frequently Asked Questions about user-personas

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build user personas from interview data?▼

Extract recurring purposes, pains, gains, and behaviours from transcripts, then cluster people by the job they are hiring the product for rather than demographics. Capture each persona's primary purpose, top pains, top gains, and selection criteria, quoting evidence where possible.

What is the difference between a customer persona and a user persona?▼

A customer persona selects and pays, judging on total cost, procurement ease, risk, and supplier track record. A user persona operates the offering daily and judges on the experience under real working conditions. B2B work usually needs at least one of each.

Should personas be based on demographics or jobs to be done?▼

Personas should be clustered by purpose and selection criteria, not age, seniority, or organisation size. Firmographics are recorded as attributes only; two personas sharing the same purpose and criteria should be merged into one.

How many personas should a market segment have?▼

Typically one customer persona and one or two user personas per segment. Each must be grounded, distinct, and non-overlapping; if two share the same purpose and judgement criteria, they are one persona.

What if my persona is built on thin evidence?▼

A persona built on thin evidence is a hypothesis and should be labelled as such on the artefact. Flag data gaps explicitly and plan further interviews or surveys before using it to drive product decisions.