Professional Documents
Culture Documents
AND
DEVELOPMENT
HOME
ABOUT THE AUTHORS
INSTRUCTOR SITE
REGISTER FOR INSTRUCTOR SITE
RESOURCES
CONTACT US
Diagram a process for planning and cooking a family dinner. Does your process
resemble the generic product development process? Is cooking dinner analogous to
a market-pull, technology-push, process-intensive, or customization process?
EX 2.2
Define a process for finding a job. For what types of endeavors does a well defined
process enhance performance?
EX 2.3
EX 2.4
TQ 2.1
What role does basic technological research play in the product development
process? How would you modify Exhibit 2-3 to better represent the research and
technology development activities in product development?
This is a large and open-ended question. There is a good discussion of this topic in
Clark and Wheelwright Revolutionizing Product Development. One answer is that
technology development is a parallel activity that provides proven technologies that
can be taken "off the shelf" and used in product development efforts. Clark and
Wheelwright call this the "pizza bin" approach, because technological "ingredients"
are proven and then shelved until they are needed to create a "pizza" (product). The
amendment to Exhibit 2-3 would include a technology development activity with an
arrow to the concept development activity. Some might argue that technology
development may also lead to the identification of new product opportunities. In this
case, the technology development activity would have an arrow to an earlier product
planning or product strategy activity (not shown in Exhibit 2-3).
In some settings the technology development and product development are more
tightly coupled. For example, some start-up companies begin with a basic
technology or invention and then work to quickly commercialize it. In such cases,
much of their early work could be considered technology development. It is fraught
with uncertainty and, in fact, may result in failure. Nevertheless, there are some
technologies with so much commercial promise that these risks are worth taking.
TQ 2.2
Although a university has many purposes, its primary purpose is the development of
undergraduate students. The student development process is analogous to the
product development process. The student development process takes as its input a
high school graduate whose mission statement is to get an undergraduate degree.
Its output, instead of a product launch is the graduation of the student. Along the way
there is a well-defined series of steps complete with milestones as in the product
development process. Although the detailed series of steps in the student
development process is different than in the product development process, the
advantages of the well-defined process are similar. In both cases the process
ensures the quality of the output of the process (student), the coordination of the
resources on the development team (faculty, admissions, physical plant), the timely
completion of the project (graduation in 4 years), the management of the project, and
the improvement of the process.
Having established the analogy between the product development process and the
student development process, the next step is to look at the analogy between the
product development organization and the university. The two primary organizational
types are the functional organization where the primary links are among those who
perform similar functions and the project organization where the primary links are
among those who work on the same project. A university is a functional organization.
Some of these functions include:
There are certainly other functions that make up a university but using just these four
as an example we can see that they are indeed organized by the function they
perform. Although they are all part of the development of the "product", the student,
their strongest ties are to those who share the same function. As in a product
development organization, those sharing the same function are usually located near
each other and report to the same manager.
If we look even further into the organization of the faculty we see that within the
faculty the organization continues to be a functional organization. Breaking it down
further we see:
TQ 2.3
This is a classic project organization. Although the students may come from different
"functions" (e.g., departments, educational backgrounds), they do not have strong
organizational linkages to these functions. For the purposes of the course, they have
one goal: to get the project done. Especially if they are graded as a team, the
organizational structure closely mirrors that of a "start-up" or other autonomous
project teams. Note that a strong project organization can exist even without
heavyweight project managers. In a course, no manager is explicitly assigned to
each team, yet the team is autonomous and has the ultimate authority and
responsibility to make decisions.
TQ 2.4
Yes, this is possible. In fact it happens all the time. A team may consist of several
members who have strong organizational links to the project and of members with
strong functional links. The team members with strong functional links tend to be
part-time participants. Examples include industrial designers, stress analysts,
technical writers, model makers, and sales people. The design, manufacturing, and
marketing people on the team with on-going responsibilities for project work may be
linked together by strong project ties, while the part-time participants may not share
those links.