WEBVTT - Smart Talks with IBM: Why Business Needs Blockchain

0:00:00.080 --> 0:00:05.360
<v Speaker 1>I'm talking about blockchain. As a tech podcaster, I've found

0:00:05.400 --> 0:00:09.840
<v Speaker 1>it challenging to explain blockchain from a technical perspective because

0:00:09.840 --> 0:00:14.120
<v Speaker 1>it requires a certain level of familiarity with several other concepts,

0:00:14.120 --> 0:00:17.880
<v Speaker 1>and by the time I finished explaining those basic concepts,

0:00:18.280 --> 0:00:22.120
<v Speaker 1>there's very little time left for the star attraction. Jason,

0:00:22.360 --> 0:00:25.560
<v Speaker 1>as you will hear, has a very different approach and

0:00:25.760 --> 0:00:29.560
<v Speaker 1>one that I find particularly effective. I chatted with Jason

0:00:29.600 --> 0:00:33.440
<v Speaker 1>about his work at IBM, how the pandemic continues to

0:00:33.520 --> 0:00:37.320
<v Speaker 1>present enormous challenges to businesses and the average person alike,

0:00:37.840 --> 0:00:40.960
<v Speaker 1>and how blockchain can play a role in industries that

0:00:41.320 --> 0:00:46.080
<v Speaker 1>found themselves in a rapidly shifting and dynamic situation. Have

0:00:46.200 --> 0:00:50.680
<v Speaker 1>a listen, Jason. Before we get started, I was hoping

0:00:50.720 --> 0:00:54.040
<v Speaker 1>maybe you could give us a little background information on

0:00:54.120 --> 0:00:59.720
<v Speaker 1>yourself and what you do with IBM. So take it away,

0:00:59.760 --> 0:01:02.400
<v Speaker 1>tell us all about yourself. A sure, John, Let me

0:01:02.440 --> 0:01:05.240
<v Speaker 1>see if I can keep this contained in a minute blurb.

0:01:05.959 --> 0:01:11.400
<v Speaker 1>Probably not so, IBM. IBM has been my career within

0:01:12.440 --> 0:01:15.800
<v Speaker 1>the last number of years. I started. My first career

0:01:16.120 --> 0:01:19.040
<v Speaker 1>out of school was a military on my army, veteran

0:01:19.080 --> 0:01:22.360
<v Speaker 1>airborne ranger. All that fun stuff my body gave up

0:01:22.400 --> 0:01:26.200
<v Speaker 1>before I did. From the military. I then went through

0:01:26.240 --> 0:01:29.160
<v Speaker 1>a number of careers, from running a subsidiary of a

0:01:29.160 --> 0:01:32.880
<v Speaker 1>company that was ultimately sold to Berkshire Hathaway, did a

0:01:32.920 --> 0:01:37.800
<v Speaker 1>stint as I exect on Loan and public service UH,

0:01:37.840 --> 0:01:43.679
<v Speaker 1>and then started my own company, later sold and then

0:01:44.120 --> 0:01:49.080
<v Speaker 1>ended up at IBM, starting new companies through solutions throughout

0:01:49.440 --> 0:01:53.040
<v Speaker 1>North America and now globally, having started parts of our

0:01:53.080 --> 0:01:57.440
<v Speaker 1>business in Southeast Asia as well as China. And so

0:01:57.720 --> 0:02:00.840
<v Speaker 1>what's consistent and all that is a lot of starting

0:02:00.880 --> 0:02:07.280
<v Speaker 1>things up, growing them based on solid teams and technology,

0:02:07.360 --> 0:02:10.639
<v Speaker 1>based in data. And so here we are now. As

0:02:10.720 --> 0:02:14.120
<v Speaker 1>I recently in the last five years was running our

0:02:14.160 --> 0:02:16.840
<v Speaker 1>solutions group for all of our services, I ran an

0:02:16.840 --> 0:02:20.640
<v Speaker 1>experiment on this thing called blockchain, and so here I

0:02:20.680 --> 0:02:26.200
<v Speaker 1>am now four years almost four years later, at the

0:02:26.320 --> 0:02:31.320
<v Speaker 1>head of our blockchain business globally and enjoying some of

0:02:31.320 --> 0:02:34.679
<v Speaker 1>the most talented people I've ever worked with in my

0:02:35.000 --> 0:02:39.400
<v Speaker 1>multiple careers. I love that we've already got the cattle

0:02:39.400 --> 0:02:42.560
<v Speaker 1>of the bag with the blockchain term. I find in

0:02:42.600 --> 0:02:46.640
<v Speaker 1>technology that every few years a new term will emerge

0:02:46.800 --> 0:02:51.359
<v Speaker 1>that that the mainstream find it difficult to really grock

0:02:51.560 --> 0:02:55.600
<v Speaker 1>like cloud computing was one of those examples, right, And blockchain,

0:02:55.639 --> 0:02:58.280
<v Speaker 1>I feel, is one of those things. For a lot

0:02:58.320 --> 0:03:02.560
<v Speaker 1>of people where they hear the term, they are they

0:03:02.639 --> 0:03:04.960
<v Speaker 1>might be somewhat familiar with it. A lot of people

0:03:05.080 --> 0:03:09.800
<v Speaker 1>their touchstone is cryptocurrency, but they don't really have any

0:03:10.040 --> 0:03:13.399
<v Speaker 1>grasp of what it actually means. So when you're describing

0:03:13.639 --> 0:03:18.000
<v Speaker 1>your work to someone who is unfamiliar with blockchain, how

0:03:18.000 --> 0:03:21.920
<v Speaker 1>do you explain what it is? Well, it's great you

0:03:21.960 --> 0:03:24.920
<v Speaker 1>asked that question, Jonathan, because I usually leave out the

0:03:25.000 --> 0:03:29.200
<v Speaker 1>B word. Um, let's think of taking the word apart,

0:03:29.280 --> 0:03:32.000
<v Speaker 1>get rid of the block part, because people hear blockchain

0:03:32.000 --> 0:03:34.280
<v Speaker 1>and they start thinking crypto, and that's not what we're

0:03:34.320 --> 0:03:37.160
<v Speaker 1>talking about, it's what's behind that. So if you just

0:03:37.520 --> 0:03:40.040
<v Speaker 1>think of chain, I'll give you an example, and this

0:03:40.120 --> 0:03:43.480
<v Speaker 1>is this example hopefully will help you understand the outcome

0:03:43.560 --> 0:03:46.200
<v Speaker 1>we get from this technology. And if you just put

0:03:46.280 --> 0:03:50.640
<v Speaker 1>supply where the B word was in supply chain and

0:03:50.720 --> 0:03:53.080
<v Speaker 1>let me ask you, so, Jonathan, do you drink coffee

0:03:53.160 --> 0:03:57.840
<v Speaker 1>or tea or anything of that sort either one I do. Indeed,

0:03:57.880 --> 0:04:01.400
<v Speaker 1>I drink both tea and coffee and coffee okay, great,

0:04:01.720 --> 0:04:05.120
<v Speaker 1>Now let me ask you, uh, at any time, do

0:04:05.200 --> 0:04:08.680
<v Speaker 1>you have organic to your coffee? I have had it

0:04:08.840 --> 0:04:11.440
<v Speaker 1>on occasion, yes, on occasion. Well you probably paid a

0:04:11.520 --> 0:04:13.640
<v Speaker 1>little bit more for it because it's organic. Now, so

