Proto-Persona: Sketch Users from Team Assumptions
A proto-persona sketches your team's user assumptions in a quick workshop, creating shared targets without new research. It aligns Lean teams, but the footgun is treating these guessed profiles as facts rather than hypotheses.
Why it exists
Design teams often operate on unspoken assumptions about who their users are and what those users need. When each teammate holds a different mental picture of the audience, decisions fracture and the product ends up serving no one well. Proto-personas exist to surface those hidden assumptions quickly and forge a shared direction before a single line of code is written.
The mental model
Think of a proto-persona as a sketch drawn from memory rather than a photograph taken in the field. It captures the team's current best guess about user goals, frustrations, and context. The value is not in the accuracy of the portrait but in making the team's implicit beliefs explicit so they can be debated, aligned, and later tested against reality.
How it works
A proto-persona workshop typically runs two to four hours and includes designers, stakeholders, and anyone with user-facing context. Each participant individually drafts two to five simple persona sketches using a basic template. The group then shares their sketches, discusses overlaps and contradictions, and remixes the attributes into a final set of three to six proto-personas. These are not carved in stone; they are treated as living hypotheses.
When to use it
Proto-personas fit teams working in Lean UX environments, startups with no research budget, or organizations with low UX maturity that would otherwise skip persona work entirely. They are also useful when a project is moving fast and the team needs immediate alignment on who they are building for before formal research can be scheduled.
When not to use it
Do not use proto-personas as a permanent substitute for research-backed qualitative personas. If your team treats these assumption-based sketches as verified facts, you risk building features for imagined users while ignoring real behavior. They should also be avoided when major strategic decisions depend on precise user segmentation, since the profiles may reflect internal bias rather than external reality.
One canonical example
A cross-functional team with no budget for new research needs to align on who will use its upcoming product release. In a single afternoon workshop, the designer, product manager, and two developers each sketch three simple proto-persona cards based on their existing assumptions. One participant describes a busy parent shopping on a phone during a commute, while another imagines a price-sensitive student on a laptop. The group discovers they hold contradictory assumptions about mobile versus desktop usage. By remixing the sketches into four shared proto-personas, the team exposes its blind spots and agrees on a responsive design priority before scheduling real interviews to test the hypotheses.
Interview question
What is the main benefit of running a proto-persona workshop before formal user research?
- a.It guarantees the product will match real user needs on launch
- b.It eliminates the need to conduct interviews by capturing the team's expertise
- c.It produces research-backed personas faster than traditional methods
- d.It creates shared, explicit assumptions that the team can align on and later testCorrect
Why? this is the answer
Proto-personas are sketches based on team assumptions, not research, so their value lies in surfacing implicit beliefs for alignment and later validation. Option C is tempting because it sounds efficient, but proto-personas are explicitly not research-backed and should not be treated as verified facts.
Just read this? Test yourself on what you have been reading.
Read the original → nngroup.com
- #ux research
- #personas
- #proto-persona
- #lean ux
You just looked this up. Could you explain it out loud?
That is the part interviews actually test. Tezvyn takes questions like this one and gives you what the interviewer is really checking, the answer that lands, and the mistake that ends the conversation, in the four minutes before your next meeting.
The iPhone app is on the way
We are building it. Until it lands, nothing here is held back from you: every interview card, your saved cards, streaks and the job board all work in Safari, plus hundreds of free practice quizzes of thirty questions each. Sign in and it all carries over to the app the day it arrives.
Want it as an icon? Tap Share at the bottom of Safari, then Add to Home Screen. It opens full screen and the cards you have read stay available offline.
We are hiring for this. Open roles that interview on ux research — each one lists the topics its interview covers.
See open roles