A pattern-based user type derived from behavioral clusters across research data rather than demographics or job titles. Archetypes describe how people approach goals and interact with systems — for instance 'the delegator' or 'the explorer' — making them more transferable across product contexts than persona formats tied to specific demographics.
Common contexts
- Identifying that power users cluster around 'efficiency-seekers' regardless of their job title or industry
- Using behavioral archetypes to design an onboarding flow that serves both explorers and task-focused users
- Reframing a persona library around archetypes when the product expanded to a new vertical
Use when
Use archetypes over demographic personas when designing for a platform used across multiple industries or roles — a 'systematic planner' behaves consistently whether they're a marketing manager or a software developer, which makes the archetype more durable as the product scales.
Avoid when
Archetypes built without actual research data are just named stereotypes — calling someone 'the explorer' without behavioral evidence to back it up creates a false sense of rigor. Never present an archetype as validated unless it emerged from clustering real observations, not workshop assumptions.
Archetypes earn their value by surviving product pivots — if your user types need to be completely rewritten when the target industry changes, you built personas, not archetypes.
Real-world examples
- Mailchimp's brand voice is built around the 'Friend' archetype—approachable, helpful, and occasionally funny—shaping all UX copy from error messages to onboarding tooltips.
- Apple positions itself as the 'Creator' archetype, which informs its product design language: minimal, empowering, and aesthetically refined.
- Harley-Davidson embodies the 'Outlaw' archetype, and this identity permeates every touchpoint from the website's dark visual language to its community forum design.