Search results

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.

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.

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.

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

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.

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.

Kaleidofin was co-founded in 2017 by Puneet Gupta and Sucharita Mukherjee; former CFO and CEO of IFMR (Institute for Financial Management and Research) Holdings Pvt Ltd. As part of their roles at IFMR, Gupta and Mukherjee focused on designing products and developing technology to push for financial inclusion. In their field interactions, the co-founders had an epiphany of the challenges faced by people while trying to save towards important life goals. They saw an opportunity in the large segment of financially under-served people in India and quit their jobs to start Kaleidofin. Kaleidofin was conceptualised as a digital platform that offers customised financial solutions to help customers meet their life goals. The start-up partnered with mutual fund companies for solutions on one hand and network partners (NGOs, microfinance organizations, cooperative banks) on the other for access to their existing customers.

Kaleidofin grew from 50 customers in January 2018 to 15,000 customers by March 2019. Aiming to grow to 1 million customers in the next 30 months Kaleidofin faces a dilemma about its future course. The start-up could continue to grow by expanding its current target segment which is the low-income households and preserve its vision at the risk of increasing costs. The second option would be to look at other potential target segments, such as, middle-income households and risk diluting their vision. The case study highlights the unique customer-centric model of Kaleidofin and the need for start-ups to understand the value proposition of their products/services.