The case follows the innovations of Gooru, a nonprofit with global reach that uses technology to empower learning experiences, from early childhood through lifelong studies, tailored to each student's needs. Gooru assesses students' current knowledge and provides them and their educators with the areas and guidance for improvement, as well as a scope of learning opportunities. It licenses its "GPS for learning.By October 2023, Gooru had been in operation for a dozen years, had received more than $35 million in grants, and was serving institutions and individuals including U.S. K-12 schools, the U.S. Department of Defense, SAP in Silicon Valley, and customers in India, South Africa, and the Middle East. A central question that Gooru now faces is whether it can scale significantly toward its educational goals while remaining a nonprofit.

Tesla, an extraordinary innovator in the automotive industry and pace-setter for manufacturing electric vehicles (EVs), was founded in 2003 by Martin Eberhard and Marc Tarpenning with the vision of creating a car manufacturer that was also a technology company. Tesla set out to integrate innovative battery technologies, computer software, and a proprietary electric motor system to produce highly attractive, zero-emission vehicles. The case introduces the history and challenges faced by the early EV industry and how Tesla reshaped it, revolutionary innovations initiated by Tesla, and its sustaining strong performance. The challenges of traditional automotive companies' transitions to EVs is discussed, especially with regard to driving range and charging, and how Tesla changed the game by introducing its Roadster in 2008. During the next 14+ years Tesla achieved the distinction of producing the first best-selling global vehicle powered by batteries. Included in the case is how Tesla questioned traditional assumptions in the automotive business model - and how it leveraged digital technology capabilities to introduce the next practices in vehicle design, manufacturing, sales and service, pricing, and customer engagement. The case explores the transformation in customer experience and vehicle management as Tesla made its automobiles "connected" with software and sensors, and introduced new capabilities in remote tracking, vehicle intelligence, remote servicing, and the potential for autonomous driving. The case concludes by highlighting some of the challenges Tesla faced with wide adoption of EV technology including the market valuation of its stock, and the emergence of several competitors such as new EV manufacturers and traditional automakers switching to EV.

The case follows innovations by Drishti, a start-up company that uses artificial intelligence (AI) and computer vision to provide manufacturers with granular process data on manual assembly, giving them a system-wide view into their manufacturing operations. The firm was founded in 2016 by Dr. Prasad Akella, Dr. Krishnendu Chaudhury, and Dr. Ashish Gupta, who all had extensive experience in industrial process automation. They prioritized the value of enhancing human potential in an increasingly automated world. Noting the limitations of traditional manufacturing line performance evaluation and process improvement, Drishti Technologies presented new capabilities for real-time monitoring and performance improvements. This case is about entrepreneurs creating a new software in an established industry. The case also describes the core functionality and solutions developed from the new software, value provided to customers, and the strategic business model choices faced by the leadership in moving from start-up to scale.

A leading cement producer in southern India, Madras Cement is having trouble controlling costs due to its disorganized reporting processes. This case documents the company's two attempts to resolve these issues with the implementation of an Enterprise Resource Planning (ERP) system. The company's first attempt fails. After a company leader takes the bold step of admitting he made mistakes during this effort, Madras is ready to dig in and make the necessary changes to make the second attempt a success. The case initially seems to be about software implementation, but it is really a story about change management, transformation through transparency, business centric approaches, and the creation of a new social architecture. The company uses innovation to develop new processes that can ultimately be applied to other organizations, allowing the merger and acquisition process to begin.

This case takes students through the evolution of LEGO's business model from a traditional product-centric "make and sell" model to a more customer-centric "anticipate and lead" model in which products are co-created with customers, and customers are leveraged as a key factor in the company's innovation strategy. It begins with LEGO's struggles in the late 1990s to early 2000s, as competitors and imitators posed threats to LEGO as did the increasing alternative modes of electronic and Internet-based play. LEGO posted losses for a handful of years, and the company's culture waned. The case then takes students from the early 2000s into 2013, a period through which LEGO underwent significant transformation, which began with a new CEO, Jørgen Vig Knudstorp. The case highlights the company's evolution through three lenses - its organizational evolution, community evolution, and technological evolution.

After settling a $78-million lawsuit with a St. Louis woman who was struck by one of its drivers, Domino's Pizza decided to eliminate its 30-minute delivery guarantee and transform its business model through innovations in the areas of technology, social architecture, and operations. The company provided consistency of experience for customers by introducing its Pizza Tracker - a web-based application that allowed customers to track their pizza at each stage of the process - standardizing the layout and processes used in each of its stores, and providing more transparency into employee performance. Students are asked to evaluate how Domino's used technology and innovation to improve efficiency, quality, customer relationship management (CRM), and employee relations as well as assess its change management process.

