2.1.2: Case Study- Boeing and the Outsourcing Dilemma

Case Study: Boeing and the Outsourcing Dilemma

Engineering Dreams, Protecting Secrets – The Global Gamble of Building Big

Setting the Stage (A Plane That Could Change Everything)

In 2003, the mood at Boeing’s Seattle headquarters was charged with ambition. The company had just announced its most daring commercial aviation project in decades: the Boeing 787 Dreamliner.

This new aircraft would be lighter, faster, more fuel-efficient, and built using carbon fiber composites rather than traditional aluminum. It would revolutionize long-haul travel—and Boeing intended to build it faster and cheaper than any wide-body jet before it.

But to do that, Boeing would need help.

Enter Global Outsourcing

Boeing made a bold decision: outsource 70% of the Dreamliner’s components to global partners, many of whom had never before built commercial aircraft sections at this scale.

Rather than building everything in-house, Boeing would act as a system integrator—coordinating a vast global supply chain with vendors building wings, fuselages, avionics systems, and interiors. Major components would be designed, manufactured, and even partially assembled in Japan, Italy, South Korea, Canada, and China, then flown to final assembly lines in Everett, Washington and Charleston, South Carolina using custom-built Dreamlifter cargo planes.

Among these suppliers was AVIC (Aviation Industry Corporation of China)—a state-owned Chinese aerospace conglomerate.

Manufacturing in China: Promise and Risk

AVIC was selected to build rudders and composite trailing edge components for the Dreamliner’s tail. These parts were relatively small—but strategically symbolic. Boeing hoped to deepen its footprint in the Chinese aviation market, where regulators held increasing sway over aircraft certification and sales.

But from the moment the contracts were signed, Boeing’s IP security teams were on high alert.

Why?

• China was not just a supplier—it was also a potential future competitor.
  • The Chinese government was already funding the development of COMAC, a domestic jet manufacturer expected to compete with Boeing and Airbus by the 2020s.
• Intellectual property leakage was not just theoretical—it was structural.
  • Under Chinese joint venture laws, foreign companies were often required to share proprietary information with local partners in exchange for market access.
• Cybersecurity threats were growing.

Boeing had already been the target of multiple state-sponsored cyberattacks traced back to groups operating in China.

“We want the Chinese market,” said one internal strategy memo, “but we also need to accept that what we teach today may become our competition tomorrow.”

To mitigate risk, Boeing:

• Limited the scope of AVIC’s access to proprietary design files
• Used “black box” subassembly design to conceal core engineering logic
• Implemented rigorous compartmentalization of source files and production tolerances
• Required AVIC to complete all work using Boeing-supplied machines and protocols

Still, tension simmered.

Engineering Meets Integration Challenges

By 2009, Boeing was two years behind schedule on the 787. The reasons were many: untested materials, late supplier deliveries, quality inconsistencies, and integration nightmares.

But one recurring issue was this: outsourced components didn’t always fit together.

Some Chinese-built components arrived with deviations just millimeters off—but enough to require rework. Engineers in Everett joked that the plane was “more puzzle than platform.”

A senior project manager put it bluntly:

“We were outsourcing precision work across 10 time zones, under 6 different legal regimes, and expecting it to snap together like Ikea furniture.”

The Software Side: Outsourcing Code at Altitude

At the same time, Boeing was quietly expanding its global software development outsourcing, especially in India and Russia.

Much of this was for internal tools: configuration systems, simulation software, internal dashboards, and maintenance tracking platforms. But increasingly, Boeing began outsourcing parts of embedded avionics software—code that ran diagnostic and safety systems onboard aircraft.

This triggered internal debates.

Some engineers argued that outsourcing UI dashboards or internal data platforms was fine—but anything touching safety systems or aircraft telemetry was too sensitive.
Others believed that carefully managed outsourcing, with code reviews and controlled modules, was not only safe but fiscally necessary in an industry with razor-thin margins.

To strike a balance, Boeing:

• Required all mission-critical code to undergo internal security and reliability audits
• Enforced supplier development under strict Software Engineering Institute (SEI) standards
• Maintained full internal ownership of system architecture
• Divided software into “low risk” and “high risk” modules

Even so, when one news report in 2019 revealed that parts of the 737 MAX software had been written by outsourced contractors making $9/hour, Boeing faced public scrutiny—regardless of whether the code itself caused the issue.

The optics were damning.

“Boeing is outsourcing safety,” critics said.

Internally, project managers were reminded of an old truth:
Outsourcing doesn’t remove accountability. It just changes how you exercise it.

The IP Balance Sheet

So—was outsourcing worth it?

By 2021, Boeing’s China-based suppliers had delivered millions of parts for 787s, 737s, and 777s. The Dreamliner program, despite delays, became a commercial success. And Boeing retained (for now) a strong presence in the Chinese aviation market.

But COMAC had also launched the C919—a narrow-body jet with clear echoes of Boeing and Airbus designs. Boeing’s IP had not been stolen, but some of its thinking had certainly been mirrored.

The PMs in Seattle, Shenzhen, and Shanghai all understood one thing:

“If you’re going to outsource manufacturing or software development to a potential rival, you’d better build a system of containment, measurement, and compartmentalization—or risk being out-built in 10 years.”

Lessons for Project Managers

This case illustrates the power and peril of outsourcing complex work across borders.

As a PM, your role is to:

• Decide what’s strategic and what’s tactical
• Protect core IP while enabling global scale
• Manage multiple vendor relationships—some of which may evolve into competitors
• Segment workflows so that no one vendor has full ownership of your crown jewels
• Oversee delivery while maintaining compliance, quality, and integration

Outsourcing doesn't just lower costs. It exposes your architecture, your thinking, and sometimes your future. But with the right boundaries, it can build dreams at a scale no internal team ever could.