The CEO is clearly the most important executive when it comes to creating and implementing organizational strategy. Who’s the second most important executive for strategy?
The standard answer is probably the Chief Operation Officer — especially in terms of carrying out the strategy. But I’m starting to think that the COO is only the third or fourth most important strategic officer. So, who’s number 2? I’m leaning towards the head of Human Resources. Let’s call him or her the Chief Human Resources Officer or CHRO.
I’m leaning toward the CHRO because I’ve always believed that the soft stuff is hard. It’s not easy to get your culture right or to motivate employees for the long haul. It is all too easy to get your strategy crosswise with your culture. As I’ve noted before , when it’s culture versus strategy, culture always wins.
Similarly, I’ve never seen a company falter because they couldn’t find enough “numbers guys”. Our B-schools just keep churning them out. On the other hand, I have seen companies falter because they couldn’t find good communicators and motivators. Understanding human behavior is much more difficult than understanding the numbers. While we can teach people the “soft arts,” it doesn’t seem to be a popular specialty at university.
What’s really pushing me toward the CHRO as strategy leader is Scott Keller and Colin Price’s book, Beyond Performance: How Great Organizations Build Ultimate Competitive Advantage. (Click here for the book or here for a white paper). Keller and Price argue that too many companies pay close attention to performance (“the numbers”) but not nearly enough attention to organizational health. Their “…central message is that focusing on organizational health — the ability of your organization to align, execute, and renew itself faster than the competition — is just as important as focusing on the traditional drivers of business performance.” This has everything to do with the “people-oriented aspects of leading an organization.” In my mind, that means the CHRO better be intimately involved.
Keller and Price present a lot of statistical evidence to buttress their case. (They are McKinsey guys, after all). There is a distinct correlation between organizational health and organizational performance. They also present five “frames” for viewing both health and performance during transformation change: 1) Aspire; 2) Assess; 3) Architect; 4) Act; 5) Advance. I’ll write more about these in the future but the bottom line is that you need to use these frames to view both performance and health to develop a sustainable, high performance organization.
While I think the CRHO could and should be a strategy leader, in my experience, it doesn’t happen very often. I’ve seen HR organizations launch very interesting programs but, too often, the programs exist in their own right rather than as strategic enablers. They don’t impede the strategy but they don’t help it either. I also see the numbers guys set the strategy and then turn to the CHRO and say, in effect, “OK, here’s the strategy, now get us the people we need.” (In technology, this happens to CIOs all the time). To be effective, the CHRO really needs to be at the strategy table.
Why wouldn’t the CHRO be invited to the strategy table? Perhaps because they understand the soft stuff but not the business. I’ve seen CHROs (and CIOs) make naive comments in strategy meetings, showing that they clearly don’t understand the business. The result is a bunch of numbers guys rolling their eyeballs and looking vaguely embarrassed. Numbers guys need to learn more about the soft stuff. By the same token, CHROs (and their staffs) need to learn more about the performance side of the business. Perhaps then, they can truly become strategy leaders.
 In my critical thinking class, we’ve been using Paul Nutt’s book, Why Decisions Fail. It’s an interesting look at debacles … “botched decision[s] that attract attention and get a public airing.” In the coming weeks, I’ll draw some examples from Nutt’s database of famously bad decisions.
