Driving Innovation with Generative AI on AWS | The Six Five Summit

Hi, this is Pat Moorhead, and welcome back to the six five Summit 2024. As you can tell, it's all about AI at this year's summit. It's not only about building out the infrastructure and the tools, but also about the benefits that enterprises and even consumers are getting around that.

Now, one of the, the key things we're seeing from a research perspective is the dawn of these end-to-end enterprise AI platforms. And that's essentially all the way from data ingest to getting your AI application to do what you need to do, and everything in between from a, a, a generative, uh, uh, point of view, uh, using ai, but obviously also, uh, machine learning. And I can't, couldn't even think of a better person to have this conversation with, uh, than Matt Wood who runs artificial intelligence products at AWS.

Matt, welcome to the summit. Thank you so much, Pam. It's a pleasure to be here.

I appreciate it. Absolutely. You know, it's been, uh, fun, uh, watching what you have been doing, uh, from the outset, uh, with Bedrock.

Well, first of all, I mean, uh, AWS is not new to ai, uh, industry leading, uh, cloud AI platforms for developers, uh, and enterprises. Uh, SageMaker, I believe, was the first, uh, end-to-end machine learning platform. Uh, we're getting even more information about Q but it is exciting stuff.

So I have a real question here, uh, and it's probably the most important, which is what distinguishes AWS from all of the noise out here that we've heard of agents and co-pilots and assistance. Yeah, sure. I think number one, thank you for having me.

Again, appreciate it. Um, I think number two, this is just an incredibly exciting time, uh, for machine learning, uh, for artificial intelligence, for cloud computing, for technologists, but also for, uh, business leaders who are looking to kind of seize the opportunity of this technology to completely reinvent, you know, their own customer experiences to kickstart or accelerate their, uh, journey through digital transformation. And not just reinvent their own business and their own products and their own processes, but drive that transformation, you know, deep into their, into their industry as well.

So it's an incredibly exciting time. This is probably the single largest shift in technology of how we're gonna interact with data and information and each other. com, went on to experience pretty tremendous growth, uh, in the intervening decades.

And it's my guess that, you know, today, customers that are investing in generative AI in a similar way are gonna experience multiple Amazons of growth, uh, over the next yeah. Couple of decades as well. So it really, really is an exciting time.

You know, uh, as you say, we've been doing a lot of work around, uh, machine learning and artificial intelligence at AWS for many, many years. Uh, I actually helped launch the very first Amazon machine learning service all the way back in 2016, 2017, I think, um, that evolved to become, uh, a SageMaker, uh, which has been, you know, really become the, the de facto standard way. The most organizations have been working on machine learning.

We have hundreds of thousands of customers, uh, using SageMaker today. Um, but generative AI is kind of really changing the game, again in a number of different ways. Uh, there's two really remarkable changes that are happening at, at the same time that in isolation would be interesting and exciting, but happening together I think is really demonstrating why generative AI is different and why a lot of customers are are excited about it.

The first is, there's just a step function increase in the complexity of tasks that you can now solve using machine learning through artificial intelligence. And so these tasks are, are, were once very kind of, uh, one dimensional. You could take simple inputs and, you know, build a model to predict simple outputs and then more complicated outputs.

But today, you know, that, that, uh, that complexity of the type of problems that we can solve is just, uh, uh, just getting combinator larger as the technology continues to improve. At, at the same time, the skills required to be successful with machine learning and artificial intelligence, uh, are, are, are, are reducing. And as a result, the technology is, is democratizing and becoming much more accessible, uh, in than it ever has done before.

And so, the result of that is that, you know, more and more customers are getting started, you know, either training and tuning their own models. Uh, the large foundation frontier model providers like Anthropic and Misra, and, you know, Amazon and others, you know, there's a lot of that work happening. But increasingly, I think what we'll see is the more customers are, are able to, because the technology is democratizing, are able to take those foundation models as a starting point and use the underlying technology to be able to, uh, customize them, to specialize them in really meaningful ways for their organization.

