Persona Development: Why Most Audience Profiles Collect Dust

Persona development is the process of building structured profiles of your target audience based on real behavioural, attitudinal, and contextual data, so that your marketing decisions reflect how actual people think and buy rather than how you hope they do. Done well, it sharpens briefs, focuses spend, and gives creative teams something concrete to work against. Done badly, it produces laminated slides with stock photo faces and fictional names that nobody references after the workshop.

Most persona work falls into the second category. Not because marketers lack skill, but because the process is usually treated as a deliverable rather than a decision-making tool. This article is about building personas that get used.

Why Most Persona Work Fails Before It Starts

I have sat in more persona workshops than I care to count. The format is usually the same: a facilitator draws boxes on a whiteboard, the room brainstorms job titles and pain points, someone suggests a name like “Marketing Mary” or “Decision-Maker Dave,” and by the end of the session the team feels like they have accomplished something. They have not. They have documented their existing assumptions in a more organised way.

This is the core problem with how persona development gets practiced. It is treated as a creative exercise rather than a research exercise. The starting point is internal knowledge rather than external evidence. And internal knowledge, however well-intentioned, is shaped by proximity bias. You know the customers who complain loudly, the ones who champion your product, and the ones your sales team talks about most. You do not have a representative picture of the full customer base, and you almost certainly have no picture at all of the people who considered you and chose someone else.

When I was running an agency and we took on a new client in financial services, their existing personas were beautifully designed. Proper brand colours, consistent layout, printed and framed in the marketing office. They had been built two years earlier based on a single focus group and a survey of existing customers. The problem was that the product had since expanded into a completely different segment, and the personas had never been updated. The team was writing briefs for an audience that no longer represented the majority of their revenue. Nobody had noticed because the personas looked authoritative.

Good persona development starts with honesty about what you actually know versus what you are assuming. That distinction matters more than any template or framework.

If you want to understand how persona development fits into a broader research and intelligence programme, the Market Research and Competitive Intel hub covers the full landscape, from search intelligence to behavioural analytics to audience segmentation.

What Data Should Actually Feed a Persona?

Personas are only as good as the data behind them. The question is which data sources are worth prioritising and which ones create the illusion of insight without the substance.

Demographics are the most commonly used input and the least useful on their own. Knowing that your typical customer is a 35 to 50 year old professional in a mid-to-large organisation tells you almost nothing about what motivates them, what they are worried about, or what would make them choose you over a competitor. Demographics describe the container. They do not describe what is inside it.

Behavioural data is far more valuable. How do people find you? What content do they consume before converting? Where do they drop off? What search terms bring in your highest-value customers versus your highest-churn customers? This kind of data reveals actual decision-making patterns rather than assumed ones. Web analytics, CRM data, and paid search conversion paths are all underused inputs in most persona projects.

Qualitative research, specifically interviews with real customers and lost prospects, is the input most teams skip because it takes time. It is also the input that produces the most useful material. A thirty-minute conversation with someone who evaluated your product and chose a competitor will tell you more about your positioning gaps than a year of internal workshops. The language people use to describe their problems, the criteria they apply when evaluating solutions, the moment they decided to act: none of that comes from a survey or a CRM export. It comes from listening.

Third-party data has a role too, but it needs to be used carefully. Audience intelligence platforms can surface interest clusters, media consumption habits, and attitudinal data at scale. The risk is treating aggregated panel data as if it represents your specific audience. It describes a population. Your customers are a subset of that population, shaped by your product, your pricing, your distribution, and your history. The overlap may be significant or it may be thin. You need your own data to know which.

How Many Personas Do You Actually Need?

There is a persistent belief in marketing that more personas means more rigour. It does not. It usually means more dilution. I have seen persona decks with twelve distinct profiles for a product that realistically had two or three meaningfully different buyer types. The team had worked hard to find nuance where nuance did not exist, and the result was a set of profiles so granular that nobody could hold them in their head long enough to apply them.

The right number of personas is the number that reflects genuinely distinct decision-making patterns in your audience. Not distinct demographics. Not distinct job titles. Distinct patterns in how people become aware of the problem, evaluate solutions, and make purchase decisions.

For most businesses, that number is between two and four. Occasionally five, if the product genuinely serves very different use cases with very different buyer journeys. Anything beyond that is usually the result of over-segmenting demographic data rather than identifying real behavioural differences.

A useful test: if you swapped the names and photos on two of your personas and nobody in the room noticed the briefs had changed, those two personas are not meaningfully different. They should be merged or one should be cut.

