Blog Archives

What Your Prototype Says About You

Product Development, Leardon Solutions, Manufacturing, San Diego, Southern CaliforniaDesigning and fabricating prototypes during the product development life cycle is a critical part of the product learning process. Successful prototypes will prove that the product idea is feasible, will help qualify the engineering design, and are needed to receive customer feedback prior to producing higher production volumes. The interesting thing about a prototype is that it is an extension of you, your company, and the values of your company. In other words, these prototypes give others a first impression of you and your efforts. Below are four questions investors, distributors, customers, and suppliers will immediately answer upon seeing your prototype:

(1) At what stage is the product in the product development life cycle? A prototype will portray the stage of your product in the product development life cycle. It is immediately apparent to an expert if your product is 5% complete or 95% complete after seeing the prototype. It is important to accurately describe how far along the product is in the product development process when speaking with experts, otherwise it will be very clear that you don’t know much about developing products.

(2) How well have you thought through your product idea? The prototype is a physical embodiment of your product idea. When people see your prototype, they will immediately know if you have thought through only the simple aspects of your product idea or if you have dug deep into the critical aspects of the product such as the user and human interface, the detailed design, the interactions with other products, and the manufacturing or assembly issues. Also, the prototype will show if you have a true innovation, an improvement on an existing product, or a trivial reinvention. If you show up to a meeting with a product prototype that only displays the external features of the product but doesn’t demonstrate the functionality, you will get many questions about how you intend to design the product so it functions properly. If you say “I’ll let the engineers handle that….”, then it will be apparent that you haven’t thought through the idea well.

(3) Do you understand the costs associated with developing a product? When an entrepreneur is in a meeting with a potential investor, the investor is typically looking very closely at the financial forecast and plan to determine if it is realistic. If an entrepreneur brings a mature production prototype to this meeting, the investor will expect that the financial plan has very detailed and accurate numbers. This production prototype allows the entrepreneur to get accurate quotes on the costs associated with taking the product to the next level. If the prototype is only at the proof-of-concept level, the financial plan will include rough estimates and the accuracy of the financial model will be scrutinized in detail.

(4) How prepared are you for the challenges ahead? Nobody ever said that product development is an easy endeavor. There are many roadblocks and potholes on the product development path that must be overcome. Producing prototypes is one of the first. Based on the quality, functionality, and overall look of the prototype, people can easily gauge how prepared you are to take on the challenges ahead. Show them that you are prepared for the future challenges of product qualification, production, and manufacturing scale-up by demonstrating your prototype is the best possible embodiment of your product idea.

Need more information? Please contact us with any questions or contact me directly at joseph.donoghue ( at ) leardon.com

Tagged , , , ,

Do not Ignore the Balloon Effect: Tip #2

Product Development, Leardon Solutions, Manufacturing, San Diego, Southern California

Tip #2: Do Not Ignore The Balloon Effect

An analogy that best describes the constraints of the product development process is one of a balloon. If a balloon is pressed or squeezed in one place, the fixed volume of air is just displaced and the balloon deforms. Here is how this analogy relates to product development. A program manager or engineer might attempt to squeeze cost or time out of the product development process only to find that there are counter effects to these efforts. These counter effects could be increased schedule, lower quality, or mismatch of customer performance requirements. The product development process is the air in the balloon and the program constraints are the balloon holding the air. If the balloon is pressed too much, expect the balloon to pop! There are no free rides in product development.

