A deliberately excluded user archetype that defines who the product is NOT designed for. Antipersonas help teams resist scope creep by articulating the segment whose needs would require compromising core design principles or the business model. Making exclusions explicit is as strategically valuable as defining target users.
Common contexts
- Defining that a B2B SaaS tool is not designed for solo freelancers to block feature requests from that segment
- Explicitly excluding one-time guests from personalization investments on a subscription platform
- Using an antipersona in a critique to reject a feature that only benefits a non-target user type
Use when
Create an antipersona when the team keeps entertaining feature requests from a user type that would require compromising the core product experience — having a documented, stakeholder-approved exclusion transforms a recurring debate into a single reference point.
Avoid when
Don't use antipersonas as a blanket justification for ignoring accessibility or underserved groups — excluding someone because their needs require more design effort is an ethical failure, not a product strategy. An antipersona should document a genuine strategic mismatch, not protect the team from difficult work.
Antipersonas are most useful not when the team is in agreement, but when a vocal stakeholder keeps pulling design scope toward an audience the product was never meant to serve.
Real-world examples
- A children's educational platform explicitly defines an antipersona of an unsupervised adult seeking inappropriate content, informing content moderation and onboarding gate design.
- Slack created antipersonas representing lone freelancers who want a free-forever tool with no collaboration need, helping the team focus features on team-based workflows.
- A fintech startup mapped an antipersona of a user who wants to gamble with investments, steering the product away from features that could enable harmful financial behaviour.