Define what the route should teach you
A useful distribution experiment produces evidence about reaching a relevant person and understanding their task. It does not turn attention into a purchase. This guide builds a proposed route for a product-brief planning service, using an existing public text artifact. No invitation, interview, customer trial or sale was carried out for this example.
Bring one artifact and a qualification rule
Start with the bounded pilot card and the coffee storyboard planning case. The example shows a three-shot text plan. It is useful discussion material precisely because its inputs and outputs are visible; it is not a finished video or proof of a commercial outcome.
Write a situation rather than a broad audience label. A hypothetical qualification rule might be: someone who recently prepared or reviewed a brief for a short product video and can discuss that process without sharing confidential material. Ask what they actually did, when the work occurred and which part they owned. GOV.UK's recruitment guidance emphasizes actual or likely users; applying that principle avoids counting an unrelated visitor as a useful participant.
1. Choose one permitted route
Use an existing relationship, an opted-in research list or a community that allows this kind of invitation. Record the permission basis and how someone can decline. Ask the community owner when its rules are unclear. This guide does not authorize automated comments, mass direct messages, bought leads or access to private member data.
Keep the first route bounded. For example, you could plan a small number of invitations within a defined week and stop at the chosen cap. Pick limits suitable for the relationship and your available time. They are planning choices, not predicted response rates. Stripe Atlas's early-sales guide is a useful reference for connecting qualification with concrete conversations; its examples are not results achieved by this site.
2. Prepare an invitation that describes the actual offer
I am researching how people hand off short product-video briefs. If you recently prepared or reviewed one, would you be willing to discuss that process? I can show a public three-shot text plan as a conversation aid. It is a planning example, not a generated video. Please do not send confidential assets; declining is completely fine.
Adapt that draft to the channel and explain the time commitment before a person agrees. Provide a real reply or booking route you can operate. The paragraph above is an example to review, not a message sent by this workflow or a promise that a community will permit it.
3. Ask about a recent task before presenting features
Prepare neutral questions using the GOV.UK interviewing guide as a reference:
- What prompted the most recent brief, and who needed the result?
- How did you communicate the shot sequence and the details that needed to stay consistent?
- Where did someone need clarification or rework?
- What happened after the brief was handed over?
- What would make a text-only plan useful or insufficient for that task?
Only then show the sample plan, if the participant agrees. Ask them to explain the next action they would take and record where its limits matter. Do not present a list of future integrations as working features. Keep consented notes private and collect only what the research question needs.
4. Keep a stage-separated observation ledger
Use a participant code rather than personal details in the shared summary. For each permitted contact, record channel, permission basis, invitation status, qualification result, recent-task evidence, artifact attempted, unresolved issue and agreed next step. Keep purchases in a separate field.
- Attention: a visible response or other observation you can actually substantiate.
- Relevant participation: the person met the stated situation and discussed a concrete recent task.
- Task evidence: what happened when they inspected the sample, including confusion and refusal.
- Commitment: a specific follow-up was agreed, with an owner and timing.
- Purchase: an authorized offer was accepted and money actually collected. Interest alone does not fill this field.
Leave missing observations unknown. If you later calculate a rate, show its denominator and keep differently recruited groups separate. An initial blank ledger contains no measured conversion rate.
Choose the next decision from the observed failure point
If the route does not reach qualified people, revise the route or situation before concluding there is no demand. If the task is relevant but the text plan is insufficient, revisit the pilot's boundary and stop rule. If a follow-up trial is appropriate, carry its handling work into the cost scenario and support budget. This path ends with a more defensible research decision, not a claim of market size, sales or guaranteed growth.