Before Your Team Votes on an Audience, Compare the Buying Reasons
A client meeting has three audience proposals on the screen. One stakeholder prefers an industry. Another chooses a job title. Someone else wants to keep the message broad so nobody feels excluded.

A client meeting has three audience proposals on the screen. One stakeholder prefers an industry. Another chooses a job title. Someone else wants to keep the message broad so nobody feels excluded.
You could ask for a vote, but the options are not yet comparable. People may be choosing based on familiarity or personal preference while imagining different products, benefits and next steps.
Give each direction the same short explanation first. The discussion then has something concrete to assess before the team decides what to produce.
Compare complete directions
For each audience option, write these five points:
Situation: [what is happening for this group]
Relevant benefit: [what the offer helps them do]
Buying reason: [why that benefit may matter now]
Support: [actual product fact or available evidence]
Next step: [what the proposed content would invite]
A buying reason is a reason someone could care about choosing the offer. It should connect the benefit to their situation, rather than repeat the feature in different words.
Keep each direction short enough to read in the meeting. A detailed presentation can hide the very difference you need people to discuss.
Use one offer across the comparison
Imagine an agency working with a company that supplies a scheduling tool. In this fictional example, the tool shows shared appointments in one view.
A small service team may care about seeing which appointments overlap. An owner working alone may care about reviewing the week before accepting another booking. The product fact stays the same; the work around it changes.
Do not improve one direction by inventing a feature the others do not have. If the tool lacks a capability a group needs, make that gap visible. It may be a reason to choose another direction or change the proposed scope.
Ask the same questions of every option
Review the directions together:
- Is the situation clear enough to recognise?
- Does the actual offer address an important part of it?
- Can we explain the benefit with a useful example?
- What do we know, and what are we assuming?
- Can we reach this group through the activity we are planning?
You can record answers as clear, uncertain or missing. Numbers are optional. A score becomes less useful when nobody agrees what it measures or when a precise total hides uncertain inputs.
If someone prefers an option, ask which answer makes it stronger for this particular piece of work. That keeps the discussion open while giving the preference a reason others can examine.
Decide what happens next
The decision may be to choose one direction, develop two short concept drafts, or gather a missing piece of information. Name the next action and who will take it.
For example: “We will draft an opening for the small service-team situation, using the shared-appointments view as the main example. The client will confirm the actual booking workflow before we complete the page.”
That is enough direction for a writer to begin without pretending the whole market question has been settled.
Keep the alternatives and the reasoning
Save the comparison with the chosen brief. When a stakeholder asks later why another audience was not selected, you can return to the reasons instead of relying on a memory of the meeting.
You can also review the decision when relevant feedback arrives. A customer question may reveal a missing explanation, while repeated problems with product fit may justify revisiting the direction itself.
Customer StarMap for marketing professionals guides the move from a benefit map towards customer groups, buying reasons and practical messages. Those outputs can provide material for a team comparison, with the final judgement remaining yours.
Before the next vote, make the options comparable. You may still disagree, but you will be discussing the same decisions.



Keskustelu 0
Mitä ajatuksia julkaisu herätti?