0:04:13.720 --> 0:04:16.200
<v Speaker 1>you a fun fact that many people spread and know

0:04:16.360 --> 0:04:22.360
<v Speaker 1>that there's more organic food consumed every year than is produced.

0:04:23.560 --> 0:04:27.800
<v Speaker 1>So think on that for a second. Right, So, so

0:04:27.880 --> 0:04:32.400
<v Speaker 1>somewhere in there in this supply chain, and now think

0:04:32.400 --> 0:04:34.840
<v Speaker 1>of the linear supply chain. I'm trying to paint a

0:04:35.040 --> 0:04:38.840
<v Speaker 1>visual picture for you. You know, let's let's think from

0:04:38.880 --> 0:04:43.400
<v Speaker 1>in this case, from from farm to to cup. Using

0:04:43.400 --> 0:04:46.160
<v Speaker 1>that time farm the fork kind of thing. Think think

0:04:46.200 --> 0:04:50.280
<v Speaker 1>of that that supply chain forget to be where it's

0:04:50.320 --> 0:04:55.760
<v Speaker 1>supply chain, and think of how that coffee being or

0:04:55.839 --> 0:04:59.599
<v Speaker 1>t leaf grew someplace and then went through a number

0:04:59.640 --> 0:05:02.039
<v Speaker 1>of sta ages to finally get to a store where

0:05:02.080 --> 0:05:04.919
<v Speaker 1>you picked it up or to a location where you

0:05:05.000 --> 0:05:09.640
<v Speaker 1>bought that cup of to your coffee. So that chain,

0:05:09.960 --> 0:05:14.719
<v Speaker 1>it's typically these multiple handshakes. So just think about a

0:05:14.760 --> 0:05:17.559
<v Speaker 1>matter of moving it from one place to the next

0:05:17.760 --> 0:05:22.039
<v Speaker 1>very literally and handshakes, passing it from one place to

0:05:22.040 --> 0:05:24.520
<v Speaker 1>the next, so that when you get it that final

0:05:24.560 --> 0:05:27.479
<v Speaker 1>handshake where you get to consume it. Jonathan, you say

0:05:27.520 --> 0:05:31.039
<v Speaker 1>okay with that handshake, I know that this coffee is

0:05:31.240 --> 0:05:34.280
<v Speaker 1>organic because it says it on the label or it's

0:05:34.279 --> 0:05:36.960
<v Speaker 1>set it on the menu. That's all you have at

0:05:36.960 --> 0:05:40.120
<v Speaker 1>this point, And think of those handshakes. It's just a

0:05:40.160 --> 0:05:43.000
<v Speaker 1>passing of data. Forget the tea or coffee. It's just

0:05:43.200 --> 0:05:45.960
<v Speaker 1>data about the t your coffee that you're going to consume,

0:05:46.080 --> 0:05:50.760
<v Speaker 1>something you're putting in your body. That data is going

0:05:50.800 --> 0:05:53.640
<v Speaker 1>from one place to the next until you consume it.

0:05:54.760 --> 0:05:58.919
<v Speaker 1>And in that chain, those handshakes are what you trust.

0:05:59.440 --> 0:06:01.919
<v Speaker 1>And there's some thing that you're trusting there first that

0:06:01.920 --> 0:06:05.440
<v Speaker 1>that data is shared accurately, and then no one's changed it.

0:06:06.480 --> 0:06:12.839
<v Speaker 1>That chain of data is something that you trust just inherently. Now,

0:06:12.920 --> 0:06:17.320
<v Speaker 1>what if, Jonathan, what if you could guarantee that that

0:06:17.320 --> 0:06:20.000
<v Speaker 1>that being or that t leaf that you consumed was

0:06:20.080 --> 0:06:25.600
<v Speaker 1>actually organic by ensuring that that data could be accurately

0:06:25.680 --> 0:06:28.320
<v Speaker 1>shared and you wouldn't have to worry about it going

0:06:28.360 --> 0:06:32.000
<v Speaker 1>from handshake to handshake. You would know from where you

0:06:32.080 --> 0:06:35.320
<v Speaker 1>consumed it all the way back to that farm or

0:06:35.400 --> 0:06:38.280
<v Speaker 1>to that tree or wherever it was grown. If you

0:06:38.320 --> 0:06:42.039
<v Speaker 1>could get rid of the handshakes. Instead of having a

0:06:42.160 --> 0:06:46.640
<v Speaker 1>supply chain, you would have a block chain because each

0:06:46.680 --> 0:06:52.839
<v Speaker 1>one of those handshakes would be digital technology that is unchangeable,

0:06:52.960 --> 0:06:57.080
<v Speaker 1>often called a mutable, and you would be able to

0:06:57.120 --> 0:07:02.839
<v Speaker 1>make sure that that t is organic because you, as

0:07:02.880 --> 0:07:06.080
<v Speaker 1>the consumer, would be able to see digitally all the

0:07:06.120 --> 0:07:10.080
<v Speaker 1>way back to the point of origination. So there you go. Excellent. Well,

0:07:10.080 --> 0:07:13.600
<v Speaker 1>I love that that explanation. I love that narrative approach.

0:07:14.000 --> 0:07:16.400
<v Speaker 1>From a certain perspective, I think a lot of people

0:07:16.680 --> 0:07:22.360
<v Speaker 1>immediately can kind of identify with the importance of this technology.

0:07:22.400 --> 0:07:26.119
<v Speaker 1>I mean, we we've seen depictions of our perhaps even

0:07:26.240 --> 0:07:29.680
<v Speaker 1>encountered the experience of the hey kid, you want to

0:07:29.680 --> 0:07:32.560
<v Speaker 1>buy a watch kind of thing, right, the idea, the

0:07:32.560 --> 0:07:35.920
<v Speaker 1>guy who's got got the These are all trust me,

0:07:36.000 --> 0:07:39.840
<v Speaker 1>these are all Rolexes. These are all brand brands that

0:07:39.920 --> 0:07:43.200
<v Speaker 1>you want, and you're immediately the red flag should come

0:07:43.240 --> 0:07:46.640
<v Speaker 1>up of really, that's probably not true. So in a

0:07:46.640 --> 0:07:49.880
<v Speaker 1>lot of ways, from what you're describing this, this approach

0:07:50.240 --> 0:07:53.280
<v Speaker 1>is a way of verifying through every single step of

0:07:53.320 --> 0:07:57.200
<v Speaker 1>the process that the thing you are trying to take

0:07:57.600 --> 0:08:00.000
<v Speaker 1>possession of, or the thing you're trying to purchase or

0:08:00.080 --> 0:08:04.840
<v Speaker 1>sell is genuine. It's the actual thing, and you can

0:08:04.880 --> 0:08:08.920
<v Speaker 1>easily see where that would be a really valuable approach.

0:08:09.560 --> 0:08:13.480
<v Speaker 1>That's that's exactly a Jonathan and and to simplify it

0:08:13.560 --> 0:08:16.920
<v Speaker 1>even more, the outcome is what's key here. Think of

0:08:16.960 --> 0:08:19.480
<v Speaker 1>that chain of custody almost going from one to next,

0:08:19.600 --> 0:08:23.640
<v Speaker 1>or here you go watch the dad joke chain of trustity.

0:08:23.720 --> 0:08:29.240
<v Speaker 1>So it's that trust going going from from source to

0:08:29.320 --> 0:08:32.640
<v Speaker 1>the consumer. And so that's called provenance. And it's one

