Copyright © 2005 Rochester Institute of Technology

Slides:



Advertisements
Similar presentations
Identifying Customer Needs
Advertisements

Using QFD to Establish Design Specifications
User-Centered Design: From Concept to Product Peter Merholz peterme
Components of a Product Vision/Strategy
Product Design and Development. A Generic Development Process Concept developmen t System design Detail design Testing and refinement Production ramp.
EDGE™ Needs Assessment prepared by Prof. Marcos Esterman (ISE) Copyright © 2005 Rochester Institute of Technology All rights reserved.
Analysis Concepts and Principles
Lecture 4— Capturing the Voice of the Customer Or Marketing 101
Objective Trees and Customer Needs Statements
Chapter 4 Requirements Engineering
Identifying Customer Needs
Identifying Customer Needs
Identifying Customer Needs
1 Rev: 02/12/2007 MSE-415: B. Hawrylo MSE-415: Product Design Lecture #3 Chapter 4 Identifying Customer Needs.
Identifying Customer Needs
Teaching materials to accompany:
What is a Business Analyst? A Business Analyst is someone who works as a liaison among stakeholders in order to elicit, analyze, communicate and validate.
Marcos Esterman, Associate Professor Industrial and Systems Engineering Department Rochester Institute of Technology Multidisciplinary.
Copyright  2007 McGraw-Hill Pty Ltd PPTs t/a Marketing Research 2e by Hair, Lukas, Bush and Ortinau Slides prepared by Judy Rex 1-1 Chapter One Overview.
Marcos Esterman, Associate Professor Industrial and Systems Engineering Department Rochester Institute of Technology Multidisciplinary.
Search Engine Optimization © HiTech Institute. All rights reserved. Slide 1 What is Solution Assessment & Validation?
Chapter 6: THE EIGHT STEP PROCESS FOCUS: This chapter provides a description of the application of customer-driven project management.
R. I. T Mechanical Engineering Design Project Management Voice of the Customer: Interviews and Observations Rochester Institute of Technology Mechanical.
Identifying Customer Needs
Marcos Esterman, Associate Professor Industrial and Systems Engineering Department Rochester Institute of Technology Multidisciplinary.
Chapter 4: Identifying Customer Needs Product Design and Development Fourth Edition by Karl T. Ulrich and Steven D. Eppinger.
CHAPTER 2 SYSTEM PLANNING DFC4013 System Analysis & Design.
4 Chapter 4: Beginning the Analysis: Investigating System Requirements Systems Analysis and Design in a Changing World, 3 rd Edition.
Investigating System Requirements
Bell Ringer List five reasons why you think that some new businesses have almost immediate success while others fail miserably.
PowerPoint to accompany:
GKR 2113: INTRODUCTION TO DESIGN PROCESS
Customer Insights Group 3 - Cell Phone
Stakeholder consultations
Fundamentals of Information Systems, Sixth Edition
Imran Hussain University of Management and Technology (UMT)
SAMPLE Develop a Comprehensive Competency Framework
Benchmarking.
Concept Level Project Plan P08008 – ArcWorks Process Improvement
SDLC: System Development Life Cycle
SEM II : Marketing Research
IENG 451 / 452 Voice of the Customer: Analysis (KANO, CTQ)
Systems Analysis and Design in a Changing World, 6th Edition
The design process Software engineering and the design process for interactive systems Standards and guidelines as design rules Usability engineering.
The design process Software engineering and the design process for interactive systems Standards and guidelines as design rules Usability engineering.
PRODUCT PLANNING.
Design Process Overview
Expanding Product Accessibility with Primary Market Research Techniques Jennifer L Flagg Center on Knowledge Translation for Technology Transfer, University.
Project Audit and Closure
Quality Function Deployment
Requirements Analysis
Design Process Overview
MINGGU KE 9: PROSES DESAIN PRODUK BARU
Market Research.
Understanding and Planning Business Reports and Proposals
Design Process Overview
Design Process Overview
Gathering Requirements
Anatomy of a Project A project has a beginning and an end.
User Studies Basic principles, methods, and examples
Design Process Overview
MGT601 SME MANAGEMENT.
Design Process Overview
Chapter 11 Quality Function Deployment (QFD)
THE PROCESS OF INTERACTION DESIGN
Where We Are Now 14–2. Where We Are Now 14–2 Major Tasks of Project Closure Evaluate if the project delivered the expected benefits to all stakeholders.
Project Audit and Closure
Identifying Customer Needs
CUSTOMER SATISFACTION
Lesson 3.2 Product Planning
Presentation transcript:

Copyright © 2005 Rochester Institute of Technology Needs Assessment prepared by Prof. Marcos Esterman (ISE) Copyright © 2005 Rochester Institute of Technology All rights reserved.

Goals of Needs Identification Provide basis for PD decisions Elicit needs that may not be so obvious Provide basis for engineering metrics Ensure critical needs are elicited Develop a common understanding of the needs Archiving of needs Ulrich,K.T. and S. Eppinger, Product Design and Development, Third Edition, 2004

Steps in Identifying Customer Needs Gather the raw data Interpret the raw data Organize the needs Establish relative importance of needs Sanity Check! Ulrich,K.T. and S. Eppinger, Product Design and Development, Third Edition, 2004

Pre-conditions: A Project Exists! Mission Statement: Screwdriver Project Product Description A Handheld, power-assisted device for installing threaded fasteners Key Business Goals Q4 ’06 Product Introduction 50% Gross Margin 10% Market Share by ‘08 Primary Market Do-it-yourself consumer Secondary Markets Casual consumer Light-duty professional Assumptions Hand-held Power-assisted Nickel-Metal-Hydride battery Stakeholders User Retailer Sales Force Service Center Production Legal Dept.

Methods for Gathering Raw Data Brainstorming Method best suited for your projects Interviews 1-on-1 Dialog Directly w/Company personnel Focus Groups 8-12 People (Typically Paid) Moderator Company personnel observe group Observing the Product in Use Direct Observation (Contextual Inquiry) Virtual Observation Use Cases Task Oriented Simulate and document the steps to accomplish the task Ulrich,K.T. and S. Eppinger, Product Design and Development, Third Edition, 2004

Affinity Diagram: KJ Method Structured brainstorming and analysis Developed by Prof. Jiro Kawakita (U. Of Kyoto) Basic steps Collect narrative data and compile into cards Sort and label cards (clustering) Develop the KJ diagram and present to team Ishii, K.,“Introduction to Design for Manufacturability (DFM)", ME317A dfM: Product Definition, Stanford University, Lecture 1/7/2004 Copyright © 2007 Rochester Institute of Technology All rights reserved.

Hair Dryer Example Ishii, K.,“Introduction to Design for Manufacturability (DFM)", ME317A dfM: Product Definition, Stanford University, Lecture 1/7/2004

KAWAKITA Jiro (KJ) Method First come up with anything... Colorful Dries Fast Quiet Operating Cost Easy to Hold Portable Reliable Good Style Easy to Use Safe Long Lasting Fan Motor Weight Heater Control Switch Handle Heat Grip Airflow Casing Ishii, K.,“Introduction to Design for Manufacturability (DFM)", ME317A dfM: Product Definition, Stanford University, Lecture 1/7/2004 Copyright © 2007 Rochester Institute of Technology All rights reserved.

Then Sort and Cluster... Functional Ergonomic Esthetic Colorful Dries Fast Quiet Operating Cost Easy to Hold Portable Easy to Use Good Style Reliable Long Lasting Safe Fan Motor Weight Heater Control Switch Handle Heat Grip Airflow Casing Product Characteristic Structural Attribute Ishii, K.,“Introduction to Design for Manufacturability (DFM)", ME317A dfM: Product Definition, Stanford University, Lecture 1/7/2004 Copyright © 2007 Rochester Institute of Technology All rights reserved.

Choosing Customers Sample Size Always gather from end user Ulrich & Eppinger Recommend, 10 < n < 50 Always gather from end user Don’t forget other key customers/stakeholders from CVCA Know your market space & sample appropriately* Level of abstraction of the need Nokia 9300?, Nokia Phones?, Cell Phones?, Voice Communication?, Communication? Type of User Lead?, Satisfied?, Dissatisfied?, Former?, Customers Never Had *Burchill, G., Concept Engineering: an Investigation of Time vs. Market Orientation in Product Concept development. Massachusetts Institute of Technology Ph.D. Thesis, 1993.

