Watson, come here, we need you

I spent some time with Watson over the past week or so at various conferences and I came away impressed. This is IBM’s Jeopardy-solving computer. At the St. Louis Gateway to Innovation conference, IBM had a kiosk showing off its prowess. You had your chance to try to come up with the correct question (remember, the game gives you the answers) before the computer did. Now, I consider myself a fairly decent Jeopardy player: when I watch the show on TV, I can usually get the right question more than half the time. But that is sitting in the comfort of my own living room.

When it came to standing in front of the Watson kiosk, I choked. Big time. It was interesting, because you get to see how Watson “thinks” and formulates its replies. I could barely start typing before it had finished figuring out its (correct) question. The kiosk doesn’t contain the actual Watson computer: it is just a remote interface. You can see a picture of part of the kiosk here, and how it judges among three different possible responses, along with assigning confidence values to each.

Then, at the IBM Impact conference in Vegas, I got to attend one of the sessions where Bob Madey, one of Watson’s developers, was talking about their next steps. Watson isn’t a product: with all the processors and storage it isn’t exactly portable. And you can’t really buy it anyway. It isn’t quite a service yet, although IBM is working on commercial versions for healthcare and financial services, and eventually for other industries such as sales contact management. But what is interesting is how IBM is going to make money from their efforts with this research project.

Anyone who signs up for Watson (and you better believe there is a waiting list) has to agree to a unique arrangement: IBM will take 40% of the calculated savings from its use. So if Watson is helping to diagnose diseases (as was being shown in the session that I attended), the hospital and IBM will come to some agreement as to what the cost savings will be from this activity. It is an intriguing way to sell computer services. The client only pays if Watson delivers.

This differs from usual computer services types of deals where you pay by the CPU minute or the amount of storage or other resources consumed. But that wouldn’t do for Watson, because there are a lot of resources involved in processing its natural language queries and storing all the data it needs to figure out the context of the query and possible answers to your questions. And one other thing: IBM will own all the data that is fed into Watson. You just get the results, and that’s it.

There are 220 people involved in the Watson project and this large staff is needed. It took them more than a week to load in a new database for each Jeopardy build. For the medical apps they are currently working on, it still takes them several days to retrain Watson. Part of the problem here is in understanding how to retire old data, or to assign lesser confidence intervals as you learn new things about the particular subjects you are covering. One of the audience members at Impact raised that issue, and it was an important one. Another asked how long it would take IBM to develop the Watson equivalent of a WebMD.com that anyone could query its medical data online. While Madey was cagey about answering this, if Watson would be allowed to reply the machine would probably agree that was a reasonable goal. I started thinking of the HAL9000 computer that powers the spaceship in 2001. “Dave, that’s a really good idea.”

It was fun to watch Watson on TV last year, although none of the human contestants stood a chance and eventually it was a total silicon rout. I know a bit how those fellow carbon-based life forms all felt: it was humbling just to try my hand at a couple of questions. But it is exciting to see where IBM is taking the project, and I suspect we will be hearing more about this curious machine sometime soon.


6 thoughts on “Watson, come here, we need you

  1. Thanks Dave! I’m a big watson fan and I’m looking forward to learning more about its various healthcare and other uses. If you know more about the healthcare trials, in particular, I would love to hear about it! Write it up, man.

  2. David, interesting update on Watson. Tom Brokaw, last nite at the Speakers Series commented that the computer would eventually be collapsed into the phone
    It would be interesting to get your perspective on this prediction.

    • Well, I don’t think we will be completely phone-centric, but it will certainly become more powerful. I am actually writing something about this for next week! Stay tuned.

  3. One of my readers wrote in: The problem with gainshare pricing is the “what have you done for me lately” problem. Even if you can agree on metrics for first year savings, what happens in year two when those savings are now the status quo? Claiming that you are the source of all savings from a baseline N years ago cannot work.

  4. Pingback: Law Firm Salaries Down, Automated Legal Analysis Systems Marketed – Evidence of the Effects of Technology on Production and Distribution? | My Distribution Law

  5. I hardly comment, however i did a few searching and wound up here Watson,
    come here, we need you | David Strom’s Web Informant. And I do have some questions for you if it’s
    allright. Could it be simply me or does it look like some of the comments appear as if they are coming from brain dead people?

    😛 And, if you are writing at additional places, I would like to keep up with everything new you have to post.
    Would you make a list of all of your public sites like your linkedin profile, Facebook page or twitter

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s