Search results

1 – 6 of 6
Case study
Publication date: 13 November 2019

John-Gabriel Licht, Jamie O’Brien and Marc Schaffer

This case has three primary objectives. First, it allows students to think through a conceptual cost and benefit analysis associated with the decision-making process in line with…

Abstract

Theoretical basis

This case has three primary objectives. First, it allows students to think through a conceptual cost and benefit analysis associated with the decision-making process in line with basic economic thinking. Students will revisit core concepts of marginal benefit vs marginal cost, the notion of opportunity costs and the role of sunk costs in this type of analysis, while also highlighting the nature of market structure, oligopolies and competition across firms in an industry. The second goal of this case is to consider the role of business ethics in the DC-10 case: specifically, to consider the potential influence of moral awareness and moral disengagement in unethical decisions made by McDonnell Douglas. Students will develop an understanding of these concepts and solidify their learning by applying them to the case and engaging in active discussion. Finally, the third goal of the case allows students to explore organizational culture and specifically offer recommendations for organizations thinking about the link between decision-making, the role of ethics and culture.

Research methodology

The technical reports released by the National Transportation Safety Board along with secondary data such as available public data such as news reports were used to round out the synopsis of the case study.

Case overview /synopsis

This case explores the accidents of two McDonnell Douglas DC-10s in the early 1970s at the onset of the jumbo jet race between Boeing, Lockheed and McDonnell Douglas. It explores the series of events during the “Windsor Incident” in 1972 and the subsequent accident over Paris in 1974. It explores the reasons why the cargo door on the DC-10 was faulty and subsequently why the door was not fixed. It examines the interplay of industry suppliers such as McDonnell Douglas and how they interact with oversight authorities such as the Federal Aviation Authority. The Teaching Note focuses on the economic thinking at McDonnell Douglas, behavioral ethics and organizational culture.

Complexity academic level

This case is best explored over a 90 min session but could be expanded to take up one 3 h session. The authors have used this case format in an undergraduate organizational behavior class, an MBA Leadership and Organizational Change class, and an MBA Economics of Managers class. It works particularly well in the MBA setting, as students with work experience can see the links between the mistakes made by McDonnell Douglas and their workplaces.

Case study
Publication date: 12 July 2023

Jamie O'Brien and Anna R. Antos

The technical report released by the National Transportation Safety Board, along with the primary flight cockpit voice recorder data and archival interview data, were used as the…

Abstract

Research methodology

The technical report released by the National Transportation Safety Board, along with the primary flight cockpit voice recorder data and archival interview data, were used as the basis for this case. Other available public data such as news reports were used to round out the synopsis of the case study.

Case overview/synopsis

United Express Flight 5925 was a scheduled commuter passenger flight operated by Great Lakes Airlines with a Beechcraft 1900 twin turboprop. It was a regularly scheduled flight from Chicago O'Hare International Airport to Quincy, Illinois, with an intermediate stop in Burlington, Iowa. Drawing from various first-hand accounts (cockpit voice recorder) and secondary evidence (news reports, archival interview data, and online sources) of the tragedy, the case provides a detailed account of the key events that took place leading up to the accident at Quincy regional airport. The case describes how the radio interactions, a jammed door and degradation of situational awareness all contributed to the accident. Through many of the quotes in the text and eyewitness accounts, readers gain an understanding of the impressions and perceptions of the pilots, including how they felt about many of the critical decisions in the last minutes of the flight and the situation at the airport.

Complexity academic level

When the authors teach this case, the students are required to read it as pre-reading before class. Various readings and materials (see supplemental readings below and Exhibit 3) are made available to students before class, and the instructor can choose to use some of these materials to further explore areas of interest. This case is best explored over a 90-min session but could be expanded to take up one 3-h session. This case can be covered in an undergraduate senior capstone organizational behaviour seminar, any general organizational behaviour class (including introductory in nature), an undergraduate communication theory class or an MBA class that focuses on applied organizational behaviour concepts. It works particularly well in the MBA class, as students with work experience can make the links between the behaviours explored in the case and their everyday workplaces.

Case study
Publication date: 15 February 2022

Jamie O’Brien and John-Gabriel Licht

The technical reports released by the National Transportation Safety Board, along with secondary data in the form of available public data, such as news reports, interviews and…

Abstract

Research methodology

The technical reports released by the National Transportation Safety Board, along with secondary data in the form of available public data, such as news reports, interviews and memos, were used to round out the synopsis of the case study.

Case overview/synopsis

This case explores the events that led up to the crash of United Airlines Flight 717 (for anonymity), in Sioux City, Iowa, on July 19, 1989, and the subsequent investigation. The case uses secondary sources to highlight the positive team interactions between the pilots that led to the crash landing not being as catastrophic as it might have been with 185 survivors in an extreme crisis scenario. The teaching note focuses on the importance of cognitive bias, psychological safety and teamwork in a crisis situation, and practical recommendations for managers at all levels.

Complexity academic level

Organizational Behavior at the undergraduate and graduate level. Leadership and Change at the graduate and graduate level.

