Your first week in a real plant is an apology tour for everything you were so confident about in school. You walk in thinking "design" means clean geometry and correct equations. Then the floor hands you reality in steel-toe boots. The fastest way to learn this is to watch a technician solve your problem in five minutes, then keep solving it for the next five years. See Reason #16. And when you try to explain what you "meant," you discover your meaning does not ship. See Reason #10.
The gap is structural, not personal. Your curriculum spent its budget on canonical thermodynamics and fluid mechanics that have not changed in decades. See Reason #35. The electives that were supposed to let you specialize gave you three courses, a sampler platter, not a skill set. See Reason #41. James Trevelyan spent years studying what engineers actually do versus what they believe they do. His ethnographic research, published in the Journal of Engineering Education, found that engineers spend approximately 60 percent of their time communicating with others and less than 30 percent on solitary technical work (Trevelyan, 2007). Early-career engineers spend 50 to 70 percent of their time on direct interpersonal interactions (Trevelyan and Tilli, 2008). His 2014 book, The Making of an Expert Engineer, catalogs over 100 misconceptions that engineering students carry into the workplace. The most persistent one is that engineering is primarily about technical problem-solving rather than coordination and communication. The plant corrects that misconception in the first week.
In class, constraints are tidy and announced. In a plant, constraints arrive as a forklift turning radius, a fixture that already exists, a vendor that can only hold that tolerance on Tuesdays, and a lead time that makes your "better" material irrelevant. Your elegant part fails because it cannot be deburred without cutting gloves, because the operator cannot reach that fastener without removing two guards, because the paint line racks it by the one surface you made critical, because the packaging drop test turns your crisp edge into a warranty claim. You start noticing that the important dimensions are the ones you never thought to dimension.
A Robinson (2012) time study of 78 design engineers over 20 working days, generating 11,137 data points, found that even their "technical" work was saturated with information management. The same engineers spent 55.75 percent of their time seeking, receiving, or providing information (Robinson, 2010). The plant rewrites your sense of what "engineering" is. You spend less time proving the mechanism and more time proving it can be built, inspected, shipped, serviced, and repeated. You learn to fear ERP substitutions, revision locks, and the quiet power of a nonconformance tag. You learn that the drawing is not the truth. The process is. A perfect CAD model is just a suggestion until the gage says no and the line stops.
And the irony is you still have to act like the degree taught you this. You will talk about analysis and "design intent" while you are really negotiating with reality: cycle time, scrap rate, torque access, training burden, rework risk, and whatever the shop can actually do this week. The plant does not care what you know. It cares what you can get to ship. You might expect the employer to close the gap the university left open. They do not. Your training is a safety video and a supervisor who points at the line. See Reason #54.
You were trained to solve problems. You were hired to learn which problems you are allowed to solve.
References:
Trevelyan, J. P. (2007). Technical coordination in engineering practice. Journal of Engineering Education, 96(3), 191-204. https://doi.org/10.1002/j.2168-9830.2007.tb00929.x
Trevelyan, J. P. (2014). The making of an expert engineer. CRC Press.
Robinson, M. A. (2012). How design engineers spend their time: Job content and task satisfaction. Design Studies, 33(4), 391-425. https://doi.org/10.1016/j.destud.2012.03.002
Robinson, M. A. (2010). An empirical analysis of engineers' information behaviors. Journal of the American Society for Information Science and Technology, 61(4), 640-658.
I like the way of your blog post content. Thanks
ReplyDeleteTrain Horn Kits