Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.usecustory.com/llms.txt

Use this file to discover all available pages before exploring further.

Personas help your team talk about important customer types in a simple way. They should make product decisions clearer, not become long research documents.

​
What to include

A useful persona usually includes:
  • Name or label
  • Role or situation
  • Main goal
  • Main problems
  • What success looks like
  • Relevant journeys
Example:

Ops founder

A solo founder who wants to understand customer friction quickly, without building a large research process.
Connect a persona to the journeys they care about. For example:
  • A new buyer persona may link to the trial journey
  • A support-heavy persona may link to the help center journey
  • An admin persona may link to setup and team invite journeys
This helps your team see which customer group is affected by each problem.

​
Keep personas practical

Avoid making personas too detailed. Good personas help answer:
  • Who is this problem affecting?
  • What are they trying to do?
  • What makes this hard for them?
  • What would make the experience better?
If a persona does not help with decisions, shorten it.