Details

The CASE Journal, vol. 18 no. 2
Type: Case Study
ISSN: 1544-9106

Keywords

Case study
Publication date: 1 March 2019

Jamie O’Brien

This case has two primary purposes. First, it allows students to examine how cognitive bias can affect decision making in stressful situations. Students explore why individuals…

Abstract

Theoretical basis

This case has two primary purposes. First, it allows students to examine how cognitive bias can affect decision making in stressful situations. Students explore why individuals make flawed choices. They learn about how managers shape the context and the process through which teams make decisions. For instance, automation can create a climate in which people then struggle to cope with the unexpected when it happens. Students examine why individuals make these systematic errors in judgment. The case demonstrates that leaders need to be aware of the traps that individuals and teams encounter when they make decisions in crisis situations, and it enables students to discuss the strategies that leaders can employ to avoid these traps. Second, the case provides an opportunity to examine a catastrophic failure in detail. Students discover that it can be nearly impossible to identify a single factor that caused the failure. Instead, they learn how to apply multiple theoretical perspectives to examine a serious organizational breakdown. They become familiar with important concepts from behavioral decision theory, such as complex systems theory and how it interacts with cognitive bias.

Research methodology

The technical report released by the French Aviation Authority along with the primary flight cockpit voice recorder data were used as the basis for this case. Other available public data such as news reports were used to round out the case study.

Case overview/synopsis

On June 9, 2009, on a routine flight from Rio de Janeiro to Paris, Air France 447 (AF 447), carrying 220 people crashed in the mid-Atlantic Ocean. Drawing from various first-hand accounts (cockpit voice recorder) and secondary evidence of the tragedy, the case provides a detailed account of the key events that took place leading up to the accident. The case describes how the pilots on AF447 were confronted with a scenario they had not faced before, and through the confusion made a series of errors. Through many of the quotes in the text, readers gain an understanding of the impressions and perceptions of the pilots, including how they felt about many of the critical decisions and incidents during the last minutes of the flight. The case concludes by highlighting the main findings of the BEA report.

Complexity academic level

This case study is appropriate for undergraduate students studying organizational behavior. It is also appropriate for MBA-level leadership and behavior classes.

Case study
Publication date: 6 July 2020

Jamie O’Brien and Rebecca A. Bull Schaefer

On the evening of December 29, 1972, Eastern Air 401 (EA401) was on a routine flight from New York to Miami. Despite EA401 flying one of the most advanced aircraft at the time…

Abstract

Case overview/synopsis

On the evening of December 29, 1972, Eastern Air 401 (EA401) was on a routine flight from New York to Miami. Despite EA401 flying one of the most advanced aircraft at the time (the Lockheed L-1011), it crashed in the Florida Everglades killing 101 of its 176 passengers. Drawing from various first-hand accounts (cockpit voice recorder) and secondary evidence (news reports and online sources) of the tragedy, this teaching case provides a detailed account of the key events that took place leading up to the accident. The case describes how the pilots on EA401 were confronted with a simple scenario, a landing gear bulb not working in the cockpit, and through the distraction that ensued made a series of errors. Through many of the quotes in the text, readers gain an understanding of the impressions and perceptions of the pilots, including how they felt about many of the critical decisions and incidents during the last minutes of the flight. The case concludes by highlighting the main findings of the NTSB report.

Complexity academic level

Depending on individual course objectives, this case can take two or one day to debrief. Specifically, if this case is used in an organizational behavior course, most of the case questions could be discussed in one day. However, if this case is used in a capstone HRM or group dynamics type course on teams and team training and performance, a second day could be used to develop documentation outlining training design or performance evaluation designs.

Case study
Publication date: 20 October 2022

Randa El Bedawy and Mayar Farrag Elsayed

The case can be used to discuss leadership issues in young ventures. It also allows for a discussion of effective sales and marketing functions for a new product. The case also…

Abstract

Learning outcomes

The case can be used to discuss leadership issues in young ventures. It also allows for a discussion of effective sales and marketing functions for a new product. The case also addresses the different challenges facing certain business models in the market, and finally the importance of having a supporting team.

Case overview/synopsis

The case traces the development of an Egyptian startup software venture and the challenges faced regarding the entrepreneurship ecosystem. The startup’s main dilemma is whether to continue in its existing market or to extend elsewhere. Launching the main services of the startup is another challenge, as the market needs to be educated to see its value. Despite the success story, as a young Egyptian entrepreneur, the founder is expected to face various challenges to excel in the Egyptian market, such as financing, marketing, teamwork and self-development of the entrepreneur himself.

Complexity academic level

The case can be used at all levels, from undergraduate and MBA classes to executive seminars, because the issues it addresses are of broad interest.

Supplementary materials

Teaching notes are available for educators only.

Subject code

CSS 3: Entrepreneurship.

Details

Emerald Emerging Markets Case Studies, vol. 12 no. 4
Type: Case Study
ISSN:

Keywords

1 – 6 of 6