In my critical thinking class, we’ve been using Paul Nutt’s book, Why Decisions Fail. It’s an interesting look at debacles … “botched decision[s] that attract attention and get a public airing.” In the coming weeks, I’ll draw some examples from Nutt’s database of famously bad decisions.
While I like the book in many regards, I think it’s a mistake to study only failures. Hopefully, business is about more than avoiding something negative. It’s also about attaining something positive. So I’ve been looking for a counterpoint — a study of why decisions succeed. I haven’t found a comprehensive study, but I did find an intriguing article from Boston Consulting Group, “Winning Practices of Adaptive Leadership Teams.” The BCG researchers interviewed 93 executives and identified five traits of successful executive teams. Here they are:
One voice — effective leadership teams “take the time to get completely aligned about the organization’s vision, values, and vital priorities, while respecting individual differences of opinion and experience.” While this implies good communication and mutual respect, it also implies that each team member has an enterprise-wide sense of responsibility. As one executive put it, “If my division is successful, but another division is not, I would not regard that as a victory.”
Sense-and-respond capacity — the most effective teams spend a lot of time surveying the environment, identifying trends, and synthesizing information. Among other things, they make heavy investments in information technology and pattern seeking software. The goal is to successfully “… monitor the external forces that drive change in their business environment.”
Information processing — the investment in IT often generates a large volume of data. The adaptive team then has to process it to create useful information. The team needs to share the data effectively and debate it transparently. Several teams developed “…highly disciplined meeting designs and agenda formats to ensure that they routinely exchange key information through a streamlined process that breaks down silos of communication.” Many teams also emphasize “overcommunication”.
Freedom within a framework — several teams spoke of “guardrails”. Within those guardrails, executives have a lot of room to maneuver; they can make their own decisions on how to get things done. As they prove themselves, the team widens the guardrails. Within the guardrails, “…failure [is] seen as a possible and an acceptable outcome. Failure is debilitating only if the lessons learned are not disseminated and applied quickly.”
Boundary fluidity — executives move both horizontally and vertically. There’s a sense that successful executives are “utility players” — any executive could fill in for any other executive if need be. There’s also a sense that silos are self-defeating. As one executive put it: “We always try to move people around so that their perspectives evolve and things don’t get stale.”
So does it work? BCG has developed an Adaptive Advantage Index and applied it to over 2,200 public companies in the U.S. The index is strongly correlated to growth in market capitalization.
Why Decisions Fail can tell you what not to do. That’s an important perspective. On the other hand, the BCG study (and others like it) can tell you how to succeed. In my opinion, that’s more important. I’d rather focus on succeeding than not failing.
When I go on a long bike ride, I usually wear a heart monitor. I like to know how hard my ticker is tocking. I also carry a smartphone with GPS in it. I like to know where I am … and where the nearest hospital is.
Let’s do a little mashup thinking. What if my heart monitor were connected to the phone and GPS? Here’s a scenario: the heart monitor notices that my heart is going haywire. It sends a signal to the phone. The phone uses GPS to locate the nearest hospital, sends an emergency call (perhaps using Amcom Mobile Connect*), along with my location. The hospital dispatches an ambulance to my GPS location to pick me up. It could save my life. And it’s all based on currently available technologies. All we have to do is mash them up.
A few weeks ago I wrote a post about how a strategist might think about healthcare costs. All the experts say that healthcare costs are bound to go up. In my experience, when all the experts point in one direction, it’s always useful to look in the other direction — just to make sure.
Several of my friends let me know that I was wrong — healthcare costs will continue to rise, if for no other reason than the government is involved. That wasn’t really my point. I was merely trying to illustrate strategic thinking. But now I am thinking about healthcare costs and I wonder if new technologies won’t have a huge impact. By and large, many of those technologies are already available. We just need to mash them up.
Here’s a simple example — the HAPIfork, which was introduced at this year’s Consumer Electronic Show (CES). The HAPIfork mashes up a fork, a timer, and (perhaps) an accelerometer to keep track of how fast you’re eating. HAPIfork measures the number of “fork servings per minute” and loads the data to a dashboard on your smartphone. You can keep track of how fast you’re eating. Apparently, eating slowly is better for you. You can adjust your behavior to be healthier.
I don’t think HAPIfork is going to revolutionize healthcare – but it hints at things to come. As the internet of things evolves, we’ll connect more and more sensors to monitor the word around us. We’ll also monitor our health with sensors that can inform us more precisely of our own condition. Am I getting dehydrated? Is my blood pressure up? Do I need to take corrective actions? A connected sensor could also alert my physician to potential trouble. Imagine, for instance, an internet toilet that uses chemical sensors to monitor your, um, output. If something is out of whack it lets you know. If something is really out of whack it lets your physician know.
Could connected healthcare reduce our costs in the long run? The real answer is that nobody knows. But it’s a question worth asking and technology worth pursuing. It’s an “unforeseen” solution that could just prove the experts wrong.
* I consult to Amcom and, yes, this is a shameless attempt to generate publicity for one of my clients.
In his book, Thinking Fast and Slow, Daniel Kahneman has an interesting example of a heuristic bias. Read the description, then answer the question.
Steve is very shy and withdrawn, invariably helpful but with little interest in people or in the world of reality. A meek and tidy soul, he has a need for order and structure, and a passion for detail.
Is Steve more likely to be a librarian or a farmer?
I used this example in my critical thinking class the other night. About two-thirds of the students guessed that Steve is a librarian; one-third said he’s a farmer. As we debated Steve’s profession, the class focused exclusively on the information in the simple description.
Kahneman’s example illustrates two problems with the rules of thumb (heuristics) that are often associated with our System 1 thinking. The first is simply stereotyping. The description fits our widely held stereotype of male librarians. It’s easy to conclude that Steve fits the stereotype. Therefore, he must be a librarian.
The second problem is more subtle — what evidence do we use to draw a conclusion? In the class, no one asked for additional information. (This is partially because I encouraged them to reach a decision quickly. They did what their teacher asked them to do. Not always a good idea.) Rather they used the information that was available. This is often known as the availability bias — we make a decision based on the information that’s readily available to us. As it happens, male farmers in the United States outnumber male librarians by a ratio of about 20 to 1. If my students had asked about this, they might have concluded that Steve is probably a farmer — statistically at least.
The availability bias can get you into big trouble in business. To illustrate, I’ll draw on an example (somewhat paraphrased) from Paul Nutt’s book, Why Decisions Fail.
Peca Products is locked in a fierce competitive battle with its archrival, Frangro Enterprises. Peca has lost 4% market share over the past three quarters. Frangro has added 4% in the same period. A board member at Peca — a seasoned and respected business veteran — grows alarmed and concludes that Peca has a quality problem. She sends memos to the executive team saying, “We have to solve our quality problem and we have to do it now!” The executive team starts chasing down the quality issues.
The Peca Products executive team is falling into the availability trap. Because someone who is known to be smart and savvy and experienced says the company has a quality problem, the executives believe that the company has a quality problem. But what if it’s a customer service problem? Or a logistics problem? Peca’s executives may well be solving exactly the wrong problem. No one stopped to ask for additional information. Rather, they relied on the available information. After all, it came from a trusted source.
So, what to do? The first thing to remember in making any significant decision is to ask questions. It’s not enough to ask questions about the information you have. You also need to seek out additional information. Questioning also allows you to challenge a superior in a politically acceptable manner. Rather than saying “you’re wrong!” (and maybe getting fired), you can ask, “Why do you think that? What leads you to believe that we have a quality problem?” Proverbs says that “a gentle answer turneth away wrath”. So does an insightful question.