0:08:32.679 --> 0:08:35.880
<v Speaker 1>of the three letters that we call out here that

0:08:36.000 --> 0:08:40.080
<v Speaker 1>you've mentioned in your Luxury good or Rolex example. Is

0:08:40.120 --> 0:08:43.440
<v Speaker 1>that first there's a thought of tokenization. I just mean

0:08:43.640 --> 0:08:48.360
<v Speaker 1>tokenizing an asset, digitizing something that has physical value. So

0:08:48.480 --> 0:08:51.480
<v Speaker 1>you've now token ized that watch because you've made it

0:08:51.520 --> 0:08:54.120
<v Speaker 1>digitally given to the digital And here comes the second

0:08:54.120 --> 0:08:57.559
<v Speaker 1>word identity. And so whether it's an identity of a

0:08:57.600 --> 0:09:01.080
<v Speaker 1>good or of a service or of a person, you

0:09:01.160 --> 0:09:03.880
<v Speaker 1>have identity. And then I mentioned the P provenance, So

0:09:04.000 --> 0:09:07.120
<v Speaker 1>T I P. If you can remember those three things,

0:09:07.679 --> 0:09:09.600
<v Speaker 1>that's all you need to know about that B word

0:09:09.679 --> 0:09:12.520
<v Speaker 1>because that's what it delivers as an outcome, and not

0:09:12.600 --> 0:09:16.960
<v Speaker 1>mutually exclusively either because as your in your rolex example,

0:09:17.440 --> 0:09:20.440
<v Speaker 1>there is a digitization of it, so it's hokenize there.

0:09:20.679 --> 0:09:22.600
<v Speaker 1>There is you could say, an identity to make sure

0:09:22.640 --> 0:09:26.600
<v Speaker 1>it's that same watch. And then from the from the

0:09:26.640 --> 0:09:29.480
<v Speaker 1>source of manufacturer to year rist so you know, then

0:09:29.520 --> 0:09:32.920
<v Speaker 1>the provenance. So those three things will be common outcomes

0:09:33.040 --> 0:09:36.640
<v Speaker 1>of of using this this new technology to kind of

0:09:36.920 --> 0:09:40.600
<v Speaker 1>shift a little bit. We've also seen obviously this past

0:09:40.679 --> 0:09:46.280
<v Speaker 1>year some tumultuous changes as companies have had to find

0:09:46.320 --> 0:09:51.199
<v Speaker 1>new ways to be flexible in the the coronavirus outbreak,

0:09:51.840 --> 0:09:55.480
<v Speaker 1>and that ended up being a big news story in

0:09:55.559 --> 0:09:59.600
<v Speaker 1>itself that the coronavirus outbreak and COVID nineteen we're having

0:09:59.600 --> 0:10:03.720
<v Speaker 1>a maze ger impact on companies and their supply chains.

0:10:03.960 --> 0:10:06.840
<v Speaker 1>Can you go into a little bit about why that was?

0:10:06.960 --> 0:10:11.160
<v Speaker 1>Why was that's such a an enormous impact early on

0:10:11.559 --> 0:10:14.160
<v Speaker 1>with the and and continues to be for several companies

0:10:14.440 --> 0:10:17.439
<v Speaker 1>with the outbreak of COVID nineteen. I think you had

0:10:17.679 --> 0:10:20.560
<v Speaker 1>you got to keep point there, Joathan. It continues to

0:10:20.600 --> 0:10:24.360
<v Speaker 1>be and it always this thought of supply chains and

0:10:24.640 --> 0:10:29.440
<v Speaker 1>supply chain visibility. Um, you know, having that that understanding

0:10:29.480 --> 0:10:33.640
<v Speaker 1>has always been elusive, always talked about so so what's

0:10:33.640 --> 0:10:37.240
<v Speaker 1>so what happened with with our current pandemic is it?

0:10:37.600 --> 0:10:41.720
<v Speaker 1>I think everyone realized just how fragile, or in this case,

0:10:41.760 --> 0:10:46.679
<v Speaker 1>how brittle their supply chains are not flexible at all.

0:10:47.000 --> 0:10:51.920
<v Speaker 1>And what we also realized was that the current demand

0:10:53.440 --> 0:10:56.359
<v Speaker 1>is different than it's ever been before. In the pandemic

0:10:56.880 --> 0:11:01.080
<v Speaker 1>it was giving an example, we had everyone needed hand

0:11:01.440 --> 0:11:06.000
<v Speaker 1>sanitizer and mask right you had ppe personal protective equipment,

0:11:06.480 --> 0:11:09.920
<v Speaker 1>and everyone was looking for it and could make enough.

0:11:10.280 --> 0:11:13.400
<v Speaker 1>And we had challenge companies that said, well maybe if

0:11:13.400 --> 0:11:15.680
<v Speaker 1>I make some of that, I can save save save

0:11:15.720 --> 0:11:18.000
<v Speaker 1>our company. So a brewery that says, now I'm going

0:11:18.080 --> 0:11:21.400
<v Speaker 1>to make hand sanitizer. Now you have a brewery that

0:11:21.640 --> 0:11:24.640
<v Speaker 1>is creating something they've never created before, trying to tie

0:11:24.640 --> 0:11:28.319
<v Speaker 1>into an ecosystem and a supply chain that they've never

0:11:28.360 --> 0:11:30.720
<v Speaker 1>tied into, and they're going to try and get that

0:11:30.760 --> 0:11:33.080
<v Speaker 1>to let's say, a hospital that needs a lot of

0:11:33.120 --> 0:11:36.400
<v Speaker 1>hand sanitizer. Keep the story going, but not too long.

0:11:37.200 --> 0:11:41.200
<v Speaker 1>They finally get that hand sanitizer to that hospital. And

0:11:41.200 --> 0:11:45.080
<v Speaker 1>then a hospital gets so much because they've over overbought.

0:11:45.640 --> 0:11:47.440
<v Speaker 1>Now they need to get rid of it. They want

0:11:47.520 --> 0:11:48.959
<v Speaker 1>to make sure they're not just going to throw it out,

0:11:49.000 --> 0:11:51.439
<v Speaker 1>they need to get to another hospital perhaps, so now

0:11:51.480 --> 0:11:54.760
<v Speaker 1>they instead of being a buyer, they're now a supplier.

0:11:54.840 --> 0:11:58.240
<v Speaker 1>So how do they tie into a different type of

0:11:58.600 --> 0:12:02.239
<v Speaker 1>business process where they're supply line other hospitals. I imagine

0:12:02.280 --> 0:12:05.880
<v Speaker 1>that visibility also comes in very handy when you are

0:12:05.920 --> 0:12:09.640
<v Speaker 1>trying to identify the specific points within a supply chain

0:12:09.720 --> 0:12:14.120
<v Speaker 1>where you're you've got either active problems or potential problems

0:12:14.160 --> 0:12:18.080
<v Speaker 1>down the line. Uh. Since I cover technology, I cover

0:12:18.160 --> 0:12:22.080
<v Speaker 1>a lot of companies that are building products that have

0:12:23.120 --> 0:12:27.200
<v Speaker 1>numerous components within them, all potentially all of them from

0:12:27.400 --> 0:12:33.640
<v Speaker 1>different suppliers, are different manufacturers, and any one of those,

0:12:33.880 --> 0:12:37.440
<v Speaker 1>any one point of failure can cause a delay in

