Building Personas That Actually Help

You don't need a psychology degree or expensive research budget to build useful personas. You need real data about BC's population and about 30 minutes to think through who struggles with your work.

What Makes a Good Persona

Part 1 showed why personas matter—they help you catch barriers before launch, not after complaints arrive. A useful persona has five components. You need demographics—age, location, family situation, employment. You need context: digital access, language comfort, mobility, income level. You capture what they're trying to accomplish with government services and what obstacles they face. You include a quote that captures their perspective.

That's it. You're not writing a novel. You're creating a reference point that helps you spot problems.

Four BC Personas You Can Use Right Now

Margaret Chen is a 73-year-old retiree living alone in Victoria on a fixed income. She has a smartphone but no computer, gets uncertain about new technology, though she maintains strong community connections. She needs clear information about seniors' services, accessible healthcare, and simple application processes. Small screen sizes frustrate her. Complex forms assume she has email access. Government jargon confuses her. "I'm willing to learn new things, but I need instructions I can follow step by step."

James Blackwater is 38, lives in Northern BC, and is a member of the Carrier First Nation with a family of four. His internet connection is spotty. He works shifts while his school-age children need his attention. He needs services accessible outside business hours and information relevant to Indigenous communities. Service hours don't match his schedule. In-person services require long drives. Service design often misses cultural context. "If I have to drive 90 minutes to an office that's only open when I'm at work, that program doesn't exist for me."

Amira Hassan is 29, lives in Surrey, and arrived from Syria 18 months ago with two young children. Her written English is strong, but she's still building confidence speaking it. She relies heavily on community networks. She needs clear explanations of programs available to newcomers and culturally appropriate help navigating services. Government structures are unfamiliar. She's uncertain about eligibility. She fears making mistakes. "I don't know what I don't know—how do I find out what services exist?"

Dev Sharma is 45, runs a small business in Kelowna, and uses a wheelchair. He's tech-savvy with excellent online access but maintains a busy schedule. He needs efficient digital services and physical accessibility when in-person visits are required. PDF forms aren't screen-reader compatible. Buildings lack accessible entrances. Too many services offer "just call us" as the only option. "I can run a business online, but I can't fill out a government form without printing it?"

Where to Find Real Data

Don't invent details. Build personas from actual information: BC Stats for demographic data, ministry service usage analytics for patterns in who accesses what, community consultation records for barriers people actually report, accessibility feedback your ministry has received, GBA+ resources for equity considerations, and frontline staff who interact with these populations daily. The goal isn't creative writing. It's capturing real patterns that affect real people.

Building Your Own Ministry-Specific Persona

Start with someone you know struggles with your work. Maybe it's a population your frontline staff mention frequently, or a group that shows up in complaints.

Where do they live? Urban and rural locations have different internet reliability and service access. How do they access information—phone, computer, or in-person? What's their relationship with government services? Are they frequent users, first-time users, or uncertain about the system? What language considerations exist? What barriers have they mentioned or experienced?

Spend 15 minutes documenting this. You now have a persona.

Warning: Common Mistakes

Don't confuse personas with stereotypes. "Old people don't like technology" is a stereotype. "Margaret has a smartphone but gets frustrated when apps don't work predictably" is a persona detail based on actual behavior patterns.

Don't make them too perfect. If your persona has no barriers and understands everything, they're not useful. The point is to identify where things break down.

Don't use them to skip consultation. Personas help you prepare better questions and design better consultation processes. They don't replace talking to real people.

Don't let them gather dust. If you build personas and never use them, you wasted your time. The value is reviewing your work through their eyes.

Test Your Persona

Show your persona to a colleague and ask: Does this feel like a real person or a caricature? Are the barriers specific enough to be actionable? Would this persona reveal problems in our current work?

If your colleague says "yeah, we serve people like this all the time," you're on track.

Putting Personas to Work

You have four ready-to-use personas and know how to build your own. Part 3 covers practical prompting templates and three detailed scenarios: using personas to test a new service, review a policy, and evaluate vendor proposals.