how to teach with hands-on technical workshops

there’s one lesson that’s shaped how i think about teaching more than anything else, and it came from watching mechanical engineers try to learn soldering and pcb work at the motion studio: lower the barrier to entry, or you lose people before they even get interested.

sounds almost too simple to be a real insight, but watching it happen in real time taught me more than any teaching guide could have. someone genuinely curious about electronics hits a confusing step, and you can just see them deflate. when the task felt hard, interest dropped. when it felt approachable, people leaned in. small wins build motivation. big, ambiguous obstacles kill it.

so here’s what that lesson looks like in practice, using feedback from a real workshop (a drone-building session) as the case study.

1. ambiguity is the biggest barrier, bigger than difficulty itself

people don’t mind that soldering is hard, they mind not knowing whether they’re doing it correctly. the single most common category of feedback from the drone workshop wasn’t “this is too hard,” it was “i don’t know if i’m doing this right”:

none of these are hard questions, but when the instructions aren’t specific, every participant has to make their own judgment call, and every judgment call is a tiny moment of self-doubt that chips away at confidence. multiply that by twenty steps and you’ve built a workshop that feels hard even though no individual step actually was.

the fix isn’t removing difficulty, it’s adding certainty. specify the exact fastener. say which two holes, and reference something visual and unambiguous, like the straight lines on the frame instead of “the ones on the left.”

2. sequence matters just as much as content

some of the best feedback wasn’t about what was taught, it was about the order it was taught in:

the pattern here: teach the check before the risk, not after. if someone needs to verify something—a solder joint, a print bed, a wire connection—before moving forward, that verification step belongs at the front of the section, not as a footnote three steps later.

3. “general enough to reuse” beats “specific to this one setup”

one instinct in technical documentation is to be maximally specific: exact printer model, exact tool, exact part number. that instinct is usually right, but it can go too far. the workshop notes called this out directly:

both of these fail the same way. someone follows the instructions exactly as written, gets to a screen or menu that doesn’t match what’s described, and has no idea whether they messed up or the documentation is just wrong.

practical takeaway: name the specific hardware or software version right at the top, before a single instruction. and where a concept generalizes, like “select the correct build plate material,” write the general principle first, then give the specific example as one illustration, not the only case covered.

4. show the thing, don’t just describe the thing

by far the most repeated request across every section of the workshop was simply: more pictures.

there’s a reason this came up more than anything else. text is great for sequence and reasoning: “do this, then this, because…” it’s genuinely bad at spatial stuff: which hole, which orientation, which wire goes where. anytime a workshop step is really about spatial correctness (orientation, wiring, pin mapping), a labeled photo does in one glance what several sentences struggle to do at all.

and a photo also removes the extra step of making someone translate text into a mental image before they can even check their own work. it just collapses that whole bit of effort.

5. write down the failures, not just the happy path

some of the most valuable lines in the workshop notes were the ones that admitted something didn’t go according to plan:

a guide that only describes the ideal path becomes actively harmful the moment reality doesn’t match it, and in hands-on hardware work, it often doesn’t. the person hits the exact bug the instructions never warned about, and now they’re debugging and wondering if they broke something at the same time.

a huge part of electrical engineering is debugging—embrace it. writing down the known failure modes and their workarounds up front doesn’t make a workshop look less polished. it’s the difference between someone thinking “oh, this is the known issue, here’s the fix” and someone spiraling into “i’ve ruined this and i don’t know how.”

6. materials lists are part of the instructions, not a footnote

there was a recurring, almost mundane thread throughout the feedback: components that were used didn’t match what was written down.

none of these are conceptually hard problems. but each one forces a small, unplanned decision right when someone is deep in a task and least equipped to make a judgment call.

a complete, accurate materials list at the very start isn’t administrative overhead, it’s part of lowering the barrier. it means nobody has to stop mid-task and wonder whether the slightly different-looking part in their hand is a mistake or just an update the docs haven’t caught up to yet.

concluding

every one of these—ambiguous fastener sizes, propellers before soldering, printer-specific wording, missing photos, undocumented bugs, incomplete parts lists—is really just a different flavor of the same failure: a small, avoidable moment of uncertainty that a participant has to resolve on their own, at the worst possible time, with no feedback on whether they got it right.

none of them actually make the underlying task—soldering, 3d printing, flight controller configuration—harder. they just make it feel less certain, less safe to attempt, less likely that a wrong guess gets caught before it costs time. and that feeling is basically what decides whether someone’s curiosity turns into confidence, or turns into “this isn’t for me.”

if there’s one operating principle underneath all of this, it’s the same one that started this whole line of thinking back at the motion studio: build in small, verifiable wins, as often as you can.

whether it’s a continuity test that confirms a solder joint is good or a labeled photo that confirms a wire really does go there. none of these lower the ceiling on what people can learn. what matters more is how people apply the knowledge they gain from workshops to future projects they’ll be motivated to pursue because they now have that basic foundation.