proto-persona
Create a proto-persona from current research, market signals, and team knowledge. Use when you need a working customer profile before deeper validation.
Author
Category
Product DesignInstall
Hot:2
Download and extract to your skills directory
Copy command and send to AI Agent for auto-install:
Download and install this skill https://openskills.cc/api/download?slug=deanpeters-skills-proto-persona&locale=en&source=copy
Proto-Persona
Skill Overview
Proto-Persona is a hypothesis-driven proto-persona tool that helps product teams quickly build a structured target-user profile in 15–25 minutes when formal user research is unavailable, based on existing data, market signals, and team experience. It is used to align the team’s understanding and plan subsequent validation research.
Use Cases
Core Features
[ASSUMPTION—VALIDATE], clearly distinguishing “known facts” from “hypotheses to validate.” This prevents the team from treating assumptions as conclusions and makes those assumptions open to discussion and challenge.Frequently Asked Questions
What is the difference between a proto-persona and a validated user persona?
A proto-persona is a working hypothesis based on assumptions and limited information that can be completed within a few hours to a few days. It is used for early team alignment and to guide initial design decisions. A validated persona is based on user research conducted over several weeks to several months, offering higher confidence and relative stability. Proto-personas evolve quickly and are continuously updated as research findings emerge; the two are sequential stages rather than substitutes for one another.
Can it be used without any user research data?
Yes. That is precisely its purpose: to build a profile from any available signals, including support tickets, sales anecdotes, analytics, and team experience. However, the skill explicitly requires that you do not fabricate information—when information is missing, you should mark the gap and plan research to fill it. User quotes in the profile should either come from real source material or be marked as
[PLACEHOLDER—NEEDS RESEARCH].After creating a persona, how can you avoid treating it as fact?
Three actions: label uncertain content with
[ASSUMPTION—VALIDATE]; share it with the team to test whether it “feels like a real person”; and use the persona to guide interview planning while continuously updating it based on new learning. The skill’s section on common pitfalls also clearly warns that treating assumptions as facts, fabricating quotes, creating ten personas at once, and never updating a persona for six months are all anti-patterns to avoid. It also cannot replace quantitative data or formal user research.