Professional Documents
Culture Documents
Caso Cessna Skyhawk
Caso Cessna Skyhawk
Sales of general aviation aircraft, which had topped out at 17,000 planes per year,
dropped to 12,000 planes within a year, and over the next decade finally hit rock bottom
at 928 planes for the entire industry. During the same time, Cessna’s sales of piston-
engine planes, like the Skyhawk, dropped from 8,000 per year to just 600. Cessna was
forced to lay off 75 percent of the employees at its piston-engine plane factories (Cessna
also makes business jets and larger planes) and eventually stopped making piston-
engine planes altogether. However, after the economy improved and the U.S.
government approved the General Aviation Revitalization Act (barring product liability
lawsuits on any plane over 18 years old), Cessna decided to start building its legendary
Skyhawks again.
This is where you come in. With nearly 20 years in the company, your first job with
Cessna was teaching Cessna dealers how to service and maintain single-engine planes.
But now, with profits flowing again and the company’s legal risk greatly reduced thanks
to the Revitalization Act, you’ve been made the vice-president of Cessna’s “new”
single-engine business. It’s your job to rebuild this part of the business from the ground
up. And because pilots tend to remain loyal to the kind of airplane on which they
learned to fly, much depends on your success or failure. If you can rebuild Cessna’s
singleengine business, the pilots who learn to fly on today’s Cessna Skyhawks will be
buying Cessna business jets 20 years from now.
One of the advantages of starting completely over is that you get to design the entire
production facility, from its location, to the new workers, to the suppliers, everything is
up for grabs. For instance, Cessna does most of its production in Wichita, Kansas. But
since it left the single-engine plane business, Wichita mostly produces a small number
of highly customized jets each year, just the opposite of your business, which is a high
number of standardized, single-engine planes. So, given the differences, you locate the
new single-engine plane factory in Independence, Kansas, two hours away by car, and
only 40 minutes away in one of Cessna’s small planes. Along with a new location,
you’re debating taking a new approach to manufacturing planes by using production
teams. This decision may strike some colleagues as radical, particularly at conservative-
minded Cessna where, one of your fellow managers admitted, “we probably got into a
mode of doing things for the future based on how we’d always done things in the past.”
But the more you think about it, the more you are convinced that it is the right decision.
Instead of using a standard production line where each worker does just one task, you
are thinking about using teams to assemble Skyhawks and other single-engine planes. In
an incredible departure from the engineeringbased standards in which the motions of
every worker on the assembly line are studied for time, cost, and efficiency
implications, production teams would be completely responsible for assembling the
planes and for costs and quality.
You expect to see several benefits from a team-based approach, increased customer
satisfaction from improved product quality, faster, more efficient production, and higher
employee job satisfaction. A few things worry you, however. Despite all of their
promise, teams and teamwork are also prone to significant disadvantages. They’re
expensive to implement. They require significant training. And they only work
about a third of the time they’re used. So, despite their promise, you can’t ignore the
reality that using teams would be quite risky for Cessna.
Still, you can’t help thinking that teams could pay off and that there might be ways for
you to minimize the risk of failure. For example, because the plant will be in a new
location, Independence, Kansas, you get to start with a brand new workforce. What
kinds of people should you hire for teamwork? What kinds of skills and experience Will
they need to succeed in a team environment? If you decide to take the plunge and use
teams, how much authority and responsibility should you give them? Should they be
limited to just advising management, or should you make them totally responsible for
quality, costs, and productivity? Finally, while you’re considering using teams on the
assembly line, are there other places in which you might use teams? Not all teams are
alike. Maybe there are other places in which teams could contribute to the success of
Cessna’s “new” single-engine plane-manufacturing facility?
If you were in charge of Cessna’s “new” single-engine factory, what would you do?