Skip to content

Business models for health care: Andy Kessler’s take on the future of medicine

The End of Medicine: How Silicon Valley (and Naked Mice) Will Reboot Your Doctor, Kessler, Andy

 

Andy Kessler is a former Wall Street investment analyst turned author. He learned his trade following Silicon Valley and its successful, long-term, obsession with Moore’s Law. In that world, as technology scales, costs fall predictably, and new markets emerge. In The End of Medicine, Kessler takes to the world of health care and medicine to discover how and where that underlying investment model might apply. It’s an interesting premise and, despite some annoying stylistic quirks, Kessler delivers some real value. It doesn’t get to anything remotely like an answer, but it collects and organizes a lot of useful information that might help us get closer to one.

Kessler opts for a highly anecdotal style; presumably to put a more human face on a large, complex, subject. For me, he overshoots the mark and loses the big picture. The color commentary overwhelms the underlying story line, which was my primary interest. But there is a good story line that is worth finding and holding on to.

Medicine’s roots are in making the sick and injured better. Triage is baked into the system at all levels. Observe symptoms, diagnose problem, apply treatment, repeat. Over time we’ve increased our capacity to observe symptoms and have gotten more sophisticated in the treatments we can apply, but the underlying logic is based on pathology. Also over time, a collection of industries have evolved around this core logic and these industries have grown in particularly organic and unsystematic ways.

Kessler runs into these roots and this logic throughout his journey. However, coming from the semiconductor and computer industries, as he does, he doesn’t fully pick up on their relevance. As industries, computers and semiconductors are infants compared to medicine and health care. Not only do Kessler’s industries operate according to Moore’s Law, but they are structurally designed around it. His analysis of health care identifies a number of crucial pieces, but he stops short of assembling a picture of the puzzle.

Kessler focuses much of his attention on developments in imaging and diagnostics. Both areas have seen tremendous advances and hold out promises of continued technological development similar to what we’ve seen in semiconductors.

Imaging is a computationally intensive area that benefits fully as an application of computing technologies. What is far less clear is whether the current structure of the health care industry will be able to absorb advances in imaging technologies at the pace that will let Moore’s Law play out in full force.

There is a second problem with imaging technologies that applies equally to other diagnostic improvement efforts. As we get better and better at capturing detail, we run into the problem of correctly distinguishing normal from pathological. While we may know what a tumor looks like on a mammogram what we really want to know is whether that fuzzy patch is an early warning sign of a future tumor or something we can safely ignore. The better we get at detecting and resolving the details of smaller and smaller fuzzy patches, the more we run into the problem of false positives; finding indicators of what might be a tumor that turn out on closer inspection to be false alarms. Our health care system is organized around pathologies; we fix things that are broken. Because of that, the data samples we work with are skewed; we have a much fuzzier picture of what normal looks like than what broken looks like.

This is the underlying conceptual problem that efforts to improve diagnostics and early detection have to tackle. Kessler devotes much of his later stories to this problem. He profiles the work of Don Listwin, successful Silicon Valley entrepreneur, and his Canary Fund efforts. Here’s the conundrum. If you detect cancers early, treatment is generally straightforward and highly successful. If you catch them later, treatment is difficult and success is problematic. Figuring out how to reliably detect cancer early has a huge potential payoff.

The kicker is the word “reliably” and the problem of false positives, especially as you begin screening larger and larger populations. If you have a test that is 99% accurate, then for every 100 people you screen you will get the answer wrong for one person. The test will either report a false positive - that you have cancer when, in fact, you don’t - or a false negative - that you are cancer-free when you aren’t. As you pursue early detection, the false positive problem becomes the bigger problem. Screen a million people and you will have 10,000 mistakes to deal with, the vast majority of which will be false positives. That represents a lot of worry and a lot of unnecessary expense to get to the right answer.

Kessler brings us to this point but doesn’t push through to a satisfactory analysis of the implications. Implicitly, he leaves it as an exercise for the reader. His suggestion is that this transition will present an opportunity for the scaling laws he is familiar with to operate. I think that shows an insufficient appreciation for the complexities of industry structure in health care. Nonetheless, Kessler’s book is worth your time in spite of its flaws.

Reblog this post [with Zemanta]
Tagged ,

Simple competence as an overarching theme for 2009

I’m increasingly fond of Bob Sutton’s work at Stanford. Here’s a recent post of his on a critical observation from organizational theorist James March.

After working with Stanford’s bureaucracy for month and months to try to get a scholar appointed and paid (we have the money, that is not the problem), and still not having luck, I was reminded of a lovely and rather obscure article by James March   It was based on an address that he gave to academic administrators at the University of Illinois in 1980.  This excerpt seems especially appropriate at the moment:

“The importance of simple competence in the routines of organizational life is often overlooked when we sing the grand arias of management, but effective bureaucracies are rarely dramatic…. Much of what distinguishes a good bureaucracy from a bad one is how it accomplishes the trivia of day-to-day relations with clients and day-to-day problems in maintaining and operating its technology.  Accomplishing these trivia may involve considerable planning, complex coordination, and central direction, but is more commonly linked to the effectiveness of large numbers of people doing minor things competently. As a result, it is probably true that the conspicuous differences around the world in the quality of bureaucratic performance are due primarily to variance in the competence of the ordinary clerk, bureaucrat, and lower manager, and to the effectiveness of routine procedures for dealing with problems at a local level.  This appears to be true of armies, factories, postal services, hotels, and universities.”

Right now, some simple competence sounds pretty damn good to me. As you may have gathered, March is not much of a fan of heroic leaders, he believes more in well-designed systems filled with competent people.  His quote also reminds me of one I heard from the folks at the Institute for Health Improvement (they credited the Army Corp of Engineers): Strategy is for amateurs; execution is for professionals. 

The above quote is from “How We Talk and How We Act: Administrative Theory and Administrative Life,” which March published here. For a general tour of his work, check out Decisions and Organizations and The Pursuit of Organizational Intelligence.

P.S. The post is dedicated to that very patient scholar!

In Praise of Simple Competence
Bobsutton
Sat, 27 Dec 2008 00:01:14 GMT

Helping individuals and organizations operate more competently seems to be an excellent underlying goal for 2009.

Reblog this post [with Zemanta]

Cisco as an emerging Enterprise 2.0 case example

Cisco Systems, Inc.

Image via Wikipedia

[cross-posted at FastForward blog]

The current issue of Fast Company has a cover article on Cisco and their ongoing efforts to reorganize into something that is an excellent case study of what Enterprise 2.0 may look like in an established organization. It shouldn’t be any surprise that the quintessential networking company is on the leading edge of network thinking applied to organizational design. At the same time, Cisco is a large, successful, hierarchical, engineering-centric organization that isn’t likely to be terribly interested in organizational fads.

Here’s the argument in a nutshell:

Chambers has greater ambitions, even now, in the midst of turmoil. Or, perhaps, especially now. He has been taking Cisco through a massive, radical, often bumpy reorganization. The goal is to spread the company’s leadership and decision making far wider than any big company has attempted before, to working groups that currently involve 500 executives. This move, Chambers says, reflects a new philosophy about how business can best work in a networked world. “In 2001, we were like most high-tech companies, with one or two primary products that were really important to us,” he explains. “All decisions came to the top 10 people in the company, and we drove things back down from there.” Today, a network of councils and boards empowered to launch new businesses, plus an evolving set of Web 2.0 gizmos — not to mention a new financial incentive system — encourage executives to work together like never before. Pull back the tent flaps and Cisco citizens are blogging, vlogging, and virtualizing, using social-networking tools that they’ve made themselves and that, in many cases, far exceed the capabilities of the commercially available wikis, YouTubes, and Facebooks created by the kids up the road in Palo Alto.

The bumpy part — and the eye-opener — is that the leaders of business units formerly competing for power and resources now share responsibility for one another’s success. What used to be “me” is now “we.” The goal is to get more products to market faster, and Chambers crows at the results. “The boards and councils have been able to innovate with tremendous speed. Fifteen minutes and one week to get a [business] plan that used to take six months!” As storm clouds form for the rest of the business community, he says, “We’re going to gain market share.” ["How Cisco's CEO John Chambers is Turning the Tech Giant Socialist", Ellen McGirt]

What makes this case study useful and interesting is its emphasis on organization not technology. There’s an undercurrent in the article that everything is all a bit “socialist” somehow and isn’t that a surprise, which I found annoying at points. The more interesting point is that a bunch of engineers and big-organization executives are essentially concluding that hierarchy isn’t scaling well enough to meet their goals.

More than anything else, this story provides a well-documented case study that is an existence proof to other skeptical executives that the combination of Enterprise 2.0 technologies and the right organizational principles and practices can succeed.

Reblog this post [with Zemanta]
Tagged ,

UC Berkeley demonstrates its intelligence; awards danah boyd her Ph.D.

UC Berkeley took its time, but clearly shows excellent judgment and intelligence in awarding danah boyd her Ph.D. at long last. We’ve known how smart danah is here for some time.

Well done, danah!

OMG. I have my PhD! OMG!!!!!

PS: I will post my dissertation in January when I return from vacation.

dissertation phd

OMG. I have my PhD! OMG!!!!!
zephoria
Tue, 09 Dec 2008 11:40:50 GMT

Tagged

The best sales video ever

We could all benefit from this level of energy and commitment

With a hat tip to Espen for finding and sharing this.

Social media lessons from the Obama campaign

[cross posted at FAST Forward]

The Obama campaign was innovative on a number of dimensions, particularly with the use of social media and the effective leverage of committed volunteers. There’s been some good reporting that captures the ground truth of what the campaign actually did and some early efforts to make sense out of these facts in a way that offers lessons for those of us interested in their relevance to broader organizational and enterprise needs.

Use of social media

Effective use of engaged volunteers

Lessons for organizational design and strategy

Tagged

JP Rangaswami on KM … “Clear, Transparent, Searchable, Archivable, Retrievable”