How do you convince American parents living in the Midwest to hire tutors from India? How do you convince them to hire a tutor that they and their children will never meet in person? Can you build a personal connection between students and tutors when they are separated by thousands of miles and come from vastly different cultures? These are questions that faced Krishnan Ganesh as he began thinking about remote tutoring. A year later he founded TutorVista, an internet-based remote tutoring services company. So far, the remote tutoring firm seems to have the right answers to all of the questions above.

Jim Bush, Executive Vice President of American Express (Amex) World Service, was confronted with a challenge in the mid 2000s: After working for Amex for 24 years, he began to worry that the company was focusing too much on cost reduction. Customer service was eroding as the company strove to stay competitive during hard economic times. In response, he led the organization in a large-scale reinvention of its customer service strategy with an initiative called Relationship Care. By empowering employees with technology and information, Amex greatly improved its customer service and profits. Moving forward, students must help Amex address the challenges of taking "Relationship Care" global.

This case study on India's wireless giant Bharti Airtel (Airtel) is the second of two cases on the company that show how the firm exemplifies many of the tenets set forth in the book The New Age of Innovation by CK Prahalad and MS Krishnan. Case B presents the students with the varied strategies that Airtel has pursued to become one of the most profitable wireless telecommunications companies in the world, despite the fact that it operates in one of the poorest countries on Earth. Airtel changed the industry by moving away from such standard metrics as Average Revenue Per User (ARPU) and has employed alternative measurements for success. It has also relied heavily on outsourcing non-core functions and designed unique Value-Added Services (VAS) for its varied customer base. The case asks students how Airtel can maintain its culture of innovation while growing quickly. How will it be able to remain agile, entrepreneurial, and flexible in the face of the necessary standardization that accompanies global expansion?

India's wireless giant Bharti Airtel (Airtel) exemplifies many of the tenets set forth in the book The New Age of Innovation by CK Prahalad and MS Krishnan. Divided into two segments, Case (A) asks students to analyze the Indian environment and Airtel's capabilities in order to determine strategies for growth. Case (B) reviews the strategies Airtel pursued and the subsequent results.

This is an MIT Sloan Management Review article. In an often overemphasized focus on efficiency, many companies turn to packaged information technology systems to manage business processes. University of Michigan Business School professors C.K. Prahalad and M.S. Krisnhan suggest they should be more concerned with strategy--and getting line managers and IT managers to use information systems in ways that facilitate strategic change. A new applications-portfolio scorecard helps managers assess information infrastructure before making investments. Six key considerations are: each IT application's role in strategy, whether the knowledge embodied in the application (say, salaries in a payroll application) is stable or evolving, how much change will be needed, where the application will be sourced, whether the data are proprietary or public, and the application's freedom from conformance defects. Those parameters differ for different functions. Only those companies that deeply analyze what they need from each IT application will acquire the right portfolio. The authors' work with 500 executives reveals that few managers believe their information infrastructure can handle the pressures from deregulation, globalization, ubiquitous connectivity, and the convergence of industries and technologies. Though fully aware their organizations lack rapid-response capability or flexibility, the managers rarely knew how to fix the disconnection between the quality of IT infrastructures and the need for strategic change. Considering that information-infrastructure expenditures are generally 2% to 8% of companies' revenues, new measures to address the disconnection are essential. A corresponding change in the mind-sets and skill sets of smart line managers and IT managers also helps improve overall competitiveness.

Software applications are now a mission-critical source of competitive advantage for most companies. They are also a source of great risk, as the Y2K bug has made clear. Yet many line managers still haven't confronted software issues--partly because they aren't sure how best to define the quality of the applications in their IT infrastructures. Some companies such as Wal-Mart and the Gap have successfully integrated the software in their networks, but most have accumulated an unwieldy number of incompatible applications--all designed to perform the same tasks. The authors provide a framework for measuring the performance of software in a company's IT portfolio. Quality traditionally has been measured according to a product's ability to meet certain specifications; other views of quality have emerged that measure a product's adaptability to customers' needs and a product's ability to encourage innovation. To judge software quality properly, argue the authors, managers must measure applications against all three approaches. Understanding the domain of a software application is an important part of that process. The domain is the body of knowledge about a user's needs and expectations for a product. Software domains change frequently based on how a consumer chooses to use, for example, Microsoft Word or a spreadsheet application. The domain can also be influenced by general changes in technology, such as the development of a new software platform. Thus, applications can't be judged only according to whether they conform to specifications. The authors discuss how to identify domain characteristics and software risks and suggest ways to reduce the variability of software domains.