Presentation by Design Concepts President Dave Franchino on sources of failure in product development and how to mitigate risks. Delivered in Madison, WI, on July 25, 2019.
a move fast method to sharp the idea and design in five days. It has been proven to most of the startup under Google ventures. Want to know more how to build it, just contact me. :)
It doesn’t matter if you’re a one-person freelancer, a budding 5-10 person agency, or an established small to mid-sized company - you will always contend with the challenges of growth. This month, key employees from Raleigh-based web shop Atlantic BT (ABT) will share their experiences on how to build and maintain a foundation for growth in light of pressures from increasing demand.
COO, Software Development Manager, and Creative Director will share some patterns that triggered growth, and how each handled them.
Business people in corporations and SME struggle with the notions of ‘design thinking’ & ‘design research’. Here are 8 ‘business’ figures to explain the value of Design Thinking & Design Research for organizations.
Event 5, which focuses on the activity of "Validate," is the final task of a 5-Day Lean Design Sprint. This presentation provides visual checklists and templates that can be used to facilitate the activity of "Validate."
The Design Sprint: A Fast Start to Creating Digital Products People Wantdpdnyc
In this talk, you'll learn how to plan, facilitate, and optimize the five phases of a Design Sprint: Understand, Diverge, Converge, Prototype, and Test. You’ll learn why and how Design Sprints work and how you can use Design Sprints to enhance your own design process.
a move fast method to sharp the idea and design in five days. It has been proven to most of the startup under Google ventures. Want to know more how to build it, just contact me. :)
It doesn’t matter if you’re a one-person freelancer, a budding 5-10 person agency, or an established small to mid-sized company - you will always contend with the challenges of growth. This month, key employees from Raleigh-based web shop Atlantic BT (ABT) will share their experiences on how to build and maintain a foundation for growth in light of pressures from increasing demand.
COO, Software Development Manager, and Creative Director will share some patterns that triggered growth, and how each handled them.
Business people in corporations and SME struggle with the notions of ‘design thinking’ & ‘design research’. Here are 8 ‘business’ figures to explain the value of Design Thinking & Design Research for organizations.
Event 5, which focuses on the activity of "Validate," is the final task of a 5-Day Lean Design Sprint. This presentation provides visual checklists and templates that can be used to facilitate the activity of "Validate."
The Design Sprint: A Fast Start to Creating Digital Products People Wantdpdnyc
In this talk, you'll learn how to plan, facilitate, and optimize the five phases of a Design Sprint: Understand, Diverge, Converge, Prototype, and Test. You’ll learn why and how Design Sprints work and how you can use Design Sprints to enhance your own design process.
The Design Sprints are a 2-5 days process for answering critical business questions through design, prototyping, and testing ideas with customers.
In this keynote I present you the Google Venture Design Sprints Methodology.
These slides were part of a 30 minute presentation. The focus was on creating common (design thinking) ground between design, marketing and sales people inside a company.
These slides include a bit about me but mostly function as a backdrop I refer to during my oral presentation.
I do not read my slides :-)
How Design Thinking works, or: Design Thinking Unpacked: an evolutionary algo...J. M. Korhonen
A presentation accompanying a paper* presented at EAD 2009 conference in Aberdeen, Scotland. We're trying to develop a theory why "design thinking" works in practice, and what may be its limits. The idea is that "design thinking" has similarities to a general class of algorithms known as evolutionary algorithms, and some comparisons can be made.
* Korhonen, J. M. & Hassi, L. (2009). Design Thinking Unpacked: An Evolutionary Algorithm. In Proceedings of the Eight European Academy of Design International Conference, 261-265. Aberdeen, UK.
Webinar: Design Sprint Process by Douglas FergusonSynerzip
In this webinar, Douglas will rapidly lead you through all five stages of the Design Sprint process, teaching how the various steps fit together and why and how they work. You’ll learn tips and tricks for facilitating a Design Sprint (whether it’s your first or 101st) and for incorporating these techniques into normal meetings.
There will be plenty of time for Q&A, so you can learn from Douglas’ experience running many Design Sprints with teams at Google and some of the world’s most exciting startups, from consumer to enterprise, from hardware to software, and in fields from healthcare to retail to robotics to agriculture.
Agile, Human-Centered Design and InnovationAgile Montréal
The conference will address design-thinking principles, discuss their implementation in an agile framework, leveraging specific artifacts and innovation practices in your organization.
Chloe Benaroya
Design Thinking explained with project experiences.
- What is Design Thinking
- What are the steps
- What is SAP Apphaus
- The Next View Design Experience Center Amsterdam
How did we sell DT, how did the workshops with clients and users, which methods work and which ones do not.
Examples of real projects: both successful and not very)
- What is DT and why everyone is talking about it
- Key DT elements
- How DT works in outsourcing
- How the theory differs in practice
- How to sell DT
- How a project with DT fails
IDEO - Field Guide To Human Centered Designprojectoxygen
n April 2015, IDEO.org launched an exciting new evolution of the HCD Toolkit the Field Guide to Human-Centered Design. The Field Guide is the latest in IDEO.org’s suite of teaching tools and a step forward in sharing the practice and promise of human-centered design with the social sector.
The main deliverable of Event 3 ("Decide") is a storyboard that would be subsequently used for prototyping the desired customer experience of pre-qualified customers. Before preparing a storyboard, however, the best conceptual solution (sketch) has to be selected and, if necessary, remixed with the best features of alternatives to produce an "ideal (strongest) solution." This presentation visually summarizes the required process while providing three case studies to facilitate understanding of the process of "Decide."
A design process is a systematic problem-solving strategy, with criteria and constraints, used to develop many possible solutions to solve or satisfy human needs or wants and to narrow down the possible solutions to one final choice.
This presentation came up from a discussion that
emerged in a ‘lean startup’ meet-up in San
Francisco 2 years ago. We had to choose a theme
for discussion and I proposed ‘Design Thinking’ VS
‘Lean Startup’. Rapidly my talk was the most voted
and the war began … the room split in 2 groups,
fighting to prove which methodology was the right
one...
After this , I decided to give a deeper study to the
matter ... Each methododology is great... Actually its
usage or mindset depends on different factors and
objectives. This presentation is the result of this
deeper study and some [personal] conclusions.
adelavillanueva.com Hope it helps. Enjoy!
Going from Good to Great with Concept TestingAtlassian
Running experiments in your product will tell you what your customers are doing, but they don't often tell you why they're doing it. So even after experimenting, you can be left wondering: which option would be better to ship? One way that Atlassian has tackled this is by taking the "concept testing" technique to a whole new level. Get a first-hand look into how we run concept tests to extract the right insights – before a single line of code has been written. You'll learn how they can work side-by-side with quantitative experimentation to help you get smarter metrics, and have greater confidence in knowing how to take your product from good to great.
The Design Sprints are a 2-5 days process for answering critical business questions through design, prototyping, and testing ideas with customers.
In this keynote I present you the Google Venture Design Sprints Methodology.
These slides were part of a 30 minute presentation. The focus was on creating common (design thinking) ground between design, marketing and sales people inside a company.
These slides include a bit about me but mostly function as a backdrop I refer to during my oral presentation.
I do not read my slides :-)
How Design Thinking works, or: Design Thinking Unpacked: an evolutionary algo...J. M. Korhonen
A presentation accompanying a paper* presented at EAD 2009 conference in Aberdeen, Scotland. We're trying to develop a theory why "design thinking" works in practice, and what may be its limits. The idea is that "design thinking" has similarities to a general class of algorithms known as evolutionary algorithms, and some comparisons can be made.
* Korhonen, J. M. & Hassi, L. (2009). Design Thinking Unpacked: An Evolutionary Algorithm. In Proceedings of the Eight European Academy of Design International Conference, 261-265. Aberdeen, UK.
Webinar: Design Sprint Process by Douglas FergusonSynerzip
In this webinar, Douglas will rapidly lead you through all five stages of the Design Sprint process, teaching how the various steps fit together and why and how they work. You’ll learn tips and tricks for facilitating a Design Sprint (whether it’s your first or 101st) and for incorporating these techniques into normal meetings.
There will be plenty of time for Q&A, so you can learn from Douglas’ experience running many Design Sprints with teams at Google and some of the world’s most exciting startups, from consumer to enterprise, from hardware to software, and in fields from healthcare to retail to robotics to agriculture.
Agile, Human-Centered Design and InnovationAgile Montréal
The conference will address design-thinking principles, discuss their implementation in an agile framework, leveraging specific artifacts and innovation practices in your organization.
Chloe Benaroya
Design Thinking explained with project experiences.
- What is Design Thinking
- What are the steps
- What is SAP Apphaus
- The Next View Design Experience Center Amsterdam
How did we sell DT, how did the workshops with clients and users, which methods work and which ones do not.
Examples of real projects: both successful and not very)
- What is DT and why everyone is talking about it
- Key DT elements
- How DT works in outsourcing
- How the theory differs in practice
- How to sell DT
- How a project with DT fails
IDEO - Field Guide To Human Centered Designprojectoxygen
n April 2015, IDEO.org launched an exciting new evolution of the HCD Toolkit the Field Guide to Human-Centered Design. The Field Guide is the latest in IDEO.org’s suite of teaching tools and a step forward in sharing the practice and promise of human-centered design with the social sector.
The main deliverable of Event 3 ("Decide") is a storyboard that would be subsequently used for prototyping the desired customer experience of pre-qualified customers. Before preparing a storyboard, however, the best conceptual solution (sketch) has to be selected and, if necessary, remixed with the best features of alternatives to produce an "ideal (strongest) solution." This presentation visually summarizes the required process while providing three case studies to facilitate understanding of the process of "Decide."
A design process is a systematic problem-solving strategy, with criteria and constraints, used to develop many possible solutions to solve or satisfy human needs or wants and to narrow down the possible solutions to one final choice.
This presentation came up from a discussion that
emerged in a ‘lean startup’ meet-up in San
Francisco 2 years ago. We had to choose a theme
for discussion and I proposed ‘Design Thinking’ VS
‘Lean Startup’. Rapidly my talk was the most voted
and the war began … the room split in 2 groups,
fighting to prove which methodology was the right
one...
After this , I decided to give a deeper study to the
matter ... Each methododology is great... Actually its
usage or mindset depends on different factors and
objectives. This presentation is the result of this
deeper study and some [personal] conclusions.
adelavillanueva.com Hope it helps. Enjoy!
Going from Good to Great with Concept TestingAtlassian
Running experiments in your product will tell you what your customers are doing, but they don't often tell you why they're doing it. So even after experimenting, you can be left wondering: which option would be better to ship? One way that Atlassian has tackled this is by taking the "concept testing" technique to a whole new level. Get a first-hand look into how we run concept tests to extract the right insights – before a single line of code has been written. You'll learn how they can work side-by-side with quantitative experimentation to help you get smarter metrics, and have greater confidence in knowing how to take your product from good to great.
7 Wonders of Engineering Design ProcessGOVINDYADAV56
Have Dreams Bigger Than The Universe? If Yes then come and Join #SDNx an Open Learning Platform That Is Designed To Provide Space Awareness Activities, Educational Programs, Research & Development Of Space Exploration Technologies And Major Space Industry Events To Serve The Global Space Community.
This is an outline for Corporate innovation and acceleration. We have used this to create a way for corporates to ingest technology and business practices that can scale their business thought leadership and help take them ahead of there competitors.
[Note: This is a partial preview. To download this presentation, visit:
https://www.oeconsulting.com.sg/training-presentations]
Design Thinking is 'outside the box' thinking. It allows everyone to use creative tools to address a vast range of challenges. The process is action-oriented, embraces simple mindset shifts and tackles problems from a new direction.
Some of the world's leading brands, such as Apple, Nike, Starbucks and GE have rapidly adopted the design thinking approach. What's more, design thinking is being taught at leading universities around the world, including Stanford, Harvard and MIT.
Design Thinking encourages organizations to focus on the people they are creating for, which leads to better products, services, and internal processes. The framework is fully compatible with analytical problem solving approaches.
This introductory presentation provides useful information for management and staff who are new to Design Thinking and are interested to learn more about its benefits and applications.
Learning Objectives
1. Gain knowledge on the key concepts of Design Thinking
2. Understand the mindsets and methodology of Design Thinking
3. Identify best practices and transforming your organization
Contents
1. Key Concepts of Design Thinking
2. Design Thinking Mindsets
2.1 Focus on Human Values
2.2 Show Don't Tell
2.3 Craft Clarity
2.4 Embrace Experimentation
2.5 Be Mindful of Process
2.6 Bias Toward Action
2.7 Radical Collaboration
3. Design Thinking Methodology
3.1 Empathize
3.2 Define
3.3 Ideate
3.4 Prototype
3.5 Test
4. Best Practices & Transforming Your Organization
To download the complete presentation, visit: https://www.oeconsulting.com.sg/training-presentations
The Design Mind: Design Thinking Strategies for Facilitating Growth and Perfo...Aggregage
Design thinking is at the root of creative success. Seriously! But do you know how to shift your mindset and creative process – as well as that of your team – to create and ideate in ways that are truly innovative? The most inspired and innovative teams and individual designers need to be a part of a culture that enables forward-thinking, acceleration, and efficiency. It’s a combination of creative, analytical, and collaborative approaches that produce results.
How to build a startup SLASSSCOM Talk Aug 2015Raomal Perera
An introduction on how to build a startup using lean techniques. The talk was hosted by SLASSCOM and sponsored by Virtusa, Regus Sri Lanka and Pick Me.
Do Tank - Visual Report for Introduction to Business Design Thinking (Santa M...Do Tank
On Wednesday 25th April 2018, against a backdrop of glorious Santa Monica sunshine, a delightful collection of like-minded business people gathered to experience a 1 day public Learning Lab from Do Tank – “An introduction to Business Design Thinking”. Expert Dojo was our amazing host as we took full advantage of their inspiring space. This Visual Report offers a snapshot of the essence of the day for us to look back on.
Dee Scarano - Creating Better Products, Faster with Design Sprintsnois3
Speech of Dee Scarano, Product designer and lead Design sprint for AJ&Smart, at World Usability Day Rome 2018. An introduction of Design Sprint methodology.
Startup Secrets presents a lecture on how to build a compelling value proposition. Learn about stories, the information necessary, and the questions to ask yourself about how to show people you're worth the money!
Building Winning Business, the Human-Centered wayLamin Mansaray
Business problems come in all shapes and sizes, the complexity of those issues are only growing. Human Centered Design (Design Thinking) is the best-kept problem-solving approach to adaptive challenges.
TOP 10 B TECH COLLEGES IN JAIPUR 2024.pptxnikitacareer3
Looking for the best engineering colleges in Jaipur for 2024?
Check out our list of the top 10 B.Tech colleges to help you make the right choice for your future career!
1) MNIT
2) MANIPAL UNIV
3) LNMIIT
4) NIMS UNIV
5) JECRC
6) VIVEKANANDA GLOBAL UNIV
7) BIT JAIPUR
8) APEX UNIV
9) AMITY UNIV.
10) JNU
TO KNOW MORE ABOUT COLLEGES, FEES AND PLACEMENT, WATCH THE FULL VIDEO GIVEN BELOW ON "TOP 10 B TECH COLLEGES IN JAIPUR"
https://www.youtube.com/watch?v=vSNje0MBh7g
VISIT CAREER MANTRA PORTAL TO KNOW MORE ABOUT COLLEGES/UNIVERSITITES in Jaipur:
https://careermantra.net/colleges/3378/Jaipur/b-tech
Get all the information you need to plan your next steps in your medical career with Career Mantra!
https://careermantra.net/
HEAP SORT ILLUSTRATED WITH HEAPIFY, BUILD HEAP FOR DYNAMIC ARRAYS.
Heap sort is a comparison-based sorting technique based on Binary Heap data structure. It is similar to the selection sort where we first find the minimum element and place the minimum element at the beginning. Repeat the same process for the remaining elements.
Understanding Inductive Bias in Machine LearningSUTEJAS
This presentation explores the concept of inductive bias in machine learning. It explains how algorithms come with built-in assumptions and preferences that guide the learning process. You'll learn about the different types of inductive bias and how they can impact the performance and generalizability of machine learning models.
The presentation also covers the positive and negative aspects of inductive bias, along with strategies for mitigating potential drawbacks. We'll explore examples of how bias manifests in algorithms like neural networks and decision trees.
By understanding inductive bias, you can gain valuable insights into how machine learning models work and make informed decisions when building and deploying them.
NUMERICAL SIMULATIONS OF HEAT AND MASS TRANSFER IN CONDENSING HEAT EXCHANGERS...ssuser7dcef0
Power plants release a large amount of water vapor into the
atmosphere through the stack. The flue gas can be a potential
source for obtaining much needed cooling water for a power
plant. If a power plant could recover and reuse a portion of this
moisture, it could reduce its total cooling water intake
requirement. One of the most practical way to recover water
from flue gas is to use a condensing heat exchanger. The power
plant could also recover latent heat due to condensation as well
as sensible heat due to lowering the flue gas exit temperature.
Additionally, harmful acids released from the stack can be
reduced in a condensing heat exchanger by acid condensation. reduced in a condensing heat exchanger by acid condensation.
Condensation of vapors in flue gas is a complicated
phenomenon since heat and mass transfer of water vapor and
various acids simultaneously occur in the presence of noncondensable
gases such as nitrogen and oxygen. Design of a
condenser depends on the knowledge and understanding of the
heat and mass transfer processes. A computer program for
numerical simulations of water (H2O) and sulfuric acid (H2SO4)
condensation in a flue gas condensing heat exchanger was
developed using MATLAB. Governing equations based on
mass and energy balances for the system were derived to
predict variables such as flue gas exit temperature, cooling
water outlet temperature, mole fraction and condensation rates
of water and sulfuric acid vapors. The equations were solved
using an iterative solution technique with calculations of heat
and mass transfer coefficients and physical properties.
6th International Conference on Machine Learning & Applications (CMLA 2024)ClaraZara1
6th International Conference on Machine Learning & Applications (CMLA 2024) will provide an excellent international forum for sharing knowledge and results in theory, methodology and applications of on Machine Learning & Applications.
ACEP Magazine edition 4th launched on 05.06.2024Rahul
This document provides information about the third edition of the magazine "Sthapatya" published by the Association of Civil Engineers (Practicing) Aurangabad. It includes messages from current and past presidents of ACEP, memories and photos from past ACEP events, information on life time achievement awards given by ACEP, and a technical article on concrete maintenance, repairs and strengthening. The document highlights activities of ACEP and provides a technical educational article for members.
2. Whilewearewaiting…
Thinkof a product or service outside of your firm thatyou’d
consider to be a “failure”
Think of a project or product within your company that you’d
consider to be a “failure”
What made them failures in your mind?
Could failurehave been prevented by different or better
engineering or design?
DESIGN CONCEPTS, INC. 2
3. T E R R I B L E , W O N D E R F U L
DESIGN CONCEPTS, INC. 3
4. The role of in innovation
DESIGN CONCEPTS, INC. 4
14. Strategic planning Conceptual design Engineering or
development
Manufacturing /
deployment
Following product
launch
All “Failure”is NotCreated Equal
DESIGN CONCEPTS, INC. 14
15. The Cost Of “Failure”
DESIGN CONCEPTS, INC. 15
Strategic planning Conceptual design Engineering or
development
Manufacturing /
deployment
Following product
launch
16. DESIGN CONCEPTS, INC. 16
Groupcontemplation:
When in the development cycle do you thinkit
should have been apparent that it wasn’t going to be
a success?
18. Oddsof failurevary with the project type
New-to-world innovation
(New User Needs, New business model or New technology
New-to-company innovation
(Entering anew market ora new technology foryour firm)
Major redesign of an existingproduct or service
Facelift / update of existing product or service
HigherRisk
of Failure
Lower Risk
of Failure
DESIGN CONCEPTS, INC. 18
19. DESIGN CONCEPTS, INC. 19
Groupcontemplation:
Was the failure (partially) explainedby the degree of
innovation reach?
32. “But the most significantresult of 'new Coke' by
far was that it sent anincredibly powerful signal...
a signalthat we really were ready to do whatever
was necessary to build value for the owners of our
business.”
--Roberto Goizueta -CEO
DESIGN CONCEPTS, INC. 32
33. “Yes, it infuriated the public, cost a ton of money
and lasted only 77 days before we reintroduced
Coca-Cola Classic.Still, New Coke wasa success
because it revitalized the brand and reattached the
public to Coke.”
-SergioZyman,Coca-Colahead
ofmarketing
DESIGN CONCEPTS, INC. 33
34. DESIGN CONCEPTS, INC. 34
Groupcontemplation:
Do you think there were ultimately benefits to the
company generated from this “failure”?
37. Toyota Prius –1st Generation
1997 - 2000
Battery Bus Recall
Electronic Power Steering Rack Recall
EPS Control UnitRecall
HV Transaxle Failures
Motor/Generator Failures
Master IndicatorWarning (engine fails to start)
Electronic Throttle Body Sticking
Gas Pedal Position Sensor Bad
Sales – 30,000units / year
Toyota Prius –4th Generation
2015-Present
Sales – 725,000units /year
DESIGN CONCEPTS, INC. 37
41. From:…….<……@gmail.com>
Sent:Friday,July 5,20193:37PM
To:DaveFranchinoSubject:RE:[design] The roleoffailureplaysin innovation
/rant_mode_on
Oh god, you hit a nerve. Coming from XXXXX talkingabout failure
gives me hives. XXXXX talksa brave game, repeatedly and publicly, but
internally stillsubtly punishes people for failing, allwhile saying they
celebrate it.
/rant_mode_off
DESIGN CONCEPTS, INC. 41
42. 6 Phases of a Project
1. Enthusiasm
2. Disillusionment
3. Panic
4. Search for the guilty
5. Punishment of the innocent
6. Praise and honors for the non-participants
DESIGN CONCEPTS, INC. 42
43. DESIGN CONCEPTS, INC. 43
Groupcontemplation:
To what extent do you thinkthe internalculture
impacted the ultimate failure of this product – or the
inability to learn the most from it?
48. Failure ModeEffects Analysis
DESIGN CONCEPTS, INC. 48
Severity if FailureOccurs
X
Probability of Failure Occurring
X
Likelihoodof Escaping Detection
=
Risk Priority Number
49. 1. Acknowledge
2. Frontload
3. Align expectation
4. Patience, perseverance and pivots
5. Design Spirals
6. Fight the hottest fire
7. Parallel path
8. Killthe Zombies
9. Learn
DESIGN CONCEPTS, INC. 49
50. The Cost Of “Failure”
DESIGN CONCEPTS, INC. 50
Strategic planning Conceptual design Engineering or
development
Manufacturing /
deployment
Following product
launch
51. Desired pointof “Failure”
DESIGN CONCEPTS, INC. 51
Strategic planning Conceptual design Engineering or
development
Manufacturing /
deployment
Following product
launch
52. All “Failure”is NotCreated Equal
DESIGN CONCEPTS, INC. 52
Strategic planning Conceptual design Engineering or
development
Manufacturing /
deployment
Following product
launch
Encourage Expect Tolerate Avoid Shun
Project Failure Product
Failure!
53. 1. Acknowledge
2. Frontload
3. Align expectation
4. Patience, perseverance and pivots
5. Design Spirals
6. Fight the hottest fire
7. Parallel path
8. Killthe Zombies
9. Learn
DESIGN CONCEPTS, INC. 53
54. Calibrateplansandexpectationswiththe project type
New-to-world innovation
(New User Needs, New business model or New technology
New-to-company innovation
(Entering anew market ora new technology foryour firm)
Major redesign of an existingproduct or service
Facelift or model update of existing product or service
HigherTolerance
of Failure
Lower Tolerance
of Failure
DESIGN CONCEPTS, INC. 54
65. 1. Acknowledge
2. Frontload
3. Align expectation
4. Patience, perseverance and pivots
5. Design Spirals
6. Fight the hottest fire
7. Parallel path
8. Killthe Zombies
9. Learn
DESIGN CONCEPTS, INC. 65
66. DESIGN CONCEPTS, INC. 66
The Post-Mortem
What went right and deserves to be celebrated?
What went wrong?
What did we learn thatcan make us better?
What are the positives for our firm?
Etc.
67. 1. Acknowledge
2. Frontload
3. Align expectation
4. Patience, perseverance and pivots
5. Design Spirals
6. Fight the hottest fire
7. Parallel path
8. Killthe Zombies
9. Learn
DESIGN CONCEPTS, INC. 67
68. Go forth and Fail!
(elegantly,appropriately and early and on a limited basis)
DESIGN CONCEPTS, INC. 68
I think this it the first of our after-hours events that I’ve personally hosted and I’m trying hard not to draw conclusions from the fact that the team asked me to speak to the topic of failure. It’s true that I’ve been at this a pretty long time – and accordingly I’ve got my fair share – and some would say more than my fair share of failures to draw on. But it is true that I’ve spent a lot of time thinking about the role of failure in innovation – and it’s actually sort of a fun honor to be part of a discussion on this sensitive, important topic.
I happen to be an engineer – and I teach a class in product design at UW Madison and some time ago I noticed an engineer proudly rocking this t-shirt. I get what it’s trying to convey – it ties into the pride sense of responsibility many engineers feel when they view their craft.
But honestly, if you think about it, it’s a bit ironic. Because the reality is that history is absolutely littered with some pretty dramatic and spectacular examples of engineering failure – extending back as long as mankind has been trying to invent new things.
And it’s not like we’re really getting any better at it. We learn more and more from each passing generation, Our tools have become more sophisticated. We have the wisdom of previous failures to build on. And yet, we still seem to find ways to fail spectacularly and regularly.
And the dramatic, headline grabbing, sometime tragic failures like these are really just the tip of the iceberg. The vast majority of failures are far less public but still leave their mark. They’re products that just don’t work well – cause frustration or disappointment and get cast aside, or products that work as intended but never sell. Or products that can’t quite sustain a business and never make any money. And the products that make it into the marketplace are just a small fraction of the failed projects that consume remarkable amounts of time, money and resources to never see the light of day or make it onto a shelf.
There are really no accurate statistics on product failures – A Harvard study a while ago estimated that between 80-95% of all products introduced into the market fail. this is an old slide but I suspect its directionally illustrative. And the most interesting and jaw dropping statistic on this slide is that about half of all the resources, time and money allocated to development ends up being spent on failed products.
In some aspects, the failure rates we tolerate on new product development are sort of mind boggling. We don’t expect or tolerate those in any other aspect of commerce. I mean, if you and your spouse decide you’re going to build a new house, how would you react to a builder telling you – well the cost is going to be $200,000. And by the way, there’s an 80% chance when we’re done you won’t be able to live in it. We’d never tolerate that. When we launch a new web site, decide to build a new factory, finance a new purchase, there’s a reasonable expectation that they may not achieve all our aspirations but there’s not an 80% chance of complete failure. When those activities are done we rightfully assume we’re sort of going to have what we expected.
So obviously, the reason for these failure rates lies in our insatiable desire for the innovative and new. Innovation improves our lives, it drives our businesses and it separates us from our competition. But the this striving for innovation inherently implies taking risk. And the very definition of risk is something that might end in failure. So Innovation, Risk and Failure are intractably linked and frankly always will be. And any effort to eliminate risk and failure from new product development is a fool’s errand.
A true story – I sit on a board with a sr. manager at a large equipment company you would all recognize. And some time ago we were out to diner and he was bragging that he had never in his career undertaken a project that didn’t go to market. And I found myself biting my tongue. Because there’s no possible way you can be driving your business forward in an intensely competitive environment without some level of controlled failure. And I challenge you to pick absolutely any company you admire – including your own, and I’m positive that you’re going to find a fair degree of failure littered in their past.
Part of this can be explained by the sheer number of things that have to go perfectly right to succeed in new product development and innovation. It’s perhaps the only activity a corporation undertakes that requires the integrated collaboration of just about aspect of the firm from strategic planning, finance, accounting, legal, engineering, manufacturing, distribution, sales.
And aside from the inherently cross discipline collaboration required for most highly integrated products or services a lot of things need to fall into place perfectly. If you consider that you were likely to be successful ¾ of the time on each of these isolated activities – when you combine them the cumulative probability of something being the weak link the chain helps explain why so many projects are doomed to fail.
So all this is interesting and perhaps somewhat intuitive – but not particularly actionable. I guess you could all go back to your bosses and tell them you went to a presentation on the role of failure in new product development and I told you it was inevitable so just deal with it. But I suspect that might not go all that well.
So let’s spend a bit of time trying to develop some context around failure and then talk about ways you can increase your chances for success and minimize the impacts of the failures that do occur. And let’s start with the “when” of failure.
Which is basically an observation that all failure is not created equal. A reasonable development process at your company might start with strategic planning, developing a business case, determining a user need – progress from considering different concepts into engineering programming development and then get deployed into the market.
Each one of these activities represents an area of risk and a possibility for failure. Although I might start by arguing that it’s actually a misnomer to call them failures when projects are truncated early in the process. And another intuitive observation is that the sunken costs of failure rise – fairly dramatically as you move through the process. Early on, when you’re doing strategic planning and conceptual design, the costs committed to projects in terms of people, time and money can actually be pretty insignificant. So intuitively, you want to drive or tolerate failure as early in the process as possible.
Turning back to the failed products you thought earlier, spend just a couple of minutes contemplating – with the benefit of hindsight – when in the development process do you think it might have become apparent that the product wasn’t going to be successful. And although we don’t have the benefit of hindsight in our own projects – when you think about some of the more dramatic, public and tragic failures of recent and distant history – there are often some pretty significant markers that were missed and flat-out ingored during the development process.
Beyond the when, it’s also worth considering the “what” of failure -
And by that I mean recognizing the realization that all innovation isn’t equally ambitious. And it stands to reason that the further your company is “reaching” from it’s current products and services, the higher the risk of failure. Ground-breaking – new to world technologies, emerging or previously unmet user needs or brand new business models carry a much higher threshold of risk and higher development failures. Conversely, if you’re introducing Version 4.5 of an existing product that represents a facelift or a modest update, there should be a much higher expectation of success – back to that house you and your spouse are building. There should be plenty of organization experience and muscle memory that make this a much more likely endeavor.
So spend a bit of time contemplating the failed products you identified – and consider whether the failure could at least be partially explained by the degree of innovation reach undertaken. Not always certainly.
Finally, there is the “why” of failure. Because products fail for a really broad range of reasons.
But one pretty useful taxonomy for deconstructing failure is shown in this nifty graphic. Which seeks to illustrate that to be successful a product has to achieve three broad aims. At it’s core – it has to be desirable. That means it needs to meet a need in the marketplace and be valued and desired by your customers. Stereotypically, this is the prevue of the marketing team although I’ll argue in a different after-hours event that it’s the responsibility of everyone who engages in innovation. Beyond that however, the product need to be feasible –often this is the bailiwick of the engineers. By feasible I mean it needs to work as intended and expected. It needs to be safe, reliable, conform to applicable standards and deliver the features and functions expected in a dependable and delightful manner. And then finally, for a product to be a success in the market it needs to be viable – and by this I mean it needs to create a sustainable business for you. You need to be able to manufacturing, distribute and price the product or service in way that covers your costs and leaves some left over for that most capitalistic of endeavors –the profit margin. And each one of these three areas represents a distinct venue for product risk and failure.
Consider desirability. The Segway, google glass and the nike fuel band are perhaps examples of products that delivered on the expected features and function in a reasonably cost-effective manner – but simply didn’t create enough user value to justify their existence.
Accordingly, the fairly recent and fairly spectacular failure of Munchery, the online food ordering and meal delivery service that managed to burn through $125mm in venture funding as well as the Jawbone fitness tracker and my beloved General Motors EV-1 are all examples of innovation that actually created a pretty loyal and devoted following – but weren’t able to tip over into a sustainable business money.
As a bit of an automobile nut, I fear for tesla in this regard but that’s a topic for another talk.
And then finally, there are the spectacular technical flame-outs. As an engineer, these are the ones that give us night-sweats. Where when all is said and done , in spite of all our sophisticated tools and best efforts, the product simply doesn’t work as intended or desired
So spend a bit of time thinking about your failed product and project. Why do you think it failed primarily – was it because it didn’t’ meet a customer need? It couldn’t justify or sustain the business? It didn’t work technical?
So although I’ve postulated that failure is an inevitable part of innovation, that doesn’t mean that any particular product is intrinsically headed for failure from the onset. Sometimes products start out fine and get screwed up down the road.
Consider the case of the much beleaguered Pontiac Aztek The current poster child for a failed car. Immortalized by Walter White of breaking bad fame and perhaps one of the most loathed cars in recent history. And if I do say so myself, that is one really ugly car.
But what most people forget is that the GM was essentially pressed into executing the Aztek by the wildly successful Aztec concept car introduced at the 1999 Detroit auto show. Pre-dating the Honda Element and Scion XB, the Aztec lead the pack as a concept for a funky, utilitarian sports minded cross over. Although this image is now 20 years old, the original Aztek concept car looked really freakin’ cool. And then us engineers completely screwed it up.
So consider again your failed product. What are the chances that the basic concept was sound and it was just poorly executed.
We have a visceral fascination with the concept of failure. I think the German phrase Schadenfreude – taking delight in other’s pain really does apply here. Whether it’s Thearnos, or Boeing or Juiceroo we love to pile on the misery of others.
But sometimes the real truth behind the failure isn’t quite as devastating as our public perception. Consider the cast of New Coke – perhaps the most compelling failure story in modern commerce. Some of you younger folks might not recall that new coke was a reformulation of the iconic brand, driven by dropping market share in the mid early 90’s
It’s been argued that new coke was the most thoroughly market-tested product in modern history and the product was uniformly preferred to existing coke and it’s rival Pepsi in blind taste tests. And yet when new coke was introduced, it was a colossal, embarrassing and remarkable expensive failure. Lasting only 77 days on the market.
And yet, if coke is to be believed, there are many aspects of the new coke experiment that were a resounding success for the company.
It’s even been speculated – although denied – that new coke was simply a marketing ploy to drive interest in the coke brand.
Finally, while failure might be an intrinsic part of the innovation process, sometimes it’s a really effective stepping stone to much greater future success.
Consider for example, the failed Apple Lisa – many parts of which when on the inspire the remarkably successful, iconic and groundbreaking Apple Macintosh.
In another automotive example, consider the original Toyota Prius. The first-generation Prius back in 1997 took some bold technological steps – and suffered from some pretty dramatic teething pains. And it only sold a fairly paltry 30,000 unit. But Toyota has a great track record of playing the “long game” and stuck with it to create what might be one of the most beloved, dependable and successful small cars in modern history.
Compare that if you will to the GM EV-1. driven by California fuel mandates and the pending gas crisis, the EV1 , introduced in 1996 actually had a very favorable reception. But GM believed electric cars were doomed as an unprofitable niche and balled the whole thing up – literally – in 1999.
So imagine what would happen if GM had stuck with the EV 1 with a 10 year head start on Tesla. And what the EV7 might look like today. We’ll never know.
None of these failures exist in a vacuum and none of them were developed in a test tube. They’re all the results of efforts in dynamic, complex and flawed corporate cultures – like yours – each subject to imperfect information, market and cost pressures,
And one of the biggest contributors to a culture of innovation is how a culture deals with failure. And that certainly spans the gamut.
When I was preparing for this talk, I sent a quick note out to some former classmates and friends on the Stanford University list-serve asking for input on how various companies deal with failure – and I got this screaming rant back from a former employee of a very noted technology company you would all recognize. As you can see, here is one pretty cynical perspective.
And I suspect when it come to product and project failure, all of you
So we’ve talked a fair amount about types, reasons and the context of failure. And we’ve described it as an inevitable, healthy and sometimes even positive part of the innovation process. But all is not lost here. There are things we can do that increase our odds of success, reduce the cost and impact and ensure that failure is minimized and sequestered to the greatest extent possible.
So let’s review
The first of these is basically what we’ve been doing throughout this entire presentation. To have a frank, candid, honest and realistic discussion about risk and the possibility of failure. And I’m sort of amazed how many companies the concept of risk or failure is taboo. And whether or not you want to call it wargaming, scenario planning, worst case, common sense or just plain realism, encouraging dialogues about risk and failure is a really critical part of the process.
The engineers in the room have a wonderful process they use for formally assessing risk – called an FMEA – or failure Mode effects analysis. In spite of the fancy name but it’s actually quick simple.
It involves a group of engineers sitting in a room and basically trying to think of all the ways things can go pear shaped.
Beyond this though, the FMEA actually asks the engineers to rank failure in three different areas;
On a scale of one to 10
So, while the engineers use this as a structured methodology for assessing design or process risk – we’ve noticed it works really effectively for just about any aspect of the development process. For the strategic plan – for conceptualization – for manufacturing, pricing and distribution.
Whether you use this particular tool or not, baking in formal discussions on risk into your process and talking about failure modes and mitigations is a really powerful tool.
The next technique is to frontload failures into the early part of the process.
Each one of these activities represents an area of risk and a possibility for failure. Although I might start by arguing that it’s actually a misnomer to call them failures when projects are truncated early in the process. And another intuitive observation is that the sunken costs of failure rise – fairly dramatically as you move through the process. Early on, when you’re doing strategic planning and conceptual design, the costs committed to projects in terms of people, time and money can actually be pretty insignificant. So intuitively, you want to drive or tolerate failure as early in the process as possible.
Because like we mentioned the costs of failure rise dramatically down the road. So it stands to reason that failing earlier will conserve precious resources.
So like to say that failure should be encouraged during strategic planning.
Next as we mention – and perhaps closely tied into acknowledging risk – is to recognize that the probability of failure increase with the more innovative you’re trying to be. So taking the time and an organization to asses your appetite for risk and make sure you honestly don’t bite off more than you are willing to chew is another technique of mature companies.
We talked earlier about all the innovation that could have been – had the company simply been willing to preserve. And while being willing to kill deeply flawed projects is a characrteristic of winning companies, likewise, recognizing that your first effort is seldom likely to be your best or be optimized. A development plan that candidly recognizes the potential for warts, flaws and misteps in the initial lauch – think in terms of Lean Start-ups MVP can be a very powerful tool.
Think what might have happened if GM had cosndiered the EV 1 to be the first step in a multi phase journey.
Whenever we talk about failure there is going to be a lot of talk about rapid prototyping, iteration
But I actually think a better metaphor is the spiral – where there are a series of design/test/protoype iterations that all progressively move you closer and closer to a final product. Whenever I see a development plan that moves right from a first protoype into production – or worse yet – skips the prototype entirely – I am deeply skeptical and worried. So make sure your development plans include progressive iterative spirals toward an optimized target.
We talked earlier about the different ways that product can fail.
Another prudent technique – with some caveats – is to formally decide what aspects of your innovation require a parallel path. By parallel path, I mean an alternative, less risky approach or fall-back that’s co-developed in conjunction with highly risky aspects of the design. Now clearly these consume costs and resources but often time the cost and time of a parallel path easly offsets the risk of failing an aspect of your product that has no contingency.
One dirty corporate secret that I wanted to bring to light is the zombie project. By that I mean the project that’s clearly dead but for some reason still consuming precious time, money and resources. It’s often some sr. manager’s pet project – or there is a department or staff member puttering away in a back room that nobody want’s to offend. There is never enough support to bring them into the market but conversely, there isn’t enough momentum to kill them. The best companies ferret out the zombie projects.
And finally, perhaps the most important tool of all is a willingness and appetite to learn as much as you possibly can from every failure. The recognition that innovation is a really difficult, messy and risky business where some degree of sub-optimal results are going to occur. Failure is expensive. It’s painful. It can be embarrassing because we all have professional pride.
The Post-Mortem - What went right and deserves to be celebrated?
What went wrong?
What did we learn that can make us better?
What are the positives for our firm?