“All My Students Do Is Tinker.” How Do I Get Them to Use the Science?

A teacher wrote to me with a version of a complaint I hear constantly:

“When I do engineering projects, it seems like all students do is tinker and they do not learn much about the science I need to teach. Any advice?”

My first piece of advice is to stop treating this as a student problem. Trial and error is a rational strategy. If a challenge can be solved by adjusting materials until something works, students will solve it that way, because it is faster than thinking and it earns the same credit.

Students use the science when the science is the shortest path to a good solution. Whether it is the shortest path gets decided when the task is designed, not when it is assigned. Here are nine keys.

1. Check whether the science is actually required. This is an uncomfortable test but a quick one. Could a student produce a winning solution without using the disciplinary core idea you care about? For the tallest tower, the farthest catapult, and the egg drop, the answer is almost always yes. Trial and error is sufficient, and often optimal. Once you look at it this way, the tinkering problem stops looking like a motivation problem and starts looking like what it is.

2. Choose a problem whose solution depends on the idea you are teaching. Heat Packs for Cold Snaps requires students to reason about exothermic reactions, because there is no way to fiddle your way to a bag that reaches 40 degrees Celsius and holds it. Solar Fan, a fourth grade challenge, requires ideas about energy transfer. Insect Trap for Monitoring Biodiversity requires ideas about ecosystem interactions. In each case the disciplinary idea is load-bearing. Remove it and the design collapses.

3. Set constraints that trial and error cannot satisfy. Look at what the heat pack has to do. Reach at least 40 degrees Celsius from room temperature. Never exceed 60 degrees, because above that it burns skin. Stay above 40 degrees for at least ten minutes, and longer is better. Not start until someone wants it to. Come in under a $200 budget that includes paying everyone who works on it at least minimum wage. The ceiling is the part I would point to. A floor alone rewards more of everything. A floor plus a ceiling forces students to reason about how much reactant to use, and reasoning about amount means reasoning about the reaction.

4. Put the ideas on the table before design, and expect them back later. In the Ideas stage, students read and discuss three short texts drawn from science, engineering, and mathematics and record the ideas that seem useful. Do not front-load vocabulary here, and do not tell students what they are supposed to learn by the end. The point is to make the ideas available, not to pre-teach them. They come back when students are writing arguments and justifying evidence, and that is when they get used for real.

5. Require a model, not a sketch. A sketch shows what a thing looks like. A model shows how it works, including the parts you cannot see. Push students to represent forces with arrows, to use callouts for things too small to see, and to show change over time with a sequence of images. This single requirement does more to interrupt tinkering than anything else on this list, because you cannot draw a mechanism you have not thought about.

6. Make students choose among concepts rather than build the first one. Every student generates a concept, reviews two others against the constraints, revises, and generates a second. The group ends up with six or more designs and ranks them against the criteria in a decision matrix, with any design that violates a constraint thrown out rather than scored. What makes this valuable is not the matrix but the argument it produces, because a group that has to justify why depth matters more than ease of use is reasoning about the problem rather than about the materials.

7. Test for data, not for “did it work.” Ask students to record measurements and observations on every cycle, along with what they changed and why. Then, when you circulate, ask about the reasoning rather than the result. “What are you trying to optimize, and why?” “Why are you assuming that will work?” A group that cannot answer the second question is tinkering, and now you both know it.

8. End with an argument and a report, not a demo. A demonstration answers “what we did.” An argument answers “how we know.” Students put up a claim about the best solution, the evidence from their testing, and a justification for why that evidence supports the claim. The justification is where the science lives, because explaining why your evidence counts requires naming the idea that makes it count. Then each student writes a report, peer reviews two others, and revises. Writing is where a lot of the learning consolidates, and it is the stage teachers cut first when they are short on time. I would cut something else.

9. Debrief the ideas separately from the practices. Hold two conversations at the end rather than one. First revisit the disciplinary ideas and ask students to use them to explain what happened with their designs. Then, separately, talk about the process: what went well, what did not, what the class would do differently. If you only debrief the process, students will reasonably conclude that the challenge was about the process.

Putting It All Together

Tinkering is not a character flaw. It is a symptom of a task that permits it. Students are efficient, and they will find the cheapest route to whatever you are counting.

So make the science the cheapest route. Choose a problem where the disciplinary idea does real work, write constraints with both a floor and a ceiling, require a model that shows a mechanism, force a choice among competing concepts, and end with an argument rather than a demonstration. Do those five things and the tinkering mostly takes care of itself.

How ADI Makes This Easier

Designing a challenge where the science is genuinely load-bearing is the hard part. You have to know the content, know what students do instead of using it, and then write criteria and constraints tight enough to close off the shortcuts without making the problem impossible.

That is the design work built into the ADI STEM design challenges. The criteria and constraints are written to require the disciplinary ideas, the informational texts put those ideas on the table before students design, and the seven-stage model builds in the concept review, the decision matrix, three build and test cycles, the argumentation session, and the peer-reviewed report.

Want to See What This Looks Like?

Browse the challenges and the Three-Dimensional STEM Challenges with Argument-Driven Inquiry books at shop.argumentdriveninquiry.com/collections/engineering-challenges, or learn more about ADI curriculum materials, the ADI Learning Hub, and our professional learning options at argumentdriveninquiry.com.