Uh, we also see, you know, a huge increase in the usage of people just using generative AI to be able to build net new applications. And there we make available a service called Bedrock. Uh, so Foundation Models and Bedrock, see what we did there.

Uh, so Bedrock gives you access to, you know, the broadest set of foundation models, uh, that are available anywhere. It gives you access to the broadest set of additional capabilities for not just prototyping, but also taking those prototypes through to production with guardrails and knowledge grounding and fine tuning and agentic systems. And in addition to that, uh, is able to deliver all of that, not just in a, in a, in a cul-de-sac, where all you can do is prototype, but in an environment where any organization can bring the most sensitive data, right?

And trust that that data will be used, uh, uh, will not be used to improve the underlying models, won't be reviewed by humans, doesn't travel over the public internet, uh, and all those sorts of things. And so through Bedrock, we're really seeing, you know, we have tens of thousands of customers using Bedrock today, uh, to build and transform their organization precisely because to do that, you need access to data. And to be able to access data with these models, you need to be able to have the right security, uh, confidentiality and privacy controls.

And then finally, we're making a set of applications available to customers, uh, which we call Amazon Queue, which is by far the most capable assistant, which is available to complete tasks at work. So we have tasks that will help you write software more quickly, analyze data more quickly, and knowledge informa, uh, manage knowledge inside your organization more effectively as well. So for all of those reasons, uh, the majority of customers that are getting started on their generative AI applications today are doing so starting with AWS and those that maybe, you know, started prototyping earlier, uh, at the beginning of last year are migrating to AWS really as quickly as they can.

So I appreciate that, all those comments there. And, you know, whenever we get a, a major inflection point, uh, in the industry, right, uh, it comes down to use cases, it comes down to workloads that support those use cases. Then we get into this ever present horizontal versus vertical and industries, uh, matrices.

And I, and I'm, I'm curious for you at this point right now, are there certain, uh, industries or and use cases that are, that are bubbling, uh, to the top, you know, first mover type of things? Because, you know, when I talk to Enterprise, some of their biggest questions are, where do I start and, and what do I do? And, you know, pos beyond POC and then beyond POC, uh, to really get things going?

Yeah, it's, it's a good question. I think, um, you know, e every customer that I speak to, uh, which is, you know, several hundred at this point, but every customer I speak to, you know, I I really have not seen this level of energy and enthusiasm and momentum, and most organizations are being very deliberate. Uh, they're finding the use cases that they think can be really meaningful.

Uh, they are, they're prototyping Stein taken through to production, uh, and, and being pretty successful with a, with a, uh, with a majority of them. Uh, but there is a group that's kind of moving faster than the average. Um, and it's, at least to me, it was slightly counterintuitive.

Uh, but it's actually the regulated industries that are moving faster than the average, uh, in this, in this new world. It is interesting. I, I think if you'd have even told me a year ago that 160 year old life insurance companies were operating in the vanguard of artificial intelligence, I probably would've been pretty surprised to find out that that was the case.

But it is what we're seeing today, and there's a couple of reasons for this, I think, uh, the, the first is that a lot of the regulations around financial services, uh, life sciences, healthcare, manufacturing, insurance, you know, these, these regulated industries have had to comply with, uh, governance requirements around their data for, you know, 20 years or so. And those, though that compliance may have felt like a bit of a headwind at the time, I'm sure, but it actually forced all the right behaviors inside these organizations to get their data quality up, to put the right governance in place so they understood, you know, what data they had, what it could be used for, which tools it could be used with, who could do what with it. And they have the right privacy and security controls, you know, around that data.

And those are all the things that you need to do to be successful with generative ai. And these groups have already done it. And so, as a result, the incremental investment to be successful with generative AI is actually relatively small, and they're able to move much faster as a result.

So that's the first reason. The second is that, um, most of these organizations have absolutely huge volumes of private text data. You know, if you think of market reports or clinical trials or manufacturing results or health records, these are, these are not on the public internet.

You know, the foundation and frontier models, I've never seen them before. Um, and, but there is so much information and net new knowledge inside them that organizations want to be able to leverage in more meaningful ways. So sometimes that can be just summarizing what's in there.

