Case studies

In November 2005 Fidelity Homestead, a savings bank in Louisiana, began noticing suspicious charges from Mexico and southern California on its customers' credit cards. More than a year later, an audit revealed peculiarities in the credit card data in the computer systems of TJX Companies, the parent company of more than 2,600 discount fashion and home accessories retail stores in the United States, Canada, and Europe.

The U.S. Secret Service, the U.S. Justice Department, and the Royal Canadian Mounted Police found that hackers had penetrated TJX's systems in mid-2005, accessing information that dated as far back as 2003. TJX had violated industry security standards by failing to update its in-store wireless networks and by storing credit card numbers and expiration dates without adequate encryption. When TJX announced the intrusion in January 2007, it admitted that hackers had compromised nearly 46 million debit and credit card numbers, the largest-ever data breach in the United States.

After analyzing and discussing the case, students should be able to:

• Understand imbedded operational risks

• Analyze how operational risk decisions are made in a firm

• Understand the challenges in the electronic payment transmission process, which relies on each participant in the process to operate best-in-class safety systems to ensure the safety of the entire process

• Recognize the sophistication of IT security threats

Understand imbedded operational risks

Analyze how operational risk decisions are made in a firm

Understand the challenges in the electronic payment transmission process, which relies on each participant in the process to operate best-in-class safety systems to ensure the safety of the entire process

Recognize the sophistication of IT security threats

After it introduced the extremely successful Droid smartphone into the market in 2009, Motorola quickly moved to develop the next-generation Droid 2 before the next wave of smartphones (including the rumored iPhone 4) flooded the market. The development process was moving smoothly for the company when Verizon, its biggest partner, dropped a bombshell. It wasn't happy with the mechanical camera button on the Droid 2 (citing customer feedback) and wanted it to be changed to a software button like the iPhone's. This request immediately placed Motorola in the proverbial horns of a dilemma. On the one hand, it couldn't brush away the request of its biggest and most important partner. On the other hand, changing the camera button now would mean delaying the Droid 2's entry into the market. Should the Droid 2 team remove the camera's hardware button in favor of a software button per Verizon's request, or not?

John Smith, the product manager, leads the cross-functional Droid 2 team. The case setting is an emergency “war room” meeting to address this critical issue, just weeks prior to launch. John's objective is to obtain the salient facts and opinions of team members quickly so he can make an informed recommendation to his boss by the end of the day. He is concerned that this last-minute request for a design change will not only threaten to delay the launch, which would have significant financial implications, but could potentially create deep fissures in a hitherto effective team that had been running like a well-oiled machine.

The case puts students in a situation that simulates a real-world discussion and allows them to experience what it is like, as a product manager, to orchestrate a meeting with cross-functional teams that have conflicting priorities and agendas. It illustrates the challenges a product manager faces while striving to make important decisions with little or no direct authority over the various teams.

After reading and analyzing this case, students will be able to:

• Experience the dynamics of cross-functional teams in product management

• Practice running effective and productive meetings

• Practice bringing together various personalities and points of view

• Understand the importance of setting goals and clear expectations

• Internalize the importance of building relationships and influencing teams, even when you do not have direct authority

Experience the dynamics of cross-functional teams in product management

Practice running effective and productive meetings

Practice bringing together various personalities and points of view

Understand the importance of setting goals and clear expectations

Internalize the importance of building relationships and influencing teams, even when you do not have direct authority

Supplements the (A) case.