I was satisficing. If only I had known.
What’s a debacle? According to Paul Nutt, it’s “…merely a botched decision that attracts attention and gets a public airing.” Nutt goes on to write that his “…research shows that half of the decisions made in business and related organizations fail.” Actually, it may be higher because, “failed decisions that avoid a public airing are apt to be covered up.”
Remember that I wrote not long ago (click here) that perhaps 70% of change management efforts fail? Now we learn that half — or more — of all business decisions fail. We’re not doing so well. Nutt has studied over 400 debacles — botched decisions that became public disasters — and has created an anatomy of why and how they happen. Nutt’s book, Why Decisions Fail, is a sobering look at how we manage our organizations and, more specifically, our decisions.
Critical thinking should help us avoid botched decisions and public debacles. I’ll be writing about critical thinking over the next several months and, from time to time, will pull ideas from Nutt’s book. Today, let’s set the stage by looking at the basics. Nutt writes that blunders happen because of three broad reasons:
Nutt also criticizes contingency theory — the idea that your situation dictates your tactics. For instance, if you’re faced with a community boycott, you should do X; if you’re faced with cost overruns, you should do Y. Nutt concludes that, “Best practices can be followed regardless of the decision to be made or the circumstances surrounding it.” The bulk of his book outlines what those best practices are.
Of course, there’s a lot more to it. I’ll outline the highlights in future posts and put Nutt’s findings in the general context of critical thinking. I hope you’ll follow along. In the meantime, don’t make any premature commitments.