The Product Development Balloon EffectHere are some of the mistakes made and product development constraints ignored in the product development process.

  1. There is always a tradeoff between product cost, program schedule, and product features/scope that cannot be ignored without consequences. One objective cannot be changed with affecting the others. This is sometimes referred to as the Project Management Triangle in product development circles. The concept is that cost, schedule, and features are all program objectives that are connected and should be prioritized in a properly managed product development process. Sounds very familiar to the the balloon analogy, doesn’t it? The program objective that has the highest priority must not be compromised. The second program objective must be optimized based on the results of the highest program objective. Finally, the team has no control over the last program objective and it lands where it lands. Here is an example. If a team is developing a product that requires the lowest market price, then it is obvious that product cost is the highest priority objective. If the team requires a faster schedule, then either the cost must go up or product features must be dropped from the plan. In this case, the team would choose to drop product features since the product cost is the highest priority.
  2. Proper product development is a process that must be followed with the main objective of shipping products to customers and achievingfirst customership.” The best product development teams follow this process to the letter and don’t attempt to skip steps in order to save money or speed up the schedule. This will only result in failure and a popped balloon.
  3. The cost of a part or product is driven by the complexity as well as the quantity produced. Some people ignore economies of scale and believe that pure negotiation or playing one supplier off of another will result in a part cost that is below market price. Economies of Scale is the economic principle that the cost of something will decrease as the purchased quantity increases. This makes sense in manufacturing since efficiency increases and raw material prices decrease as higher quantities are produced. The best process to follow to get the best price for a product or part is to get multiple quotations from suppliers in the same country. When these quotations are received, have a meeting to work through the details of the quotation and break out costs that are bucketed together in one number. Don’t try to use quotations or prices from other countries to negotiate as this is like comparing apples to oranges. Also remember that if you are able to negotiate what you believe is a “below market” price for your part or product, changes are high that this lower cost will be the result of skipped steps resulting in lower quality.
  4. The relationship between fabrication tooling cost and part cost is an interesting tradeoff that is typically overlooked. When determining the cost of a part, it is important to consider the cost of the tooling required to make the part. If a very low part cost is required, it is necessary not only to order a high quantity but also to invest in high-volume tooling to bring the cost of the product down. Here is the rule of thumb. If you need low tooling costs, then the part cost will be higher. If you need low part cost, then the tooling cost will be higher. Here is an example. If you only needed ten pieces of a part, it is very unlikely that a production tool would be made. If you needed ten thousand pieces of this part, there is no doubt that a production tool would be required. It would cost more per part to make ten pieces versus ten thousand but the tooling cost would be higher for ten thousand. Remember that if you push hard on the part price, changes are high that it will bulge out in the price of the production tooling.

Smart product development teams don’t ignore the balloon effect and understand that there are constraints that mandate that nothing comes for free.

Need more information? Please contact us with any questions or contact me directly at joseph.donoghue ( at ) leardon.com

Tagged , , , ,

Avoid Design Changes When Possible: Tip #1

Product Development, Leardon Solutions, Manufacturing, San Diego, Southern California

At Leardon Solutions, we are starting a new blog series to help provide more information on the product development process. Our new series is called “The Insider’s Perspective” and will focus on tips and teaching that we have learned along the way that we want to share with you. It is our hope that these tid bits of valuable product development knowledge will help you succeed as you begin your journey into the product development lifecycle. If you have a suggestion for one of these blog posts, please contact us, We would love to hear from you.

Tip #1: Avoid Design Changes When Possible

Product development is a creative team process. Engineers and designers take on the difficult task of creating a product that meets all the customer’s needs and wants. The team typically strives for product perfection but unfortunately perfection can never be achieved due to time and money constraints. Therefore, in order to get the product shipped and into the hands of customers, it is important to prevent unnecessary product design changes so the team can go out and manufacture the product for sale.

Product design change is sometimes seen as the enemy of an efficient and cost effective product development process. Of course, change is inevitable and necessary but minimizing unnecessary product change is important to keep the project on schedule and within budget while continuing to meet all the product specifications. Here is the insider’s perspective on why a product development team should avoid design changes when possible.

  1. The objective of the product development team is to deliver a product to a target customer. If change isn’t managed properly, the team members will each make “required” changes based on their own opinions and needs. This will result in change chaos.
  2.  

  3. In order to validate that the product design meets the customer’s quality requirements, the product must be tested. If changes are continually being made in the background, there will never be a stable design that can be formally qualified.
  4.  

  5. If engineers and designers were allowed to continuously change the product design, it would be almost impossible to know what design was qualified and which to manufacture.
  6.  

  7. Changes should only be made if product defects and issue arise. A defect or issue can be raised by anybody on the product development team and the program manager can determine if it is worthy of making a change based on change management rules. Why change if there isn’t a defect?
  8.  

  9. If the product development team has a rigorous defect review process and change system, then only necessary changes will result from the product change management system.
  10.  

  11. Changes cost money and take time. When a change is made, the product development team must make the modifications to the product and qualify the change. This sometimes requires that fabrication tools are scrapped or test data is retaken. This can take significant time and delay the product sale.

Avoid making unnecessary changes to be part of a successful product development team.

Need more information? Please contact us with any questions or contact me directly at joseph.donoghue ( at ) leardon.com

Tagged , , , ,