Audience Research vs Assumptions: Keep the Difference Visible

Open the Audience Persona & Messaging Canvas alongside your own notes. This guide follows an imagined training provider reviewing enquiries about a team reporting course. All sample findings are fictional. The exercise is to decide which statements can guide a message, which need narrower wording, and which should remain questions.

Define the claim before deciding whether it is supported

Start with one statement you are considering using in your content. The fictional training provider has written Managers want the shortest possible course. That statement combines a group, a preference, and a strong comparison. Before calling it a finding, ask what material could actually support each part. A question about how long a course takes does not necessarily establish that the person prefers the shortest option, or that they are making the decision as a manager.

Break the statement into smaller claims. Someone asked about time away from normal work is an observation if the enquiry record shows it. Time commitment may affect the decision is an interpretation. A shorter course would be more attractive is a further hypothesis. These claims can lead to different work: explaining the timetable, asking about staffing constraints, or testing a shorter offer. Keeping them separate prevents one recorded question from silently justifying a product change.

Give the review a practical boundary. You might examine recent enquiries about one course, not every person who has ever encountered the provider. Write that boundary into the segment summary and relevant source notes. An apparently strong conclusion can become unhelpful when its scope disappears. Course enquiries from existing clients, for example, may not answer the same questions as enquiries from people who have never seen the provider teach.

Choose the decision the evidence must support. If you are deciding whether the course page needs a clearer schedule, a narrow record of timetable questions may be enough to try a revision. If you are considering removing half the teaching, you need a different investigation. The same note is not equally useful for every decision. A canvas should help you judge that fit rather than making all documented observations look equally decisive.

Build an evidence inventory with a route back to the original

Review material you already hold before asking new questions. Relevant sources might include an enquiry summary, notes from a voluntary conversation, an existing research report, or a record of a support question. Keep the original material in your normal files. The canvas is a concise research record, not a storage location for complete transcripts. Select the part that bears on the current decision and explain where you can inspect its context.

A useful source note answers three practical questions: where did this come from, which situation did it cover, and what limits matter? For the fictional course, October enquiry review; team course only; pre-booking questions gives a reviewer a better starting point than Sales. You do not need personal names or copied contact details. Use a neutral reference that lets you find the record without turning the persona into a directory of identifiable people.

Preserve the difference between a direct record and a recollection. A colleague’s memory that people often ask about homework can suggest a useful research question. It should not become a counted finding simply because the colleague has worked with customers for years. If the underlying notes are available, review them. If not, describe the basis honestly and keep the claim provisional. Familiarity with a topic is helpful context, not a substitute for the missing record.

Source notes are plain text and are never fetched or checked by the tool. A file label, reference, or written scope note remains something you supply. Research text is limited to 600 characters per area and the source field to 180, so summarise selectively. Keep the observation, its boundary, and its basis; remove narrative background first. A shorter traceable note is more useful here than an impressive source label attached to a vague conclusion.

Separate what happened from what you think it means

Read a note once for the event and again for the explanation. In the imagined enquiry review, a prospective learner asks whether there is work between sessions. That supports recording the question. It does not by itself show that homework is unwelcome. The learner could be checking workload, hoping for practice, or preparing an internal request. Those explanations are alternatives to investigate, not details you should add to make the persona feel more human.

Use observed for an accurately described record, hypothesis for an unconfirmed explanation, and unknown for an unanswered issue. Apply the status to the actual text in the area. Do not mark a paragraph observed when its first sentence is a documented question but its second sentence invents the motive. Split the reasoning across appropriate areas, or rewrite the note so its single status describes the whole claim. One clear statement is easier to review than a mixed paragraph.

Distinguish a reported belief from an independently supported fact. If an enquiry says the course looks too advanced, you can record that reaction within its scope. You cannot conclude that the course is too advanced for every beginner. Equally, if someone says a manager must approve the purchase, that records what was reported in that enquiry. It does not establish the approval process of every organisation the provider might serve.

Keep the original audience wording when you have it and identify a paraphrase when you do not. A polished marketing sentence is not a better research quotation merely because it is shorter. If the precise wording is unavailable, explain the question in your own words without presenting it as a transcript. You can still use a careful paraphrase to plan an answer while leaving the audience wording area unknown until you have an appropriate record.

Use unknowns and contradictions to sharpen the next question

A blank field tells a reviewer little about why information is missing. An unknown note can name the gap: We do not know whether between-session practice affects approval. That is a useful research direction. Do not replace it with No concerns about homework because nobody in a small set of enquiries mentioned it. Absence from your notes may reflect what people were asked, what the note-taker recorded, or who chose to make contact.

Treat conflicting observations as material to understand rather than noise to remove. In the fictional example, one learner asks for more practice while another worries about workload. Both can be accurately recorded. They may reflect different starting knowledge, schedules, or purposes, but those are possible explanations, not established facts. First check whether the records concern the same course and stage. A request after attending a session is not directly equivalent to a concern before booking.

Look for a narrower question that could resolve the content decision. Instead of asking whether the audience likes homework, ask what people need to know about the time and purpose of practice before choosing the course. That question can support a clearer explanation without forcing everyone into one preference. If the course has optional and required work, verify the actual distinction with the provider before writing content; do not infer it from the enquiry language.

Preserve inconvenient evidence when it changes your interpretation. If the most enthusiastic enquiries come from existing clients, note that boundary rather than presenting their language as a general reaction from new prospects. A disagreement can also reveal that a proposed segment is too broad. The aim is not a perfectly consistent story. It is a sufficiently accurate account of the uncertainty to choose the next useful question, edit, or test.

