4 responses to “Key to a Successful Design – Confidence?”

  1. Chris Gammell

    Everybody likes being right and comes to the table with their own agenda. Doubly so in design reviews. Be prepared to defend your position and know your design well.

  2. An old engineer

    Great blog. Every technical team thinks that they can make anything work. That is the inert nature of an engineer. But, you need to remember that there are multiple parts of a good design. One is the technical aspect where you deal with the stresses, deflection, etc.

    Another part is the financial one. Can you design, build it, assemble it, and test it for what you say it should cost? This is usually the one that is the biggest unknown especially for cutting edge technology.

    What it cost to put together a working prototype really has no bearing on what it cost to design a production version of a piece of equipment. This is something that upper management really needs to understand.

    Also, quantity and complexity of the design has alot to do with it. Designing a wigit for the automotive industry is much different that designing a wigit for the space shuttle. Designing for low quantities and unusual circumstances does limit you to the type of fabrication and assembly techniques you can afford to use.

    A checklist is one way of making sure that you’ve crossed your “t” and dotted your “i”. I always liked to have a mini-design review before the real one. It doesn’t have to be anything formal, a review by several of your peers within and outside of your department (e.g. machine shop, etc) have saved my butt many a time.

    Someone once told me that “you don’t know everything”. How true he was.

  3. Weekend Journal: Know Your Nerd Audience | Engineer Blogs

    […] the end use — In my case, I found myself thinking, “We are not process engineers, we are product designers!’ This is not always the case and there are some people that would love hearing about the […]

  4. Weekend Journal: When The Deadline Is "Right Now" | Engineer Blogs

    […] Do you test or retest changes to a product or process to ensure the problem is truly fixed? Or do you confidently declare that the design change was properly analyzed and that there will be no problems that will affect […]