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.
No comments:
Post a Comment