What is a Lead User? (Eric Von Hippel is a much cited author in this area) Innovators: a couple of percent Early adoptors: 10-15 % Early Majority: ~1/3 Late Majority: ~1/3 Laggards: the rest Note: life cycle model says basis of competition changes from early adopters to laggards Early Need Users Early Majority Late Majority Laggards Time LEAD USERS Burchill, G., Brodie, C., Voices into Choices: Acting on the Voice of the Customer. Center for Quality Management, 1997. pg. 54 Copyright © 2007 Rochester Institute of Technology All rights reserved.

Lead User Characteristics Big need for capability of your product Their needs foreshadow the market Have extended current product beyond their intended limits They often have solutions Conceptualized or Implemented Burchill, G., Brodie, C., Voices into Choices: Acting on the Voice of the Customer. Center for Quality Management, 1997. pg. 54

Eliciting Customer Needs Prepare an interview guide Elicit dialog on a particular task or problem Have them walk through a specific instance Don’t ask them to generalize! Better yet, have them show you Go with the flow Use visual stimuli and props Avoid leading questions Avoid yes/no questions Be prepared for latent needs Focus on the customer pain What’s the underlying problem that needs to be solved Document, Document, Document HP Example

Contextual Inquiry Needs expressed in action Observe customer using products in normal context Allows the team to better Support, Extend, and Transform customers’ activities Important aspect of context Location People Culture Values Clausing, D., Total Quality Development,: A Step-By-Step Guide to World Class Concurrent Engineering, ASME Press, NY 1994, pp. 116- 117

Levels of Contextual Awareness Interviews site interview phone call to customer High Process Participation field service calls Intervention with User human performance lab Participant Observation field observations Low Far Distance from User Environment Close Burchill, G., Concept Engineering: an Investigation of Time vs. Market Orientation in Product Concept development. Massachusetts Institute of Technology Ph.D. Thesis, 1993. Pictorial Representation from K. Ishii. Copyright © 2007 Rochester Institute of Technology All rights reserved.

Sources of Existing Data External Sources Customer Complaints Technical Specifications Market Research Reports Customer Surveys Customer Profiles Industry Benchmarking Studies Competitor Assessments Journals Internal Sources Benchmarking Studies Company Policies Employees Surveys Suggestion Systems Customer Profiles Internal Publications Burchill, G., Brodie, C., Voices into Choices: Acting on the Voice of the Customer. Center for Quality Management, 1997. pg. 42

Developing Needs Statements: Guidelines for Interpreting the Data Understand the value proposition Your product is solving some problems What are they? What value do you allow your customer to deliver? Stay close to the customer language What, not how Specificity equal to the raw data Positive, not negative Product Attribute Avoid “must” & “should” Ulrich,K.T. and S. Eppinger, Product Design and Development, Third Edition, 2004

Need Statements Guidelines (pg. 63) Ulrich,K.T. and S. Eppinger, Product Design and Development, Third Edition, 2004

Organize the Needs Hierarchically (pg. 64) Perfect Application for Affinity Diagrams Ulrich,K.T. and S. Eppinger, Product Design and Development, Third Edition, 2004

Establish Relative Importance of Needs Development Team Consensus Customer Surveys Characterize the need

Development Team Consensus Rating Weight Very Important 9 Important 3 Somewhat Important 1

Customer Surveys Only a subset will be practical to prioritize N ~ 50 is reasonable Customer Needs to Focus on Technical Trade-Offs Can eliminate needs that are obviously important Costly Features Can eliminate needs that are easy to implement Importance Rating Mean, Standard Deviation, Number of Responses in Each Category, etc. Ulrich,K.T. and S. Eppinger, Product Design and Development, Third Edition, 2004

Importance Rating Survey Example (pg. 67) Ulrich,K.T. and S. Eppinger, Product Design and Development, Third Edition, 2004

Characterize the Need: Kano Diagram Degree to Which Need is Met Customer Satisfaction Must Have Linear Satisfier Delighter The SD maintains charge for several hours of heavy use The SD automatically orients screws The SD can turn Phillips, Torx, socket, and hex head screws Ulrich,K.T. and S. Eppinger, Product Design and Development, Third Edition, 2004

Sanity Check All customer types? Latent Needs? Any follow-up areas? What do we know now that we didn’t before? Surprises? Did organization participate in process? Process improvement.