Home > Articles > Business & Management

The Fire That Changed an Industry: A Case Study on Thriving in a Networked World

📄 Contents

  1. Design Principles for Adaptive Businesses
  2. Organization of the Book
  3. Basis of the Ideas
Amit Mukherjee presents four Design Principles that senior executives can apply to transform their companies into businesses that will thrive in a networked world.
This chapter is from the book

About 8 p.m. on March 17, 2000, a lightning bolt struck a high-voltage electricity line in New Mexico. As power fluctuated across the state, a fire broke out in a fabrication line of the Royal Philips Electronics radio frequency chip manufacturing plant in Albuquerque.1 Plant personnel reacted quickly and extinguished the fire within ten minutes. At first blush, it was clear that eight trays of silicon wafers on that line were destroyed. When fully processed, these would have produced chips for several thousand cell phones. A setback, no doubt, but definitely not a calamity.

At a chip factory, production takes place in “clean-room” conditions. The cleanest of such facilities have no more than one speck of dust per cubic foot. Stated differently, these facilities are ten thousand times cleaner than hospital operating rooms.2 And therein lay the problem. Fire produces smoke and triggers sprinklers. Fire and smoke take lives, and sprinklers save them, but all—fire, smoke, and water—wreak havoc on property. As they dug deeper, plant personnel found that smoke and water had contaminated millions of chips that had been stored for shipment. Damage this extensive was definitely a calamity.

Four thousand miles away, at a Nokia plant outside Helsinki, a production planner who was following a well articulated process for managing chip inflows from Philips failed to get a routine input he needed from Philips. The failure could well have been an anomaly. Even so-called Six Sigma facilities (of which, despite the hype about the term, there are very few anywhere) produce 3.4 defects per million. Nevertheless, he informed the plant’s purchasing manager, and again following an established process, they passed on word of a possible problem to Tapio Markki, the top component purchasing manager.

In Albuquerque, Philips engineers and managers grappled with the aftermath of the fire. They realized that cleanup would take at least a week, which meant that customers would be affected, at least temporarily. Nokia and its archrival, Ericsson, accounted for 40% of the plant’s shipments. Philips management decided that their orders would be filled first when the plant returned to normal.

On March 20, Philips called its customers, including Mr. Markki. He recalls that Philips said that the disruption would last about a week. The Wall Street Journal article (cited earlier and published months later) implied that Philips had underestimated the extent of the problem.

Mr. Markki had, early in his career, worked for five years at a small semiconductor company that supplied Nokia. He told me, “I knew the cleanup would take more than one week (but) for me it wasn’t special.” Nevertheless, in a culture that encouraged discussing possible problems openly, he informed his bosses, including Pertti Korhonen, then Senior Vice President of Operations, Logistics, and Sourcing for Nokia Mobile Phones. Nokia’s production planner began checking the status of the five parts made in New Mexico once a day instead of the customary once a week. Nokia had developed this enhanced monitoring process over the prior five years. Several components—almost all from normally functioning plants—received the same treatment each year if Nokia became concerned with their maker’s performance for any reason.

A few hundred miles away, executives at Ericsson also got a call from Philips. Until this call, Ericsson’s planners and managers had not sensed any discrepancy in Philips’ performance. As such, its management had no reason to disbelieve Philips’ explanations. They certainly did not perceive a need for concern or stepped-up action.

Nokia’s intensified tracking and communications with Philips did not raise Nokia’s confidence that its partner had the problem under control. Its executives began regularly urging their counterparts at Philips to take stronger action. They also moved toward adopting the response routines they had developed for such eventualities. On March 31, exactly two weeks after the fire, Philips admitted it would need more time to fix the problem; ultimately, the plant remained out of action for six weeks.

Recognizing that Philips’ problem could affect the production of several million mobile phones, Nokia took three key steps:

  • One team of executives and engineers focused on Philips, seeking a major role in developing alternative plans. Guided by Mr. Korhonen and assisted by CEO Jorma Ollila, it pressed Nokia’s case with Philips executives, including its CEO, Cor Boonstra. Philips responded by rearranging its plans in factories as far away as Eindhoven and Shanghai.
  • A second cross-continental team redesigned some chips so that they could be produced in other Philips and non-Philips plants. Where appropriate, it consulted with Philips to assess the possible impact of its actions.
  • A third group worked to find alternative manufacturers to reduce pressure on Philips. Two current suppliers responded within five days.