0:12:37.920 --> 0:12:42.640
<v Speaker 1>production and shipping. So something like this where you're able

0:12:42.760 --> 0:12:47.120
<v Speaker 1>to have that kind of of overview of the full

0:12:47.160 --> 0:12:50.400
<v Speaker 1>supply chain because of this approach, I would imagine that

0:12:50.480 --> 0:12:53.160
<v Speaker 1>ends up being really valuable from that perspective as well,

0:12:53.240 --> 0:12:57.640
<v Speaker 1>being able to detect where any potential problems are going

0:12:57.679 --> 0:13:01.720
<v Speaker 1>to be and be more proactive in finding ways to

0:13:01.920 --> 0:13:05.360
<v Speaker 1>solve those challenges. So, can you talk a little more

0:13:05.400 --> 0:13:10.240
<v Speaker 1>about how IBM is specifically helping organizations like hospitals manage

0:13:10.280 --> 0:13:12.200
<v Speaker 1>their supply chains. We kind of touched on it a

0:13:12.240 --> 0:13:14.880
<v Speaker 1>little bit, but do you have any other stories or

0:13:14.920 --> 0:13:17.680
<v Speaker 1>examples you can share with us? Well, I think you

0:13:18.240 --> 0:13:20.800
<v Speaker 1>started with PPE, but right in our we're all talking

0:13:20.840 --> 0:13:25.959
<v Speaker 1>about the vaccine, right, and this thought that we all

0:13:26.200 --> 0:13:32.280
<v Speaker 1>and this this crosses hospitals, but then also UM, your

0:13:32.400 --> 0:13:36.240
<v Speaker 1>your your pharmaceutical dispensaries whatever that may be your your

0:13:36.400 --> 0:13:39.440
<v Speaker 1>your local drug store, or it could be UM a

0:13:39.600 --> 0:13:47.199
<v Speaker 1>healthcare provider for elderly. Uh. And so that thought, how

0:13:47.200 --> 0:13:50.240
<v Speaker 1>do you how do you take this capability that we've

0:13:50.280 --> 0:13:54.160
<v Speaker 1>just talked about the operation new operation operation system for

0:13:54.280 --> 0:13:58.280
<v Speaker 1>trust and look at this value chain. Now that does,

0:13:58.320 --> 0:14:03.640
<v Speaker 1>as I mentioned before, cross industry as well as ecosystems.

0:14:04.200 --> 0:14:09.000
<v Speaker 1>And so we started with this thought of of bringing

0:14:09.040 --> 0:14:16.000
<v Speaker 1>together the the healthcare providers, the first responders with all

0:14:16.120 --> 0:14:19.640
<v Speaker 1>the suppliers for PPE as well as ventilators. And that's

0:14:19.680 --> 0:14:21.800
<v Speaker 1>the example I gave before, and I left out the

0:14:21.920 --> 0:14:25.840
<v Speaker 1>name of what it was called Rapid Supplier connect, which

0:14:25.920 --> 0:14:28.960
<v Speaker 1>was really just taking some IBM components and we had

0:14:28.960 --> 0:14:31.080
<v Speaker 1>in blockchain as well as things that we had and

0:14:31.320 --> 0:14:35.680
<v Speaker 1>something called sterling from a supply chain perspective, and a

0:14:35.680 --> 0:14:38.200
<v Speaker 1>solution called trust your supplier and you brought them together.

0:14:38.280 --> 0:14:39.960
<v Speaker 1>So that was the first that was when you say

0:14:40.000 --> 0:14:43.240
<v Speaker 1>what were we doing? We created that call it matchmaking

0:14:43.360 --> 0:14:47.680
<v Speaker 1>service on steroids with trust. And then as you progress

0:14:47.760 --> 0:14:49.640
<v Speaker 1>to the example I'm giving now where we say, oh,

0:14:49.680 --> 0:14:52.480
<v Speaker 1>well what about vaccinations, think about think about the challenge

0:14:52.520 --> 0:14:56.360
<v Speaker 1>we have in just the United States. You have federal

0:14:58.000 --> 0:15:02.160
<v Speaker 1>level people really working hard to get things into states,

0:15:02.520 --> 0:15:05.080
<v Speaker 1>and we know that that challenge just what we've seen

0:15:05.720 --> 0:15:08.720
<v Speaker 1>dynamically from how can you get a state or how

0:15:08.720 --> 0:15:11.040
<v Speaker 1>can you see a state? Back to this, how do

0:15:11.080 --> 0:15:14.240
<v Speaker 1>you share trust amongst players and what we think are

0:15:14.240 --> 0:15:17.600
<v Speaker 1>the same ecosystem and then even within that state, there's

0:15:17.680 --> 0:15:21.440
<v Speaker 1>even more entities that are moving a vaccine around. And

0:15:21.520 --> 0:15:24.960
<v Speaker 1>so we have what's called the Vaccine Accountability Network that

0:15:25.040 --> 0:15:29.160
<v Speaker 1>does just that. What you have is a capability that

0:15:29.200 --> 0:15:32.400
<v Speaker 1>gives you this trusted data that will partner with you.

0:15:32.440 --> 0:15:38.240
<v Speaker 1>Think of your your classic enterprise resource management systems, you

0:15:38.360 --> 0:15:43.400
<v Speaker 1>have your your contact management systems, in this case, contact

0:15:43.440 --> 0:15:46.480
<v Speaker 1>tracing systems. You have all of these systems that are

0:15:46.520 --> 0:15:49.080
<v Speaker 1>in place. And what's great is because this is delivered

0:15:49.080 --> 0:15:51.400
<v Speaker 1>in the cloud. You know, I was dropping those hybrid words.

0:15:51.400 --> 0:15:53.280
<v Speaker 1>It can be on any cloud, it can be multi

0:15:53.280 --> 0:15:57.360
<v Speaker 1>clouds and on premise off premise, so that's the hybrid term,

0:15:57.400 --> 0:15:59.320
<v Speaker 1>and you don't have to rip things out. This is

0:15:59.360 --> 0:16:04.600
<v Speaker 1>a data sharing and data trust layer that goes across

0:16:04.760 --> 0:16:09.120
<v Speaker 1>what already exists. So you hopefully now see, Jonathan, and

0:16:09.200 --> 0:16:13.200
<v Speaker 1>when I talk about this thought of a vaccine accountability network,

0:16:13.280 --> 0:16:19.040
<v Speaker 1>that it brings the capabilities together. This is truly where

0:16:19.080 --> 0:16:22.080
<v Speaker 1>we liked we as IBM, we see this as as

0:16:22.480 --> 0:16:25.800
<v Speaker 1>good tech and tech for good because it's bringing great

0:16:25.840 --> 0:16:29.400
<v Speaker 1>outcomes for our citizens. It's tech that matters for us

0:16:29.400 --> 0:16:31.840
<v Speaker 1>and for the world. And on top of that, just

0:16:31.920 --> 0:16:35.840
<v Speaker 1>as a sort of a my own little anecdotal addition here,

0:16:35.920 --> 0:16:39.280
<v Speaker 1>I think that it's incredibly valuable not just from the

0:16:39.280 --> 0:16:42.560
<v Speaker 1>the supply chain and technical side of things, but the

0:16:42.600 --> 0:16:46.920
<v Speaker 1>fact that you have that reassurance that this is you know,

0:16:47.000 --> 0:16:51.320
<v Speaker 1>it's all accounted for. We understand exactly where this has

