A data-import film can skip from a spreadsheet to a populated application and make the transfer look self-explanatory. The important decision may have happened in between: deciding which incoming column belongs in which destination field. If mapping is part of the demonstrated workflow, give it enough screen time to remain understandable.
Use a fictional dataset approved for demonstration. The product owner should confirm the actual mapping behaviour, including any suggestions the interface makes and any choices the user must supply. A production graphic should not imply that the system understands every unfamiliar heading automatically.
Choose names that require a real decision
A sample in which every source heading exactly matches its destination can hide the purpose of mapping. A useful example might have a source column called reference and a destination field called project code, with the relationship clearly approved for this fictional dataset.
Do not make the example ambiguous simply to create drama. The audience should be able to understand the correct assignment from the scenario. The point is to reveal a meaningful decision, not to turn the film into a puzzle about business terminology.
Hold the source and destination together
Frame the mapping view so that both sides remain legible. If the interface is too wide for the final film, use a deliberate sequence that preserves the relationship rather than alternating unrelated close-ups. An editorial connector can help, provided viewers can distinguish it from a native product feature.
In a fictional supplier directory, one column contains organisation names and another contains a short internal code. The film shows their different destinations before proceeding. A quick preview then confirms that the example values arrived in the intended fields, rather than merely showing that some rows were created.
Separate mapping from cleaning
Assigning a column to a field does not, by itself, establish that every value is suitable. If the demonstration includes format changes, blank values or rejected rows, identify those as separate behaviours. Do not make a successful mapping screen appear to validate the business meaning of all imported information.
The production brief can keep the current sequence narrow. It may explain mapping and direct viewers to a separate approved resource for data preparation. That is preferable to compressing several different responsibilities into a reassuring phrase such as the system takes care of the rest.
Retain the check after the import
Choose one or two fictional records that can be recognised before and after the transfer. Their values should make a mistaken assignment obvious. Keep the check proportionate; the film is demonstrating the relationship, not auditing a real operational dataset.
At approval, ask which source column supplied a nominated destination value. If reviewers cannot trace it, revisit the mapping passage. The finished demonstration should make the user's assignment visible and distinguish it from any automated suggestion, so viewers understand what has actually been confirmed before the import proceeds.
Discuss the proposed explanation with Live Images and confirm suitability, production scope and the content owner’s review responsibilities. This unpublished draft uses a fictional example, not a claimed client project.
Prepared with AI assistance for Live Images. Planning guidance is general; suitability and production scope must be agreed for your project.