Increasingly, it's connecting the dots and finding similarities and differences, and then using that information for brainstorming to come up with new ideas and new strategies inside the organization that are gonna be gonna be really, really meaningful. And so having access to that text data in a way which is well governed, and being able to find the right model through Bedrock to be able to handle all of those different use cases, uh, has been, uh, has been really transformative. And then the third area is that I think, you know, charitably these organizations in part because of compliance, but also just that they are traditionally a little bit more conservative.

Um, they're just earlier in their digital transformation journey. And I think that they have been looking at, you know, the, the, the transformation that has happened in hospitality and travel and media and gaming, you know, the Netflixes and Airbnbs and Expedia of the world that have been able to use the cloud to be able to, you know, disrupt and transform, you know, their entire industry. Uh, they'd be looking at that kind of, uh, generously from the sidelines.

And today they see generative AI through the cloud as not just also a way to catch up with that level of transformation, right? And actually lead from ahead of it. And so, for all of those reasons, it's, it's actually those, you know, somewhat counterintuitively, it's actually those types of industries that are moving the fastest to deliver value in production, uh, on generative ai.

I, I'll admit, you know, as analysts, we're not supposed to admit, not supposed to say we're surprised, but I'm surprised that you brought that up. 'cause typically they're the laggards, uh, when it comes to that. But in my conversation with a lot of enterprise, it's like security and data, right?

Data management and, and security. And it sounds like in, in a interesting, an interesting shift in normally who the fast movers are. Uh, here we are.

Um, I think that, that, I, I think that that may not be the last surprise that we see. Okay. You know, imper is a really discontinuous flux, you know, you will expect to be surprised along the way, right?

I think we have a lot of organizations are surprised by how easy it is to prototype with this, with this, uh, with this technology. Uh, I think they're surprised to find the breadth of utility of this technology. I think they're surprised by, you know, what the, the journey they have to go on in some cases to be able to take those prototypes and, and take them into production.

So a lot of what we are focused on is helping with like those sorts of surprises, right? Helping customers through the, the, the, the prototyping, the, the use case identification, and then the delivery into production. 'cause there is actually a little bit more work than I think most people appreciate that after the initial conviction, uh, that you get from a, from a successful prototype, For sure.

So, you know, this track is about end-to-end generative AI platforms, or AI plat enterprise AI platforms. And you have a managed service for generative AI or foundational models called Bedrock. And sometimes, you know, we can all dive into the tech and dis construct it and confuse everybody, but, but a lot of the times it, it starts with an elevator pitch.

What's the elevator pitch for, uh, for Bedrock that is, um, resonating, uh, with your customers? Yeah, I think it's, uh, it's pretty straightforward. You know, bedrock, you know, customers tap us is the fastest, most cost effective, safest way to deliver generative AI applications into production.

That's it. Yeah. And, you know, under the hood, in order to be able to do that, yeah, there's a lot of pieces that we need to be able to deliver, uh, deliver in ways that are better than anyone else, uh, is able to do so with a level of breadth of capability that is broader than anyone else is able to deliver.

And because this area is moving really, really quickly, you know, we have to keep on top of that, uh, that innovation as well. And you see that, you know, across AWS we've actually, we've actually delivered twice as many, um, net new features for machine learning and artificial intelligence, inter general availability than all of the other cloud providers combined. And so it's not enough just to have the breadth.

It's not enough just to have the models. It's not enough just to have the best models. You also want, uh, customers tell us, you know, platforms that are able to keep up with this pace.

And, you know, from that perspective, it, it doesn't even seem much of a fair fight to me. Ooh, I like that. I like it.

I like that a lot. So, um, by the way, one thing I really appreciate about, about Bedrock is, is its simplicity and the fact that you don't even need to have pick a compute method. Uh, it picks the right one for you.

And quite frankly, um, that's another element of simplification that, that, um, enter enterprises, uh, and governments are, are looking for. So, uh, congratulations on going ga on q. Um, we, uh, wrote a research, uh, paper, uh, out there that, uh, I, I thought w was pretty good.