0:16:51.320 --> 0:16:54.640
<v Speaker 1>been every step of the way. It helps combat something

0:16:54.680 --> 0:16:59.640
<v Speaker 1>that we have unfortunately really seen become more and more prevalent,

0:16:59.680 --> 0:17:03.800
<v Speaker 1>which is just the vast amount of misinformation that can

0:17:03.840 --> 0:17:09.119
<v Speaker 1>come out, whether purposefully or or you know, unconsciously, and

0:17:09.119 --> 0:17:12.080
<v Speaker 1>then just it can it can spread so quickly. Having

0:17:12.680 --> 0:17:17.679
<v Speaker 1>the capability of saying this is trustworthy and we have

0:17:17.760 --> 0:17:21.720
<v Speaker 1>the technology to prove that it's trustworthy and have that

0:17:21.800 --> 0:17:24.360
<v Speaker 1>reassurance there. I think that ends up being a valuable

0:17:24.400 --> 0:17:27.760
<v Speaker 1>tool as well. It's sort of an additional benefit of

0:17:27.800 --> 0:17:31.679
<v Speaker 1>this something that uh, you know, we're fortunate that the

0:17:31.840 --> 0:17:36.800
<v Speaker 1>technology has that capability while we are unfortunately in an

0:17:36.800 --> 0:17:39.919
<v Speaker 1>era of misinformation. So having something that you can actually

0:17:39.960 --> 0:17:45.399
<v Speaker 1>depend upon is incredibly reassuring and refreshing in a in

0:17:45.440 --> 0:17:49.640
<v Speaker 1>a world that occasionally feels like that is a luxury

0:17:49.760 --> 0:17:52.919
<v Speaker 1>as opposed to something you should just expect. So to me,

0:17:53.040 --> 0:17:56.560
<v Speaker 1>like that is another benefit of this technology. On top

0:17:56.640 --> 0:17:59.600
<v Speaker 1>of the logistical side of it, it's sort of a

0:17:59.600 --> 0:18:03.639
<v Speaker 1>psychle logical side right right, and I think a personalizing

0:18:04.040 --> 0:18:06.840
<v Speaker 1>like that. When you start talking about trust and information,

0:18:07.640 --> 0:18:10.399
<v Speaker 1>it brings to light something else that we've seen in

0:18:10.440 --> 0:18:15.000
<v Speaker 1>this pandemic where whilst people tend to think trust and information,

0:18:15.040 --> 0:18:18.240
<v Speaker 1>they go straight to you know, maybe media and news,

0:18:18.240 --> 0:18:20.240
<v Speaker 1>but we think of things that all of us can

0:18:20.280 --> 0:18:24.360
<v Speaker 1>personalize and its credentials. I talked about identity, but not

0:18:24.480 --> 0:18:27.240
<v Speaker 1>just are you who you say you are, Jonathan, but

0:18:27.320 --> 0:18:30.960
<v Speaker 1>what about your credentials. What about you know, your your diploma,

0:18:31.200 --> 0:18:34.240
<v Speaker 1>you're learning credentials, you know something that sits somewhere out

0:18:34.280 --> 0:18:36.240
<v Speaker 1>and we go, wait, what government agency that we go

0:18:36.320 --> 0:18:37.359
<v Speaker 1>to for that? And do I have to go to

0:18:37.400 --> 0:18:39.760
<v Speaker 1>my college? You know all of those things that you

0:18:39.800 --> 0:18:43.320
<v Speaker 1>start thinking about credentials in the thought of, uh, you know,

0:18:43.880 --> 0:18:46.720
<v Speaker 1>information about my health? Back to current pandemic. How do

0:18:46.800 --> 0:18:50.359
<v Speaker 1>I know if I've been vaccinated? Or how do I

0:18:50.400 --> 0:18:52.600
<v Speaker 1>know that if I'm COVID negative or positive? Don't we

0:18:52.640 --> 0:18:56.480
<v Speaker 1>want to document that in a credentialing type of way. Well,

0:18:57.560 --> 0:19:00.199
<v Speaker 1>this type of information is starting to become even more

0:19:01.119 --> 0:19:03.320
<v Speaker 1>more powerful when we take what I've just said and

0:19:03.359 --> 0:19:07.440
<v Speaker 1>applied it to a vaccine or to your health status,

0:19:07.920 --> 0:19:10.640
<v Speaker 1>and we we have this wonderful way if we went

0:19:10.640 --> 0:19:13.080
<v Speaker 1>through that vaccine thing, you know, how do you know

0:19:13.119 --> 0:19:15.440
<v Speaker 1>if you have been immunized? You could have a health

0:19:15.520 --> 0:19:17.800
<v Speaker 1>pass and that's something else you can google as as

0:19:17.800 --> 0:19:21.960
<v Speaker 1>we work with with that capability. But beyond health, think

0:19:21.960 --> 0:19:26.800
<v Speaker 1>about opening up new opportunities with this technology and using

0:19:26.880 --> 0:19:30.360
<v Speaker 1>information that can help others where you and I may

0:19:30.440 --> 0:19:32.840
<v Speaker 1>use it to validate that we went to high school

0:19:32.960 --> 0:19:36.080
<v Speaker 1>or that we have graduate degrees or college degrees. What

0:19:36.160 --> 0:19:41.360
<v Speaker 1>about using this to empower information that allows someone who

0:19:41.359 --> 0:19:43.479
<v Speaker 1>may not go to school for four years but just

0:19:43.560 --> 0:19:46.640
<v Speaker 1>needs a certification to get a great job. It can't

0:19:46.640 --> 0:19:48.840
<v Speaker 1>say okay, well great, go back to college and come

0:19:48.880 --> 0:19:50.879
<v Speaker 1>back to me in four years. So what if we

0:19:50.920 --> 0:19:54.720
<v Speaker 1>could put that personal credential on on a device that

0:19:54.800 --> 0:19:56.920
<v Speaker 1>you have in your pocket. So that's what we started.

0:19:56.960 --> 0:20:00.959
<v Speaker 1>We start about accurate, accuracy, reliable, and trust as well

0:20:00.960 --> 0:20:05.320
<v Speaker 1>as portability of information. That's what this capability enables, and

0:20:05.359 --> 0:20:07.960
<v Speaker 1>that's where I think it should, you know, really get

0:20:07.960 --> 0:20:11.560
<v Speaker 1>people excited when we talk about real information and real

0:20:11.600 --> 0:20:15.760
<v Speaker 1>trusted information is empowering and opening up markets. Finding not

0:20:15.960 --> 0:20:18.960
<v Speaker 1>something that's a blue collar job or a white collar job,

0:20:18.960 --> 0:20:21.840
<v Speaker 1>but thinking about these new collar jobs that just require

0:20:21.960 --> 0:20:26.159
<v Speaker 1>trusted certifications. I love that you have have really gone

0:20:26.200 --> 0:20:30.359
<v Speaker 1>to kind of the the endpoint the individual person with

0:20:30.480 --> 0:20:34.199
<v Speaker 1>that sort of application of this technology and how that

0:20:34.240 --> 0:20:36.080
<v Speaker 1>can make an impact. Because a lot of the time

0:20:36.119 --> 0:20:39.720
<v Speaker 1>when we talk about these big ideas in tech, uh,

0:20:39.760 --> 0:20:41.840
<v Speaker 1>it can seem distance. It can seem like, oh, well,

