3 The Engineering Design Process

The design cycle

Engineering design is a practical, iterative way to develop a solution to a need or problem. A common cycle is to define the need, generate ideas, select a concept, build a prototype, test it, and improve the design. Although the process is often shown as a sequence, engineers may return to earlier steps when new information or test results reveal a problem.

Define the problem

Before designing, clarify who needs a solution and what it must do. Identify the criteria—the features or performance the solution must achieve—and the constraints, which are limits the design must respect. Clear criteria make it possible to judge whether a design works.

For example, a paper-bridge challenge might require a bridge to span a 20-centimeter gap and support as many washers as possible, while using no more than two sheets of paper. The span and load are criteria; the material limit is a constraint.

Generate ideas

Explore several possible approaches before settling on one. Sketching, discussing, and combining ideas can help a team consider alternatives. Aim for variety at first rather than dismissing ideas too quickly; afterward, develop promising options into clearer concepts.

For the paper bridge, concepts might include a flat sheet, a folded beam, or a structure made from rolled-paper tubes. These options involve different trade-offs in strength, material use, and ease of construction.

Select a concept

Compare ideas against the problem’s criteria and constraints rather than choosing only by personal preference. A decision matrix can help a team list criteria, assign weights if some criteria matter more, and score each concept. Discuss the results together. The matrix supports a reasoned choice but does not replace judgment, especially when assumptions are uncertain and need testing.

A team might compare bridge concepts by load capacity, material use, and ease of assembly. It could select a folded beam to prototype while keeping another idea as a backup. Selecting a concept also involves planning how to build and evaluate it.

Build a prototype

A prototype is an early model used to explore or test a design. It may use inexpensive materials and does not need to look like a finished product. Choose its form based on what the team needs to learn: a quick sketch or model may clarify shape, while a working prototype can reveal performance. Build it carefully enough for its test results to be useful.

For the bridge, the team could fold paper into a beam and place it across the test gap. Recording dimensions and construction details helps the team reproduce or modify the design.

Test and evaluate

Plan a test that measures performance against the criteria. Keep conditions as consistent as possible, record observations or measurements, and note failures as well as successes.

For a bridge test, use the same gap and loading method each time. Add washers consistently and record the load at which the bridge bends or collapses. Comparing results with the original criteria helps the team decide whether to refine the design or reconsider its concept.

Testing can reveal not only whether a design worked, but how well it worked, where it failed, and what might be changed.

Iterate and improve

Iteration means using feedback and test evidence to revise a design, build another version, and test again. When practical, change one feature at a time so it is easier to connect a change with its result. For example, the team might add folds to the bridge, repeat the same load test, and compare the results with those from the first version.

Poor performance may call for more than a small adjustment: the team may need to revisit its concept, constraints, or understanding of the problem. Continue until the solution meets the important criteria within the constraints, or until evidence shows that a different approach is needed. The design cycle supports learning and improvement; it does not guarantee that the first idea will succeed.