Keep roles separate when the evidence suggests different decisions

A learner, a team manager, and someone evaluating a purchase can take part in the same enquiry while needing different information. The learner may ask what they will be able to do. The manager may ask about time away from the team. The evaluator may ask what the course includes. These are fictional possibilities, not fixed job-title profiles. Separate them only when your own material indicates that the difference changes the message or its supporting evidence.

Use the segment scope to describe a decision role rather than guessing a biography. Team member checking course suitability is more useful than an invented age, salary, and preferred device. Stage matters too: an early enquiry needs orientation, while a person comparing a specific outline may need detail. Do not assume the same individual always stays in one role. Someone could attend the training and also help organise it for colleagues.

Before adding a segment, compare the research areas you would enter. If only the name changes, the split probably adds administration without a new editorial decision. If the evidence needed and next step differ, the distinction may earn its place. Work within the maximum of five segments and use separate documents for unrelated courses. The canvas organises the groups you define; it does not cluster your notes or discover buyer roles automatically.

For professional purchasing situations, the LinkedIn buyer persona guide develops the handoff between users, evaluators, and buyers. You can open a LinkedIn-labelled canvas to identify that working version. The selector changes the context label only, so the same six areas and all three brief structures remain available. It does not turn an enquiry into evidence about a social account or a wider professional audience.

Read the coverage count without turning it into a verdict

Coverage describes the organisation of six areas: desired outcome or job, question, objection, evidence needed, useful content or format, and audience wording. An area with nonblank text, observed status, and a source note counts as a sourced observation. Text marked hypothesis counts as a working assumption. Other combinations remain needs research. This is a fixed classification of your entries, not an assessment of research depth, sample balance, accuracy, or commercial importance.

Two canvases can show the same sourced count while containing very different evidence. One may draw every area from a single enquiry; another may summarise several carefully scoped records. Neither count tells you whether those records suit the decision. Inspect the notes themselves. The count also cannot distinguish six independent observations from six statements derived from one source. Repeating a source label across areas does not create additional people or separate confirmation.

If you choose observed but omit a source, the warning leaves your explicit status intact. That allows you to correct the missing basis without the workspace rewriting your judgment. Do not solve the warning with a decorative label such as Verified research unless that phrase accurately describes your own record. The tool neither opens the source nor confirms its contents. A completed field is an organisational fact, not a certificate of truth.

Prioritise gaps by consequence rather than by how easily you can increase the count. An unsupported claim about what the course teaches may matter more than a missing format preference. A well-supported audience question can justify a useful explanation even when other areas remain unknown. Keep the research honest enough that another editor can see why you chose the topic. Your target is a defensible next action, not a full set of reassuring indicators.

Choose a research step that could change your mind

Turn a consequential assumption into an answerable question. If you think managers reject the course because of homework, ask what information they need to judge the total time commitment. Avoid asking whether they agree that homework is a problem. A useful investigation leaves room for a different explanation. Decide which result would cause you to change the message, narrow the segment, or stop pursuing the proposed content before collecting more material.

Choose a modest activity that fits the decision. You might review the relevant enquiry records, ask a voluntary follow-up question, or show an accurate course outline and ask someone to explain their understanding. These activities happen outside the tool. The canvas does not recruit participants, send questions, collect answers, or analyse a response. Use the test field to record the plan and later enter your own account of what you learned.

For the fictional provider, a useful test could examine whether a clearer time breakdown answers the original concern. Ask what remains unclear after reading it rather than offering only a yes-or-no approval question. Record the circumstances of the response and avoid turning a small review into a population claim. Understanding one person’s interpretation can improve a sentence while leaving broader demand, purchase intent, and the needs of other roles unresolved.

When new evidence arrives, revise the claim rather than merely adding a more confident adjective. Keep a dated JSON version before a material change because the canvas has no automatic research history. You may discover that your first assumption was partly right but too broad. The next version could distinguish required teaching time from optional practice if the actual offer supports that distinction. Let the evidence change the description instead of forcing it to defend the original wording.

Hand over the reasoning with the message

An editor receiving the canvas should be able to locate the audience question, understand its limits, and identify the evidence still needed. The three fixed structures arrange your entries as answer a question, address an objection, or show a useful example. They retain status and source labels and show Not provided for missing inputs. They are not AI interpretations of your research. Any finished explanation must still be written and checked by the person producing it.

Use the question-to-brief guide when a supported question is ready to become an assignment. Then plan the chosen topic separately in the Content Calendar Generator. A date in a production plan does not settle an unresolved research issue. If an essential fact is still missing, make checking it part of the assignment rather than allowing the deadline to turn the assumption into a public statement.

Save JSON to reopen and revise the research, including a valid unfinished draft. Send TXT or normalised CSV when a colleague needs selectable notes, or copy the complete canvas for a text handoff. Use the paginated PDF for flattened visual review once there is actual content. It is not a selectable transcript. Save files yourself: the workspace has no autosave, private-content upload, login, or public sharing service that preserves a project for later.

Keep the delivery focused on the decision and leave identifying details in the original records where appropriate. Explore the free tools directory for other preparation tasks. The LinkedIn automation overview concerns a separate part of SMTasker, not research validation or delivery of this canvas. You can evaluate that application through the five-day trial without treating the trial as a requirement for maintaining this free local research document.

Questions about Audience Research vs Assumptions

Continue with another audience planning guide

Organise your audience notes in the Audience Persona & Messaging Canvas, or choose a focused guide below. More browser-based helpers are in the free tools directory.