PART 2: Get the Mechanical Engineer "In the Game"

A mechanical resource should be a part of any product development at the kickoff. Not necessarily as a full time contributor but so the mechanical aspects could start being considered and vetted.  Get the player in the game.  Brett Favre wants to play each week no matter what--even if the pay is the same. So to the best mechanical engineers.

Invaluable familiarity can be gained by the mechanical expert during the feasibility and prototype phase involvement.  The resource would likely identify the key design challenges and begin to ponder effective solutions. 

There is no charge for pondering or otherwise considering the challenge.  It is free engineering for the organization. A passionate engineer often goes through a daily routine with your problem in his or her mind. The best ideas in not always discovered at the office or on demand.  Sometimes it is in the shower or when walking on the beach. A great idea just pops up.

On a recent vacation I as on an RV trip to Colorado.  I needed an elegant solution to resolve a positioning and securing problem for a power supply.  My boss, with an HR background, was convinced it was a simple problem.  But he did not appreciate the challenges of the physics. While entering the RV I noticed the door latch.  Eureka! The scheme fit my application. I snapped a picture on my Blackberry and sent it off to the design engineer. He applied the basic scheme our current application. There is no question that the engaged mind is a perk for a manager to recognize and leverage.

It is unreasonable to hold off the mechanical until the last minute; Then expect the engineer to invent on demand.  A result likely will be achieved. But is it the best one could offer?  Not always. Not usually.

Other early stage benefits that can be achieved are risk management, computerized simulation and/or breadboard testing.  Also, the best engineers typically comb the internet for similar types of product and functions that can readily adapt to new applications. These logical approaches are best leveraged with time and research rather than a crunch time environment. 

Remember that the mechanical engineer is not the only team member that benefits the development and time to market. Consider the other stakeholders:  Manufacturing, Quality, Purchasing, and others all can be informed engaged as a role player. This concurrent engineering atmosphere demonstrates respect for each player and their respective roles and can embolden a team.  

PRODUCT DEVELOPMENT: ROLE OF EFFECTIVE MECHANICAL ENGINEER

PART 1: INTRODUCTION

When do you bring a mechanical engineer into the stream of hardware product development?  This is ultimately a managing decision for the organization considering cost, resources, and timing. But this key decision can lead to dramatically different results.  Early engagement will likely we rewarded with higher quality, more profitable product with an improved market share and return on investment.

Recently, I observed a company that likely waited too long to engage the mechanical piece of the engineering puzzle.  An excellent team of optical, software and electrical engineers were closing in on perfecting the primary functions of a new security imaging system.  Their product had gone through many iterations with mechanical role filled ad hoc by electrical engineers.

The result has been a functionally performing system that is seventy pound and spread out on a table.  Their goal is to have a system less than ten pounds in short order.  To their credit they recognize the need for a mechanical engineer (ME). They are urgently seeking that person to assist in achieving their  goals. Admittedly, they now have unreasonable expectations for the soon-to-be hire. It would be presumptive to say a mistake was made. But it appears that an opportunity was not seized.  

This is an introduction to  a multi-part series being rolled out in the next few weeks. It outlines many of the often overlooked contributions of the a effective practical mechanical engineer in hardware development. 

How many parts will depend on how the spirits move me. My hope is that you enjoy this series and that it helps guide your organization toward many product development success stories.