And it's getting some, uh, pickup out there. Uh, a lot of the questions that I get as a analyst and pundit company out there is, Hey, how is it different, right? We have assistants, we have co-pilots, we have agents, we have all these different terms being thrown around by a bunch of different companies.

Um, uh, let's talk why, why q What sets it apart? Yeah, for sure. I mean, Q is today the, the most capable assistant for completing tasks at work.

And you can think of Q as a, as a way to interact with a, an assistant that is an expert in lots of different pieces of your organization and helps with lots of different tasks inside of your organization. Yeah. And so we have by far the broadest set of, of, of, of those tasks that we can help with.

Um, Q is, uh, particularly good at working with software development and accelerating software development. So Q can help you write code, uh, it can help you write tests and understand code and documentation, all those sorts of pieces. You know, that's a really big accelerator.

And, you know, we found that today the code generated by Q is not only more secure than other assistant, uh, but is also used and consumed and accepted in, uh, in more cases than any other assistant that we've seen with published results. So customers, uh, have told us that they will, they actually accept about 50% of the code that, uh, q generates. So, which is higher than anyone else.

So just from a software development code, generation code suggestion task, you know, you can expect to see, you know, pretty significant speedups for software development there. And really what we're trying to do in all of these tasks is kind of what we did with cloud computing. With cloud computing.

Our original goal was to, our original observation was that about 70% of the work of like putting an idea together wasn't the building and the construction and the idea and the product development. It was just this sort of undifferentiated mark of having to do the work and provision the infrastructure in the terms of the cloud and get the servers and the storage. And yeah, nobody wants to do any of that.

And what we've noticed is that the, this 70 30 balance is, is actually pretty common with lots of different areas inside the enterprise and the type of work that we do. Software development is a really good example of that. If you talk to software developers, only about 30% of the time that they're, that they're spending writing code is on the code.

The other 70% is on the, the undifferentiated muck. Yeah. And so what Q is trying to do is just remove that undifferentiated muck, and we, we do co-generation, and that's very useful.

But where q really shines is we have a set of, uh, helper assistant agents, which will not just generate code for you, but will, uh, take an objective work backwards from that objective, create a plan, and then systematically work through that plan to complete higher order tasks on your behalf. So, as an example, Q has a, a, a feature development agent, uh, uh, which will take in not, Hey, I wanna write a new sort function for this data, but there you say, Hey, I wanna write a favorites list for my social media application. Yeah.

And Q understands the code, it understands all the code that you're working with and everything in inside the repository. It looks at all of that code, and it comes up with a, with a strategy. It says, here's the code that we need to rewrite, here's the additional code that we need to add.

Is the test that we need to run as we're going to make sure nothing breaks, is the additional tests we need to add, is the documentation and so on and so forth. And you can review that strategy upfront, but when you're happy with it, you just hit go and queue works through it systematically, and you can watch it go and it'll solve problems as it goes and pulls in information as it needs and is pretty fascinating to watch. But at the end of it, you get a completed update, a set of pull requests of new code that you can commit across your application, which develops that feature.

5 or two x speed up. This is more like a 10 to 50 x speed up in terms of developer productivity. You're moving all of that mark associated with developing a new feature and allowing developers to take their idea and get it into the product you are in, in an order of magnitude less time.

And we've also got 'em for other just muck work like, you know, transformation, co transformation or migration, right? So moving from one version of Java to another version of Java, right? That's just undifferentiated fixed cost work, no engineer, thanks you for tasking them that work.

The best you end up with is you end up right back where you started, but like two months later it's just Yik. And so what key will do will say, Hey, I see what version of Java you're running, running on. I'm gonna produce a strategy to migrate you and do all the code optimization and run the test to safely migrate you from one version to another version.

The developer just clicks a button and reviews the code and you're done. And so there you're really looking at, you know, two orders of magnitude speed up in terms of delivery. And when you look at, uh, q from a software developer perspective, uh, against all the other benchmarks that are out there today, publicly available today, Q is the king of the hill.

