A product team needs a model to review the design. A marketing team needs images to explain it. Using the same starting material sounds efficient, but it only works when both uses are planned. A model prepared for a mechanical check may have unfinished surfaces. A model prepared for a camera may hide details that matter to the test.
BDWY's product design and content production work meet at this decision. The aim is to define what can be shared, what needs separate work and what must be approved before the next team uses it.
Start with the two decisions
Write the design decision and the communication task separately. For example, a team may need to choose a grip profile while showing prospective buyers how a tool is used. The first task needs a handling review. The second needs a clear demonstration, suitable framing and an accurate account of the product's current state.
These tasks can inform each other without being identical. Do not let a pleasing image settle an unresolved design question. Equally, do not assume that a technically useful model will explain itself in a short film.
Agree which details are final
List approved geometry, colours, materials, markings and moving parts. Mark anything still provisional. A change to a seam or a control can affect a close-up that was already approved. Keep a clear revision reference for the model and for the image or film review.
If the material is not final, choose how that uncertainty will appear in the presentation. A concept should be described as a concept. An image of a prototype should not quietly become evidence of a finished product available for sale.
Plan physical access and digital handover
For a physical model, discuss the views before fabrication. Does a part need to be removed for a cutaway? Will hands touch the surface? Is the underside visible? Will a mechanism repeat the same movement across several takes? These questions can change finish and assembly choices.
For digital work, agree the delivery format and intended use. A scene arranged for image production is not automatically an editable manufacturing model. Ask which source files are included, which components can change, and who will prepare materials, lighting and camera views.
Two useful examples, with clear limits
In a hypothetical finish review, a physical sample could provide a reference for a CGI material. The team would still need to review the rendered result in its intended lighting. Having a sample does not make every image an exact record of appearance.
In another example, a photo model could have a removable back to allow a better view inside. That may help explain the product, but it could make the same model unsuitable for a handling or stiffness test. Record the modification so the model is not reused for the wrong purpose.
Copy this shared production brief
Product and current stage: [description].
Design decision: [what must be learned].
Audience and communication task: [what they must understand].
Approved details: [geometry, finish, colour, markings].
Provisional details: [list].
Required views or actions: [shot and scene list].
Channels and formats: [website, sales, social or other].
Model and file revision: [reference].
Editable files and usage rights: [to agree].
Review owner, deadline and budget: [details].
Buy the scope you need
If the product is ready and you only need content, keep the engagement focused on production. If design decisions and launch material are moving together, coordinate their approvals from the beginning. The useful saving is avoiding unsuitable work or a late rebuild, not forcing every deliverable into one model.
BDWY Studios
Back to the journal