Skip to content

Learning from the failures of others; billion-dollar lessons for next to nothing

Billion-Dollar Lessons: What You Can Learn from the Most Inexcusable Business Failures of the Last 25 Years, Carroll, Paul B. and Chunka Mui

Progress in science and engineering proceeds from the dispassionate analysis of failure. We learn more when we screw up than when we succeed. However, since Waterman and Peters In Search of Excellence,  the trend in business books has been to celebrate and analyze apparent success. In Billion-Dollar Lessons, Paul Carroll and Chunka Mui demonstrate the power of good failure analysis. They turn their attention to what can be learned from large-scale business failure. First, a necessary disclaimer; Paul and Chunka were partners of mine at Diamond Consultants in the 1990s. I already know how smart and insightful they are.

If they were to succeed simply in making failure analysis respectable, Paul and Chunka would be making a major contribution. They manage to do considerably more. First, they debunk the conventional wisdom that failure is the result of poor execution. The danger in attributing failure to solely execution factors is that it gets you off the hook from drawing useful lessons. If the failure is yours, you need only try harder the next time. If it belongs to someone else, you, of course, wouldn’t have made such foolish mistakes.

Instead, Carroll and Mui construct a compelling case that real failures stem from poor strategic thinking; identifying seven patterns of strategic failure ranging from unrealistic belief in synergy to a poor grasp of technology evolution and change. These patterns provide a valuable set of lenses to examine and assess strategic options.

There is a thread through much of the first half of the book that failure occurs when ego trumps evidence. But the authors avoid the temptation of settling on that as the underlying explanation. Actually, their awareness of temptation leads them to the another of the major contributions of this book. While ego and misdirected drive can be found in most strategic failures, ego and correctly focused drive are essential to strategic success.

The question becomes how to bring evidence to strategic debates so that it can be incorporated most effectively. Better due diligence processes can help. So can a deeper appreciation of our innate cognitive biases. While covering these topics, Carroll and Mui have a more provocative idea; they call for organizations to establish the strategic equivalent of the Catholic Church’s Devil’s Advocate. The role of the Devil’s Advocate is to argue against the proposal under consideration. Formalizing and structuring that role in organizations offers a potential counterbalance to the forces arrayed in favor of the strategic actions that Billion-Dollar Lessons call into question.

There is, of course, a website to accompany the book. There is also a Billion-Dollar Lessons blog. I’ve subscribed in the hope that it will become an ongoing source of lessons.

Knowledge work and micro-processes

[cross-posted at Fast Forward blog]

Recently, I sat through a presentation about a Sharepoint-based intranet project to improve processes within the HR group of a medium-sized organization. The process in question was one of collecting annual performance reviews throughout the organization. Using Sharepoint, the HR group and their consultants replaced Word documents, spreadsheets, and email with Infopath forms and programmatic workflows. The client was happy and the consultants had a nice demo they could show to their prospects. Nonetheless, I found myself dissatisfied.

For all the new technology deployed, this effort struck me as an example of what my old friend and mentor Benn Konsynski calls "speeding up the mess." This HR process is an instance of the micro-processes that comprise knowledge work activities in organizations.

Other examples might include:

  • Customizing an existing sales presentation for a meeting with a new prospect
  • Designing the agenda and preparing materials for an internal brainstorming meeting
  • Putting together the briefing materials for a quarterly business review meeting
  • Analyzing and making sense out of a competitor’s recent pricing announcement

These micro-processes are characterized by:

  • A small number of steps
  • Ad hoc design created by the knowledge workers responsible for the process
  • Loose definitions of the beginning and end of the process
  • Loose notions of control, sign-offs, and approvals
  • Technology-enabled, if at all, by email and office suite tools.

None of these processes were ever explicitly designed; they’ve evolved over time. The cumulative pain and productivity drag imposed by these processes is accepted as a fact of organizational life. While various technologies are offered up as ways out of the swamp, we need an overall improvement strategy to provide the necessary direction.

The appropriate strategy is readily available. It is the same strategy originally deployed by Frederick Taylor in improving the productivity of manual labor in factory settings. The late Peter Drucker summarizes this strategy nicely:

