Label what each unit can do
List appearance models, working units, engineering samples and intended production versions separately. Tell the crew which functions work on set, which need temporary connections and which are still goals. A model that shows the shape of a product may be useful, but it cannot also prove its performance.
Test the actions in the storyboard
Turn each planned action into a test: start, connect, run, reset and recover from an error. For example, one successful print does not establish that a portable printer is ready for a shoot. Test paper changes, phone pairing and repeated takes. Record the setting and accessories needed for each result.
Plan support, not hidden fixes
List cables, power supplies, spare parts and firmware versions. The need for spare units or an engineer depends on the shoot; there is no useful universal count. Agree on who decides when a unit fails. Use a different shot or postpone the demo rather than manufacturing a false result in post-production.
Keep the content team in the loop
Maintain a version sheet that links the prototype to the claims it supports. A design change may affect the ports, shape or way the product is used. Check captions and specification graphics when that happens. Film a short rehearsal before the main shoot and use it to decide what is ready.
Put this into practice
- Assign a unit and firmware version to each key shot.
- Test repeated takes, resets and error recovery.
- Confirm technical support and fallback shots before booking.
