To make a video for a product design class, tell the story of your decisions rather than showing off the final product. Open with the user and the problem, show what you learned from research, walk through two or three concepts and why you dropped all but one, show at least one prototype that failed a test and what you changed, then present the final design with how it is used. Five to eight minutes is typical. Use drawn scenes for the parts that are hard to film (the user's problem, the comparison of concepts, an exploded view of how the parts fit) and real photos or clips of your physical prototypes as evidence. Tutors mark the reasoning, so make every decision visible on screen.

What a product design tutor is marking

Product design briefs vary between schools, but the assessment almost always tracks some version of the design process. The Design Council's Double Diamond (Discover, Define, Develop, Deliver) is the model many courses teach, and even courses that use a different one are asking the same four things.

The pattern in the right-hand column is the same every time. Students show outcomes and hide the decisions, because the decisions include things that did not work. The decisions are where the marks are.

Show the failures

The most common weakness in a design process video is that every prototype looks like it worked. That is not believable, and it removes the evidence that you were designing at all.

A good iteration scene has three parts, each one sentence:

1. What you tested and how. "We gave the first prototype to six children aged seven and eight and watched them use it for ten minutes."
2. What happened. "Four of them pulled the magnetic connectors apart in the first minute and lost interest when the pieces would not stay together."
3. What you changed and why. "We switched to a twist-lock joint and doubled the magnet strength on the base plate."

Three sentences per test, one or two tests per concept, and your Develop section is already stronger than most. Keep your test numbers small and real. Six children is a fine sample for a class project. An invented "survey of 200 users" is not, and tutors can usually tell.

Drawn scenes and real footage, each for its own job

A product design video has two kinds of material, and mixing them up is the second most common problem.

Real footage and photos are evidence. Your sketchbook pages, your cardboard and foam models, the 3D print with the support marks still on it, a test session (with permission from anyone filmed, and with children only with parents' and the school's consent). Tutors want to see that these exist.

Drawn scenes are explanation. The user's problem before your product exists. The three concepts side by side on the same template. An exploded view showing how the parts go together. The sequence of how someone uses it. These are hard or impossible to film and much clearer drawn, because a drawing can leave out everything irrelevant.

A drawn explainer will not show your actual prototype, and it should not pretend to. Make the drawn scenes as one video, then put them together with your photos and clips in any basic video editor, or alternate them in your presentation. If you are comparing your concepts, how to explain a comparison in a video covers the split-scene layout that suits it.

Worked example: a modular educational toy

Here is a scene list for a six minute video. The project is a set of interlocking blocks that teach fractions to children aged six to eight. Each block is a fraction of a whole bar, and the pieces only lock flat when they add up to one.

Scene 11 matters more than it looks. Naming what you did not test is a sign you understand evaluation, and most marking criteria reward it explicitly.

Writing the narration

At roughly 150 spoken words a minute, a six minute video is about 900 words. That is tight for eleven scenes, so each scene gets two to four sentences.

• Lead with the decision, then the reason. "We dropped the wheel because children could not tell when they had it right" beats a paragraph that builds up to it.
• Use your design vocabulary correctly. Criteria, iteration, ergonomics, tolerance, user testing. Tutors listen for it, and they also notice when it is used as decoration.
• Say numbers aloud. "Four of six children" is stronger than "most children".
• Do not narrate the render. If the final product is on screen, the narration should be telling the viewer why it looks like that, not describing what they can already see.

Make it

1. 1

   List your real decisions first

   Write down every point where you chose one option over another, and the reason. That list is the spine of the video. If it has fewer than four entries, go back to your sketchbook.

2. 2

   Gather your evidence

   Photos of sketches, models, prototypes and test sessions, in order. Check you have permission for anything showing other people.

3. 3

   Write 800 to 1,000 words of narration

   One section per stage: discover, define, develop, deliver, plus limits. Two to four sentences a scene, decision then reason.

4. 4

   Draft the explanation scenes

   In openCanviz, paste the script and set the target length. Whiteboard or poster suit product design; a clean drawn exploded view or concept comparison reads as technical rather than decorative.

5. 5

   Correct every label and number

   Check part names on the exploded view, the scores in the concept table and the test numbers. Drafted diagrams will add parts you did not design.

6. 6

   Combine with your photos and clips

   Put the drawn scenes and your real footage together in a video editor, or alternate them in your presentation, so explanation and evidence sit next to each other.

Common questions

How long should a product design video be? Use the length in the brief. Without one, five to eight minutes covers a full process. A short pitch for the final product alone is a different video, closer to how to make an educational game pitch video.

Do I need CAD renders? Only if your course asks for them. A clear drawing of how the parts fit often explains more than a photorealistic render, and the render is not evidence of process. If you have renders, show them briefly in the Deliver section.

Can I use a generated voice? Usually yes, unless the brief assesses your presentation skills. You can also record your own narration and use it instead, which some tutors prefer because it sounds like your project.

What about AI tools and academic honesty? The design decisions, the research and the testing have to be yours. Using a tool to draw explanatory scenes from a script you wrote is closer to using presentation software, but check your school's policy and declare it if asked. How to make a video for a school project has more on where that line usually sits.