Your next audience may be asking the wrong name for your work.

01Start with the task a person cannot finish

A portfolio category describes what you make. A useful audience hypothesis describes why someone needs it. Those may use entirely different words. A team looking for an accessible product demonstration may never search for computational storytelling. The connection is plausible, but it remains a hypothesis until observed questions and subsequent behavior support it.

The GOV.UK Service Manual recommends learning what people are trying to do, how they do it now, and where they encounter problems. It explicitly treats opinions that do not come from users as assumptions requiring research. We apply that distinction here as an editorial method; government-service guidance is not evidence that a particular commercial audience will buy from a studio. [1]

02Build a ledger with two kinds of truth

Swipe or scroll to compare

Keep observation and interpretation in separate cells. A public issue asking about export quality demonstrates that somebody encountered that issue. It does not tell you their budget, authority, company size, or willingness to hire. Avoid copying personal details into a publication when a paraphrased task and a relevant source are sufficient.

03An adjacent audience, worked carefully

Consider an illustrative studio with public examples of complex, readable interactive diagrams. A possible adjacent audience is technical education teams helping learners understand a branching process. The proposed need is to explain choices and consequences without making learners decode a dense diagram. This is an example, not a reported customer cohort or an observed question.

The studio could publish a small annotated example that explains how one diagram handles labels, keyboard navigation, and mobile reading. The evidence sought is whether people facing that teaching task find the explanation useful enough to apply, question, or request. A popular visual alone would not validate the educational need or commercial fit.

04Use evidence in the right order

• Inventory public work that demonstrates a capability. Keep private work out of the evidence offered to readers.
• Look for questions in public documentation discussions, issue trackers, specialist communities, and search results. Record the actual market and collection method.
• Group questions by the task and constraint, rather than by wording alone. Several phrases may belong to one answer.
• Check whether the person needs an explanation, a tool, a service, or a different product. Do not force every question toward a sale.
• Publish one answer with a practical next step, then review the quality of the resulting interactions.

GOV.UK's content guidance ties a user need to an action and recommends recording supporting evidence and acceptance criteria. That offers a useful discipline for an article brief: describe what someone can do after reading it. It is more specific than promising general awareness. [2]

05Decide what would change your mind

Write the rejection condition before collecting more evidence. A proposed audience may be a poor fit if the task rarely occurs, the existing answer is adequate, or the only solution requires capabilities you cannot demonstrate. Conversely, repeated questions from independent contexts can justify a deeper guide while commercial fit remains unknown.

Evaluate one hypothesis at a time. Track question recurrence, use of the artifact, and relevant enquiries separately; do not combine them into an invented audience score. An email download signals interest in the resource. It does not, on its own, make the person an ideal customer or establish permission for unrelated outreach.

Sources are linked above so the argument can be checked independently. Editorial revisions retain the same public address.