0:20:41.880 --> 0:20:44.760
<v Speaker 1>that's something that's going on at like the enterprise level,

0:20:45.080 --> 0:20:47.919
<v Speaker 1>but I don't see how that has any impact on me.

0:20:48.080 --> 0:20:52.240
<v Speaker 1>You've turned that around entirely with that that description and

0:20:52.280 --> 0:20:55.840
<v Speaker 1>to show this is a way where the impact of

0:20:55.840 --> 0:21:00.440
<v Speaker 1>this technology can have a real, uh positive in fluence

0:21:00.560 --> 0:21:03.240
<v Speaker 1>on the individual as opposed to this is like these

0:21:03.240 --> 0:21:09.080
<v Speaker 1>are these big financial or big industrial kind of ideas

0:21:09.119 --> 0:21:14.359
<v Speaker 1>that otherwise seemed distant. That being said, with the new

0:21:14.400 --> 0:21:18.600
<v Speaker 1>normal that we have, how how is blockchain making an

0:21:18.640 --> 0:21:21.879
<v Speaker 1>impact in other industries outside of the medical industry. Are

0:21:21.920 --> 0:21:26.560
<v Speaker 1>we starting to see other sectors adopt this technology and

0:21:26.600 --> 0:21:30.159
<v Speaker 1>if so, in what ways is it manifesting? So you

0:21:30.320 --> 0:21:34.240
<v Speaker 1>you called out one of the first industries that really

0:21:34.280 --> 0:21:39.280
<v Speaker 1>embraced this, which was the financial services sector UM banking

0:21:39.320 --> 0:21:46.640
<v Speaker 1>for example. Uh, this thought of transacting digitally, in being

0:21:46.680 --> 0:21:53.600
<v Speaker 1>able to verify, validate, and settle financial transactions. And ultimately,

0:21:53.600 --> 0:21:56.200
<v Speaker 1>when we think about that original example I gave you,

0:21:56.320 --> 0:22:00.200
<v Speaker 1>those handshakes are transactions and the more that you can

0:22:00.200 --> 0:22:03.080
<v Speaker 1>make those trusted and obviously more often than not those

0:22:03.119 --> 0:22:10.280
<v Speaker 1>handshakes have an exchange of some monetary value. And so

0:22:11.320 --> 0:22:14.760
<v Speaker 1>industries such as the banking industry have picked this up

0:22:14.760 --> 0:22:21.280
<v Speaker 1>to say, look, can we quickly transact and make sure

0:22:21.280 --> 0:22:23.560
<v Speaker 1>that it's it's digital and we all appreciate this now.

0:22:23.600 --> 0:22:25.360
<v Speaker 1>When I used to say it, people say, oh yeah,

0:22:25.480 --> 0:22:27.800
<v Speaker 1>we won't go digital sundown now everything. You know, we're

0:22:27.800 --> 0:22:29.640
<v Speaker 1>all trying to figure out how we do everything digitally

0:22:29.640 --> 0:22:33.240
<v Speaker 1>and touchless. Well, we dot trade as a as a

0:22:33.280 --> 0:22:38.119
<v Speaker 1>company that towel the largest banks in Europe that came together.

0:22:38.160 --> 0:22:40.959
<v Speaker 1>These are banks that typically compete, and back to this

0:22:40.960 --> 0:22:43.720
<v Speaker 1>thought of you know, blockchain using the B word is

0:22:43.800 --> 0:22:48.320
<v Speaker 1>a a team sport. Again, you have competitive banks that say, look,

0:22:48.359 --> 0:22:51.600
<v Speaker 1>we can actually you know, raise the tide here and

0:22:51.680 --> 0:22:56.639
<v Speaker 1>raise all boats by transacting digitally and availing trade finance quicker,

0:22:56.680 --> 0:23:00.160
<v Speaker 1>better faster than small and medium sized enterprises because as

0:23:00.240 --> 0:23:03.080
<v Speaker 1>it's digital and we can, we can make it happen quicker.

0:23:03.119 --> 0:23:07.600
<v Speaker 1>So you see this, this type of transacting happening in

0:23:07.760 --> 0:23:10.960
<v Speaker 1>financial services, and you see things as I've given a

0:23:11.000 --> 0:23:14.080
<v Speaker 1>financial services example, it's no different than what you have

0:23:14.240 --> 0:23:17.000
<v Speaker 1>in in retail here in North America. And you have

0:23:17.520 --> 0:23:23.400
<v Speaker 1>some forward thinking entities that say, my accounts receivable, accounts payable.

0:23:23.680 --> 0:23:26.760
<v Speaker 1>You know, it's a process that it takes thirty days

0:23:26.800 --> 0:23:28.800
<v Speaker 1>to settle. But what if I could see all the

0:23:28.840 --> 0:23:32.760
<v Speaker 1>way through those handshakes. As we mentioned before, I could

0:23:32.800 --> 0:23:35.120
<v Speaker 1>settle in ten days and I don't have to make

0:23:35.160 --> 0:23:38.280
<v Speaker 1>phone calls and send emails, and that would maybe reduce

0:23:38.480 --> 0:23:42.760
<v Speaker 1>my my overhead. And then finally, when you look at

0:23:43.200 --> 0:23:48.040
<v Speaker 1>where that's going, Jonathan, as we've looked at different industries,

0:23:48.359 --> 0:23:51.640
<v Speaker 1>I've told you that's going cross industry. There's words that

0:23:51.640 --> 0:23:57.560
<v Speaker 1>that identify and most industries words that that people will

0:23:57.560 --> 0:23:59.400
<v Speaker 1>not either and say, yeah, we're trying to figure that out,

0:23:59.520 --> 0:24:02.960
<v Speaker 1>such as sustainability. And so that's where we're starting to

0:24:03.040 --> 0:24:07.680
<v Speaker 1>see big concepts become material when you can put, as

0:24:07.720 --> 0:24:12.400
<v Speaker 1>you mentioned, trust and accountability in front of it. Jason, Unfortunately,

0:24:12.480 --> 0:24:16.760
<v Speaker 1>when we're recording this, we're recording this as there's a

0:24:17.520 --> 0:24:22.080
<v Speaker 1>new surge of COVID nineteen in North America. The UK

0:24:22.760 --> 0:24:28.560
<v Speaker 1>has recently entered a month long lockdown period. Uh, clearly

0:24:28.640 --> 0:24:34.240
<v Speaker 1>we're at a new phase that's at least as difficult

0:24:34.280 --> 0:24:38.119
<v Speaker 1>as the initial challenges were when we first started seeing

0:24:38.200 --> 0:24:42.640
<v Speaker 1>regions around the world lockdown. Are you seeing any difference

0:24:42.640 --> 0:24:46.840
<v Speaker 1>in approach this time around? Our Our companies getting better

0:24:47.040 --> 0:24:51.960
<v Speaker 1>at handling this with their supply chains, and I assume

0:24:52.200 --> 0:24:56.000
<v Speaker 1>those that are reliant on things like blockchain are having

0:24:56.920 --> 0:25:00.359
<v Speaker 1>less of a challenge and adapting to that than others.

0:25:00.440 --> 0:25:03.960
<v Speaker 1>But but what are you seeing out there? We're seeing

0:25:03.960 --> 0:25:08.320
<v Speaker 1>what you just alluded to, where those that have existing

0:25:08.359 --> 0:25:12.360
<v Speaker 1>capabilities um knew before that they were challenged in their