The magnitude of the cooperation between Nokia and Philips cannot be fully appreciated without a few words on Philips. Once considered a leading-edge technology company, by the mid-1990s Philips was being criticized by many an analyst. Mr. Boonstra ignored their calls to dismember the company and instead spent three years reshaping it and rebuilding its reputation. In 2000, Philips’ Semiconductor Division was functioning very well.3 It had acquired several plants from IBM and boosted its production capacity 40% over 1999 levels. Its seventeen plants were churning out eighty million chips a day; these chips were used in 80% of the mobile phones sold worldwide. That year, chip volume grew 33% and revenues 55%. Despite the fire—which did not merit a single sentence in Philips’ 2000 annual report—divisional operating income rose 119%.4 This superb performance meant that Philips simply had no surplus capacity. Helping Nokia required managerial and technical effort equivalent to pulling a rabbit out of a hat.

Philips’ predicament was not unique. In 2000, the mobile phone market was growing at over 40% per annum, but so were the markets for laptops and other electronics. Component makers, ranging from chip to liquid crystal display producers, were working at capacity.5 Some consumer electronics companies were ready to pay virtually any price for key components. By midyear, Sony, Micron Technology, Dell, Sun, and even Philips itself had announced that component shortages would rein in their (very strong) financial performances. Shortages were expected to continue unabated till year-end.

At the end of March, in this market environment, Ericsson finally came to appreciate the gravity of its problem. However, for reasons about which one can only speculate, it still did not act speedily. Jan Warby, the executive who headed the mobile phone division, did not get involved till early April. By then Ericsson had very few options left.

Nokia’s initial sensing of the problem and its rapid and effective response carried the day. In the third quarter of 2000, its profits rose 42% as it expanded its share of the global market to 30%. Its quarterly statements and annual report for 2000 did not even mention the fire.

On July 20, 2000, Ericsson reported that the fire and component shortages had caused a second-quarter operating loss of $200 million in its mobile phone division. As such, annual earnings would be lower by between $333 million and $445 million.6 Six months later, it reported divisional annual losses of $1.68 billion, a 3% loss of market share, and corporate operating losses of $167 million. It also announced the outsourcing of cell phone manufacturing to Flextronics and the elimination of several thousand jobs; Flextronics took over Ericsson’s plants in Brazil, Malaysia, Sweden, the U.K., and the U.S. In April 2001, it signed a Memorandum of Understanding to create Sony Ericsson; the informal negotiations that led to this step had started at the height of the crisis in July 2000, though Ericsson had denied it in public. The deal was finalized in October 2001.

Ericsson’s woes spread beyond mobile phones and continued into subsequent years. It finally returned to health in 2004, but as a much smaller company. Compared to 2000, its revenues had fallen 52%, total assets about 30%, and number of employees 52%; net income and operating income were almost, but not quite, the same.

The face of the mobile phone industry had changed forever, all because of a fire that had been contained in ten minutes.

That was an exciting story, but so what?

Since early 2001, stories about the fire have appeared in many publications and forums. Some—but only a fraction—of the articles that have appeared are listed in the endnotes of this and subsequent chapters. Collectively, these stories perpetuated several myths:

  • Myth #1: Nokia succeeded because it relied on individual effort, while Ericsson relied on teams. No individual—or even a group of individuals acting independently—could have pulled off the cross-continental, cross-organizational response that Nokia took. When I interviewed him at the Nokia headquarters at Espoo, Finland, in the spring of 2006, Mr. Korhonen made it clear that Nokia’s culture did not tolerate individualistic cowboys.

  • Myth #2: Nokia succeeded because it used superior information technology. Several software makers claimed that their software had helped Nokia, and some technology analysts wrote that IT had saved it from Ericsson’s fate. Like most large companies, Nokia could not have functioned without IT. However, IT played a supporting role, and the specific benefit it gave Nokia was so prosaic that no technology partisan that I know ever wrote about it.

  • Myth #3: Nokia succeeded because Finns are less cautious than Swedes. An explanation rooted in unfounded national stereotypes has little to teach us and is undoubtedly wrong. In any case, national culture played no role; a French executive, Jean-Francois Baril, who had spent many years in the U.S., led the building of many of Nokia’s capabilities.

  • Myth #4: Nokia succeeded because Mr. Korhonen was a brilliant crisis manager. Mr. Korhonen and Nokia replaced James Burke and Johnson & Johnson’s handling of the Tylenol cyanide poisoning as the poster child for impeccable crisis management. Academics use the story to illustrate types of crises that companies must be able to withstand and to cajole them to upgrade their supply chains. Risk management professionals use it to scare potential clients into buying appropriate insurance. In reality—and despite the fact that the Wall Street Journal article quoted Mr. Korhonen as calling the situation a “crisis”—Nokia successfully avoided the crisis that engulfed Ericsson. A long way into our conversation, perhaps after he felt that I understood what Nokia had really done, Mr. Korhonen said:

    • Externally, the fire has been a much bigger thing than internally. For us, it has been business as usual. We have had to manage many such things.

