Skip to content
Strynal, Digital Agency

Strategy 7 min read

Customer Personas That Teams Actually Use

Most customer personas end up in a drawer. Learn how to build personas grounded in real research, jobs-to-be-done thinking, and day-to-day decisions that matter.

By Strynal Team

Most customer personas die in a slide deck. A workshop produces four colorful portraits (Marcus the Millennial, Sarah the Small Business Owner) and six months later nobody can remember what Marcus was supposed to want. The personas were built for a presentation, not a decision. That is the problem this post is here to fix.

Why customer personas gather dust

The failure mode is almost always the same: personas built from assumption rather than evidence, loaded with demographic detail that sounds specific but tells you nothing about buying behavior.

Age, job title, and a favorite coffee order do not explain why someone switched vendors, why they stayed, or why they almost bought and then didn’t. That information has to be earned through real research: interviews, support ticket analysis, win/loss conversations. Without it, you are designing for a composite fiction.

There is a second failure mode: personas that are too broad to be useful. A “persona” that describes everyone who has ever bought from you is really a market segment, not a persona. Personas earn their keep by being precise enough that someone on your team can say, “this feature is for Marcus, not Sarah,” and have that mean something.

A persona is only as useful as the decision it can break a tie between.

Ground personas in research, not gut feel

The gap between personas that inform work and personas that decorate hallways usually comes down to one thing: how the data was gathered.

Start with the people who already bought

Your best source is customers who made the decision you are trying to understand. Schedule fifteen to twenty minute interviews. Do not ask what they like about your product. Ask what was happening in their world when they started looking for help. Ask what they almost bought instead. Ask what almost stopped them from buying at all.

These conversations produce language. Specific, direct, unpolished language that your team cannot write from imagination. That language is the raw material of a useful persona.

Layer in behavioral data

Interviews tell you why. Behavioral data tells you what. Look at onboarding completion rates segmented by company size. Look at which features power users touch that new users ignore. Look at which support topics correlate with churn. Each of these is a signal about what a segment actually needs, as opposed to what they say they need.

Do not skip the exits. If you can talk to churned customers or prospects who chose a competitor, their honesty is worth ten satisfied-customer interviews. They will tell you the real trade-offs.

Jobs-to-be-done is the frame that makes it stick

The jobs-to-be-done (JTBD) framework, developed by Clayton Christensen and refined by practitioners like Bob Moesta, shifts the question from “who is this person?” to “what progress are they trying to make?” People don’t buy products. They hire them to do a job.

When you build personas around a JTBD frame, you get answers that transfer across demographic segments. A solo consultant and a VP of Marketing might be completely different people on paper, yet hire your product for the same job: “help me prove that this initiative is working.” That insight shapes product decisions, messaging, and the strategy and positioning work that frames the whole brand.

The JTBD angle also surfaces the emotional and social dimensions of a purchase. The functional job (automate this report) is usually obvious. The emotional job (feel confident in the board meeting) and the social job (look like someone who makes smart decisions) are where differentiation lives.

Build personas that name the job, not just the person

A persona that works in practice has a different shape than the traditional demographic card. Here is a structure that holds up.

Core components of a useful persona

1. The situation. What was happening in their world when the need surfaced? This is context, not demographics. “Two direct reports quit in three months and the team is rebuilding” is far more useful than “35–44, mid-level manager.”

2. The job they’re hiring for. One sentence: what progress are they trying to make, and what does success look like? This connects directly to your value proposition and messaging decisions.

3. The anxieties that slow the decision. What could go wrong? What are they worried about admitting to themselves or their team? If you know the fear, you can address it without the customer having to voice it.

4. The competing alternatives. Not just direct competitors: what else would they do with this budget or this time if your product didn’t exist? Staying with the spreadsheet is a competitor. Hiring a contractor is a competitor. Doing nothing is a competitor.

5. The trigger. What changed that made now the moment to act? Triggers tell you where to be and what to say at the right time, which is why they matter for messaging architecture, buyer journey mapping, and channel strategy.

Keep it to three, maybe four

More personas does not mean more precision. It usually means less clarity. If your team cannot hold your personas in working memory, they will not use them. Three well-researched personas are worth more than eight demographic sketches.

If you genuinely serve very different audiences, consider building a separate ideal customer profile and persona set for each, rather than one master list.

How to keep personas alive in day-to-day work

A persona is a living document or it is a historical artifact. The difference is whether the team refers back to it when decisions are being made.

Attach personas to decisions, not documents

The most effective way to keep personas in circulation is to make them the frame for prioritization conversations. “Which persona does this feature serve?” should be a normal question in a product or content review. Competitive analysis gets sharper when you run it through a persona lens. You are not just mapping what competitors offer, but understanding whose job they are trying to win.

Build a lightweight habit: when a new piece of copy, a new feature, or a new campaign is being reviewed, name the persona. If nobody can name one, that is a signal the work is unfocused.

Schedule persona reviews

Set a calendar reminder every six months. Block two hours, pull up the transcripts from recent customer interviews, and ask: is this still true? Markets move. Buyer profiles change. The startup founder who needed scrappy solutions in Year 1 needs different things in Year 3. Your personas should reflect that drift.

If you have not done primary research in over a year, your personas are probably stale. Not wrong, just stale. The skeleton holds but the details have aged.

Use personas in hiring and onboarding

This is underused. When a new team member joins, walking them through your personas, including the research and reasoning behind them, is one of the fastest ways to give them a working model of who you serve. It is also a healthy forcing function: if you cannot explain the persona out loud to a new hire, the persona is probably not as sharp as it looks on paper.

The research trap to avoid

There is one research pattern that consistently produces personas that feel rigorous but aren’t: surveying your existing audience and treating the averages as ground truth.

Survey data tells you what people say; it rarely tells you what they do. It also over-represents people who are engaged enough to answer a survey, which skews toward your most committed customers, not the whole range of people you need to understand. Use surveys to generate hypotheses. Use interviews to test them.

The brand voice and tone work at most agencies runs into the same problem: they survey customers about adjectives they like (“innovative,” “trustworthy”), then write brand guidelines around adjective lists. What they needed was to know what job the brand is being hired for.

How Strynal approaches persona work

At Strynal, personas are built into how we start strategy engagements, not as a deliverable to hand over, but as a shared frame that the whole project runs through. Every engagement starts on a blank page: no recycled archetypes, no demographic templates borrowed from a previous client. We do the research, identify the jobs, and build personas that your team will actually reference when decisions get hard.

If your current personas are living in a drawer, or if you are starting from scratch with a new product or a repositioned brand, let’s talk through the work. The research phase is where the real leverage is, and it is where most teams shortcut too early.