My first time inside a working manufacturing operation, and the first place I watched a machine go from raw stock to a programmed, running system. I started on the debur and part-finishing team and moved into machine assembly and electrical panel wiring, building food automation equipment alongside the technicians on the line.
Before I could suggest improving anything, I had to understand how these machines were actually put together. Working directly with technicians taught me to read mechanical and wiring schematics, use the shop's power and hand tools, and inspect incoming parts against print tolerances. That last habit mattered most. A feature out of spec doesn't stop at one station; it forces rework three or four operations downstream.
Once I understood the process, the inefficiency was hard to unsee. Technicians were context-switching between unlike assemblies and walking the same parts back and forth across the shop. Every switch cost setup time and re-orientation, and none of it showed up as a defect. It showed up as hours.
I proposed a batch approach to my supervisor: group like assemblies so a technician completes one operation across several units before switching tasks. We implemented it in the assembly team, and throughput increased. The change also freed floor space that had been consumed by parts in transit, which let the team stage new assemblies and reorganize the shop, cutting retrieval time and compounding the original gain.
The biggest takeaways from this experience was process problems are usually visible from the floor before they're visible in the numbers, and the fastest way to earn the standing to fix one is to build the thing yourself first.