Apr 18 - May 8Phase 1May 8 - 27May 28 - Jun 5
How to tell whether your organization is truly adaptable.
Most of us have no trouble in coming up with examples of companies that failed to mobilize around a major new opportunity (e.g., Intel and chips for mobile devices), or procrastinated when confronted with a wrenching discontinuity (e.g., Kodak and digital photography), or struggled to let go of a beloved but dying strategy (e.g. General Motors and its bloated brand portfolio.) In most of the cases of strategic inertia I’ve come across, HR wasn’t the primary culprit, but neither was it a powerful force for proactive change. We’ve launched this hackathon with our friends at CIPD because we believe HR can play a hugely positive role in helping companies to become adaptable at their core.
I’ve always loved this quote from Ralph Waldo Emerson: “There are always two parties—the party of the past and the party of the future, the establishment and the movement.” The question is, to which party does the HR function belong? Imagine if we posed the following survey question to everyone in your company:
Which of these two statements most accurately describes the HR function in this organization?
1. HR is a powerful catalyst for change.
2. HR is a major impediment to change.
Ideally, more than 90% of your associates would pick statement #1, but I suspect this might not be the case if you ran the survey today. However, if we work together, we can start to change this. As we tackle this challenge, we need to start with a shared definition of adaptability. What, after all, is the distinction between “agile,” “resilient” “flexible,” and “adaptable?” To an extent these terms are interchangeable, and whatever the word, any definition is at least somewhat arbitrary. So instead of consulting the dictionary, let’s get clear about the sort of organizations we are trying to build.
I’m betting you’d like to work for an organization that . . .
- Never takes refuge in denial
- Is positively discontent
- Always plays offense and never defense
- Rushes out to meet the future
- Is relentlessly optimistic
- Regularly reinvents itself and its industry
- Captures more than its fair share of tomorrow’s opportunities
- Frequently surprises both its customers and competitors
. . . and does all this in the absence of a crisis. Now that would be an adaptable organization.
I like to make a distinction between operational agility, and strategic adaptability. Operational agility implies an ability to respond quickly to shifts in demand or customer preference within the boundaries of an existing business model. A great example of an initiative focused on agility would be Volkswagen Group’s new MQB manufacturing strategy. (Translated into English, Modularer Querbaukasten means Modular Transverse Matrix.) The MQB architecture allows a wide range of vehicles (Audis, Seats, Skodas and VWs) to be produced on a small number of platforms.
Strategic adaptability, by contrast, refers to a company’s capacity to reconfigure its underlying business concept, by dramatically rethinking . . .
- Its core mission
- Its primary value proposition
- The identify and nature of the end customer
- The method or channels of distribution
- Its revenue or pricing model
- The markets or industries in which it competes
- Its core competencies
- Its ecosystem of business partners
- The degree to which it is vertically or horizontally integrated
- The basic way in which it produces products and services
To take an example, we’ve all experienced Amazon’s operational agility—it’s ability to rapidly assemble our unique order from tens of thousands of SKUs and deliver it to us in day or two. But Amazon is also a case study in strategic adaptability. During it’s brief history, it has morphed from a Web-based bookseller, to an online retail platform, to a digital media powerhouse, and most recently, to a leader in cloud computing.
Amazon is rather unique in that it has changed its business model in the absence of a performance crisis. Usually, major strategic shifts are driven by a financial meltdown, or years of substandard returns. As I’ve said on numerous occasions, deep change in big companies usually happens the same way it happens in poorly governed dictatorships—infrequently, belated, and convulsively; and for the same reason—a top-down authority structure frustrates bottom-up change. All too often, by the time an issue gets big enough to attract the CEO’s attention, whether an opportunity or a threat, it’s too late to do anything but react. A case in point: By the time Google’s top brass roused themselves to do something serious about social media, Facebook had already built a nearly insurmountable lead. In my experience, the vast majority of corporate “change” programs are “catch-up” programs.
In my view, it shouldn’t require a financial crisis, swinging lay-offs, a clean sweep of the executive suite and a crippled share price to realign a company’s strategy. That’s why we need to change the way we change. Change needs to happen a whole lot faster and a whole lot cheaper than it does now.
To put it simply, we’re trying to maximize the following ratio . . .
Frequency and amplitude of strategic change
Time, treasure and trauma required to produce that change
To borrow from military doctrine, we’re trying to find ways of tightening the “OODA loop”—the time it takes in a dynamic environment to observe, orient, decide and act. On the battlefield, the army with the shortest OODA loop usually wins. The same holds true in business. If you can make sense of what’s changing more quickly, and redeploy your resources more rapidly, you win.
As the pace of change accelerates, so must the pace of strategic renewal. Indeed, one of the most important questions for any enterprise today is this: Are we changing as fast as the world around us? All to often, the answer is no. Hence this hackathon.
Given the primary role HR plays in many of an organization’s core processes (e.g., performance review, talent deployment, organizational development, change management, compensation), HR has the chance to be a true catalyst for strategic adaptability. So let’s push ourselves to imagine how HR can get out in front and raise the banner for the party of the future.
Dear hackathon participants, we’d love to hear what adaptability means to you (please provide your thoughts as a comment to this blog post). Here are a couple of questions to get you started:
- How would you define strategic adaptability?
- How would you tell whether an organization is truly adaptable (i.e., what are its distinguishing traits)?