Download as ppt, pdf, or txt
Download as ppt, pdf, or txt
You are on page 1of 46

Md.

Golam Kibria
Assistant Professor
Dept. of IEM, KUET.

PRODUCT DESIGN AND


DEVELOPMENT
Chapter 2 : Development Processes and Organizations
A PRODUCT DEVELOPMENT PROCESS

06/06/24
 A process is a sequence of steps that transforms a set of
inputs into a set of outputs.
 A Product development process is the sequence of steps
or activities that an enterprise employs to conceive,
design and commercialize a product.
 Many of these steps and activities are intellectual and
organizational rather than physical.

2
USEFULNESS OF A WELL-DEFINED
DEVELOPMENT PROCESS
 Quality assurance

06/06/24
 Quality assurance  Following the process is one way to
 Coordination assure the quality of the product
 Coordination
 Planning  It helps act like a master plan to let
 Management team members know when to
contribute and whom to work with to
 Improvement exchange information & materials
 Morale & Satisfaction
 Planning
 Built in milestones related to each
phase
 Management
 Able to assess performance of the
ongoing development effort
 Improvement
 Good documentation helps to identify3
opportunities to improve
SIX PHASES OF THE GENERIC
DEVELOPMENT PROCESS

06/06/24
0. Planning 1. Concept 2. System- 3. Detail 4. Testing and 5.
Development Level Design Design Refinement Production
Ramp-Up

4
PLANNING

06/06/24
 Often referred to as “phase zero” since it precedes the
project approval and launch of the actual product
development process.

 Output: Target market, business goals, key assumptions


and constraints.

5
CONCEPT DEVELOPMENT

06/06/24
 Needs of the target market are identified, alternative
products concepts are generated and evaluated, and one
more concepts are selected for further development and
testing.

6
SYSTEM-LEVEL DESIGN

06/06/24
 Includes the definition of the product architecture and
the decomposition of the product into subsystems and
components.
 The final assembly scheme for the production system is
usually defined during this phase.

7
DETAIL DESIGN

06/06/24
 Includes complete product specifications such as
tolerances, materials, geometry, etc.
 Specifications of the purchased parts

 Process plans and assembly plans of the product defined

 Output is control documentation -----the drawing or


computer files describing of each part and its production
tooling.

8
TESTING AND REFINEMENT
 Involves construction and evaluation of several

06/06/24
preproduction versions of the product
 Early (alpha) prototypes: Usually built with
production-intent parts -- parts with the same geometry
and material properties as the production version but
not necessarily fabricated with the actual processes to
be used in production.
 Alpha prototypes tested to determine whether (a) the
product will work as designed and (b) product satisfies
key customer needs.

9
TESTING AND REFINEMENT

06/06/24
 Beta prototypes are usually built with parts
supplied by the intended production processes
but may not be assembled using the intended
final assembly process.
 Beta prototypes used to answer questions about
performance and reliability in order to identify
necessary engineering changes.

10
PRODUCTION RAMP-UP

06/06/24
 The product is made using the intended production
system.
 Purpose is to train the work force and weed out any
remaining problems in the production processes
 Transition from ramp-up to normal production is
gradual

11
THE GENERIC PRODUCT DEVELOPMENT
PROCESS

06/06/24
12
Concept Development: The Front-
End Process
Expansion of concept development phase into Front-

06/06/24
end process. The front-end process generally contains
many interrelated activities, ordered shown in figure.

13
CONCEPT DEVELOPMENT ACTIVITIES

06/06/24
 Identifying customer needs
 Establishing target specifications
 Concept generation
 Concept selection
 Concept testing
 Setting final specifications
 Project planning
 Economic analysis
 Benchmarking of competitive products
 Modeling and prototyping 14
IDENTIFYING CUSTOMER NEEDS

06/06/24
 The goal of this activity is to understand customers’ needs
and to effectively communicate them to the development
team.

 Output: organized customer needs list, importance rating


for each need

15
ESTABLISHING TARGET
SPECIFICATIONS

06/06/24
 Specifications provide a precise description of what a
product has to do. They are translation of the customer
needs into technical terms.
 Targets for the specifications are set early in the process
and represent the hopes of the development team.

