User Persona

Most personas are a stock photo, an age range and a favourite coffee. Nobody opens them twice, because there is nothing in them a team can build from.

What is on the board

• The header. Name, then a single line of role, age, city, device and frequency. Under it, a pull quote in her own words, taken from an interview.
• 01 Bio. A short paragraph of how she works: where, with whom, at what time, and how she pays. Times and places, not adjectives.
• 02 Goals, 03 Frustrations, 04 Behaviours. Three bulleted blocks, four lines each. Goals are what she is trying to get done, frustrations are what stops her, behaviours are what she already does without being asked.
• 05 Tools and apps. What is actually on her phone and which of it she uses for this job, including the apps she uses for something else.
• 06 Motivations. Four labelled bars scored out of five. The fill is bound to the accent variable, so the bars restyle with the board.
• 07 A day with the product. Three timestamped lines through one real session, start to finish.
• 08 Design implications. Three numbered lines. What this persona means for the interface, so the board does not end at the poster.

Before and after

• Before: A stock photo and a favourite coffee.
  After: Eight blocks a team can build from.
• Before: “Tech savvy, 25 to 34.”
  After: A bio with a time, a place and a payment method.
• Before: Adjectives about the user.
  After: Observed behaviours, in the order she does them.
• Before: Motivations described in a paragraph.
  After: Four bars, scored out of five.
• Before: A persona that ends at the poster.
  After: Three design implications at the bottom of it.
• Before: An Arabic persona translated from the English.
  After: A Levantine bio, and bars that fill right to left.

What lands in the download

• FIG The template. One Figma file, four pages: English light, English dark, Arabic light, Arabic dark, all on one variable collection. Auto layout throughout, so every cell grows as you type.
• PDF The guide. 8 pages: the four boards, a five step how to use, and a glossary of every field with its Arabic label beside it.
• PDF, MD Pro. Five Claude prompts: fill it from my notes, critique it, Arabic edition, turn it into insights, push it to Figma.
• PDF Pro. The facilitation guide. A thirty minute session: what to ask, in what order, and how to close it.
• FIG Pro. A second worked example in a second market, as its own Figma file, so you can read the method instead of guessing at it.
• FOLDER Pro. The Claude Code skill. Point it at your notes folder and it fills the board, then writes it into your own Figma file by layer name.

Who it is for, and when to run it

For product teams who need one agreed user before the first screen. Build it from real interviews, one persona per job to be done, and pin the design implications where the team argues.

Two editions. Free: the Figma file and the PDF. Pro, 10 dollars: adds the five prompts, the facilitation guide, the second worked example and the Claude Code skill.