Persona Library
Community-sourced UX research

Who actually uses these products,
and what made them stay.

Deep persona profiles for the tools that run modern work. Community-validated. Exportable. Open for contribution.

6
sanityAPP-186
4 comments

The Sanity Content Architect

A developer or content architect who uses Sanity because they think about content as structured data, not pages. They design content models that serve web, mobile, email, and API consumers from a single source. They've built custom studios, created real-time collaborative editing environments, and used GROQ to query content in ways traditional CMS query languages can't express. They are the architect of the content layer, and they treat content modeling with the same rigor as database schema design.

Aha

Not a single dramatic moment — more like a Tuesday at 3pm when they realized they hadn't thought about customizing the Studio deeply requires significant React knowledge, raising the bar for non-senior developers in two weeks.”

sanityAPP-073
4 comments

The Sanity Developer-Content Team

A developer who chose Sanity for a project that needed a content infrastructure serious enough to model complex relationships and flexible enough to be customized for a non-developer content team. They built the schema. They configured the Studio. They wrote the GROQ queries. The content team uses what they built every day. The developer's relationship with Sanity is: maintenance, evolution, and occasional deep satisfaction when the content model they designed months ago handles a new requirement gracefully.

Aha

Not a single dramatic moment — more like a Tuesday at 3pm when they realized they hadn't thought about schema changes that require migration scripts for existing content — the cost in two weeks.”

craftAPP-017
3 comments

The Craft Docs Intentional Writer

A product manager, writer, consultant, or knowledge worker who uses Craft as their primary document and note environment because it is the only tool that takes both writing and structure seriously at the same time. They're on Apple devices — Mac and iPhone, usually iPad. They've tried Notion (too database-y), Bear (too simple), Obsidian (too much tinkering), and Apple Notes (not embarrassed about this, just limited). Craft is what they settled on. The fact that it looks good is not superficial to them — environment affects their thinking.

Aha

It happened mid-workflow — they're preparing a strategy document for a quarterly review.”

notion-aiAPP-167
3 comments

The Notion AI Content Strategist

A content strategist, knowledge manager, or team lead who uses Notion AI as part of their daily workflow inside Notion. They don't use it to write blog posts from scratch — they use it to summarize 45-minute meeting transcripts into action items, turn rough notes into structured documents, answer questions about information buried in the team's wiki, and draft from templates. They've found the sweet spot: AI handles the structure, they handle the thinking.

Aha

The shift was quiet.”

perplexityAPP-164
4 comments

The Perplexity Research Analyst

A research analyst, journalist, consultant, or knowledge worker who has replaced their Google-and-10-tabs workflow with Perplexity. They don't search for links — they ask questions and expect synthesized answers with citations. They use it for competitive analysis, market research, fact-checking, and deep dives into topics where they need to learn fast. They've learned which types of questions Perplexity handles well (factual synthesis) and which it doesn't (opinion-based, very recent events). They trust it more than ChatGPT because of the citations, but they still verify.

Aha

A teammate asked how they managed get comprehensive, cited answers to complex research questions in minutes instead of hours.”

liveblocksAPP-184
4 comments

The Liveblocks Real-Time Developer

A frontend developer who needs to add real-time collaboration to an existing app — live cursors, presence indicators, shared document editing, or collaborative whiteboards. They chose Liveblocks because building WebSocket infrastructure from scratch is a project in itself, and they need to ship the feature, not the infrastructure. They understand React, they understand state management, and Liveblocks extends those mental models to multiplayer. They are building the "Google Docs" experience for their product.

Aha

It happened mid-workflow — the developer is adding collaborative editing to a project management tool.”

Recognize yourself in one of these?

Every field in every persona can be confirmed, corrected, or extended by real users. Your lived experience is more accurate than any researcher's archetype.

+ Contribute to a persona