16
CONCEPT GENERATION

06/06/24
 The goal is to thoroughly explore the space of product
concepts that may address the customer needs
 Concept generation includes a mix of internal and
external search
 Output: Usually a set of 10-20 concepts, each typically
represented by a sketch and brief descriptive text

17
CONCEPT SELECTION

06/06/24
 Concept selection is the activity in which various
product concepts are analyzed and sequentially
eliminated to identify the most promising concept(s).

18
CONCEPT TESTING

06/06/24
 One or more concepts are tested to verify that the
customer needs have been met, assess the market
potential of the product, and identify any shortcomings.

19
SETTING FINAL SPECIFICATIONS

06/06/24
 The target specifications set earlier in the process are
revisited after a concept has been selected and tested.

20
PROJECT PLANNING

06/06/24
 The team creates a detailed development schedule,
devises a strategy to minimize development time, and
identifies the resources required to complete the project.
 Major results of the front-end activities are captured in a
contract book which contains the mission statement, the
customer needs, the detail of the selected concept, the
product specifications, the economic analysis of the
product, the development schedule, the project staffing,
and the budget.

21
ECONOMIC ANALYSIS

06/06/24
 The team often with the support of a financial analyst,
builds an economic model for the new product.
 This model is used to justify continuation of the overall
development program and to resolve specific trade-off
among, for example, development costs and
manufacturing costs.

22
BENCHMARKING OF COMPETITIVE
PRODUCTS

06/06/24
 An understanding of competitive products is critical to
successful positioning of a new product and can provide
a rich source of ideas for the product and production
process design.

23
MODELING AND PROTOTYPING

06/06/24
 Every stage of the concept development process involves
various forms of models and prototypes. These may
include, among others: early “proof-of-concept” models,
which help the development team to demonstrate
feasibility: “form-only” models, which can be shown to
customers to evaluate ergonomics and style; and
spreadsheet models of technical trade-offs.

24
ADAPTING THE GENERIC PRODUCT
DEVELOPMENT PROCESS

06/06/24
 Market Pull Products
 Technology Push Products
 Platform Products
 Process-intensive Products
 Customized Products
 High-Risk Products
 Quick-Build Products
 Complex Systems
25
VARIANTS OF GENERIC DEVELOPMENT
PROCESS

06/06/24
26
06/06/24
27
PRODUCT DEVELOPMENT
ORGANIZATIONS

06/06/24
The scheme by which individual designers and developers
are linked together into groups. Organizations are formed
by establishing formal or informal links among individuals
 Reporting relationships: Reporting relationships
give rise to the classic notion of supervisor and
subordinate.
 Financial arrangements: Individuals are linked by
being part of the same financial entity, such as that
defined by a particular budget category or profit-and-
loss statement.
 Physical Layout: links are created between
individuals when they share the same office, floor,
building, or site. 28
PRODUCT DEVELOPMENT
ORGANIZATIONS

06/06/24
 Regardless of their organizational links, particular
individuals can be classified in two different ways:
according to their function and according to the projects
they work on.

29
PRODUCT DEVELOPMENT
ORGANIZATIONS

06/06/24
 A function (in organizational terms) is an area of
responsibility usually involving specialized education,
training, or experience.
 Regardless of their functions, individuals apply their
expertise to specific projects.
 In product development, a project is the set of activities
in the development process for a particular product.

30
FUNCTIONAL & PROJECT
ORGANIZATIONS

06/06/24
 In functional organizations, the organizational links are
primarily among those who perform similar functions.
 In project organizations, the organizational links are
primarily among those who work on the same project.

31
MATRIX ORGANIZATIONS

06/06/24
 The matrix organization was conceived as a
hybrid of functional and project organizations.
 In the matrix organization, individuals are linked
to others according to both the project they work
on and their function.
 Typically each individual has two supervisors,
one a project manager and one a functional
manager.

32
VARIANTS OF THE MATRIX
ORGANIZATION
 Heavyweight project organization

06/06/24
 Lightweight project organization.

A heavy weight project organization contains strong


project links. Project manager has complete budget
authority, performance evaluation, resource allocation
decisions.

A light weight project organization contains weaker


