A customer persona is so familiar that many companies assume they only need to fill in a few boxes about age, job title, income, and interests. The problem is that these personas often look good on slides but do little to support decisions. When the team enters a meeting about product, communication, pricing, or sales, it still does not know what the customer is trying to solve, what triggers the search for a solution, how alternatives are compared, and who truly influences the purchase decision. A valuable customer persona is not an imagined portrait of a buyer. It is an evidence-based summary of the customer’s decision context.
The right starting question, therefore, is not simply “who is our customer?” in a demographic sense. A more useful question is: “in what situation does the customer begin to need us, and what kind of progress are they trying to make?” This shifts attention from describing a person to understanding the situation, motivation, barriers, and choice criteria. That is the difference between a persona used for decoration and a persona that can guide action.
Do not start with a profile photo and a short biography
Many popular persona templates begin with a fictional name, profile photo, age, occupation, income level, interests, and a quote that sounds representative of the customer. These details are not wrong, but if they appear too early, the team can mistake concreteness for real understanding. A character such as “Lan, 35, marketing manager, enjoys reading and uses social media” may feel relatable, but it still does not answer the important questions: what problem is Lan facing at work, what makes her feel the need to change, why would she choose one solution over another, and what makes her hesitate?
In practice, the same age and job title can lead to very different buying behaviours. A marketing manager in a fast-growing company may prioritise speed of implementation, while someone with the same title in a more stable company may care more about risk control, internal coordination, and reporting capability. If the persona stops at demographics, the marketing team tends to write generic messages, the sales team struggles to handle objections, and the product team does not know what to prioritise.
A useful persona describes a decision situation
A more practical approach is to start with the trigger situation. Customers usually do not wake up simply wanting to buy a product. They begin looking for a solution when a specific situation makes the current way of working no longer acceptable. Revenue may be slowing down, operating costs may be increasing, customer complaints may be rising, leaders may demand more transparent reports, or the team may no longer be able to handle the workload manually. The trigger situation helps the company understand when the customer is more likely to listen, which message carries weight, and what evidence should be provided.
The next element is the progress the customer wants to make. This progress is rarely only functional. A sales director does not simply want “a CRM system”; they want to reduce dependence on each salesperson’s memory, see the quality of the pipeline, control revenue commitments, and have a basis for coaching the sales team. When a persona is described around desired progress, the message can move from “our product has many features” to “this solution helps you see sales bottlenecks before revenue falls short of target.”
Applied example
If a training company is building a persona for B2B customers, it should not merely write “HR manager, 30–45 years old, interested in employee development.” A more useful description would be: “An HR manager in a fast-growing company who is under pressure to standardise middle-management capability after opening new branches. They need a training programme that does not only inspire participants, but helps managers handle real situations, provides tools to apply after class, and offers a way to report results to senior leaders.” This description immediately suggests the sales message, programme structure, proof of capability, and post-training follow-up.
Five elements a customer persona should include
A customer persona that can be used in daily work should include five elements. The first is the context and trigger situation: what makes the customer start looking for change. The second is the desired progress: what better state the customer wants to reach. The third is barriers and concerns: why they have not bought, changed, committed, or persuaded others yet. The fourth is choice criteria: how they compare available options. The fifth is observable signals: what marketing and sales teams can see in order to identify a good-fit customer.
| Element | Question to answer | Managerial use |
|---|---|---|
| Trigger situation | When does the customer begin to feel the need to change? | Select timing and content themes. |
| Desired progress | What better state does the customer want to reach? | Write messages around outcomes, not only features. |
| Barriers | What makes the customer delay or reject? | Prepare evidence, demos, cases, and objection handling. |
| Choice criteria | What factors guide the evaluation of options? | Design solution packages, pricing, and sales materials. |
| Observable signals | What signs show that the customer is a good fit? | Prioritise leads and align marketing with sales. |
Personas need evidence, not only internal impressions
A common mistake is to let the internal team sit together and “invent” personas. This can help at the starting point, but it is not enough for decision-making. Personas should be built from different sources of evidence: customer interviews, sales notes, customer service data, feedback on social media, transaction history, survey results, and observed behaviour on the website. Each source has its own limits, but when placed together, they help the team see the gap between what the company assumes and what customers actually care about.
Not every company needs a large research project to build a useful persona. A small business can interview 8–12 recent customers, review 30–50 sales or service conversations, and group repeated decision situations. That already produces a persona far more useful than a template downloaded from the internet. The important point is to state clearly what evidence the persona is based on, what evidence is still missing, and when it should be updated.
A persona must lead to concrete decisions
A good persona should change how the company acts. If the advertising message remains the same, the website content does not change, the sales script becomes no clearer, and the product team gains no new priorities, the persona has not fulfilled its managerial function. Each persona should be connected to application decisions: the main message, content to be written, evidence to be provided, sales questions to ask, objections to prepare for, and experience points to improve.
This is especially important in B2B markets, where there should not be only one persona for “the customer.” Purchase decisions often involve several roles: user, proposer, approver, budget owner, and technical influencer. Each role has different concerns and criteria. Users need ease of use, managers need operational effectiveness, finance needs cost control, and senior leaders need strategic impact. If the company merges all of them into one generic character, both content and sales lose precision.
When should a customer persona be updated?
A persona is not a document to be created once and left unchanged for years. Companies should update personas when the product, sales channel, target segment, information-search behaviour, competitive context, or economic environment changes. One clear signal is when conversion rates decline, leads respond differently, sales cycles become longer, or the sales team repeatedly faces new objections. In such cases, the problem may not be advertising technique. It may be that the company is speaking to an outdated customer persona.
The update process does not need to be complicated. A company can run a quarterly review: select 10 won opportunities, 10 lost opportunities, and 10 customers who are using the solution well; then compare their trigger situations, reasons for choosing or not choosing, main objections, and expected outcomes. Repeated patterns will show which personas remain valid, which need revision, and which should be separated into a distinct segment.
Conclusion
A customer persona should not begin with the customer’s age, job, or interests. It should begin with the situation the customer is in and the progress they want to make. Built in this way, a persona becomes a real management tool: it helps marketing write the right content, sales ask better questions, product teams prioritise the right problems, and leaders see which segments deserve investment. The value of a persona is not that it looks vivid on a slide. Its value is that it helps the company make better decisions.
References
Christensen, C. M., Hall, T., Dillon, K., & Duncan, D. S. (2016). Know your customers’ “jobs to be done.” Harvard Business Review, 94(9), 54–62.
Cooper, A. (1999). The inmates are running the asylum. Sams.
