|
Picture this: a relatively inexperienced engineer working for a large
manufacturing company makes an error in his process control duties, disrupting
the product line in a big way that costs the company an estimated $500,000 in
product damage.
The manager invites the young engineer into his office. He reviews the
events leading up to and during the accident, and finds the engineer to be
completely at fault. What does the manager do?
He considers just firing him and starting over. Pulling the plug on this guy
would mean a fresh start and a chance to find somebody more capable. But
instead, the manager asks the engineer what he learned. He then reviews the
correct course of action and makes sure the engineer is clear on his roles and
responsibilities going forward.

Image Credit: Thousandaire.com
The young professional, expecting to have been fired, can't help but ask why
he hadn't been let go. The manager tells him that it would be unwise to fire him after the company just invested $500,000 in his training.
--
This account, fictitious and exaggerated as it is, emphasizes both the
importance of proper on-the-job training/education (to prevent costly
mistakes) and the value of mistakes in the learning process.
Sometimes, despite our best efforts, the best learning and training we get
is through our mistakes. They not only show us what not to do, but give us
visual perspective on the implications of our actions and on the chasm between things
on paper and things in the real world.
What are some of the "best" mistakes you've ever made (or
witnessed) as an engineer or technical professional that helped you learn the
most?
|
Good Answers:
"Almost" Good Answers: