Agility for the Strategist: the Slo Framework

"From the strategist’s point of view, agility is about one of the central challenges of organizations: adapting to changing circumstances." Agility is the fashion of the day. Companies in industries as diverse as information technology, finance, hospitality and manufacturing operate agility programs. The challenge is, however, that nobody seems to have a clear idea of what agility is or what it entails; and those who do, tend to disagree with others in the know. This is hardly surprising given the multiple roots of agility. Becoming popular as a way to organise software coding efforts in a flexible, client-oriented and scalable way, agility was initially inspired by the Toyota Production System, the “rugby” approach to innovation, and even prior total quality management principles taught by Deming. The “agility manifesto”, created in 2001 by 17 software engineers in Utah, codified some principles of software development such as “people over processes and tools”, “respond to change rather than follow a plan” and “working prototypes over excessive documentation”. These principles make sense, but they appear more operational and relevant to software development than assuaging the concerns of the strategist wondering how agile their organization is or what agile actually means from a strategic point of view. In my work with organizations including NASA’s Johnson Space Center, I have developed a framework that can help to pin down agility for strategists and leaders. In 2014 the Johnson Space Center initiated a programme referred to as JSC 2.0 that aims to make the Center “more lean, agile and adaptive to change”. I created the SLO framework as a way to spur strategic conversations about what agility might mean and entail. From the strategist’s point of view, agility is about one of the central challenges of organizations: adapting to changing circumstances. Leaders should be able to sense signals, evaluate them and take initiative; re-configure the organization accordingly and in alignment with the strategy, also subject to amendment as needed. Each of the three elements of strategy, leadership and organization (hence the SLO framework) is necessary but not sufficient; only synergy among the three can enable a company to be truly agile. Agile leaders are those who can raise their perspective from the day-to-day, sense signals, reflect on the implications of those signals, and then spur initiatives to drive their organization to do what’s needed. A variety of organizational features such as routines, worldviews and sunk costs continuously operate against this process. In this sense agile leaders are champions of questioning accepted truths. Elon Musk may be the archetype of such a leader. His initiatives in space exploration, electronic vehicles, solar energy and even tunnel-building in cities reveal his ability to read signals of what is needed and what is possible, work out the implications and then lead initiatives to take things forward, doing so in novel ways and surmounting obstacles that would stop others in their tracks. "Re-shaping business models is most often a long-term task that entails ongoing commitment." From a strategic perspective, agile organizations are able to overcome inertia and reshape their business models, balance change and stability, and build inter-organizational networks to push forward learning and influence their environments. Re-shaping business models is most often a long-term task that entails ongoing commitment. IBM’s long-term shifts from a hardware producer to a solutions provider and currently to a “cognitive solutions and cloud platform provider” is one example. GE’s various strategic shifts over the decades, such as portfolio re-shaping, the move from a manufacturing focus to service businesses, and currently its focus on becoming a digital enterprise, is another. At a strategic level agility does not have to be immediate, and indeed it cannot be for large corporations. It takes time to change the direction of a steamer. Corporations require both periodic strategic changes over time, while at the same time re-configuring their operations to maintain efficiency and responsiveness; one manifestation of the elusive capability of ambidexterity. Finally, organizational agility requires experimentation, cross-functional collaboration, re-allocation of resources to support exploration, learning, as well as active un-learning of routines and processes that are no longer relevant. Alphabet may be the archetype of an agile organization. A multitude of experiments take place; some fail (Google Glass, Dodgeball), some go on to create new multi-billion dollar markets (Google Search, Google Play), and some are emerging, showing immense promise (DeepMind, that will support a multitude of offerings supported by AI). Alphabet learns and also unlearns, shutting down experiments that don’t show results and reallocates resources to those that do. At any time, many flowers are allowed to bloom, and some of those will fill the valley. The framework below can allow strategists to evaluate their company’s agility levels and pinpoint where attention should be focused. The elements of the framework can spur strategic conversations about agility by asking the right questions about essential capabilities. These nine elements fit together like a jigsaw puzzle. Take one out, and the likelihood of achieving agility is diminished. The synergy across these components is what can lead to results. This framework boils down several agility-related concepts to their essence, in a way that can help strategists and leaders pin down what it means, evaluate their organization, and take action.

Indian government’s ‘Make in India’ campaign

The Ecosystem of Poverty: Lessons Learned from the $300 House Project

In Conversation with Prasad Kaipa

Big Idea by Nilofer Merchant

Outthink the Future

In Conversation with Michael Porter

Infrastructure in the Age of Innovation

How business and society can work together towards solving the social problems of the world

Agility for the Strategist: the Slo Framework

Error thrown