Teaching mechanical design to high school robotics students

Robotics can hook students immediately, but the most valuable learning often happens when a team moves beyond a working prototype and asks why each part exists, how it carries a load, and how it can be manufactured affordably. The classroom becomes a place to test engineering judgement, not merely assemble components.

Mechanical design principles give students a shared language for turning a competition objective into a functioning machine. They connect sketches, CAD models, material choices, fasteners, gear trains, linkages, tolerances and test data. Used deliberately, those ideas help learners explain trade-offs, predict failure modes and improve a design without wasting expensive competition hardware.

The strongest high-school robotics programmes treat design as a cycle of framing, imagining, building and revising. Teams begin with a need or problem, create several concepts, make a testable version and compare predictions with measurements. Errors become useful evidence rather than embarrassing setbacks, and every subsystem receives a clear purpose within the whole robot.

This cycle fits Australian classrooms well. Teams in Melbourne, Sydney, Perth and Adelaide come from very different school settings, including selective schools, comprehensive colleges and vocational campuses. Mentors can link the work to the Australian Curriculum’s science, technologies and maths capabilities, while local engineering businesses and community makerspaces provide tools, site visits and practical expertise.

Why design thinking drives better robots

Design thinking gives students a repeatable route from a vague challenge to testable requirements. Instead of beginning with a motor or a preferred component, teams identify the job each mechanism must perform. They sketch alternative solutions, estimate loads and motion, then select a concept against agreed criteria such as mass, cost, reliability and buildability.

The balance between digital modelling and physical making should be visible to learners. A compact classroom comparison makes those trade-offs easier to discuss and assess.

Teaching approach	Student activity	Main design skill	Common pitfall
Concept first	Sketch and rank alternatives before choosing parts	Requirements-based decision making	Delaying useful testing
CAD first	Model fit, motion and loads in software	Spatial reasoning and documentation	Treating a polished model as proof
Build first	Fabricate and test a simple mechanism quickly	Hands-on diagnosis	Accumulating hidden design errors

No approach is automatically best. CAD-first work strengthens visualisation, while a deliberately simple prototype can answer a mechanical question faster than a detailed model. Strong programmes alternate the two, asking students to record what changed, why it changed and which evidence justifies the next revision.

Turn the brief into measurable constraints

Start from measurable constraints rather than a prescribed answer. A requirement such as “raise a game piece cleanly between two obstacles” becomes an acceptance test with defined travel, clearance, payload and repeatability. Students then choose suitable sensors, actuators and linkages. This structure gives every proposed design something concrete to satisfy or disprove.

Competition objectives can become acceptance criteria rather than vague goals. FIRST Tech Challenge scoring rewards specific game behaviours, and a resource on scoring system insights can help students translate points into subsystem requirements. The link between scoring and mechanics matters because a high-value action that jams under load is not a successful design.

Constraints should also reflect the real market around a team. In Australia, sponsorship proposals, quotes and purchases are commonly handled in Australian dollars, and GST may alter supplier comparisons. A team can ask students to compare laser-cut acrylic with aluminium plate on mass, lead time and joining method while managing the tension between local fabrication and shipping components from interstate.

Teach the mechanics behind the mechanism

Once requirements are clear, students need a mechanical model that explains behaviour. Loads travel through members; torque depends on force and moment arm; gears trade speed for torque. Short practical tasks can ask teams to calculate the required torque on a lift arm, estimate a motor’s duty cycle and compare it with the result from a test.

Geometry should never be treated as decoration. Linkages determine a mechanism’s path, while the location of a payload relative to the axle affects tipping. Give students paper templates, timber linkages and extension pegs to explore motion before committing to CAD. A change in a hole position can then be linked directly to a measured change in force.

Material selection follows function, not fashion. Teams can compare stiffness, toughness and mass across plywood, acrylic, aluminium and steel, then connect each choice to a load case. The goal is not to name the “best” material, but to justify a suitable one with safety factor, expected service loads and available workshop processes.

Make CAD and prototyping inseparable

CAD gives a team a precise conversation about geometry and change. Before manufacturing, students should model clearances, fastener access, bearing fit and the path of every load. A model also exposes inconsistencies between the arm length, motor position and control assumption. The teacher can then ask whether the software and physical prototypes agree.

Prototyping should answer a chosen question rather than merely prove that a CAD file looks tidy. Paper, card, timber and 3D-printed parts can establish fit and stiffness cheaply before metal is cut. Students annotate the prototype, measure it and explain the gap between prediction and result.

Manufacturability belongs in the first sketch. Teams should prefer standard fasteners, accessible tools and shapes a local workshop can repeat. In a school with limited machinery, that may mean designing around laser-cut parts and commonly stocked M3, M4 or M5 hardware. A supplier quote in AUD becomes a design input rather than a surprise after the robot is finished.

Build a disciplined test and iteration cycle

Testing turns an idea into engineering knowledge. A useful session begins with a hypothesis, such as “the bracket will remain rigid when the arm lifts two kilograms”, followed by a measurement method. Teams record pass or fail, photograph the setup and keep the test conditions consistent. Otherwise comparison becomes guesswork.

Design for diagnosis as well as operation. Colour-coded connectors, replaceable modules and accessible fasteners help a student identify a problem at an event. Because some Australian teams travel long distances between regional and metropolitan competitions, repairability and access to spare parts matter as much as peak performance.

Failure should become a normal part of the brief. Students can run a pre-competition “what breaks first?” session and rank likely failures by probability and consequence. That ranking guides protective design, stock and practice. The payoff is faster diagnosis and confidence, not a robot that never fails.

Teach teams to design together

Mechanical design is a team sport as well as an individual discipline. Assign rotating roles such as design lead, CAD owner, mechanism tester and fabrication coordinator, then require every role to contribute to shared decisions. A design review can follow a checklist covering function, safety, cost and manufacturability, while students explain the evidence behind their recommendation.

Mentoring culture in Australian robotics often feels informal: people say “have a go”, share tools and troubleshoot beside the student rather than taking over. That approachable style works when paired with clear boundaries. Mentors ask probing questions, model safe workshop habits and encourage a fair go for quieter team members, whose ideas may be quieter too.

Communication is itself a design constraint. Teams need version-controlled CAD files, dated test notes and a decision log showing why a motor was replaced or a link shortened. Assigning a student to document changes keeps knowledge visible during competition pressure. It also makes it easier for a new mentor to join mid-season and continue the design process.

Put learning into community action

Learning extends beyond the robot and into communication, persistence and community participation. Teams can host a walk-through for younger students, demonstrate a mechanism at a school open day or help a local maker space run a safe building session. In return, the team gains fresh questions, new users and reasons to refine the machine.

Reading practice supports that broader engagement. Before summer, mentors can use the Bookert guide on encouraging reluctant readers to make technical instructions, safety notes and engineering histories more approachable. The same strategy that turns a daunting page into a short task can help a student feel capable of joining a build session.

Put the design cycle into action this week. Choose one robot subsystem, write three measurable requirements and schedule a design review with a teacher and mentor. Give students one CAD model and one test fixture, then set a date to compare predicted and measured performance. The next competition becomes a measure of the learning cycle, not just the final score.