So if you look at the, what's called the SWE benchmark or the SWE Live benchmark, Q is the best performing agent for completing, uh, software development tasks available anywhere today. And so just for software development, there's this one or two order of magnitude improvement by removing all of that muck. And we're doing the same thing with data analysis, letting you ask questions of your data, get responses and answers and relevant visualizations, and second, and being able to identify and build applications around the data inside your organization to be able to automatically, you know, drive higher levels of automation using that data.

And so, again, it's just, it's just a completely different world when you're operating with Q 'cause it has access to, by far the broadest amount of information it supports the broadest number of tasks and the tasks that it supports are industry leading and defining in many ways. And so, again, it's just a, it's, uh, it's a totally different world on AWS, uh, than than anywhere else today. Yeah.

And by the way, I saw the, the figures on the developer scores, uh, and I, not that I was ex, I mean, I was ex, AWS was foreign for developers, right? Uh, to get infrastructure outta the way 15 years ago. And your, your continued focus of developers is not a, not a surprise, but it's also nice to get a, get a benchmark, uh, win out there for the capability of, of this for, uh, specifically for developers.

I also liked, uh, the connectors you had to enterprise apps. Uh, I liked the supply chain, uh, uh, stuff that, that q uh, was doing. And I'm, I'm certain there's gonna be even more, uh, to come out later.

So in transitions and, and in new waves, uh, of technology, you know, there's a lot of debates out there, and one of these is, uh, big model, small model, horizontal model, vertical model, uh, slims. But I, I'm curious, what is your approach to foundational models that you think is the best path forward for your customers? Yeah, it's a, it is a good question.

I mean, the answer to all of those answers is, is yes. Right? There, there is not, there is not one model.

There's not one model architecture, there is not one model family that can fit all, uh, every use case. Not gonna be one that that meets out all the use cases. If you just, it, it's kind of instinctual.

Honestly, if you, if you go and talk to enterprises, you know, they'll often start their generative AI journey by looking at, you know, bottoms up all the ideas across the organization as to how they might apply this technology. And, you know, sometimes customers send them to me as a kind of gut check, and I've been sent spreadsheets of, of six, 700 ideas, right? Uh, of, of everything across the organization.

It's just impossible to imagine that a single model is the best model to fit all of those different use cases. Instead, our, our instinct, and this is turning out to be correct, um, in, in large part because we see so much success from customers on AWS but also, you know, competitors are copying us as quickly as they can, that you really want access to a broad set of models so that you can match the use case to the special capabilities of that model, right? So sometimes, as you were saying, sometimes models have different sweet spots.

Sometimes they are very general, sometimes they're very specialist, sometimes they're good at different tasks like summarization or natural language or code generation and interpretation or analysis or reasoning, whatever it might be. Other times they just have different operational characteristics, right? So sometimes they're really fast, sometimes they're really low cost, sometimes they're really intelligent.

And in every isolated case, you want to be able to take advantage and lean in on the sweet spot of that model to be able to get the best possible results. And that means that those results are at the price point that you're comfortable with, have an accuracy that is actually useful and are reliable and consistent in a way that you would actually put your company name behind it. So in isolation, you really want access to the broadest set of models in order to be able to maximize your chart so you can find the right sweet spot for your use case in isolation.

But in aggregate, you wanna be able to solve all of those six, 700 ideas across your organization to do that. And you need a lot of models. But the super power of generative AI is in the combination of the models.

Yeah. It's in the combining of those sweet spots to be able to form an assistive system, an assistive system or intelligent system, right? Which is stronger than the sum of those parts.

And that's really why a lot of customers, you know, are flocking to, to bedrock. The majority of customers on bedrock use more than one model in their, in their applications. And the reason for that is because there is a compounding effect of intelligence.

When you put these models together. It's a multiplier. Yeah.

Not, not an, and so for those reasons, plus the capabilities, plus the, we've got access to the best models with, with Claude three, Opus got access to the, the broadest set of guardrails, the best guardrails, agent agentic systems, privacy, security. You know, it's, it's, it's pretty clear why customers are choosing bedrock in, in the, in, in the drugs, Which by the way, have it your way is, has always been a hallmark as long as I've been, uh, covering you, um, your compute as an example. I mean, you want big, you want little, you want, uh, our branded stuff.

