insight / QFP

Cardboard, 3D printing or electronics: comparing prototype routes by what they let you test

The best prototype material is the one that lets your team answer this week's question fastest. Compare routes by what they let you test, not by how impressive they look.

QFP progression pathway visual

Why the route matters before the build starts

Student teams often pick a material because it looks professional or because someone owns the equipment. A better question is what the team needs to learn first. The route you choose decides how quickly you can change the object, how many tests you can run in a week and what kind of evidence you will have at the end.

This article compares three common routes: cardboard and found materials, 3D printing and simple electronics. They are not a ladder from basic to advanced. Many strong projects use more than one. The comparison uses three questions: how long does a version take to build, how costly is it to change, and which test questions can this route actually answer?

Cardboard and found materials: fast and cheap to change

Cardboard, tape, paper and similar materials let a team build a rough version in an hour. A wrong guess costs little, so teams are willing to throw a version away. This route is excellent for testing size, shape, layout, how a user holds or moves something and whether a mechanism has the right idea.

Its limits are strength and precision. A cardboard version will not tell you whether a part survives repeated loads or whether a tight tolerance works. Teams sometimes stay on this route too long because it is comfortable. Use it early, name the question it answers and move on when the remaining questions need a different material.

3D printing: precise parts, slower loops

3D printing produces parts with accurate dimensions and repeatable shapes. It suits questions about fit, such as whether two parts connect, and about small mechanisms that need precision. A printed part can also be copied, so the team can test the same design several times.

The cost is time and a heavier commitment to each version. Models must be designed, files prepared and parts printed, so one loop may take most of a day or more. A mistake in the design means waiting for another print. Plan the print queue, limit each loop to one change and consider a cardboard mock-up first to avoid wasting prints on avoidable errors.

Simple electronics: adding behaviour and measurement

Simple electronics, such as a small microcontroller board with a sensor or a motor, add behaviour to the prototype. They let a team test whether something responds, counts or measures. They also help with evidence, since a sensor reading can be logged and compared across tests.

The risks are debugging time and fragile connections. A loose wire can look like a design failure. Keep circuits simple, label connections and test each part alone before combining them. Electronics answer questions about behaviour and measurement but are poor at answering questions about comfort, size or how a person uses the object, which are better tested with a rough physical model.

Putting the three routes in one table

Draw a table with the routes as columns and three rows: time to build one version, cost of changing it, and the questions it can answer. Fill it with the team's own estimates, using hours and rough costs in your own currency. Do not copy numbers from elsewhere; your equipment and skills are particular to your team.

Then list this week's test question above the table and circle the route that answers it with the least effort. If the answer is cardboard, use cardboard even if a printer is available. If two routes seem equal, choose the one that allows more repeats of the test in the time you have.

Combining routes across a six-week project

A common pattern is to start with cardboard to settle the size and the layout, move to 3D printing for the parts that need precision, and add electronics where the object needs to sense or move. Each stage has a clear question and a clear exit condition, so the team does not drift into building for its own sake.

Keep the earlier versions. A photograph and a short log entry for each route show how the design changed and why. Reviewers and teachers can see the reasoning, which is worth more than a polished final object. Make sure everyone on the team handles the tools safely, with adult supervision where it is required.

A worked example of choosing a route

Imagine a team designing a holder that keeps a tablet at a comfortable angle on a desk. The first question is about angle and stability, so the team builds a cardboard version in an hour and tests three angles with a few different tablets or books. Two angles feel good and one slides, so the team records that result and chooses one.

The second question is about a hinge that holds the angle firmly. That needs precise parts, so the team designs a small printed hinge and tests whether it holds over repeated adjustments. No electronics are needed. Each route answered one question, and the log records which route was used and why, which makes the design history easy to follow.

Safety, supervision and access to tools

Each route has different safety needs. Cardboard work needs safe cutting tools and a clear table. 3D printers have hot parts and should be used with adult supervision and the school's rules. Electronics involve small components, soldering in some cases and power sources that need care. Plan these needs before choosing the route, not afterwards.

Access also matters. If the printer is shared by many teams, the queue may decide your real loop time. If only one adult can supervise electronics, plan when that work can happen. Writing these constraints into the comparison table keeps the choice realistic and prevents a plan that looks good but cannot be carried out.

Common mistakes and quick fixes

The first mistake is choosing the route before writing the question. The fix is to write the test sentence first. The second is skipping the cheap route because it feels childish. The fix is to remember that speed of learning is the goal. The third is mixing several changes in one version, which makes results impossible to interpret.

The last mistake is treating the final route as the point of the project. The skill being developed is the cycle of build, test and log, which works with any material. Revisit the comparison table each time the question changes, and let the question choose the material.