Developing Products That Will Perform

298 views

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
298
On SlideShare
0
From Embeds
0
Number of Embeds
81
Actions
Shares
0
Downloads
3
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Developing Products That Will Perform

  1. 1. Developing ProductsThat Will PerformJonathan Prince
  2. 2. What Are We Talking About?• How good development processesenhance performance• Design process overview• Other major contributors• The kiwi advantage
  3. 3. How does a good developmentprocess enhance performance?
  4. 4. It’s All About Value!1. Improves innovation/design/engineering2. Directs focus on the customer need3. Reduces development cost4. Reduces time to marketIncrease The Bottom Line
  5. 5. Late to MarketLost revenue1 2 3 4 5Volumes/ SalesTimeTime To Market
  6. 6. The Facts“Products that come to market six monthslate but on budget will earn 33% less profitover five years…In contrast, coming out on time and 50%over budget cuts profits by only 4%”.- McKinsey and Company
  7. 7. 1. Improves innovation/design/engineering2. Directs focus on the customer need3. Reduces development cost4. Reduces time to market5. Improves product qualityIncrease The Bottom LineIt’s All About Value!
  8. 8. The Development Process:Getting it wrong andGetting it right
  9. 9. Low & behold –We haven’t meet expected ROI!Project goes back through the Design loopReview becomes a ‘That’s not what I meant’ scenarioPhysical models createdTeam jumps straight into design – Interprets needsProject identified – Needs based on perceptionsA Common Little Gem
  10. 10. Death Spiral Down to Hell!
  11. 11. Bugger!• Increased labour, material cost• Project gets axed• Increased time to market• Doesn’t address customerneeds• Costly rework• Lost opportunity costSignificantlyReducedReturns
  12. 12. ProductionStandard Stage Gate ProcessConceptdesignDetaildesignFeasibilitystudyPre ProductionClear design briefStakeholder reviewsDesignbriefProject Scope Common start pointRobust Development Process
  13. 13. Design Brief – Why Bother?• All parties know exactly what’s being designed - andWHY!• Prevents project from going off track– Keeps team focused• Product features are clearly identified and agreed• Ensures project is:– Well researched– Well understood– Relevant to the market needCore Document – Absolutely key to project success
  14. 14. Other Major Contributors
  15. 15. Oi! You Two…Play Nice!• Collaboration is King– Cross functional teams– Industry experts– Hard & fair customers– Leverage Suppliers early• Creative culture– No Egos– Being open and honest isexpected– Make it FUN!
  16. 16. Virtual Prototyping?Nah, I’ll just whip one up!• Stress Analysis– Understand loads/ forces early– Remove unnecessary weight/ material• Flow Analysis– Can it be made?!• CAM – Machining– Complex geometries with ease• Rapid Prototyping– Visualisation– Check fitsEmbrace Technology
  17. 17. How Hard Can It Be?• Feller/De-limber• $150k per unit• Failing in the field• Analysed for failure• And then we checked it in the field!
  18. 18. Lucky?!• $1/4M prototype• 25 Year life• 10 Million cycles• 3 month test cycle• Right first time!Get it right, before you cut steel!
  19. 19. The Kiwi Advantage:You bet we can fly!• Source of fresh ideas:‘Unencumbered thinkers’• Collaborative, driven,dynamic• Constrained resource,big ambitionsAdventurous and pioneering
  20. 20. Summary• Implement a robust development process• Develop a design brief template - do yourresearch!• Create a culture of innovation• Leverage technology• Persevere - design creates a uniqueprofile for NZ companies
  21. 21. Innovate or Die!

×