Presenting Is the Last Step of MakingDefinitionPrototypeA working version of a solution built to be tested and shown to a client, rather than a finished product made for sale.The final strand of criterion C asks you to present the solution as a whole, so a build is not finished until it has been shown properly.In your ePortfolio, the solution exists as photographs, a video or a link, because nobody reading it will ever hold the object.Most MYP solutions are a prototype, a working version made to be tested, and saying so sets fair expectations for anyone judging it.Show the thing you actually made, with its real finish and its real tool marks, rather than the CAD render of what you hoped to make.Presenting comes before evaluating, since Evaluating judges a solution the reader can already see clearly.Six Shots Cover Almost Any ProductA full view on a plain background with the whole object in frame and no bench clutter behind it.A scale shot with a 30 cm ruler or a hand beside the piece, so nobody has to guess the size.Two or three detail shots of the parts that took the most skill, like the finger joints or the chamfer on the front edge.A shot from a second angle, because a single straight-on view flattens depth and hides the back.An in-use shot with the solution doing its job, such as the phone sitting in the dock with the charging cable through the slot.Any moving part photographed in both positions, so a lid appears open in one image and closed in the next.TipA window on a dull day gives better light than classroom ceiling lights.Two sheets of A2 white card, one curved behind the object and one held at the side to bounce light back, kill most hard shadows.Shoot from roughly the height of the object instead of looking down at it from standing.Make the Images Carry Size and MaterialSize only reads when something familiar shares the frame, so a ruler, a hand or a mug does the whole job.Give each image a caption with the real dimensions and material, for example "260 x 180 x 90 mm, 12 mm birch plywood, oiled".Crop in tight on the surface for one shot, because grain, weave or print quality disappear in a full view.Leave the filters alone, since a recoloured photograph misrepresents the finish you spent three lessons getting right.Use the same background and light for the whole set, which makes six images read as one solution instead of six objects.Digital Solutions Are Demonstrated, Not PhotographedA screen recording shows a digital product doing what it does, which no still image can manage.Record at the size a real user would see, so an app goes in a phone frame and a site in a window around 1280 px wide.Move the cursor slowly and rest on each screen for about two seconds, because fast clicking is impossible to follow.Caption or narrate what is happening and name the specification point each feature meets as you show it.Keep the demonstration under two minutes by showing one whole task from start to finish rather than every screen you built.Add stills of the main screens as well, so the evidence survives if the video will not play on someone else's machine.HintWrite a four line script before you record, such as open the app, add an item, mark it done, close.Rehearse it once so the recording has no dead time while you hunt for a button.Record it twice and keep the better take, which costs about four minutes in total.Show the Client Using ItThe strongest presentation shows the client using the solution for the purpose named in your design brief.Shoot it in the real setting, such as the tool rack mounted on the wall of the workshop it was made for.Capture the moment the client performs the task, not the client standing still holding the object.Ask permission before you photograph or film anyone and check they are happy for it to appear in your ePortfolio.Write down one line of what the client said while using it, which feeds straight into your evaluation.A clip of the client fumbling with one part is honest evidence and usually more useful than a perfectly smooth demonstration.Exam techniquePresent the solution before you evaluate it, so a moderator knows exactly what is being judged.Caption every image, because an unlabelled gallery leaves a reader guessing which part is which.Include at least one image of the solution in the environment named in your design brief.How a Good Build Gets Presented BadlyPhotographs taken on a workshop bench with tools and offcuts in frame make a finished piece look half done.One angle only leaves a reader unable to judge proportion, depth or how the parts join.With no scale in any image, a 60 mm keyring and a 600 mm shelf look identical on screen.A silent video with no captions leaves the viewer unsure what they are supposed to be watching.Photographing only the good side reads as hiding something, and honest images give you more to work with when you evaluate.Active recallWhy is a prototype described as a prototype when you present it?Name four of the six shots that cover a product.How do you give a viewer a sense of scale, and why does a caption alone not do it?What should a screen recording of a digital solution include besides the screens?Why is footage of the client struggling with one feature worth keeping?