Open Access

The proliferation of convergence of digital technologies SMACIT (social, mobile, analytics, cloud, and Internet of Things) has created significant threats and opportunities to established companies. Business leaders must rethink their business strategies and develop what we refer to as a digital strategy. Our research shows four keys to successfully defining and executing a digital strategy: 1. zeroing in on a customer engagement or digitized solutions strategy to guide the transformation, 2. building operational excellence, 3. creating a powerful digital services backbone to facilitate rapid innovation and responsiveness, and 4. ensuring ongoing organizational redesign. A list of publications from the research is provided at the end of this document.

By integrating its previously separate insurance, banking and investment products around customer life events (e.g., buying a car, getting married or buying a house), USAA is able to deliver a superior customer experience. To achieve the integration, USAA had to re-architect its business by redesigning structures, roles, incentives, processes and IT systems. The USAA case provides four principles for architecting a business to provide superior customer experience, which will become increasingly important in the digital economy.

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.

Successful digital business strategies rely less on strategic analysis and big bets than on experiments and learning. Consider, for example, that Airbnb grew out of the belief that people would pay to sleep on air mattress on a stranger's floor. Similarly, Instagram started as an app for checking in and hanging out with friends (and sharing pictures) that proved complicated to use. Twitter's founders had first tried a podcasting platform, Odeo, which Apple made obsolete with iTunes. AUDI AG had to kill of its "share a car with five friends" app before rolling out more successful mobility services in a number of countries. The digital successes did not grow out of a comprehensive upfront analysis. Digital strategy emerges from an idea - often, not a particularly good idea.

Successful digital offerings are created at the intersection of what technologies can deliver and what customers want and will pay for. That point of intersection, however, has proved to be elusive. To find it, companies must experiment repeatedly, cocreate with customers, and assemble cross-functional development teams - and the insights gleaned along the way must be shared internally. In this article, we discuss how several of the nearly 200 companies we've studied have built and exercised these capabilities. We also take a close look at how one company, Schneider Electric, is using them to acquire and share customer insights.