HomeIndustry Commentary

Digital by McKinsey

Like Tweet Pin it Share Share Email

Here’s an adjective/noun/object combination I never expected to type: I just read an excellent analysis by McKinsey.

Usually, when I read something by McKinsey my reaction is how useful it would have been five years ago. Not this time.

The article in question is: “Raising your Digital Quotient,” by Tanguy Catlin, Jay Scanlan, and Paul Willmott.

While you should read the original, as a public service here are some key takeaways:

  • Not every company can transform global marketplaces: Thank you! It’s easy to spot a business that’s succeeded in spectacular fashion, generalize from its success, and then recommend everyone else do the same thing. Temptation and good logic, though, rarely coexist.

The magic buzz-phrase I most often read about “digital” (and when did “digital” become a noun?) is that it “enables new business models.” Strikingly absent from most of these sources are examples of truly new business models. Even the oft-mentioned Uber is little more than a broker … a business model best described as ancient.

McKinsey’s advice for most companies is to figure out how digital stuff make them better at the business models they currently rely on.

  • Customers: McKinsey points out, and KJR completely endorses the notion that one of the most important aspects of digital disruption is how digital stuff affects or transforms how customers research and decide on products and services. Digital strategy should be built around determining how a company can best integrate itself into this new pattern.

Simple example: The big deal about Uber is supposed to be how easily you can book a ride by clicking on a mobile app. In the Minneapolis/St. Paul metro area I easily book taxis with an app called iHail … and I get a ride from a fully insured driver who has a chauffeur’s license. Had the U.S. taxi industry figured this out instead of relying on lawsuits and lobbying, I wonder if Uber would have made the inroads it did.

  • Culture overcomes: Without taking anything away from the importance of the digital technologies themselves, a “strong and adaptive culture” can overcome a lot of lacks.

The more I consult, the more convinced I am that no matter what the business change, culture is the lead story, not one factor among many in reducing an organization’s resistance to change.

  • Integrating the unintegratable: Not really unintegratable, but almost always unintegrated, are data about customers from internal systems and data about customers from the social web. Put them together — demographic and purchase history from your internal systems, combined with search patterns, consumption data, and psychographic tells from customers’ on-line behavior — and you can predict what customers are likely to want to buy far better than with either in isolation.
  • Process automation: McKinsey is more diplomatic about this than what follows:

Once upon a time, before the reign of “internal customers” put a halt to IT’s habit of provided technology leadership, conversations about the role of computers was how to automate business processes.

Whether or not there’s truly a causal relationship between the two events, at roughly the same time internal customers became IT’s reason for being, process optimization disciplines like Lean and Six Sigma supplanted the assumption of full automation.

It’s time for the past to become the future. For true processes (regular readers will recall KJR’s ongoing crusade to distinguish between processes and practices), everyone involved should assume full automation is possible, and design the process accordingly. As part of the design, kick out exceptions for human intervention when needed.

But assume you can fully automate at least the 20 percent of the cases that account for 80 percent of the work. This will inevitably reduce cycle times by orders of magnitude, reduce error rates to trivial fractions of their former selves, and cut incremental costs to the bone.

What McKinsey also doesn’t say: Do not, under any circumstances, let savings fall to the bottom line. Either use them to reinvest in your business, or to reduce product pricing. Like that annoying song about poker, it isn’t time to count your money yet — you’re still playing the game.

  • Agility applies to more than just Agile: Apply incremental “test-and-learn” (to use McKinsey’s phrase) everywhere. Or if you, like me, prefer OODA theory, increase the speed and reduce the scope of your loops. There comes a point when evidence trumps analysis. So emulate direct marketers — stop theorizing and test, test, test. It’s cheaper, and it works better besides.

There’s much more to the McKinsey paper than this. Take the time to read the whole thing.

Even though it lacks the inordinately valuable commentary I’ve added in the above summary.

Comments (1)

  • Maybe taxi response time is OK in the Twin Cities, but that’s not always the case. In San Francisco some years ago I called for a cab and waited 30-40 minutes. I was back inside the building, calling to find out why it was taking so long, when it finally drove up. I told the dispatcher “here he is!” and ran out to meet him — only to find that some bystander had gotten there first. The driver refused to take me because (1) they were already inside, and (2) they wanted to go farther than I did. He wouldn’t even drop me off en route! I had to go back inside, call the dispatcher a 3rd time, and wait another 20 minutes or so for another cab. So given the choice, I think I’ll give Uber preference over people like that who are slow to respond, and feel “entitled” and disdainful of their paying customers.

Comments are closed.