Proto-Persona: Sketch Users from Team Assumptions

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.

Source: nngroup.com