The goal is not to document every type of person who might conceivably buy from you. It is to build a clear picture of the people whose behaviour you most need to understand and influence. Precision beats comprehensiveness.

The Anatomy of a Persona That Gets Used

Most persona templates include the same fields: name, age, job title, goals, frustrations, preferred channels. This is fine as a starting structure, but the fields that actually get referenced in briefs and creative decisions are usually different from the ones that get filled in most carefully.

The most useful elements of a working persona are these.

First, the trigger. What causes this person to start looking for a solution? Not their general pain points, but the specific event or situation that moves them from passive awareness to active consideration. A trigger is concrete. “Frustrated with current provider” is not a trigger. “Received a renewal quote 20% higher than last year and started comparing alternatives” is a trigger. The difference matters because it tells you when and where to reach them.

Second, the evaluation criteria. What does this person use to compare options? What do they look for in a vendor? What would make them walk away? This is where lost prospect interviews earn their value. The criteria your winning customers cite are often different from the criteria your lost prospects cite, and the gap between those two lists is your competitive vulnerability.

Third, the objections. What would stop this person from buying, even if they like what they see? Price, complexity, risk, internal politics, switching costs: these vary significantly across different buyer types, and a persona that does not capture them is missing the most commercially useful information you could have.

Fourth, the language. How does this person describe the problem they are trying to solve? Not how your product team describes it. Not how your sales deck frames it. How the customer actually talks about it, in their own words, to their colleagues or their manager. This is the raw material for messaging that connects rather than messaging that explains.

A persona built around these four elements, even if it is only two pages long with no stock photo and no fictional name, will be more useful than a twelve-slide deck built around demographics and aspirational goals.

Where Persona Development Connects to Competitive Intelligence

Personas and competitive intelligence are usually treated as separate workstreams. They should not be. Understanding your audience and understanding your competitive landscape are two sides of the same coin, because your audience is also your competitors’ audience. The question is not just who these people are. It is why they choose you, why they choose someone else, and what would shift that calculation.

When I was at iProspect, we were growing fast and taking on clients across a wide range of sectors. One of the things that consistently separated our better briefs from our weaker ones was whether the persona work had been informed by competitive context. When we knew what alternatives a buyer was considering, and what those alternatives were saying, we could build personas that reflected real decision-making rather than idealised decision-making. The audience did not exist in a vacuum. They were choosing between options, and our messaging needed to acknowledge that.

Competitive ad creative, search behaviour around competitor brand terms, and review site data are all inputs that can sharpen persona work significantly. If a large proportion of your customers mention a specific competitor in their pre-purchase research, that competitor’s positioning is part of your audience’s mental model. Your persona should reflect that.

There is a useful parallel here with how BCG has written about supplier relationships in the context of strategic partnership: the most valuable intelligence comes not from treating the other party as an external variable but from understanding how they think and what they are optimising for. The same logic applies to understanding your audience in a competitive market. You need to understand what your competitors are offering before you can understand why your audience is or is not choosing you.

The Problem With Assumption-Led Personas in Paid Media

Persona assumptions do not just affect brand and content decisions. They have a direct impact on paid media performance, and the cost of getting them wrong is measurable.

Early in my career, I worked on a paid search campaign for a music festival. The brief was built around a fairly standard demographic assumption: young adults, music fans, urban. The campaign launched, and within a day we were seeing strong revenue numbers from a segment we had not prioritised at all. The conversion data told a completely different story from the persona. We adjusted targeting, reallocated budget, and the campaign performed significantly better for the remainder of the run. The lesson was not that the original persona was useless. It was that you should treat your first campaign as a hypothesis test, not a confirmation of what you already believe.

This is where the connection between persona development and performance data becomes critical. Platforms like Optimizely’s experimentation tools and others allow you to test audience assumptions at scale, but only if you have a clear hypothesis to test in the first place. A persona gives you that hypothesis. The campaign data either validates it or tells you to update it.

The mistake most teams make is treating the persona as fixed once it has been approved. It should be treated as a living document that gets updated every time you have new evidence. Conversion data, search query reports, customer service transcripts, sales call recordings: all of these are persona inputs, not just campaign inputs. The teams that get the most value from persona work are the ones that have built a feedback loop between their audience intelligence and their campaign execution.

Tools that support A/B testing and audience segmentation, like those reviewed on Unbounce’s testing blog, make this kind of hypothesis-driven approach more accessible. The point is not the tool. The point is the discipline of treating your audience assumptions as testable rather than settled.

How to Run a Persona Project That Produces Something Useful

The following is not a methodology. It is a sequence of decisions and inputs that consistently produce more useful output than the workshop-and-template approach.