project links and relatively stronger functional links.
Project manager is more of a coordinator and
administrator. Update schedule, arranges meetings, hiring
and firing and performance evaluation. No real authority
33
to control the project organization.
VARIOUS PRODUCT DEVELOPMENT
ORGANIZATIONS

06/06/24
34
CHOOSING AN ORGANIZATIONAL
STRUCTURE

06/06/24
 The most appropriate choice of organizational structure
depends on which organizational performance factors are
most critical to success.
 Functional organizations tend to breed specialization and
deep expertise in the functional areas.
 Project organizations tend to enable rapid and effective
coordination among diverse functions.

35
CHOOSING AN ORGANIZATIONAL
STRUCTURE

06/06/24
 How important is cross-functional integration?
 How critical is cutting-edge functional expertise to
business success?
 Can individuals from each function be fully utilized for
most of the duration of a project?
 How important is product development speed?

36
CHARACTERISTICS OF DIFFERENT
ORGANIZATIONAL STRUCTURE

06/06/24
37
TRADITIONAL DESIGN METHODS

06/06/24
 Aggregation
 (include new functions)
 Adaptation
 (adapt to new conditions)
 Application
 (apply a proven technology to a new area)
 analysis of properties
 (thorough analysis of an existing design to improve)
 Brainstorming
 (find many solutions to a problem)
TRADITIONAL DESIGN METHODS

06/06/24
 systematic search of field
 (obtain complete possible information)

39
 Questioning
 (apply a system of questions to produce mental
simulation)
 mental experiment
 (observe an idealized mental model at work)
 valueanalysis
 Evaluation
 (find best variant among a few by point-counting)
TRADITIONAL DESIGN METHODS

06/06/24
 invention
 Iteration

40
 (to solve a system with complicated interactions)
 experimentation
 division of totality

 math & computer modeling


WHAT IS THE PRODUCT LIFE
CYCLE?

The PRODUCT LIFE CYCLE is a series of STAGES that a


product goes through from when a business first creates and
sells it until the time nobody wants it any more.
FOUR STAGES EXIST IN THE ‘WORKING LIFE’ OF MOST
PRODUCTS.

STAGE 2 - PRODUCT GROWTH


SALES will start to RISE QUICKLY as many
people begin to use the product.
PROFITS will start to RISE QUICKLY as sales
rise sharply.
STAGE 3 - PRODUCT MATURITY
SALES will start to SLOW DOWN as almost
everyone who wants the product will have it.
PROFITS will be MAXIMISED as the
maximum number of sales is made.
STAGE 1 - PRODUCT INTRODUCTION
STAGE 4 - PRODUCT DECLINE
Costly stage as lots of advertising and
SALES will start to FALL as people start to use
promotion is needed to encourage sales. other better or newer products.
SALES will start to RISE SLOWLY as PROFITS will start to FALL as sales fall.
people become aware of the product.
At this stage a decision has to be made
PROFITS will start to APPEAR SLOWLY
about whether to withdraw the product
as sales rise and start up costs are repaid
or use extension strategies to inject new
life into the product.
EXTENSION STRATEGIES
The marketing mix can be changed to inject
new life into a product by:

 Changing or modifying the PRODUCT


 Altering the distribution pattern (PLACE)
 Changing the PRICE
 Using a new PROMOTIONAL campaign

These methods can delay the replacement or


withdrawal stage for some time
LIFE CYCLE VARIATIONS
The speed at which different products move
through the life cycle will vary, and some
never seem to complete their life cycle at all
Ex: Cadbury’s Dairy Milk was introduced in
1905 and is still going strong!

This tends to be because the product has a


strong brand and a loyal customer base.
CHAPTER 2: HOME WORK

06/06/24
 Exercise (Analysis of Properties)
 Focus on materials selection for an existing product
 Steps:
 1. Examine each component of a product (an incandescent bulb, stapler, can
opener).
 2. Break the product or decompose it, avoiding injury to eyes or hands and damage
to the other components.
 3. Construct and complete a table consisting the following items on its columns.
 a. list each component of the product
 b. define the function of each component
 c. identify the material used
 d. reason why it was selected
 e. select possible alternative.
 4. List five failure mechanisms
06/06/24
THAT’S ALL FOLKS !

46

You might also like