This has been lurking in my RSS aggregator for quite a while, courtesy of Jon Husband. There is really a lot of highly condensed insight in this post.

Thanks to JP Rangaswami for distilling social computing (in the context of work) to an essence.

From his post “Facebook and the Enterprise, Part 5: Knowledge Management“.

.

“More and more, knowledge management is going to be about reducing the cost of, and simplifying the process for, letting someone watch what you do. Nonintrusively. Time-shifted. Place-shifted. Searchable. Archivable. Retrievable.”

.

Via Dave Pollard via Nancy White

Powered by Qumana

JP Rangaswami on KM … “Clear, Transparent, Searchable, Archivable, Retrievable”
admin
Tue, 02 Sep 2008 13:08:06 GMT

Was being a fast follower ever a viable strategic option?

http://flickr.com/photos/davehogg/2578447228/

[cross posted at FAST Forward blog]

How often do you run across organizations that claim they intend to be “fast followers” when it comes to some dimension of strategy and innovation? Maybe I’m simply cranky because it’s Monday, but is there any way to make sense of such an approach in operational terms? The image of “fast follower” is intended to evoke a NASCAR driver drafting behind the leader, carefully waiting for the right moment to streak past and across the finish line. It’s deeply rooted in a notion that strategic success is a function of execution.

Any fast following strategy assumes learning from the leaders as a necessary first step. If you actually believe that the strategy can work, you need to be operating with something along the lines of the following as a theory of learning over time:

LearningAndFastFollowerStrategyBaseline

In this model, watching a first mover and waiting allows you to start your learning at a higher level and sometime later pass the first mover as their learning process peaks and levels off or slows down. I have two problems with this model. First, it assumes that the lessons learned by our first mover are easily observable and quickly transferable. Second, it still denigrates learning as an ongoing requirement. In this model, learning only needs to happen long enough to figure out the new strategic game and we get back to execution as the only relevant differentiator. It encourages you to undervalue and under invest in learning as a strategic competence.

I suspect that strategic learning is much more likely to follow a logistics curve of some sort. Early learning is relatively slow, followed by a period a very rapid learning, and ultimately a leveling off. If you accept that model of learning, then a fast follower strategy becomes even more suspect. In that environment, first mover advantages are likely to be more pronounced, with something like the following representing that situation:

LearningAndFastFollowerStrategyS-CurveLearning

At this point, being early in my own learning process, I mostly have more questions, not answers. Among them, in no particular order, are:

  1. What’s the relative value of competitive secrecy vs. the internal organizational drag on learning imposed by attempts to preserve secrecy?
  2. What can you do to shorten the slow ramp stage of learning?
  3. Under what circumstances would fast following remain a viable strategy? Are those circumstances strategically interesting?
  4. How do shortening learning cycles alter this argument?
Tagged

Bloglines claiming post

Just managing some administrivia for bloglines. Please ignore

Some links on social media applications within organizations

As part of my talk yesterday at the Social Media Strategies conference, I made passing reference to a number of stories, blog posts, bloggers, thinkers, and writers. It’s an occupational hazard of being a former professor.

I’ve written about different elements of yesterday’s talk over the course of various blog posts over time. Here are links to some of the most directly relevant together with links to other items I referenced:

Finally, I drew on a number of smarter people than I on the topics of expertise and organizational change. Here are some good entry points for further reading.

Seeing Organizational Patterns : A New Theory and Language of Organizational Design, Keidel, Robert W.
Keidel is an organizational theorist/designer who builds a very practical way of thinking and talking about organizations around the simple observation that all interactions in organizations can be understood in terms of the blend of control, cooperative, and autonomous ways of relating that organizational members can engage in. For the sports-minded, Keidel maps these three basic relating choices to the sports of American football, basketball, and baseball. He builds a nice case that organizational design choices can all be understood in terms of how these three fundamental relationship choices are mixed and blended.

Situated Learning: Legitimate Peripheral Participation, Lave, Jean
Jean Lave is an ethnographer working as part of Xerox’s Palo Alto Research Center. In this volume, Lave explores learning as primarily a social phenomenon and builds a very practical theory of how apprenticeship forms of skill acquisition and learning work in the real world.

 

 

 

Pragmatic Thinking and Learning: Refactor Your Wetware, Hunt, Andy
I’ve become a general fan of Andy Hunt’s pragmatic programming series of books. They are useful well beyond the narrow area of software development. In this new book, Hunt offers a useful introduction to the Dreyfus model of expertise and how it applies in the general context of knowledge work.

 

 

 

Quality Software Management (V1) : Systems Thinking, Weinberg, Gerald M.
The first of a four-volume exploration of the particular and peculiar challenges of managing the development and implementation of software. The first volume introduces fundamental notions of how to model and think about complex systems and how they respond to change. Weinberg adapts Virginia Satir’s family therapy theories to the environment of complex organizational environments.

 

 

 

Quality Software Management (V3): Congruent Action, Weinberg, Gerald M.

While all four volumes of Weinberg’s work are valuable, this volume on what Weinberg describes as “Congruent Action” is the most useful for understanding organizational change in concert with Volume 1.

Tagged