How to write personas that do not feel fake

Personas have a reputation problem because many of them deserve it. A stock photo, a fake name, an age, a quote, and a paragraph of demographic theater do not help a product team build better software.

Useful personas are not character profiles. They are decision tools.

Focus on jobs and friction

A founder-ready persona should answer:

• What job is this person trying to get done?
• What triggers the need?
• What pain or cost do they experience today?
• What workaround do they use?
• What objections would stop adoption?
• What product capabilities matter most to them?
• What would make them trust the product?

That is the information designers, engineers, marketers, and founders can actually use.

Separate user, buyer, and operator

In B2B products, the person using the product is often not the person buying it. The admin configuring it may be a third person. If the persona pack collapses them into one generic "customer", the product will miss important requirements.

Name the roles clearly. Each role has a different success definition.

Keep personas evidence-based

If a persona is not based on interviews, sales calls, support tickets, analytics, or market evidence, mark it as an assumption. Assumed personas are fine early. Pretending they are facts is what gets dangerous.

We created a Persona Pack reference with practical fields, readiness checks, and a starter template for founders.

A good persona does not make the user feel more fictional. It makes the product decision feel less vague.