STRATEGY · 6 MIN READ # Audience segmentation and customer personas How complex organisations can define the audiences that matter, understand their decisions and create communication that earns attention. By [Kyle Smith](https://kyzakis.com/about.html) · KYZAKIS Audience segmentation is often treated as a marketing exercise. In complex organisations, it is a communication discipline. The audience is not simply a list of demographic attributes. It is a set of people with different responsibilities, pressures, levels of knowledge and reasons for accepting or rejecting a message. That distinction matters in defence, government, fintech, AI and other regulated environments. A technical buyer, a procurement evaluator, a regulator, an executive sponsor and an end user may all be assessing the same proposition. They are not asking the same question, and they will not be persuaded by the same evidence. ## Start with the decision, not the demographic The most useful segmentation begins with the decision a person needs to make. Instead of starting with job title, age or organisation size, ask what the audience must approve, buy, adopt, fund, recommend or defend. A government stakeholder may need to decide whether a program is accountable and publicly defensible. A defence evaluator may need confidence that a response is compliant, deliverable and low risk. An enterprise buyer may need to show a CFO that an investment has a credible return. These are different decision contexts, even when the people involved have similar seniority. A practical first question is: *what would this person need to believe before they could move the decision forward?* That answer provides a stronger foundation for segmentation than a broad label such as “enterprise customer”. ## Separate audiences from stakeholders An audience is any group whose understanding or action affects the outcome. A stakeholder is anyone with an interest in the outcome. The groups overlap, but they are not identical. For a tender, the primary audience may be the evaluation panel. The wider stakeholder group may include technical reviewers, commercial approvers, legal advisers, delivery teams and the executive who signs the contract. The message needs to help the panel score the response, while also giving the other stakeholders enough confidence to support it. Mapping the full decision environment prevents a common error: writing only for the most visible audience. In high-stakes work, the person reading the document may not be the person who carries the risk. ## Build personas around useful differences A customer persona is a working model of a real audience. It should make better communication decisions easier. It does not need a fictional name, a stock photograph or invented personal details. A useful persona captures: - **Role in the decision:** initiator, recommender, evaluator, approver, user or blocker. - **Primary objective:** the outcome they are accountable for. - **Pressure and risk:** what could go wrong for them personally or organisationally. - **Current knowledge:** what they understand, what they distrust and what they need explained. - **Proof required:** evidence, assurances, examples, standards or commercial detail. - **Preferred action:** the next step the communication should make easier. The test is simple: if two people would respond to the same message for the same reason, they may not need separate personas. If they require different evidence, language or next steps, the distinction is probably meaningful. ## Use jobs to be done to find the real need Demographics describe a person. A job to be done describes what that person is trying to accomplish in a particular situation. This is especially useful when audiences are professional, technical or institutional. For example, a chief information officer may be hiring a security platform to reduce operational exposure, but the communications job may be to make a defensible recommendation to the board. A procurement lead may be reviewing a proposal to test compliance and comparability. A technical lead may be trying to explain an architecture without creating a new layer of risk. Good messaging connects the proposition to that job. It explains not only what the organisation offers, but how it helps the audience complete the responsibility in front of them. ## Map the buying committee and influence network Complex decisions rarely belong to one person. A buying committee or influence network can include the economic buyer, technical assessor, operational user, legal reviewer, procurement team, executive sponsor and external adviser. Map each role against three questions: - What does this person need to know? - What could cause them to object or delay? - What evidence would help them support the decision? This produces a message architecture rather than a single generic value proposition. The central argument remains consistent, but the emphasis changes. The technical assessor may need specificity. The executive may need consequences and confidence. The procurement team may need traceability. The end user may need a clear view of how the change affects their work. ## Gather evidence without inventing certainty Personas should be grounded in evidence. Useful sources include customer interviews, sales and account notes, proposal feedback, support questions, search behaviour, stakeholder workshops, lost-deal analysis and conversations with subject-matter experts. Evidence does not need to be statistically perfect to be useful, but assumptions should be marked as assumptions. A simple confidence rating can help: observed, repeatedly reported, plausible or untested. This prevents a neat persona document from becoming a collection of unchallenged opinions. In regulated settings, also record what cannot be claimed. Legal, policy, security or procurement constraints should shape the persona and the message from the beginning, not appear as an approval problem at the end. ## Turn personas into a message matrix A persona is only valuable when it changes the work. Convert the findings into a message matrix with one row per audience and columns for the decision, concern, desired outcome, proof point, language to use, language to avoid and next action. For each audience, write one clear proposition before adding supporting detail. A useful structure is: **For [audience] who need to [decision or job], [organisation or offer] helps by [specific value], supported by [credible proof].** This is not necessarily final copy. It is a test of whether the team understands the audience well enough to make a relevant claim. If the sentence is full of generalities, the segmentation probably needs more work. ## Validate the persona in the channel where it will live Different channels reveal different problems. A board paper tests whether the argument survives compression. A tender tests whether claims are traceable and scorable. A website tests whether a visitor can recognise relevance quickly. A keynote tests whether the point can be understood and remembered when heard once. Review a draft with someone who represents the audience, where possible. Ask them what they think the message is asking them to do, what they trust, what they cannot verify and what they would need next. Do not ask only whether they like it. Preference is a weak substitute for comprehension and action. ## Common segmentation mistakes The first mistake is over-segmentation. If every stakeholder gets a bespoke message, the organisation loses a coherent point of view and the content system becomes expensive to maintain. The second is confusing seniority with motivation. A chief executive and a procurement manager may both be senior, but their exposure, evidence requirements and decision rights are different. The third is treating a persona as permanent. People, markets, policy environments and buying processes change. Review the model after significant wins, losses, regulatory changes, product changes or shifts in customer questions. The fourth is writing for an imagined audience while ignoring the actual reader. In complex organisations, a document often travels beyond its original brief. Write so that the next decision-maker can understand the logic without needing the author in the room. ## A practical standard for useful personas A strong persona should help a writer choose what to lead with, what evidence to include, what objection to answer and what action to invite. If it does not change those choices, it is descriptive rather than useful. The aim is not to manipulate an audience. It is to respect the audience enough to make the relevance, risk and evidence clear. That is what turns segmentation from a marketing artefact into a practical foundation for better executive communication, proposals, technical content and public-facing information. ## One document, several audiences? I can help structure and edit your speech, proposal or report around what its readers need. [Discuss your draft](https://kyzakis.com/index.html#contact) ## Explore the related work ### Executive ghostwriting & thought leadership Executive articles, blogs and leadership messages in your voice. [Explore the work](https://kyzakis.com/index.html#leadership-change) ### Turning complex policy into practical guidance Plain-language guidance that helps people understand and use public information. [Explore the work](https://kyzakis.com/work/government-information.html) [Back to insights](https://kyzakis.com/insights.html)