Open Access

In its 100+ years of company history, IBM reinvented itself multiple times. In the last 20 years, IBM had shifted from individual products to integrated solutions and moved to become a globally integrated enterprise with standardized processes. In 2014, the expanding adoption of social, mobile, analytics, and cloud (SMAC) technologies generated excitement in the industry. IBM believed these technologies presented a huge growth opportunity. Simultaneously, management viewed SMAC technologies as disruptive forces demanding transformative changes to how IBM worked. And introducing new ways of working to 400,000 employees in 175 countries was a daunting task. Based on personal interviews with 17 IBM business and IT executives, the case illustrates organizational challenges of introducing current technologies that even providers of these technologies face – in other words, when they “eat their own cooking.” It demonstrates the difficulties large companies face when implementing technologies that students use daily and take for granted.

As businesses grow and diversify, they almost inevitably make their range of offerings more complex. Complexity brings costs - but smart use of today’s digital technologies can help companies finesse the trade-offs between complexity´s costs and benefits. Imagine a retailer that has 10 million products and hundreds of variations for each product yet keeps it simple for customers to make a choice. Impossible? Not today. Amazon.com Inc. creates value from its product complexity with simple customer-facing processes, such as search, ratings, reviews and suggestions. Now imagine a diversified high-tech company with locally differentiated products in 60 categories in more than 100 different countries. A mess of internal processes and systems? Not necessarily. Royal Philips creates value by providing locally relevant products to different markets, while keeping the vast majority of its processes standardized on digitized platforms. Until now, managing business complexity has usually involved a trade-off. This trade-off forced companies to compromise between creating value from complexity and benefiting from the efficiencies of simplicity. As businesses entered new geographies, developed new products, opened new channels and added more granular customer segments, they made their offerings more complex with the intention of adding value. But, as an almost inevitable consequence, companies also made it more difficult for customers to interact with the company and more unwieldy for employees to get things done. However, with today´s increased digitization, companies can finesse this trade-off; they can increase valueadding complexity in their product offerings while keeping processes for customers and employees simple. Our research suggests that companies operating in this "complexity sweet spot" outperform their competitors on profitability. In this article, we explain how companies achieve this breakthrough in the digital world.

The modern industrial corporation encompasses a myriad of different software applications, each of which must work in concert to deliver functionality to end-users. However, the increasingly complex and dynamic nature of competition in today’s product-markets dictates that this software portfolio be continually evolved and adapted, in order to meet new business challenges. This ability – to rapidly update, improve, remove, replace, and reimagine the software applications that underpin a firm’s competitive position – is at the heart of what has been called IT agility. Unfortunately, little work has examined the antecedents of IT agility, with respect to the choices a firm makes when designing its “Software Portfolio Architecture.” We address this gap in the literature by exploring the relationship between software portfolio architecture and IT agility at the level of the individual applications in the architecture. In particular, we draw from modular systems theory to develop a series of hypotheses about how different types of coupling impact the ability to update, remove or replace the software applications in a firm’s portfolio. We test our hypotheses using longitudinal data from a large financial services firm, comprising over 1,000 applications and over 3,000 dependencies between them. Our methods allow us to disentangle the effects of different types and levels of coupling. Our analysis reveals that applications with higher levels of coupling cost more to update, are harder to remove, and are harder to replace, than those with lower coupling. The measures of coupling that best explain differences in IT agility include all indirect dependencies between software applications (i.e., they include coupling and dependency relationships that are not easily visible to the system architect). Our results reveal the critical importance of software portfolio design decisions, in developing a portfolio of applications that can evolve and adapt over time.

In 2016, German car manufacturer the Audi Group (AUDI AG) was working on an expanding array of digital innovations. The goals of these innovations varied, and included strengthening customer- and employee-facing processes, digitally enhancing existing products, and developing new, potentially disruptive business models. Audi's IT unit was critical to each of these efforts. This case examines the different ways in which digitization can help to enhance and transform an organization's processes, products, and business models. The case also highlights the challenges that may arise as organizations attempt to expand and diversify their portfolio of digital innovations.

The digital economy has created intense demands for innovations. Companies are responding in part by creating new digital products and services to meet increasing customer expectations. MIT CISR findings indicate that product variety is NOT directly related to firm performance, and IS related to increased difficulties for costumers and employees.