Every UX course tells you to build user personas. Very few of them tell you how to do it when you are a student with no clients, no budget, no access to a research panel, and no team to help you conduct interviews.
Here is what actually works. I've used this process to build personas for capstone projects, freelance pitches, and my own portfolio — all without spending a single peso on research tools.
"A persona built from five real conversations is worth more than one built from a hundred assumptions."
What a Persona Actually Is (and Isn't)
A persona is a fictional but data-grounded representation of a user type. It gives your design decisions a human face. When you're debating whether to add a feature or simplify a flow, you ask: "Would Marco need this? Would this frustrate Ana?"
What a persona is not: a made-up character based on gut feeling. A persona built from assumptions is not a research artifact — it's a bias-confirming exercise that makes you feel like you did user research without actually doing any. The quality of your persona is only as good as the data behind it.
Free Research Methods That Actually Work
How to Structure a Persona That Designers Actually Use
A persona document with 20 fields nobody reads is useless. Here is the minimum viable structure that makes personas actionable:
-
Step 1
Name and photo. A real-looking name and a stock photo (use Unsplash or UIfaces.io) make the persona feel like a real person. This is not vanity — it reduces the psychological distance between "user" and "person."
-
Step 2
Core bio (3 lines max). Age, occupation, location, tech comfort level. This sets context instantly. Don't expand it — if you need a paragraph here, you have too many personas.
-
Step 3
Goals (2–3 bullets). What outcome are they trying to achieve? These should be their goals — not your product's goals for them. There's a big difference between "complete a task quickly" and "feel in control of the process."
-
Step 4
Frustrations (2–3 bullets). The specific things that go wrong for them today, ideally sourced directly from interviews or reviews. These drive your design decisions more than goals do.
-
Step 5
One direct quote. A sentence in their voice, synthesised from your research. "I just want to do this without having to read a manual." This becomes the sanity check you return to during design reviews.
Here is what a finished persona looks like using this structure:
Ana Jimenez
22 · BSIT Student · Bataan, Philippines
Intermediate — confident with social media and Google Workspace, avoidant of new software without tutorials.
Android phone (primary), shared family laptop for school work. Slow internet at home.
Build a portfolio before graduation · Land a remote design internship · Learn Figma without spending money
Overwhelmed by "where to start" · Portfolio templates look generic · Imposter syndrome when comparing work online
Researches everything on YouTube before committing. Asks in Facebook groups. Saves tutorials but doesn't finish them. Works best at night after family responsibilities are done.
Common Mistakes to Avoid
-
Making one persona that covers everyone
A persona that tries to represent all your users represents none of them. Two focused personas are infinitely more useful than one vague one that describes "a person who uses technology."
-
Listing demographics instead of behaviours
"Female, 25–34, college-educated" is not a persona — it's a marketing segment. What matters is what they do, how they think, and what frustrates them. Behaviour drives design. Demographics don't.
-
Building personas and never referencing them again
A persona that lives only in a Figma page nobody opens is just documentation theatre. Put the name and quote somewhere visible during design — on a sticky note, a Notion page you keep open, or literally printed out.
-
Treating personas as permanent
Users change. Products change. A persona based on research done six months ago may no longer reflect your actual users. Revisit and update them whenever you gather new data.
Conclusion
You do not need a ₱50,000 research budget to build personas that work. You need five honest conversations, a few hours reading real user feedback online, and the discipline to synthesise what you find into a document you will actually use.
The goal of a persona is to keep you from designing for yourself. It forces the question: "Is this decision serving Ana — or is it serving my aesthetic preference?" That question, asked consistently, is what separates good design from self-indulgent design.
Start with one. Five interviews, one afternoon, one page. Then use it in your next critique and watch how the conversation changes.