0:25:12.400 --> 0:25:15.600
<v Speaker 1>supply chain, and now they're thinking beyond a supply beyond

0:25:15.760 --> 0:25:19.480
<v Speaker 1>the supply chain, and they're aware of the value chain

0:25:19.560 --> 0:25:22.879
<v Speaker 1>that I mentioned that it's not just that layer of

0:25:23.040 --> 0:25:27.879
<v Speaker 1>getting a package go to service across a linear spectrum,

0:25:27.880 --> 0:25:32.480
<v Speaker 1>but it's very dynamic um more more like a series

0:25:32.520 --> 0:25:34.639
<v Speaker 1>of concentric circles of trying to get from point A

0:25:34.760 --> 0:25:38.719
<v Speaker 1>to point B wherever that is. They realize how flexible

0:25:39.119 --> 0:25:42.880
<v Speaker 1>it needs to be and that there's this capability as

0:25:42.920 --> 0:25:46.000
<v Speaker 1>you call out that says, look, you don't have to

0:25:46.040 --> 0:25:48.560
<v Speaker 1>do the rip and replace of what you have, but

0:25:48.640 --> 0:25:51.600
<v Speaker 1>you can actually work with what you have and connected

0:25:51.640 --> 0:25:55.919
<v Speaker 1>in a permission way to use data with more power

0:25:56.280 --> 0:26:01.440
<v Speaker 1>and no one has to ask to explain the B word. Instead,

0:26:02.200 --> 0:26:04.600
<v Speaker 1>what they're saying is how can I get the outcomes?

0:26:04.600 --> 0:26:07.840
<v Speaker 1>And so as you you talk about things such as

0:26:07.920 --> 0:26:11.399
<v Speaker 1>and you alluded to supply chain management, you start to

0:26:11.440 --> 0:26:15.920
<v Speaker 1>think about using your value chain and value chain integration

0:26:16.119 --> 0:26:21.440
<v Speaker 1>of these ecosystems for outcome management. Not just change that data,

0:26:21.480 --> 0:26:24.439
<v Speaker 1>but also think about the business processes that have to

0:26:24.520 --> 0:26:27.400
<v Speaker 1>change with that, because, as we said, we're pulling out

0:26:27.480 --> 0:26:31.200
<v Speaker 1>some of those handshakes, which means you're changing the workflows.

0:26:31.240 --> 0:26:33.840
<v Speaker 1>You're making those those workflows just a little bit more

0:26:33.880 --> 0:26:37.880
<v Speaker 1>intelligent as well as transparent. Right, So, if you're doing that,

0:26:37.880 --> 0:26:41.800
<v Speaker 1>that's not easy because regardless of how cool it sounds

0:26:41.960 --> 0:26:45.040
<v Speaker 1>when we talk about it Jonathan on this podcast, it

0:26:45.160 --> 0:26:48.040
<v Speaker 1>might sound cool, but it's change, and we know that

0:26:48.240 --> 0:26:52.560
<v Speaker 1>change is not easy. A fortunate outcome of an unfortunate

0:26:52.640 --> 0:26:56.680
<v Speaker 1>situation is that the sense of urgency and also collaboration

0:26:56.720 --> 0:26:59.920
<v Speaker 1>and teamwork are overcoming that challenge right now, and that's

0:27:00.080 --> 0:27:03.240
<v Speaker 1>we're seeing as a positive outcome here where people are

0:27:03.240 --> 0:27:06.600
<v Speaker 1>coming together and say, I'm not going to get all

0:27:06.600 --> 0:27:09.600
<v Speaker 1>wound up in the who, what, why, and how of technology,

0:27:09.640 --> 0:27:12.400
<v Speaker 1>but I'm going to focus on the outcome and what

0:27:12.480 --> 0:27:17.119
<v Speaker 1>does it take to put what I currently have on

0:27:17.240 --> 0:27:21.600
<v Speaker 1>steroids to that next level of capability around data and trust.

0:27:22.000 --> 0:27:24.680
<v Speaker 1>And that's that's the magic spot we're in right now

0:27:24.680 --> 0:27:28.000
<v Speaker 1>with this with this capability, I think what you say,

0:27:28.320 --> 0:27:31.480
<v Speaker 1>essentially it it really does lend credence to the old

0:27:31.560 --> 0:27:35.600
<v Speaker 1>saying necessity is the mother of invention, the idea that

0:27:35.640 --> 0:27:41.400
<v Speaker 1>we have found ourselves in this incredible circumstance and that

0:27:41.480 --> 0:27:47.840
<v Speaker 1>it calls for really innovative solutions. And so this is

0:27:47.960 --> 0:27:52.080
<v Speaker 1>an example of that about how when we are faced

0:27:52.080 --> 0:27:56.600
<v Speaker 1>with these massive challenges, there is a way to rise

0:27:56.680 --> 0:27:59.400
<v Speaker 1>up to meet those challenges, and it requires that sort

0:27:59.440 --> 0:28:05.000
<v Speaker 1>of flexible thinking and that adaptability and that that that

0:28:05.119 --> 0:28:11.240
<v Speaker 1>determination to to adopt these new approaches and and not

0:28:11.359 --> 0:28:13.800
<v Speaker 1>a fear of it. You know, there comes a point

0:28:13.840 --> 0:28:16.679
<v Speaker 1>where you really need to look at the options and

0:28:16.760 --> 0:28:19.600
<v Speaker 1>say what makes the most sense, what is going to work?

0:28:20.800 --> 0:28:24.480
<v Speaker 1>With that in mind To sort of conclude our conversation,

0:28:25.480 --> 0:28:27.960
<v Speaker 1>we're kind of seeing a trial by fire with this

0:28:28.000 --> 0:28:31.800
<v Speaker 1>particular implementation of you know, this this concept of the

0:28:31.880 --> 0:28:35.320
<v Speaker 1>value chain in extreme circumstances. But where do you see

0:28:35.760 --> 0:28:39.200
<v Speaker 1>the future of this? What what what's in store for

0:28:39.280 --> 0:28:46.280
<v Speaker 1>us once we have cleared this UH incredibly important hurdle

0:28:46.680 --> 0:28:50.840
<v Speaker 1>and we're beyond it. What is the future of IBM

0:28:50.920 --> 0:28:54.680
<v Speaker 1>S approach and UH and how our industry is going

0:28:54.680 --> 0:28:57.800
<v Speaker 1>to make use of this moving forward? Well, I think

0:28:58.120 --> 0:29:00.360
<v Speaker 1>use of this and I would I would I would

0:29:00.760 --> 0:29:03.840
<v Speaker 1>say the operative word is this, because this is beyond

0:29:03.880 --> 0:29:07.000
<v Speaker 1>that bucket of blockchain that I mentioned. I believe that

0:29:07.560 --> 0:29:13.000
<v Speaker 1>it's this. This thought of an open platform for innovation

0:29:14.160 --> 0:29:17.720
<v Speaker 1>and and platform then becomes this. Oh he said, the

0:29:17.760 --> 0:29:19.920
<v Speaker 1>big word of platform. What's that mean for you? But

0:29:20.120 --> 0:29:25.040
<v Speaker 1>just think of that as this new capability that says,

0:29:25.520 --> 0:29:30.240
<v Speaker 1>I'm not limited to the walls of my enterprise. I'm

0:29:30.240 --> 0:29:34.840
<v Speaker 1>not just a pharma company. I can pull down my