You want merchant silicon, whichever way you want it. You know, you, you want to do containers, here's the five ways you can do, uh, containers. So it really is a, uh, it's what we, I I expected from, uh, from you.

Um, hey, let's shift to, um, a lot of conversation about responsible ai. And, and I'll, I'll admit my, I try to pay attention, uh, every, every time I'm getting, getting, getting briefed, I know it's important. Uh, responsibility has a different definition to, to different people.

And, and I'm curious, uh, what does it mean, uh, to you? What does responsible AI mean? Well, to me, it really means that you are taking, uh, you are taking seriously the benefits and the shortcomings of every component of your application and assistant, and really understanding where the limitations are and doing everything that you can to control and reduce those limitations.

And what that means is that in aggregate, the final agent or the final assistant, or whatever it is, that you are building the final help up, um, you know, will be able to operate in a way which is safe, which delivers reliability, which has consistency, uh, that has, you know, truthful, um, results. Uh, and that doesn't, you know, go off on a tangent and potentially talk about things that you don't wanna talk about. And so you can kind of think of these, these foundation models, when you take them off the shelf, they've got a pretty good set of guardrails built into the models, um, yeah.

Out off the shelf. But in every case that we've found, either internally at Amazon or working with customers in all of the domains that we've been talking about, yeah, regulating and non-regulated, every customer wants to the ability to be able to shroud those models and additional layers of control. Yeah.

And sometimes that control is grounding the model in the reality of your own business. So off the shelf, these models, you know, that they're trained on the internet most of the time you, they've got a very, very broad knowledge of a lot of different concepts. That's really critically important.

But most organizations that they operate at depth and at depth, it's a bit more like Swiss cheese down there. There's like areas of information density and areas of information, sparsity and mistakes are made when these models kind of stumble into these Swiss cheese gaps and are still trying to generate responses, even though they don't have a lot of information to rely. And so a lot of what customers spend time on with Bedrock is how do I plug those, those information gaps?

How do I plug those Swiss cheese gaps such as the models have more information to rely on? Or how do I constrain the model in ways that it behaves the way that I want it to, to adjust the style and the tone to be able to integrate more safely with our first and third party systems and data? And then finally, how do I just ensure that it only stay, that it stays on topic, that it only talks about either for the inputs that get to the model or the outputs that come from the model that get back to the, the system or the user.

How do I ensure that it, that it stays on topic? And so we make available today the, the best performing set of guardrails, uh, to enable you to, to do that. And so with Bedrock, you can say, Hey, here's all the rules.

Here's everything that I don't want you to ever talk about. I never want anything to do with these terms and these rules, yes, get anywhere in the model, but also we allow you to say things like, I dunno why you'd ever wanna do this, but I never wanna talk about anything to do with basketball. For sure.

And so you can say to the model, I don't ever want anything to do with basketball to get near the model. And if the model for any reason starts talking about basketball, I wanna reject, I wanna detect it and reject it so it doesn't get back to the user. Now, that's a, uh, that's a very, uh, you know, simple example.

But in addition to just filtering based on keywords, we can filter based on entire topics, and that's what we do, which is, you know, so transformative for organizations, and it gives them the confidence to be able to not just bring their prototypes, but their real production systems that they're gonna give to their internal teams that they're gonna put their company logo on and make available to, to their external customers. There's a huge amount of brand equity and loyalty and trust built into these organizations. And guardrails like this are one of the components that we provide that allows them to, with confidence, deliver those sorts of experiences.

Yeah, it's a very pragmatic, uh, approach. I mean, in one side you have a, a doctor or something in medical on the other side, you have a gaming, gaming site where, you know, people are throwing, uh, across, uh, different things. And you know, I, I saw a ruling out of a, a different country of an airline who made a commitment, uh, on something too.

And being responsible could be even being accurate, uh, as well and giving accurate results. But I, I like, um, I, I like your, I like your definition. So great conversation.

