BA
296-1 and ME290P
Fall 1997
Managing the New Product Development Process: Design Theory and
Methodology
COURSE READINGS
Required Textbook: Product Design and Development, Karl
T. Ulrich and Steven P. Eppinger, available at the UC bookstore, Ned's and
Campus Textbook Exchange (and also used in last year's class). In the outline
below, CHAPTER X always refers to the readings from the text.
Required Course Reader: Also available from the Ned's (across
the street from the ASUC bookstore); radically changed from last year.
Library Reserves: Additional reading supplementing that provided
in class can be found on reserve in the Engineering and Business libraries.
On-Line Resources: Supplemental on-line readings to support projects.
Class 1: Introduction to New Product Development (NPD)
Wednesday, August 27th
We will cover course logistics and requirements and then develop the motivation
and framework for the course. Read the December 13, 1993 Fortune
article, PAYOFF FROM THE NEW MANAGEMENT (accessible through the Melvyl network
in the library), which describes a successful product development effort at
Thermos, CHAPTER 1: INTRODUCTION and CHAPTER 2: DEVELOPMENT PROCESSES AND
ORGANIZATIONS. Consider thought question 1 at the end of Chapter 1 and thought
question 4 at the end of Chapter 2.
Visit the following web sites to learn about some of the resources on product
design and development that are available:
(NOTE: If you have not used the Melvyl network before, here is one way you can
access the article. Log on to the network in the library or from a terminal in
the computer center. Go to the business catalog by typing "bus" and then to
the magazines and journals database by typing "mags". There are numerous ways
to find the article at this point. One approach is to type "find xt payoff"
which will give you a list of items that have the word payoff in the title.
Then type "display text 7" which will display the text for the seventh article,
which is the assigned article. Note that both find and display can be
shortened and represented by their first letters, f and d, respectively.)
Class 2: Choosing the Right NPD Process: Matching Process to Needs
Friday, August 29th
Prepare the HONEYWELL RESIDENTIAL DIVISION - NEW PRODUCT DEVELOPMENT case for
class discussion by reading the case, answering the following study questions,
and, if possible, meeting with other students in the class to discuss the case.
This case examines three product development projects conducted at Honeywell
Residential Division. Two of the projects undertaken followed the
long-established "green book" set of procedures within the division, while the
third followed a new "tiger team" approach involving corporate resources and
division personnel. The three projects represent different philosophies,
technologies and results. The case raises issues regarding the match between
the problems the development approach is intended to solve and the nature of
the approach. The following questions will guide your analysis of the case:
- Compare the three development projects discussed in the case. What explains
the differences in performance you observe? (In doing this, it might be useful
to think about how one ought to compare projects. That is, what are the
relevant dimensions and criteria for comparison?)
- What are the salient features of the traditional development process at
Honeywell Residential? What have been some of the underlying drivers and
incentives in this approach? What strengths and weaknesses does it have?
- What is your evaluation of the new direction suggested for product
development (for example, new procedures for product sourcing and product
certification as well as the tiger team approach)? What should Molson do?
Read DELTA -- A DESIGN EXERCISE and come to class prepared with any questions
you may have about the exercise. We will assign roles in class and "train" you
to play your role.
Assignment due in Class on Wednesday, September 3rd: During the
next few class sessions, we will talk about team dynamics and interactions as
being critical to new product development success. You will have a chance to
observe first-hand the difficulties in team formation and process during the
Delta Design Exercise. To provide another dimension to understanding team
dynamics, complete a simplified version of the Myers-Briggs test, the Kiersey
test, available on the WWW. (MBA students may use the results of the test they
took last year, if available.)
- First, read the background on the test available at
http://sunsite.unc.edu/personality/keirsey.html
- Then, take and score the test available at
http://sunsite.unc.edu/jembin/mb.pl. (Note that it is also available directly
from the background page.)
- Based upon the information you gather in this process, write a one-page (max)
paper about how you might use the information about your personality type and
those of the other individuals in your design group to improve your group's
work. How might others on your team use information about you? (Include your
personality profile in the paper.)
For other reading on new product development processes, see:
- Eisenhardt, Kathleen M. and Behnam N. Tabrizi, "Accelerating Adaptive
Processes: Product Innovation in the Global Computer Industry," ASQ, March
1995
- Rosenthal, Stephen R., "Structuring the Work: Phases, Gates, and
Simultaneous Engineering," pp. 17-49, Effective Product Design and Development,
One Irwin, Homewood, IL, 1992.
Class 3: Delta -- A Design Exercise
Wednesday, September 3rd
Re-read the role assignment you were given in class. Make sure that you
thoroughly understand the role you are to play. If you do not, please ask
questions of your trainer to clarify your position. Prepare any materials you
believe you will need to play the role. DO NOT discuss the other three roles
with others in the class. On the day of class, come to C110 for your room
assignment, go straight to that room and convene your team as quickly as
possible, as you will find that 1 1/2 hours is quite short for accomplishing
this work. YOU MAY WISH TO LEAVE SOME EXTRA TIME AT THE END OF THE CLASS TO
COMPLETE THE EXERCISE, or you may have to arrange with your group to meet again
before Friday's class.
Your Delta Design Team will receive another assignment on Friday, September 5th
when you will be given the design and videotape from another design team to
analyze. It would be appropriate to schedule time to do this analysis
(sometime between Friday, September 5th and Friday, September 12th) while you
are together doing the design exercise.
Due at the end of this class session:
- Your videotape with name of your team and names of all of your
team members written on it. Include those assigned to observe the team.
- Delta Design game materials. You should keep a sketch on a separate piece of
paper from the gameboard for your own purposes. The game materials will
be kept and reused by another class.
Assignment due in class on Friday, September 5th includes:
- A sketch of your final design
- The calculations of the required performance measures (e.g., interior area,
blue delta percentage, temperature, load, cost)
- A brief paragraph describing the virtues of your design
These materials will be passed along with your videotape to another team in the
class. That team will be charged with reviewing your design and analyzing the
design process your team employed.
NOTE: Project Proposals are due on Thursday, September 4th at 3 p.m.
(unless you want to bring copies to class yourself.) E-mail submission is
fine.
Class 4: Project Proposals and Team Assignments
Friday, September 5th
We will use this class session to review in some detail the various proposals
that have been put forth for design projects. See instructions for the design
project for more detail. Students who wish to sell their design ideas to the
rest of the class will be allotted time to do so during this class session. By
the end of the class session, you should be prepared to submit your top three
choices for projects on which you wish to participate.
Assignment due today: List of product ideas (see instructions for
project) - everyone must produce one regardless of whether or not you propose
one to the class.
In addition to discussing the projects, we will briefly discuss your experience
in the Delta Design Exercise. At the end of class, you will be given a copy of
another group's design and videotape, and asked to analyze them for class on
Friday, September 12th.
Assignment due in class on September 12th: Read A MODEL OF THE
MECHANICAL DESIGN PROCESS BASED ON EMPIRICAL DATA. Meet with your Delta Design
Team (including observers) to review the tapes and design documents from
another team. (You will have received these in class on Friday, September
5th.) View the tapes, analyze them, and answer the following questions:
- Estimate the percentage of time spent in assimilation, documentation,
planning, repair, specification and verification. (A full protocol analysis is
not required.)
- How did your results follow those of Ullman, et al.? How were they
different?
- What other observations to you have of the process the team used?
- Write a paper of two pages (max) describing your findings and
observations. Return the videotapes and designs with your write-up.
NOTE: Project preferences are due by 5 p.m today.
Class 5: Concept Development: Customer and User Needs Assessment
Wednesday, September 10th
Read CHAPTER 3: IDENTIFYING CUSTOMER NEEDS and LISTENING TO THE CUSTOMER - THE
CONCEPT OF A SERVICE-QUALITY INFORMATION SYSTEM by Berry and Parasuraman.
Consider the thought questions at the end of Chapter 3 and be prepared to
discuss the chapter material. Berry and Parasuraman describe an approach to
assessing service quality. What are the salient elements of their system?
Could the system be used to generate new service concepts as well? Are there
lessons from their work that apply to the development of new products in
non-service environments? Bill Rus, Market Research Manager at Autodesk, will
join us during class to discuss approaches to gathering information on customer
and user needs.
Assignment due today: Choose a product, and interview someone
about what they like and dislike about the product. (This interview can be
done very informally in 5-10 minutes.) Record what they say and interpret the
data in terms of customer needs. Prepare a one-page summary of what you have
learned.
Note that there will also be a speaker on this subject in the evening program
on September 24th. Tapan Bhat, Product Manager at Intuit, will describe
Intuit's approach to understanding customer and user needs. You are welcome to
join that session in C135 from 6 - 7:30 p.m.
For additional information on the front end of the development process see:
- Bacon, Glenn, Sara Beckman, David Mowery and Edith Wilson, "Managing Product
Definition in High-Technology Industries: A Pilot Study," California
Management Review, Spring 1994.
- Khurana, Anil and Stephen Rosenthal, "Integrating the Fuzzy Front End of New
Product Development, Sloan Management Review, Winter 1997.
- Meyer, Marc H., and James M. Utterback, "The Product Family and the Dynamics
of Core Capability," Sloan Management Review, Spring 1993.
- Wheelwright, Steven C., and Kim B. Clark, "Creating Project Plans to Focus
Product Development," Harvard Business Review, March-April 1992.
For those of you wishing additional information on customer and user needs
assessment, the following papers are on reserve:
- "Conjoint Analysis: A Manager's Guide," Harvard Business School, 1990.
- Day, George S., "Continuous Learning about Markets," California Management
Review, Summer 1994.
- Griffin, Abbie and John R. Hauser, "The Voice of the Customer," Marketing
Science, Vol. 12, No. 1, Winter 1993. (Provides more detail on the
findings presented in Ulrich and Eppinger.)
- Kaindl, Hermann, "An Integration of Scenarios with their Purposes in Task
Modeling," ACM 1995.
- Lynn, Gary S., Joseph G. Morone, and Albert S. Paulson, "Marketing and
Discontinuous Innovation: The Probe and Learn Process," California Management
Review, Spring 1996.
- Potts, Colin, "Using Schematic Scenarios to Understand User Needs,"
ACM 1995.
- Royer, Traci, "Using Scenario-Based Designs to Review User Interface Changes
and Enhancements," ACM 1995.
- Urban, Glen L. and Eric von Hippel, "Lead User Analysis for the Development
of New Industrial Products," Management Science, May 1988.
And, if you wish further depth in the market aspects of new product development
there are two Management of Technology classes that cover marketing issues:
- BA 263: New Product Development
- BA 264: High Tech Marketing
Class 6: Descriptive Studies of the Design Process
Friday, September 12th
Bring your videotape analyses to class. We will discuss your findings and
observations about the teams you observed. In addition, read THE DISCIPLINE OF
TEAMS. What does the paper say about using information from tests such as the
Myers-Briggs (Kiersey) test? What roles does the paper suggest that the course
faculty (Agogino and Beckman) should play? What role should your coaches play?
How would you have changed your Delta Design Exercise experience were you to
have read this paper ahead of time? Would discussing your Myers-Briggs
profiles with your Delta Design team members have helped you work better with
one another?
Regarding the Ullman article: Does the "task/episode accumulation" (TEA) model
developed by the authors do a good job of capturing the design process? What
do you like and dislike about the model? How would you change it? What does
the authors' approach to modeling tell you about the mechanical design process
itself?
Class 7: Concept Development: Translating the Voice of the Customer
Wednesday, September 17th
Read CHAPTER 4: ESTABLISHING PRODUCT SPECIFICATIONS, and HOUSE OF QUALITY.
Prepare the SWEETWATER case for class discussion. The SweetWater case will
allow us to understand how the "voice of the customer" must be chased back to
clearly stated needs that vividly incorporate the user experience with the
product, and will provide a structured way of thinking about stratifying user
needs. The following questions should guide your case preparation:
- Using your own perspective, what are the most important user needs in the
water purifier market? You might want to interview a few wilderness
enthusiasts to help answer this question.
- How can you structure this user's needs data to assist Sandy Platter in
creating his product concept?
- How do competitors' products meet those needs?
- What characterizes an outstanding concept for a water purification device for
backpackers and other outdoor enthusiasts?
(You should start applying some of the methods you are learning in class to
your design project. Note that you will have to select from among many methods
the ones that are most appropriate to your development project.)
For information on mapping product technologies across members of a product
family, see:
- Willyard, Charles H. and Cheryl W. McClees, "Motorola's Technology Roadmap
Process," Research Management, September-October 1987.
Class 8: Project Lab -- Mission Statement, Customer and User Needs
Analysis
Friday, September 19th
This class session will be dedicated to working with your project team and a
coach to refine your mission statement and plan for assessing customer and user
needs. See project instructions for more details.
Class 9: Concept Development: Concept Generation
Wednesday, September 24th
This class session will focus on brainstorming and "ideation" techniques used
by new product development teams to generate product ideas from their
understanding of customer wants and needs and of the available technologies.
Read CHAPTER 5: CONCEPT GENERATION. Consider thought questions 2, 3, and 5.
We will use the Vizability Software in class to show additional concept
generation techniques. This will launch the next phase of your projects'
development efforts as you begin to translate customer needs into various
product concepts.
Note that there will be a guest speaker in the Evening version of this class
who will cover this topic, and lead an "ideation" exercise. You are welcome to
attend that session. (See the end of the syllabus for details.)
Additional references for those of you interested in techniques for stimulating
creativity:
- Adams, James L., Conceptual Blockbusting
- Michalko, Michael, Thinkertoys: A Handbook of Business Creativity for the
`90s
Both books have a number of exercises intended to stimulate creativity, similar
to some of those used in class.
Class 10: Concept Development: Concept Selection
Friday, September 26th
Once you have generated a set of possible product concepts, you must identify
the one or ones that you will actually work on. During this class session, we
review methodologies for choosing from among the options. Read CHAPTER 6:
CONCEPT SELECTION. Complete exercises 3 and 4 at the end of the chapter.
Bring your results to class. During class we will review these concepts as
well as the application of probability theory and decision analysis to concept
selection. Proceed to apply these methodologies to your design projects.
Assignment due: Complete exercises 3 and 4 at the end of Chapter
6.
For a concise and brief review of probability theory, some of you may wish to
refer to the following materials which are on reserve: Agogino, A.M., "The
Logic of Probability Theory," October 1992.
Class 11: System Level Design: Product Architecture and Product
Partitioning
Wednesday, October 1st
Read CHAPTER 7: PRODUCT ARCHITECTURE and THE DESIGN AND DEVELOPMENT OF
INFORMATION PRODUCTS by Meyer and Zack. Complete exercise 2 or 3 at the end of
the chapter and be prepared to discuss thought questions 1 and 2. Those of you
developing web-based products may find the Meyer and Zack article particularly
applicable. What do Meyer and Zack mean by a product platform? What is an
"information product?" What are the key elements of the "platform" of an
information product? Why does understanding the elements of a "platform"
matter? We will discuss the importance of good product architecture and its
relationship to the organizational design of a new product development effort
as well as to the overall product strategy of a firm.
To bring these papers alive, visit Sony's web site which shows the various
models of Walkman cassette players:
How many models are displayed? What are the differences among them from a
customer perspective? How different do you expect they are from a design
perspective? What would you expect Sony's production system to look like?
Should you wish to read additional material on product architecture and
the implications of modular design, look at the following articles on
reserve:
- Butler, Keith, "Designing Deeper: Towards a User-Centered Development
Effort," ACM 1995.
- Ulrich, Karl T. and Karen Tung, "Fundamentals of Product Modularity," MIT
Working Paper #3335-91-MSA, September 1991
- Ulrich, Karl, "The Role of Product Architecture in the Manufacturing Firm,"
MIT Working Paper
Class 12: Project Lab -- Customer and user needs and concept
development
Friday, October 3rd
This lab will provide you an opportunity to review what you have learned about
your customer and user needs and your first pass at concept generation with
your project coach. See project instructions for more detail.
Class 13: Voice of the Customer Presentations
Wednesday, October 8th
This will be the first of three peer review opportunities you will have for
your project. See project instructions for more detail. Come to class prepared
to actively listen to your peers talk about their projects, ask them
constructive questions and provide them feedback on the direction their
projects are taking.
Class 14: Voice of the Customer Presentations
Friday, October 10th
See Class 13.
Class 15: Design for Usability: Role of Industrial Design and User
Interface Design
Wednesday, October 15th
This class launches a three-session module on "design for x," where x refers to
many aspects of design from manufacturability to serviceability to usability.
We have chosen to focus on product usability, with one session on industrial
design and user interface design, manufacturability and designing for
environmental soundness. Each company chooses to focus on the specific "design
for x" issues that are important in its industry.
Read CHAPTER 8: INDUSTRIAL DESIGN. Consider thought questions 1 and 3. In
preparation for the OXO case, interview at least five users with experience
using these three kitchen gadgets: peeler, can opener, pizza cutter. Ask the
product users to describe what they like and don't like about the gadgets they
use. List the specific responses to your questions on a piece of paper. At
the bottom of the page, produce a summary of the important features of these
products. Bring this paper and your favorite kitchen gadget to class for
discussion.
Assignment due: Kitchen gadget assessment
Reference On-Line Case Study in Industrial Design: Cyclone Grinder Case with Ingersoll Rand.
While the case focuses on physical design principles (e.g., ergonomics), many
of the same basic principles apply to design of software user interfaces. In
preparation for class discussion, choose three of the user interface design
rules listed below. First, interpret what they mean, and then use your
favorite software package(s) to find examples of their implementation (or lack
of implementation.)
Following is a list of user interface design rules that you may find helpful
in your team's work:
- Know thy user, and YOU are NOT thy user.
- Things that look the same should act the same.
- Everyone makes mistakes, so every mistake should be flexible.
- The information for the decision needs to be there when the decision is
needed.
- Error messages should actually mean something to the user, and tell the user
how to fix the problem.
- Every action should have a reaction.
- Don't overload the user's buffers.
- Consistency, consistency, consistency.
- Minimize the need for a mighty memory.
- Keep it simple.
- The more you do something, the easier it should be to do.
- The user should always know what is happening.
- The user should control the system. The system shouldn't control the user.
The user is the boss, and the system should show it.
- The idea is to empower the user, not speed up the system.
- Eliminate unnecessary decisions, and illuminate the rest.
- If I made an error, let me know about it before I get into REAL trouble.
- The best journey is the one with the fewest steps. Shorten the distance
between the user and their goal.
- The user should be able to do what the user wants to do.
- Things that look different should act different.
- You should always know how to find out what to do next.
- Don't let people accidentally shoot themselves.
- Even experts are novices at some point. Provide help.
- Design for regular people and the real world.
- Keep it neat. Keep it organized.
- Provide a way to bail out and start over.
- The fault is not in thyself, but in thy system.
- If it is not needed, it is not needed.
- Color is information.
- Everything in its place, and a place for everything.
- The user should be in a good mood when done.
- If I made an error, at least let me finish my thought before I have to fix
it.
- Cute is note a good adjective for systems.
- Let people shape the system to themselves, and paint it with their own
personality.
- To know the system is to love it.
(Note: This list was generated through an extensive survey of people working
in the human-computer interface design field. Results of the survey are
reported more extensively by Arnold M. Lund of Ameritech in "Expert Ratings of
Rules of Thumb for Usability.")
Other rules:
- The idea is to empower the user, not speed up the system.
- Don't overload the user's buffers.
- Let people shape the system to themselves, and paint it with their own
personality.
- Minimize the need for a mighty memory.
- Eliminate unnecessary decisions, and illuminate the rest.
These rules should prove useful as you take your product prototypes out and
test them with users.
For a deeper understanding of design (industrial design, product design,
architecture) and its role in business development, take Management of
Technology course BA 296: Design as a Strategic Business Issue. You can find
examples of great designs on the IDSA web site which shows winners of their
annual design awards. A number of these designs are shown in the Business Week
issue distributed in class. Examples of bad design can be found at
www.baddesigns.com/index.shtml. Other Web and Interface Design resources can
be found at: http://best.me.berkeley.edu/~aagogino/me290p/f97/resources.html/.
Note: There will be a guest speaker in the Evening class addressing this
topic. You are welcome to join that session. See the end of the syllabus for
details.
Class 16: Design for Manufacturability
Friday, October 17th
Read CHAPTER 9: DESIGN FOR MANUFACTURABILITY and prepare the case DESIGN FOR
MANUFACTURABILITY AT MIDWEST INDUSTRIES. This case examines the implementation
of design for manufacturability (DFM) at Midwest Industries, a $4 billion
manufacturer of retail and self-service vending equipment. The case presents
the experience of three different Midwest sites in using DFM tools and methods,
and offers an opportunity to identify DFM and how a corporate staff group has
tried to implement it in a decentralized company. Come to class prepared to
discuss the following questions:
- What does DFM mean at Midwest? What is your evaluation of Thurlow's
approach to implementing DFM at Midwest?
- Compare and evaluate the experience of Raleigh, Coventry, and Chicago in
implementing DFM. What explains the outcomes you observe? What lessons should
Midwest senior management draw from those experiences?
- Suppose you were given the job as Thurlow's replacement and charged with
moving DFM off its plateau at Midwest. What would you do? Develop a plan of
action.
To understand more about the manufacturing implications of new product designs,
take Management of Technology course BA 296/ME 221: Intelligent Manufacturing
Systems.
Reference On-Line Case Study in Design for Assembly and Manufacture: Mattel Color Spin and
IBM Proprinter.
Class 17: Design for Environmental Soundness
Friday, October 22nd
Read EVALUATION FOR POST-MANUFACTURING ISSUES IN LIFE-CYCLE DESIGN and DESIGN
FOR ENVIRONMENTABILITY. Come prepared to discuss the key issues in designing
environmentally sound products and the means by which environmental
considerations can be built into the design process. Observe examples in your
everyday life of products that were and were not designed for environmental
soundness. Would using environmental design principles make any difference to
your projects?
Professor Paul Sheng will lead the class discussion. Dr. Sheng is currently
Associate Professor in Mechanical Engineering, where his research interests are
in laser material processing and green design and manufacturing. Dr. Sheng
formed the Consortium on Green Design and Manufacturing in 1993 to develop
multidisciplinary collaborations in product design-for-environment,
manufacturing planning and organizational issues. Prior to arriving at
Berkeley, Dr. Sheng served as Senior Project Engineer in the Advanced
Manufacturing Staff at General Motors Corporation. Dr. Sheng received his Ph.D.
in Mechanical Engineering from MIT in 1991.
Class 18: Project Lab: Concept development and selection
Friday, October 24th
This lab will focus on your concept selection process and the final product
concept you have chosen. See project instructions for more detail.
Class 19: Prototype Development and Trade show Booth Preparation
Wednesday, October 29th
This class time is set aside for finalization of your product prototypes and
trade show booths for Friday's class.
Class 20: Concept and Preliminary Prototype Peer Review
Friday, October 31st
We will conduct this class session in a "trade show" format. See project
instructions for more detail.
Class 21: Economics of Product Development
Wednesday, November 5th
Read CHAPTER 11: ECONOMICS OF PRODUCT DEVELOPMENT PROJECTS and THE RETURN MAP
by Price and House in Harvard Business Review (copies on reserve).
Consider thought questions 1 and 2 at the end of the chapter. What do you like
and dislike about the "return map?" We will discuss performance measurement,
investment justification and cost accounting implications of new product
development activities.
Class 22: Project Lab: Prototype review and product testing
Friday, November 7th
At this lab, you will present your final prototype design and discuss work you
have already done, or plans you have to do work, in testing your prototype
design with prospective users. See project instructions for more detail.
Class 23: Testing and Refinement: Taguchi Method and Failure Mode
Analysis
Wednesday, November 12th
Read ROBUST QUALITY and THE TAGUCHI APPROACH TO PARAMETER DESIGN. What does
"robust quality" mean? How does a good new product development team go about
achieving it? Don Clausing has written a book called Total Quality
Development. What do you suppose the title means? We will introduce the
notion of failure mode analysis as well as review the Taguchi Method.
For your design project, make a list of key design parameters. (Note that
these are the parameters you set through the details of your design . They are
the elements of your project that most influence the performance of your
product relative to the specifications you have established.) Bring your list
to class.
Assignment due: Taguchi exercise handed out in class.
Class 24: Testing and Refinement: A Case Study
Friday, November 14th
Read CHAPTER 10: EFFECTIVE PROTOTYPING and prepare the case BMW: THE R-SERIES
PROJECT for class discussion. This case focuses on a decision about how to
prototype a product in development. Discussion of the alternatives provides
insight into the different roles that prototyping can play in product
development and why different prototyping approaches may be more or less
appropriate within specific organizational and strategic contexts. The
prototyping decision allows you to examine how the product development process
influences product quality along such dimensions as conformance, performance
and appearance.
- What are the causes and consequence of BMW's quality problems with newly
launched products? What should be done to improve "launch quality?"
- What are your recommendations to Carl-Peter Forster concerning the 7-series
prototypes? What should he do regarding future development projects?
- What changes would you recommend in the way BMW develops new models? What
attributes of newly launched products would you expect to improve as a result
of these recommendations? Which attributes might deteriorate?
- What recommendations would you make to Chairman von Kuenheim regarding BMW's
strategy to compete against new Japanese entrants into the luxury car
market?
Some of you may also be interested in reading
- Lichter, Horst, Matthias Schneider-Hufschmidt and Heinz Zullinghoven,
"Prototyping in Industrial Software Projects -- Bridging the Gap Between Theory
and Practice," IEEE Transactions on Software Engineering, Vol. 20, No. 11,
November 1994.
- Schrage, Michael, "The Culture(s) of Prototyping," Design Management Journal,
Vol. 4, No. 1, Winter 1993. (An interesting view of the different roles that
prototypes play in new product development.)
- Sutcliffe, Alistair, "Requirements Rationales: Integrating Approaches to
Requirement Analysis," ACM 1995.
Class 25: Tools for Managing NPD Projects
Wednesday, November 19th
Read CHAPTER 12: MANAGING NEW PRODUCT DEVELOPMENT PROJECTS. Complete
exercises 1, 2 and 3 at the end of the chapter and consider thought questions 3
and 4. List at least five lessons you have learned about project management
based on your experience in this course. Bring them to class for
discussion.
Assignment due: Exercises 1, 2 and 3 at the end of Chapter
12.
Class 26: Final Product Specification and Prototype
Friday, November 21st
This will be your last lab session with your project coach before the final
trade show. See project instructions for more detail.
Class 27: Project Lab: Financial Analysis
Wednesday, November 26th
This lab will not involve your IDEO coaches, but rather will entail a review of
your financial analyses to date. See project instructions for more detail.
Class 29: Class Review: NPD Team Management
Wednesday, December 3rd
Prepare QUANTUM CORPORATION -- BUSINESS AND PRODUCT TEAMS for class
discussion. This case describes the multi-year effort at Quantum Corporation, a
Silicon Valley-based disk drive company, to develop distinctive capability in
new product development. That capability, based on heavyweight product teams
under the direction of cross-functional business teams, has been the basis for
success in the corporation's efforts to gain a commanding position in the 3.5"
disk drive market. The case reviews the company's experience on a number of
development teams and the evolution of business teams for each of its three
primary businesses.
- What is required to be successful in the Winchester disk drive industry?
What do you think accounts for Quantum's success?
- What is your evaluation of Quantum's progress to-date in developing and
applying team concepts?
- How effective have the major teams been? What accounts for their primary
differences in effectiveness?
- How would you recommend that Dave Brown address the team-related issues
raised at the end of the case? Why? Are there other team issues that you
would add as high priority on his list?
- Develop an overall plan of action for addressing these issues. How should
they be linked to other aspects of Quantum's management approach? How should
they measure and track their progress in implementing that plan? (Be specific
as to actions taken, their timing, and the results expected.)
Class 30: Class Summary: Strategic Role of NPD
Friday, December 5th
Prepare the NEC case for class discussion. NEC competes in a variety of
technology-intensive businesses by effectively leveraging its R&D
resources. The case describes a series of projects that build capability in
the development of supercomputers and mainframes. The projects highlight NEC's
emphasis on discovering the system-level impact of technical choices and its
focus on increasing capability by managing a coherent stream of projects that
effectively build on each other. The impending emergence of new computer
architectures is now threatening NEC's approach, however, because the company's
existing capability base may soon become obsolete. Prepare the following
question for class discussion:
- Analyze NEC's approach to the development of products based on advanced
technologies. What are its critical elements?
- What are the advantages of NEC's approach? What are the drawbacks?
- There are three basic options for future projects to be performed by NEC's
packaging engineering group. The first two focus on the requirements of
developing a new traditional vector supercomputer by 1993 and a new mainframe
by 1995. The third deals with the development of new parallel computer
concepts. These efforts would precede a formally approved parallel computer
project which would probably begin around the middle of 1992. The options
focus on the bipolar packaging group which currently consists of 36 engineers.
The CMOS packaging group is already stretched to its limit in developing
packaging systems for laptops, personal computers, and workstations over the
next three to four years.
- Option 1: Extension of the SX-3 module. The combination of polyimide and
ceramics that had rendered the SX-2 and SX-3 successful could once again be
stretched to provide the performance necessary for the 1993 traditional vector
supercomputer and the 1995 mainframe. The project would not be easy, since the
SX-3 design is already close to several material limitations. The entire
bipolar packaging group would essentially have to be dedicated to the effort to
be certain they would finish in less than three years, as required. This would
probably be the last supercomputer generation based on this module concept.
- Option 2: Glass ceramic module. This option involved introducing the glass
ceramic technology that had been considered as the third option in the SX-2
project. Glass ceramics have thermal and electrical characteristics superior
to those of the materials used in the SX-2 and SX-3 projects. Scientists
envision large performance improvements that would suffice for at least tow
generations of future vector supercomputers. (IBM recently introduced a
mainframe module based on glass ceramics that exhibited impressive performance
characteristics.) This project would be an "all-out" technical effort
involving more resources than the first option, including at least the entire
bipolar packaging group plus ten scientists from the R&D laboratory (the
total umber of scientists with expertise in high performance packaging,)
Meeting the tight time schedule for the introduction of the 1993 vector
supercomputer would be a concern, but could probably be done.
- Option 3: Feasibility study of parallel computer module. This option
involves the systematic evaluation of parallel computer packaging concepts. At
this point in time, because there is no dominant design in the industry, there
are several ways that parallel computer concepts could develop. However, NEC's
senior management has implied that the parallel computer will be manufactured
in the same facility in Fuchu City as the vector machines. Additionally, the
results of the software and integrated circuit studies performed so far imply
that future parallel computers will probably be based on CMOS microprocessors.
The challenge for the packaging group is to find a way to package between 100
and 1,000,000 of these microprocessor close to each other. There are many ways
to exploratory projects could be implemented. First, the packaging engineering
group could devote engineers to discussing and building models of processor
concepts. The necessary resources would depend on the number of technical
approaches to be considered, involving about six engineering for each approach.
Second, NEC could initiate studies with outside suppliers. This would be a bit
expensive, and the packaging group would have to make a strong case for it to
senior management. Third, the group could simply wait a year or two, since a
full scale parallel computer project has not yet been approved. If approach,
the project would not begin until 1992.
As Watari, which of the above options would you choose and why?
Final Trade show
Saturday, December 13th, 12:30 - 3:30 p.m.
This final class session requires you to prepare a trade show booth to present
you project to people who may wish to purchase rights to the product or fund
its final development. See project instructions for more detail. Please
note that this event will be held in the Wells Fargo Room on the 5th floor of
Cheit Hall.
Last updated: 26 October 97
Send Comments to: Alice Agogino, aagogino@euler.me.berkeley.edu
Copyright © 1997 Alice Agogino and Sara Beckman;
All Rights Reserved.