0:29:35.120 --> 0:29:41.760
<v Speaker 1>barriers of business and work collaboratively with a regulatory body,

0:29:41.600 --> 0:29:46.520
<v Speaker 1>a government, or a shipping group. I can I can

0:29:46.560 --> 0:29:50.920
<v Speaker 1>work all the way down to that retail store or

0:29:51.360 --> 0:29:54.920
<v Speaker 1>or pharmacies that's distributing my good because I can see

0:29:55.400 --> 0:29:58.920
<v Speaker 1>or I'm somewhere in that value chain where I'm a

0:29:59.120 --> 0:30:05.200
<v Speaker 1>supplier to supplier to the supplier to the cooperative that's

0:30:05.680 --> 0:30:08.880
<v Speaker 1>supplying one of the players. And if you see, if

0:30:08.880 --> 0:30:10.880
<v Speaker 1>you can get that far down, it opens up the

0:30:10.960 --> 0:30:17.640
<v Speaker 1>market and it allows for new players, new areas of collaboration,

0:30:18.840 --> 0:30:22.480
<v Speaker 1>and it really allows us then to think about what

0:30:23.080 --> 0:30:27.520
<v Speaker 1>that platform of business looks like tomorrow. And it blurs

0:30:27.560 --> 0:30:30.200
<v Speaker 1>the line then between industries as I've I've called out,

0:30:30.960 --> 0:30:35.080
<v Speaker 1>because you you have them working together. It's then becomes

0:30:35.560 --> 0:30:40.120
<v Speaker 1>a blurring of my ecosystem in your ecosystem, So it's

0:30:40.160 --> 0:30:43.920
<v Speaker 1>less about my enterprise my ecosystem, and it becomes a

0:30:44.040 --> 0:30:51.920
<v Speaker 1>collaborative team sport of outcomes, and your competitiveness becomes based

0:30:51.920 --> 0:30:57.520
<v Speaker 1>on your ability to transact in that ecosystem and convene

0:30:58.000 --> 0:31:03.120
<v Speaker 1>outcomes around how you deliver value in that value chain.

0:31:03.200 --> 0:31:07.400
<v Speaker 1>So it sounds complicated, but think about getting outcomes out

0:31:07.400 --> 0:31:13.240
<v Speaker 1>of a much more level and transparent ecosystem versus me

0:31:13.400 --> 0:31:17.000
<v Speaker 1>putting my arms around a walled capability. That's that's where

0:31:17.040 --> 0:31:19.000
<v Speaker 1>the future is, and it's it's it's going to be

0:31:19.000 --> 0:31:23.880
<v Speaker 1>built on open platforms of capability with data always in

0:31:23.960 --> 0:31:26.640
<v Speaker 1>the center. So you can call out all the buzzwords

0:31:26.680 --> 0:31:32.400
<v Speaker 1>from AI, robotic, process automation, IoT, advanced analytics, all of

0:31:32.440 --> 0:31:36.440
<v Speaker 1>those use data and they're going to be operating in

0:31:36.480 --> 0:31:39.560
<v Speaker 1>an open platform. And that's where we as IBMC the future,

0:31:39.560 --> 0:31:41.680
<v Speaker 1>and that's where we're running hard and fast and leading,

0:31:42.960 --> 0:31:45.320
<v Speaker 1>leading as as quickly as we can. Well, Jason, that

0:31:45.400 --> 0:31:49.720
<v Speaker 1>to me sounds incredibly exciting. I love the idea of

0:31:49.800 --> 0:31:55.120
<v Speaker 1>this approach opening up new opportunities because ultimately that's going

0:31:55.240 --> 0:32:00.200
<v Speaker 1>to manifest as benefits to everyone down the road in

0:32:00.280 --> 0:32:03.280
<v Speaker 1>some way, whether it's a consumer good or a service

0:32:04.120 --> 0:32:09.360
<v Speaker 1>or something like life saving pharmaceuticals. Like the idea of

0:32:09.400 --> 0:32:12.440
<v Speaker 1>being able to find new ways to collaborate, in new

0:32:12.480 --> 0:32:17.280
<v Speaker 1>ways to innovate, to have that enabler there, uh, really

0:32:17.360 --> 0:32:19.600
<v Speaker 1>makes me excited about the future, which I think is

0:32:20.360 --> 0:32:24.040
<v Speaker 1>something that is is sorely needed. Honestly, the idea of

0:32:24.080 --> 0:32:26.719
<v Speaker 1>being excited about the future is a great thing. So

0:32:26.880 --> 0:32:30.800
<v Speaker 1>I thank you for coming onto my podcast and and

0:32:30.880 --> 0:32:34.440
<v Speaker 1>explaining this in a way where it doesn't make someone's

0:32:34.440 --> 0:32:37.640
<v Speaker 1>eyes just glaze over as they start to think about,

0:32:38.280 --> 0:32:41.560
<v Speaker 1>you know, hashing and making up blocks and adding another

0:32:41.600 --> 0:32:44.200
<v Speaker 1>block to the chain, and all of the all of

0:32:44.240 --> 0:32:47.920
<v Speaker 1>the ways that you can try to explain that process

0:32:47.960 --> 0:32:52.520
<v Speaker 1>that tend to lose of the audience right off the bat.

0:32:52.640 --> 0:32:55.240
<v Speaker 1>So I appreciate your approach very much. Thank you for

0:32:55.320 --> 0:32:59.320
<v Speaker 1>joining the show, Jonathan, thanks for the conversation, thoroughly enjoyed it,

0:32:59.360 --> 0:33:01.920
<v Speaker 1>and anach on all the best to you in in

0:33:02.120 --> 0:33:05.360
<v Speaker 1>the rest of you, stay stay safe, stay healthy, stay happy.

0:33:06.120 --> 0:33:10.680
<v Speaker 1>Jason's focus on outcomes rather than the technical process is

0:33:10.840 --> 0:33:14.200
<v Speaker 1>a useful one to explain how important blockchain is from

0:33:14.240 --> 0:33:20.520
<v Speaker 1>a practical application standpoint. As we've seen, flexibility and adaptability

0:33:20.560 --> 0:33:24.560
<v Speaker 1>are too important qualities for businesses in general, but particularly

0:33:24.680 --> 0:33:28.120
<v Speaker 1>during times of rapid change. With respect to that, I

0:33:28.120 --> 0:33:30.960
<v Speaker 1>think it's pretty clear how blockchain technology can play a

0:33:31.080 --> 0:33:35.000
<v Speaker 1>part in helping businesses understand exactly what's going on throughout

0:33:35.040 --> 0:33:38.520
<v Speaker 1>the entire supply chain. I would like to thank Jason

0:33:38.600 --> 0:33:42.160
<v Speaker 1>Kelly again for coming onto the show and explaining his work.

0:33:42.560 --> 0:33:45.480
<v Speaker 1>To learn more about ibm s work in blockchain, visit

0:33:45.760 --> 0:33:56.320
<v Speaker 1>www dot IBM dot com. Slash Blockchain text Stuff is

0:33:56.320 --> 0:33:59.480
<v Speaker 1>an I Heart Radio production. For more podcasts from my

0:33:59.600 --> 0:34:03.160
<v Speaker 1>heart rate you visit the I Heart Radio app, Apple Podcasts,

0:34:03.320 --> 0:34:09.840
<v Speaker 1>or wherever you listen to your favorite shows. H