Start with your data before you start with your opinions. Pull your CRM data and segment your existing customers by behaviour, not just by demographics or revenue. Look for patterns in acquisition channel, product usage, retention rate, and expansion revenue. These clusters are the raw material for your personas. They are based on what customers actually did, not what you think they did.

Run interviews before you write anything. Talk to eight to twelve customers across your key segments. Talk to three to five people who evaluated you and chose someone else. Ask open questions. Let them tell you about the problem in their own words. Record the calls if you can. The language that comes out of these interviews is more valuable than any framework you could apply to demographic data.

Layer in search data. What terms bring people to your site? What questions are they asking before they find you? Search behaviour is one of the most honest signals you have about how people think about the problem you solve, because it is not mediated by a survey or a sales conversation. It is what they type when nobody is watching.

Build the persona around the buying experience, not the buyer profile. The most useful structure is: what triggers the search, what criteria they use to evaluate, what objections they raise, and what finally converts them. Fill in the demographic and contextual details as supporting colour, not as the primary content.

Test the persona against a real brief before you finalise it. Give it to a copywriter or a creative team and ask them to write something for that persona. If they come back with questions that the persona cannot answer, those are the gaps you need to fill. A persona that cannot brief a creative is not finished.

Set a review cadence. Personas should be reviewed at minimum annually, and whenever there is a significant change in product, pricing, competitive set, or market conditions. The financial services client I mentioned earlier would have avoided a lot of wasted spend if they had reviewed their personas when they expanded into a new segment rather than assuming the old ones still applied.

The Organisational Problem Nobody Talks About

Even well-built personas fail if the organisation does not have a mechanism for using them. This is the part of persona development that gets the least attention and causes the most waste.

Personas need to be embedded into the processes where decisions get made. Brief templates. Campaign planning documents. Content calendars. Creative reviews. If the persona is a separate document that lives in a shared drive and gets referenced once a quarter in a strategy presentation, it will not change behaviour. It will be consulted when convenient and ignored when it is not.

The teams I have seen get the most value from persona work are the ones that treat it as infrastructure rather than output. The persona is not the thing you produce at the end of a research project. It is the thing you use to make every subsequent decision faster and better. That requires it to be accessible, specific, and genuinely trusted by the people doing the work.

Trust is the key variable. If the team does not believe the persona reflects real people, they will not use it. They will nod at it in workshops and then make decisions based on their own instincts. Building trust in a persona means showing your working: where did this data come from, who did you interview, what did the search data show, what did the CRM analysis reveal. A persona with a clear evidence base is credible. A persona that emerged from a workshop is not, however well-designed the slide.

There is a broader point here about how marketing teams handle research. Buffer has written thoughtfully about building products and communications around genuine user understanding rather than internal assumptions. The principle applies directly to persona work. The output is only as good as the process, and the process is only as good as the commitment to finding out what is actually true rather than confirming what you already believe.

Persona development sits at the centre of a broader market research practice. If you are building or reviewing your research capability, the Market Research and Competitive Intel hub covers the tools, methods, and frameworks that support this kind of audience intelligence work across the full research stack.

What Good Persona Development Looks Like in Practice

I want to be specific about what separates persona work that drives decisions from persona work that decorates strategy decks.

Good persona development produces something a media planner can use to make a channel allocation decision. It produces something a copywriter can use to write a headline without asking three follow-up questions. It produces something a product team can use to prioritise a feature request. If it cannot do those things, it is not finished.

The standard I apply when reviewing persona work is simple: can someone who was not in the room use this to make a better decision than they would have made without it? If the answer is yes, the work has value. If the answer is no, you have produced documentation rather than intelligence.

The organisations that get this right tend to share a few characteristics. They treat persona development as an ongoing research practice rather than a one-time project. They have clear ownership, usually in a strategy or insights function rather than split across multiple teams. They invest in qualitative research, not just quantitative. And they have built the persona into the operational processes of the marketing team rather than leaving it as a standalone artefact.

None of this requires a large budget or a sophisticated technology stack. It requires discipline, honest assessment of what you know and do not know, and a genuine commitment to understanding your audience rather than describing them. Those are not expensive. They are just less common than they should be.

Writing that connects with a real audience, as Copyblogger has long argued, starts with understanding how people think and what they care about before you think about what you want to say. That is the same principle that underlies good persona development. The audience comes first. Everything else follows from that.

About the Author

Keith Lacy is a marketing strategist and former agency CEO with 20+ years of experience across agency leadership, performance marketing, and commercial strategy. He writes The Marketing Juice to cut through the noise and share what works.

Frequently Asked Questions