Mr. Korhonen did play a key role—but mostly during the prior five years, when Nokia created the capabilities that enabled it to shrug off a challenge that has captivated the business world. These capabilities—built into its strategy, processes, and values and supported by technology—enabled it to adapt rapidly to huge changes in the assumptions embedded in its business plans. Even today, seven years after the fire and almost eleven years after Nokia began transforming itself, only a handful of large companies can do what Nokia did in 2000.

Such a capability is exceedingly important, because we live in a networked world in which each company partners with a set of other companies. A company’s network extends from its customer-facing side, through its product and technology development functions, and on to its supply network side. While such networks are critical to modern businesses, they enable shifts in market or operating conditions to rapidly propagate far beyond their origins. If a company is unable to sense such a shift and respond effectively, it can lose tremendous amounts of value, see the reputations of its senior executives tarnished, and destroy the livelihoods of thousands.

Companies—like Nokia—that can intelligently and effortlessly adjust to major shifts in market or operating conditions are Adaptive Businesses.

Design Principles for Adaptive Businesses

This book presents four Design Principles that senior executives can apply to transform their companies into businesses that will thrive in a networked world. A Design Principle is a guideline for policy, rather than a template to stamp out identical sets of tools and procedures. Indeed, I do not believe it is possible to provide replicable templates; companies must use the Principles to create their own unique solutions. The Principles are as follows:

  1. Embed sense-and-respond capabilities within normal plan-and-execute processes. The ability to detect a problem (or opportunity) early and correctly and the ability to react effectively are key determinants of competitive advantage. Unless these abilities are a part of everyday work, companies will lurch from crisis to crisis, be they big or small.

  2. Adopt strategies that promote collaborative action among network partners. As they globalize and as their supply-and-demand networks fracture, companies lose visibility into aspects of their competitive landscape. Unless they develop cooperative relationships with their partners, they will not get preferential assistance with either crisis or opportunity.

  3. Value and nurture organizational learning. Companies must collect, analyze, and share across their networks knowledge about what works and what does not. Absent such “intelligent knowledge sharing,” they will lack information to act decisively and effectively.

  4. Deploy technologies that enable intelligent adjustment to major environmental shifts. To adjust to changed conditions effectively and efficiently, companies must apply information technologies that support the prior principles.

The four Principles are deceptively simple; stating them is far easier than applying them day after day. For example, despite embarking on its transformation in 1995, Nokia has only recently become comfortable with the idea that its adaptive capabilities are inextricably interwoven into the fabric of its organization. Hewlett-Packard—another company that I will profile extensively—also began changing at the same time and is still institutionalizing the capabilities it has built.

The difficulty of implementing the Principles is what gives them their great power; collectively they change how work is performed on a day-to-day basis. For example, to sense and respond, one might need the preferential help of a partner company. This presumes that the companies look after each other’s interests. Technology aids the ability to sense and respond, but unless people can make sense of what they are sensing, all the effort will be for naught.

Companies also must consider major organizational changes in order to marshal and deploy people with the skills needed to design, create, and manage their networks. Many may decide to centralize these people in a coherent group, while others may decide to keep them dispersed but well linked. In either case, they must consider appointing a senior executive to give them a voice in top management deliberations. Whether or not he or she actually holds the title formally, this executive, the Chief Network Officer, will bear primary responsibility for the four Design Principles. No company that I know of, including Nokia, currently uses this title; nevertheless, a couple of key people at Nokia have played the Chief Network Officer’s role well.

Seen through the lenses of Adaptive Businesses and network management, Nokia and Philips treated each other as preferential partners and won. Ericsson, which had no one to “watch its back” when the chips were down (literally and figuratively!), lost. Ironically, the lesson Ericsson took away was not one of codependence; instead, it resolved never again to become dependent on a single supplier.

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020