How Engineers Think When Something Breaks

At Avanza STEM engineering workshops, something breaks at almost every session. A bridge collapses under weight. A tower falls when a block is added. A cardboard structure tips over. And almost every time, the student who built it knows exactly what went wrong the moment it happens.

That moment of understanding, 'oh, it broke right at the joint, because I did not glue it well enough,' is the most important moment in the whole session. It is not a failure. It is information.

The First Question an Engineer Asks

When something breaks, the first engineering question is not 'what did I do wrong?' It is: 'where did it break, and what does that tell me?'

A bridge that snaps in the middle tells you the middle was the weakest point. A joint that pulls apart tells you the connection was not strong enough. The break is giving you instructions for the next build.

The Improve Loop

Engineers use an iterative cycle, sometimes called the design loop. It is not a straight line from idea to success. It looks more like this:

1. 1

   Define the goal

   What exactly does the structure need to do? Hold 5 pounds? Span 30 centimeters? Weigh as little as possible?

2. 2

   Build a first version

   Do not try to make it perfect on the first try. Make it testable.

3. 3

   Test it deliberately

   Apply the actual load or stress. Do not guess how it will do.

4. 4

   Observe what failed

   Notice not just that it failed, but where and how. That detail is the data.

5. 5

   Make one change at a time

   If you change three things and the next version is better, you do not know which change helped.

6. 6

   Test again

   Repeat. Each round gives you more information than the last.

What This Looks Like at Avanza STEM Workshops

During bridge-building sessions, students usually build once and then test their structure. That single test still teaches a lot. When the bridge bends, twists, or finally breaks, students can see which part of the design carried the most stress.

The important moment is the conversation after the test: where did it fail, why did that spot give out, and what would you reinforce if you built a second version?

The One Change Rule

This rule matters more than most students realize: when something breaks, change only one thing at a time before the next test.

If a bridge breaks and you rebuild it with better joints AND a different truss shape AND more bracing, you learn very little. Maybe it holds more weight, but you do not know which change made the difference, so you cannot apply that knowledge to the next build.

This Thinking Works Everywhere

The engineering mindset is not only for structures. The same pattern of observe, hypothesize, test, and improve shows up everywhere:

• Science: a failed experiment tells you something specific about the conditions or your hypothesis
• Coding: a program that crashes gives you an error message, so read it carefully before you change anything
• Math: a wrong answer tells you which step to go back and review, not that you are bad at math
• Sports: a missed shot shows you what to adjust in your stance or timing, not that you should quit