Taylor’s principles sound deceptively simple. The first step in making the  manual worker more productive is to look at the task and to analyze its constituent motions. The next step is to record each motion, the physical effort it takes, and the time it takes. Then motions that are not needed can be eliminated; and whenever we have looked at manual work, we have found that a great many of the traditionally most- hallowed procedures turn out to be waste and do not add anything. Then, each of the motions that remain as essential to obtaining the  finished product is set up so as to be done the simplest way, the easiest way, the way that puts the least physical and  mental strain on the operator, and the  way that requires the least time. Next, these motions are put together again into a "job" that is in a logical sequence. Finally, the tools needed to do the motions are redesigned. Whenever we have looked at any job-no matter for how many thousands of years it has been performed-we have found that the traditional tools are wrong for the task.
[Peter Drucker. "Knowledge worker  productivity: The biggest challenge."  California Management Review. V41, #2.  Winter 1999. pp. 79-94.]

While the strategy of “go, look, think, improve” is sound, there are some challenges in translating it successfully to knowledge work. First, the outputs of knowledge work are fluid and ill-defined. We have no widgets of constant quality to anchor process improvements against. I’ve argued elsewhere that one of the distinguishing factors of knowledge work deliverables is achieving the necessary uniqueness in the end result (Crafting Uniqueness in Knowledge Work). Applied uncritically, Taylor’s approach can lead us to emphasize superficial uniformities over essential uniqueness. Before we can even hope to improve a knowledge work process, we need to define deliverables in a way that allows us to judge them to be of sufficient quality.

Second, many of the steps in knowledge work processes are invisible. For physical tasks, what we could observe was more than sufficient to identify places for improvement. Not so with knowledge work. Is the person banging away answering email more or less productive than the one reading the latest journal article? Is the all-day project status meeting more or less productive than a well-maintained project wiki and issue tracking system? How would you go about comparing project management approaches to decide? The challenge is to find ways to make the invisible more visible, to distinguish essential activities from peripheral, and to develop robust insights into mental work processes. For that later challenge, I’m planning on revisiting books like John Medina’ Brain Rules: 12 Principles for Surviving and Thriving at Work, Home, and School and Dan Ariely’s Predictably Irrational: The Hidden Forces That Shape Our Decisions.

Third, we need to understand how to market knowledge work improvement to knowledge workers. In the world of Frederick Taylor we could treat workers as experimental subjects to be manipulated. Not so with the knowledge workers who drive today’s economy. These are individuals with the discretion and autonomy to ignore our advice on principle or on a whim. They can’t be compelled; they must be persuaded, sold, and possibly seduced into modifying their behaviors. At the very least, we’re going to need to carefully rethink the skills and perspectives we want to have in our deployment efforts.

Tagged , , ,

Shining Eyes: Benjamin Zander on leadership

Someday I’ll manage to get myself to a TED conference.In the meantime, I will continue to take advantage of the wonderful TED videos. Benjamin Zander is someone whose work on leadership I’ve appreciated in the past. The Art of  Possibility, coauthored with his wife Rosamund Stone Zander, remains one of the most useful books on leadership I’ve read in the last several years.

This past February he spoke at TED. Ostensibly about classical music, it’s 20 minutes of powerful insight about leadership.

Tagged ,

Thought for the day

<em>There is embedded content here that you cannot see. Please <a href="http://www.mcgeesmusings.net/2008/08/08/thought-for-the-day/">open the post in a web browser</a> to see this.<em>

Hat tip to Pharyngula

Updating ‘be prepared’ for the 21st Century

The Unthinkable: Who Survives When Disaster Strikes - and Why, Ripley, Amanda

Amanda Ripley has taken an interesting premise and turned it into an excellent book. A writer for Time magazine, she’s turned her attention to the lessons to be had from the ordinary people who survive extraordinary situations; those who got out of the World Trade Center on 9/11, who survived the tsunami in 2004, who make it out of burning planes and burning buildings. In place of the “be afraid” messages conveyed by the nightly news and by too many of those in positions of authority, she digs into the psychological dimensions of “be prepared” for the range of risks, real and imagined, that confront today’s average citizen.

There are two overarching messages woven into her fascinating storytelling around disasters big and small. The first is a simple model of the psychology of response (and non-response) to the unexpected threat; an arc of denial, deliberation, and decision. Ripley touches on our generally poor abilities to assess risk, how the physiology of fear interferes with our ability to think, why some people are more likely to be resilient than others, and why panic happens far less often than we think. More importantly, she demonstrates how small doses of attention and both mental and physical rehearsal improve the chances that you will be able to do the right thing should the need arise.

The second theme is about the central importance of regular people who are prepared to act when the moment comes. Through all of Ripley’s stories, whether of the World Trade Center or an ordinary car accident, by the time that official “first responders” and the authorities arrive, it’s too late. When the unexpected occurs, what you have with you and who you are surrounded by are what you get to work with. More often than not, that’s also more than enough.

Of course, there is a website and a blog associated with the book. Both appear to be better than the norm for these sorts of thinks. In particular, I’ve found the Unthinkable Blog to be worth adding to my list of RSS subscriptions.

Michael Wesch’s anthropological introduction to YouTube

[cross posted at FastForward Blog]

All the people whose opinions I trust have been recommending Michael Wesch’s most recent effort, “An anthropological introduction to YouTube.” It’s a presentation he delivered in June at he Library of Congress. It will take you an hour, but it is definitely time and attention well spent. Wesch and his students are developing deep insights into the human dimensions and impacts of today’s technology innovations.

 

<em>There is embedded content here that you cannot see. Please <a href="http://www.mcgeesmusings.net/2008/08/06/michael-weschs-anthropological-introduction-to-youtube/">open the post in a web browser</a> to see this.<em>

 

One point that Wesch emphasizes is the importance of “participant observation” as a research strategy in this domain. To grasp what these new social media mean for organizations and culture you have to get involved. Wesch’s work is an excellent entry point, but even that won’t really make sense until you try it yourself.

Tagged , ,

Review of Tom Davenport’s "Competing on Analytics"

Competing on Analytics: The New Science of Winning, Davenport, Thomas H. and Jeanne G. Harris

 

Tom Davenport has turned his attention of late to the prospects for business intelligence and information analytics. Competing on Analytics offers a managerial introduction to the topic. It emphasizes why organizations ought to be interested in the topic, what kinds of payoffs they might expect, and how organizations will need to adapt to take advantage of robust analytics. Davenport and co-author Jeanne Harris of Accenture split the book into two major sections. The first deals with describing how analytics can be used as a competitive tool; the second with the organizational challenges of building analytical capabilities. Overall, it’s a relatively short book and is well-suited to its target audience. On the other hand, if you’re on the receiving end of a mandate to build an analytical capability after someone higher in the food chain has gotten excited about the topic, don’t expect quite as much in the way of detailed implementation advice.

Davenport and Harris set out a stage-model of analytical capabilities starting with "analytically impaired" and ending with "analytical competitors." Partly, this is to support an argument they make that there’s an advantage to managing analytics at an enterprise level. My cynical side suspects that this advantage lies primarily in providing a clear target for the likes of Accenture or SAS to sell to.

Given that every new capability benefits from senior executive attention and that everyone wants to get on the CEO’s calendar, are there, in fact, compelling reasons that analytics deserves to be on this short list? Two come to mind. One is that the expertise called for in effective analytics is scarce. Better to have that expertise directed at the targets of greatest opportunity by those best positioned to judge. Two, the competitive business opportunities that might yield to analytics are more likely to be found from the perspective of those with an integrative view of the enterprise.

The authors walk through major functions of the enterprise identifying opportunities and examples of how analytics have been successfully applied. There are clearly an abundance of opportunities to apply analytical tools and techniques to improving internal processes, optimizing supply chains, and leveraging marketing.

One problem with the focus on describing the business opportunities for analytics is that the variety of potentially applicable tools gets short shrift. All books have to make decisions about what to put in and what to leave out. Given the intended audience, I can understand the decision to focus on the business side of the equation rather than on the tools side. On the other hand, glossing over the complexities of the statistical tools and algorithms has its own risks. Organizations risk creating a new class of wizards whose dark arts must be taken on faith or they risk putting dangerous tools in the hands of amateurs who will be blind to both the limits and the dangers of the tools.

This brings us to the second part of the book and the challenges of building an analytical capability. I’ve already alluded to my fundamental concern, which is that the stage model that Davenport and Harris develop doesn’t lead to the level of actionable advice you will need to navigate from stage to stage. I’m actually not terribly concerned about the obligatory call for senior executive support. Everybody does it, it does make a difference, and you had better invest some time in making a business case that will draw and hold the attention of someone in the food chain who controls the necessary resources.

What I wanted to see (and have yet to see in any of the discussions of BI and information analytics I’ve seen so far) is a systematic way to connect analytic capabilities to decision makers. Davenport and Harris touch on this in their useful distinction between analytical professionals and analytical amateurs, but they don’t dig deeply enough.

Analytical professionals will be skilled in extracting insights from masses of data. Given an hypothesis, they are capable of testing and validating it. Whether they will have sufficient sense for the business to formulate productive hypotheses is more debatable. On the converse, analytical amateurs, more deeply knowledgeable of the business, will possess a better sense for where to look in the data and less skill in teasing out the insights buried within. Bridging this gap requires educating each side about the other. It’s a two cultures problem that I haven’t seen effectively addressed and is at the heart of getting analytics to take root organizationally beyond the tenure of the current managerial advocates.

There are two questions I am left with at the end of this book. The first is how do you make evidence and facts the ultimate source of power for decision making if they aren’t already? There will always be an existing distribution of power in any organization. In Daniel Patrick Moynihan’s famous dictum “everyone is entitled to their own opinions, but not their own facts.” Are we in an organization where the best facts win or where the strongest opinions win? How do we get from the latter to the former?

The second question I am left with is how does the role of management evolve as we move toward greater reliance on data and algorithms to make the best decisions? We survived when inventory management, for example, shifted from being a serious managerial responsibility to a programmatic system output. Although I suspect it wasn’t a great time if you were an experienced inventory manager. This is an ongoing evolutionary process, of course. But, like other technologically driven processes, the cycles of change are now faster than the cycles of managerial careers. That’s raising the anxiety levels of many people currently occupying positions of power and influence. Anxiety and power in the same mix make me anxious. Although it’s unfair and unrealistic to expect it, I would have preferred that Davenport and Harris had more advice and counsel to offer in how to reduce that anxiety.

Tagged ,

About McGee’s Musings

Welcome to those of you visiting courtesy of Liz Strauss. This place started as an experiment while I was teaching courses in IT and Knowledge Management at Northwestern’s Kellogg School of Management. This was in the Fall of 2001 and blogs were still relatively new. I saw them then and now as an important part of the puzzle of how organizations learned and learned to take advantage of what it was that they learned.

I’m a big fan of the power of curiosity. Schools and businesses make a mistake when they suppress or try to channel curiosity into approved pathways. I happen to be curious about how technology, learning, organizations, and strategy all come together. I try to make sense of that confusing intersection for myself and for the people and organizations I work with today. If you’d like a flavor of my thinking here are some links to previous posts that I’m pleased with or that have attracted interesting reactions.

That should give you some flavor for what you’ll find here.

The other reason that I blog is to continue to connect to the fascinating thinkers and doers that are out there. People like Liz and her friends. I look forward to getting to know you.

Christopher Alexander’s take on the essence of expertise

One of the many lovely things about blogging is the way that people redirect your attention to things you’ve looked at before; calling attention to important insights that you missed the first time around or have simply forgotten. Back in May, the folks at SIGNAL VS. NOISE pointed to a passage in Christopher Alexander’s A Pattern Language. Alexander is an architect whose work has strongly influenced the world of software design. Here’s the passage:

 

To begin with, such a structure allows the actual building process to be a creative act. It allows the building to be built up gradually. Members can be moved around before they are firmly in place. All those detailed design decisions which can never be worked out in advance on paper, can be made during the building process. And it allows you to see the space in three dimensions as a whole, each step of the way, as more material is added…

The essence of this process is very fundamental indeed. We may understand it best by comparing the work of a fifty-year-old carpenter with the work of a novice. The experienced carpenter keeps going. He doesn’t have to keep stopping, because every action he performs, is calculated in such a way that some later action can put it right to the extent that it is imperfect now. What is critical here, is the sequence of events. The carpenter never takes a step which he cannot correct later; so he can keep working, confidently, steadily.

The novice by comparison, spends a great deal of his time trying to figure out what to do. He does this essentially because he knows that an action he takes now may cause unretractable problems a little further down the line; and if he is not careful, he will find himself with a joint that requires the shortening of some crucial member – at a stage when it is too late to shorten that member. The fear of these kinds of mistakes forces him to spend hours trying to figure ahead: and it forces him to work as far as possible to exact drawings because they will guarantee that he avoids these kinds of mistakes.

The difference between the novice and the master is simply that the novice has not learnt, yet, how to do things in such a way that he can afford to make small mistakes. The master knows that the sequence of his actions will always allow him to cover his mistakes a little further down the line. It is this simple but essential knowledge which gives the work of a master carpenter its wonderful, smooth, relaxed, and almost unconcerned simplicity.

There’s a lot to reflect on in this passage that bears on the world of knowledge work. First off, it’s a good reminder to keep the craft nature of the knowledge work we do in mind.

Second, the notion that expertise lies partly in the ability to recover from inevitable mistakes and missteps; not in avoiding mistakes altogether. Novices freeze in fear of making a mistake. Experts take mistakes as a given and learn how to recover gracefully.

Finally, it offers an intriguing perspective on design. Too often, design attempts to reduce the human element to the same rigidities and tolerances of machines. This seems particularly likely in enterprise settings where design responsibility falls on IT and systems professionals who don’t generally have the depth of knowledge (and expertise) about the human dimensions of organization.

Tagged ,

Attitude, hypothesis, experiment, and evidence

Doing science is fundamentally a state of mind more than any particular set of tools or any particular domain of knowledge.

How do you know when you’re doing science wrong?

Easy:

Science.jpg

Read the comments on this post…

 

More in the same vein from xkcd.

Fostering these attitudes is increasingly relevant in organizational settings. We’re awash in data and in advocates of data mining, information analytics, super crunching, and other forms of extracting insight from the data. Too often, however, the emphasis elevates a new set of experts with a new set of mysterious tools saying “trust me.” Trusting them is no better than trusting your gut or someone else’s gut.

Fundamentally, the scientific method is no more than a method for how to be productively skeptical in the face of pressures and dispositions to believe and the multiple ways to be mistaken.