A user consultation seminar can contain one unusual scenario among many descriptions of ordinary activity. When commissioning a film from that material, do not let speaking time or the number of similar comments become the only measure of relevance. Ask the project owner which less frequent needs still matter to understanding the brief.
The purpose is not to rank users or decide design priorities through video. It is to make the approved account of those priorities intelligible. A short edit can unintentionally erase a consequential use case simply because only one representative explained it.
Select scenarios before selecting personalities
Request a list of the user situations the seminar is intended to explain. For each, identify the representative's remit and the approved status of the requirement. Someone describing a personal experience is providing different evidence from someone authorised to speak for an entire operating group.
Ask why each selected scenario belongs in the film. Frequency may be relevant, but so may the effect on the project brief or the need to explain a particular choice. Keep that reasoning with the editorial selection. It gives reviewers a stronger basis than whether a speaker was especially confident or concise.
Avoid inferring an absent group's position from another participant's account. If their perspective is essential and no suitable contribution exists, commission a new approved explanation or state the gap. An editor cannot create representative evidence from a reaction shot.
Make the relationship to the brief explicit
Give the content owner a focused question: what did the project do with this need? The answer may be inclusion, further investigation, deferral or a documented decision outside the current scope. The film should communicate that answer without implying every request was adopted.
Where a contribution includes sensitive personal detail, ask whether the project question can be explained without carrying that detail into the resource. The editorial value may lie in the situation, not in identifying the individual who first raised it. Obtain the appropriate content approval for the chosen treatment.
A hypothetical shared workplace
A hypothetical seminar discusses a building used mostly during ordinary office hours. One representative describes occasional evening use by a small team. An early edit removes that contribution because most speakers discuss daytime activity. The client restores a concise account because the evening scenario explains a specific requirement in the approved brief. The film does not suggest that evening use is common; it explains why the project considered it.
This choice changes the substance of the commissioned resource. The audience can now understand a requirement that otherwise appears arbitrary.
Review whose needs the edit makes visible
Compare the rough cut with the selected scenario list. Which needs have become prominent, which have disappeared and why? Ask the project owner to approve changes in emphasis rather than treating them as purely stylistic.
For acceptance, have a reviewer identify both the ordinary use and the less frequent scenario. They should be able to explain the different roles those situations played in the brief. A useful requirements film represents the reasoning behind the selected needs, not a popularity contest reconstructed from the strongest sound bites.
Discuss suitability
Contact Live Images with the proposed subject, audience and intended use to discuss suitability, scope and availability.
Editorial note
Original commissioning guidance prepared with AI assistance. Hypothetical examples are invented, not Live Images projects. This unpublished resource makes no engineering, legal or performance guarantee.