Final comment here. Um, I'm an advisor to, to the C-suite, uh, among others. And there's a lot of conversations about, uh, automation, job displacement, job, job, and then substitution, right?

Um, and keeping a human in, in the loop. And I'm curious, is it a simple that says, keeping keep the human in the loop long enough that, uh, to make sure it's accurate? Um, and, and something different than that?

How, how are you advising your customers on this? Yeah, it's, it's a good question. Uh, you know, I think even the most bearish on artificial intelligence would agree that the type of work that we're gonna do over the next couple of decades is, is, is gonna meaningfully change.

And, you know, if you, if you, if you accept my kind of stipulated argument earlier, that there's kind of 70% of the work that we do today is kind of undifferentiated, you know, that's the stuff that we're gonna get rid of. And as a result, we're gonna free up all of our time to focus more of our attention and our time and our energy and our efforts on what we only get to do 30% of the time today. And so, right, that 30% will become the hundred percent, uh, in, in all cases, but the, the, the work that we are gonna do is going to change.

And that is a very human problem. And it requires us to approach, uh, the changes. I think with, with empathy, it requires us to approach these changes with, through a human lens.

It requires us to be really focused on helping everybody whose job is gonna change to really u upskill understand how artificial intelligence can play a role in expanding that 30% to the a hundred percent, right? So they can spend more time on the really undifferentiated work that is where they wanna spend their time anyway. Yes.

So I wouldn't assume that in every case, that is just gonna be automatic. We really do have to be, uh, humane, empathetic. Yeah.

Uh, emotionally invested in the change that a lot of us are gonna have to go through in order to be able to, uh, to make that change. And there's gonna be some upskilling, there's gonna be a lot of training, there's gonna be a lot of investment, a lot of change management, you know, all those sorts of things. And as we go and as those roles change, you know, we'll see, you know, faster and faster growth.

And I suspect that, again, another surprising kind of second order effect is that for organizations that are able to plot that course and move from 30% of the time spent on differentiated work to a hundred percent of the time spent on differentiated work, their businesses are gonna grow disproportionately to that focus, right? And so as a result, I suspect where that is most effective could be software development, could be contact centers, whatever. Um, we'll end up with more people doing that work because we tend to invest in areas where we see the largest growth and the largest return on investment.

And so I suspect we're gonna end up with far more people working in software development. The work that we do will be meaningfully different, right? But I think we'll end up with far more people working on it as an example.

Yeah. Matt history's on your side too. If, if I go back 35 years, desktop publishing, you know, was gonna kill the creatives, uh, moving from machine code to cobol, uh, meant we weren't gonna need any programmers anymore.

And I heard the same thing about ides, uh, as well. And what happens is we create new, different types of jobs we create, um, we allow people to have superpowers to do even more. I remember when PowerPoint was a threat, uh, to, to, to certain, uh, industries.

Now, I like the way you talked about it has to be planned and we have to do it with empathy and, and respect. Otherwise, you know, what we didn't do right as a country, and this isn't technology, but I grew up in Cleveland, Ohio, in the Midwest, and we decided to get rid of all the jobs, and we didn't retrain anybody. Okay?

And, and, and bad things happen, uh, when, when, when those things happen. So, but I'm, I'm, I'm optimistic just because we're having these conversations that, that this is, is gonna happen. Matt, I gotta tell you this.

I can't believe that that, that, uh, this interview has been great. I, I, I really thank you for, uh, spending, uh, this time. Thank you.

I really enjoyed it as well. Appreciate it. Appreciate that.

So this is, uh, pat Morehead and Matt Wood from AWS talking about end-to-end enterprise AI platforms. I'm sure you've heard about Bedrock. I'm sure you've heard about q uh, dive in and learn more if you don't, uh, stick around for more enterprise AI platform action.

And hey, if you're into infrastructure, we have that plan computing enterprise apps, uh, we are covering the gambit here on the, on these, I was gonna say the AI Summit, the six five Summit 2024 is kind of an AI summit. So thanks for tuning in and take care.