00:00:00.320 --> 00:00:05.440
Welcome to the third in our talking data and AI webinar.
00:00:05.599 --> 00:00:10.960
For those who don't know, my name is Lyle Ritchie, head of Talent Solutions here at Head Resourcing.
00:00:12.000 --> 00:00:17.519
Today's guest knows a thing or two about turning bold ideas into smart tech.
00:00:18.239 --> 00:00:24.960
Delighted to be joined by Gary Crawford, founder of Owendell Advisory and former CIO at Warracle.
00:00:25.600 --> 00:00:31.199
Gary is someone who's been helping companies design digital products that don't just work, they think.
00:00:32.000 --> 00:00:41.840
Gary's here to talk today about what it really means to go beyond automation and how to build products that sense, adapt, and respond in real time.
00:00:42.719 --> 00:00:46.079
So before I hand over to Gary, just a couple of points.
00:00:46.320 --> 00:00:53.520
So Gary is going to talk to you all today for around 30 minutes, then there'll be a 15-minute QA session.
00:00:53.679 --> 00:01:00.960
So if you could please um thumbs up the questions you would like the answers to, and we can go from there.
00:01:01.200 --> 00:01:01.759
All right.
00:01:02.000 --> 00:01:02.399
Perfect.
00:01:02.560 --> 00:01:04.159
So look really looking forward to this.
00:01:04.239 --> 00:01:05.920
So I'll just hand over to Gary.
00:01:06.159 --> 00:01:07.040
Gary, over to you.
00:01:07.519 --> 00:01:07.920
Magic.
00:01:08.239 --> 00:01:08.959
Thanks, Lyle.
00:01:09.200 --> 00:01:12.239
Um I hope everyone's having a brilliant day.
00:01:12.400 --> 00:01:15.840
Uh Lyle obviously mentioned some of our colleagues in England.
00:01:16.000 --> 00:01:23.680
I was down in London last week, actually, with the uh Natural History Museum, and I've picked up this hideous lurk that's going around on the tube.
00:01:23.760 --> 00:01:24.400
So apologies.
00:01:24.480 --> 00:01:26.079
I hope I don't cough and splutter.
00:01:26.319 --> 00:01:32.560
I'm definitely, I'm told, not infectious over uh over the uh teleconference uh setup here.
00:01:32.719 --> 00:01:36.719
But uh apologies if I do turn away from the camera at any point.
00:01:36.879 --> 00:01:38.879
Um so as Les says, I'm Gary Crawford.
00:01:39.120 --> 00:01:42.560
I'm the founder and chief advisor at Owen Dale Advisory.
00:01:42.640 --> 00:01:53.359
Uh we work with senior leaders to help them understand what AI means for their industry, for their organization, for their strategy, operations, workforce dynamics, uh, and so on.
00:01:53.519 --> 00:01:57.040
We're a relatively young but pretty experienced company.
00:01:57.200 --> 00:02:03.920
We've got people working with that, a huge range of uh clients at the moment doing some pretty cool stuff with AI.
00:02:04.159 --> 00:02:07.519
Um, but more importantly, what are we going to talk about today?
00:02:07.760 --> 00:02:14.080
Well, firstly, we're gonna cover a little bit of a background on what's been happening over the last couple of years.
00:02:14.240 --> 00:02:20.000
Um, obviously, this is a very technical audience, so uh we're not gonna spend a huge amount of time on this.
00:02:20.240 --> 00:02:29.039
Um, one thing I'd caveat actually up front is we're not gonna get really deeply into the technology uh in a very technologist kind of way here.
00:02:29.199 --> 00:02:40.800
What we're gonna talk about really is how AI is affecting our industry and some of the changes that we're starting to see, uh, which actually I think for all of our roles and all of our careers is very, very important.
00:02:41.120 --> 00:02:52.240
So we'll take a look at what's happened over the last couple of years, and then we'll have a bit of a think about the the three key areas really within our organizations that AI is having the biggest impact.
00:02:52.400 --> 00:02:53.439
Where do we automate?
00:02:53.599 --> 00:02:58.000
Where do we enhance, and where do we evolve brand new experiences?
00:02:58.240 --> 00:03:03.439
And then uh as Lyle says, we'll make sure there's plenty of time at the end for some QA.
00:03:03.840 --> 00:03:07.840
So please do uh store up as uh challenging questions as you can.
00:03:07.919 --> 00:03:13.280
I always look forward to that, but I usually think the QA is for the really interesting, meaty things come out.
00:03:13.439 --> 00:03:17.280
Um, so without further ado, Holly Altman, what's been happening?
00:03:17.439 --> 00:03:25.919
Um, well, I'm sure if any of you are like me, your idea of AI has been built up over many, many years with Hollywood and the media.
00:03:26.080 --> 00:03:28.800
And the story tends to be really quite similar.
00:03:29.039 --> 00:03:37.199
AI goes mad and kills people, or AI pretends to fall in love and then leaves people destitute and absolutely heartbroken.
00:03:37.360 --> 00:03:48.000
Um, that particular reference is actually the movie Her that you see on the screen there with uh Jochen Phoenix uh skeleton, a fantastic movie if anyone's um not seen it before.
00:03:48.159 --> 00:04:02.080
Um, but just a few years ago, a couple of years ago, um, we started to move past this because for the very first time, the team at OpenAI put AI in the hands of everybody that can use a very simple website.
00:04:02.240 --> 00:04:10.639
If you know how to use a text box and a button, then for the first time you're able to interact with this broadly misunderstood technology.
00:04:10.800 --> 00:04:27.199
And all of a sudden, people are coming up with haikus where every word begins with the same letter, or they're planning those holidays that they always wanted but never really could wrap their heads around, or suddenly their managers are wondering how they become so unbelievably productive really, really quickly.
00:04:27.600 --> 00:04:36.399
So it's no surprise, really, that within a short period of time, ChatGPT has now become the eighth most visited website in the world.
00:04:36.480 --> 00:04:38.879
And actually, I think that possibly needs to be updated.
00:04:38.959 --> 00:04:41.680
I think it might just have moved up into sixth position.
00:04:42.079 --> 00:04:50.399
Um it's got over 300 million weekly users, and it's got over 1 billion daily messages exchanged on the platform.
00:04:50.639 --> 00:05:00.560
Now, the thing that's really interesting about this from my perspective is this isn't a huge volume of people visiting a traditional website or an app on the phone.
00:05:00.800 --> 00:05:07.839
This is one big one billion daily messages where humans are interacting with an artificial intelligence.
00:05:08.000 --> 00:05:16.399
These are essentially brand new intelligences added into economy or added into social life, which makes this an entirely new proposition.
00:05:17.600 --> 00:05:19.519
So ultimately, what are these things?
00:05:19.680 --> 00:05:23.199
Well, they're nothing more than statistical prediction machines.
00:05:23.759 --> 00:05:31.120
If you give them a body of text, they're really, really good at predicting what the next character in that sequence of characters should be.
00:05:31.519 --> 00:05:36.560
And if it does that a few times, it moves from predicting characters to predicting words.
00:05:36.879 --> 00:05:44.000
If you do it a few more times, it moves from predicting words to predicting sentences, then sentences to paragraphs, paragraphs to chapters.
00:05:44.079 --> 00:05:50.639
Um and before you know it, you're creating these incredible works that could be, you know, something like the works of Shakespeare.
00:05:50.800 --> 00:05:57.040
But all they're doing is statistical prediction, they're just predicting that next character in line.
00:05:57.600 --> 00:06:03.519
But they're able to do that because they've been trained on a huge volume of data from all over the internet.
00:06:03.920 --> 00:06:14.000
And because of the vastness of the data that contributes towards these large language models, what we find is at great scale, you start to get these kind of cultural nuances emerging.
00:06:14.160 --> 00:06:23.920
So it understands aspects of our social life or how we would interact in our working lives, starts to understand all different little nuances of how we behave as humans.
00:06:24.079 --> 00:06:29.120
So the responses that come from them actually start to look really quite human-like.
00:06:29.199 --> 00:06:32.480
Um so that gives us an incredibly powerful capability.
00:06:32.879 --> 00:06:36.480
So, why are those large language models so relevant for us in business?
00:06:36.720 --> 00:06:47.040
Well, all of our businesses are language businesses, all of our regulations that we work within are language regulations, and all of our customer interactions are language interactions.
00:06:47.279 --> 00:07:09.360
So large language models potentially have an opportunity to play any point you see in business, you're seeing regulation, you're seeing customer interactions, essentially anywhere we use language, the operating system to the entire world, there's a potential opportunity to rethink how artificial intelligence could potentially do something in that environment.
00:07:09.600 --> 00:07:17.360
Now that's made even more interesting when you start to consider how intelligent actually are these machines.
00:07:17.600 --> 00:07:26.879
And if you go back to 2003 when ChatGPD 4 came out, they were really intelligent and it was really exciting to interact with these things.
00:07:27.120 --> 00:07:38.879
But if you use IQ, and I'm not saying by any standards that IQ is a good measure of intelligence, and but if you took a look at how we'd measure IQ, it probably sits somewhere just above 80 IQ points.
00:07:39.120 --> 00:07:45.839
And then you fast forward just over a year to GPT-4 Omni, it's pushing just above 90 points.
00:07:46.079 --> 00:07:51.600
Um beginning of this year, you've got the open source deep seek models that came out of uh of China.
00:07:51.759 --> 00:07:59.439
They're in about that 100 or so mark, so starting to get really quite comparatively intelligent with your average human.
00:07:59.600 --> 00:08:01.040
But things didn't stop there.
00:08:01.279 --> 00:08:04.160
You look at 01 preview, it was just under 120.
00:08:04.319 --> 00:08:06.879
You look at 01, it was just over 130.
00:08:07.040 --> 00:08:18.240
And actually, if you look at 03, the reasoning model that was fairly recently launched, that's up just under 160 IQ points, which is some serious Einstein-level intelligence.
00:08:18.480 --> 00:08:30.319
Now, some of the leading academics in the space believe that we're now in a position where the IQ of uh a model is approximately doubling every five and a half months.
00:08:30.480 --> 00:08:33.600
So that gives you an idea of the rate of change that we're seeing.
00:08:33.759 --> 00:08:36.879
We've spoken about how quickly this is changing for a long time.
00:08:37.120 --> 00:08:41.360
Um, but by now, I think many people thought that this would be slowing down.
00:08:41.519 --> 00:08:42.480
That's not what we're seeing.
00:08:42.559 --> 00:08:46.159
It's quite the opposite, and this is continuing to accelerate.
00:08:46.879 --> 00:08:49.840
But of course, it doesn't just stop with large language models.
00:08:50.000 --> 00:08:53.360
We've got huge progress is happening in the visual space as well.
00:08:53.519 --> 00:09:07.200
So, for example, if um, if you jumped across into uh mid-Jermay about two years ago and put in a prompt for a close-up of a Victoria crown pigeon with striking blue plumage and a red chest, you'd get something like this.
00:09:07.360 --> 00:09:15.120
Uh, and I think probably we'd all be phoning up our local councils and wondering if a business is dumping some dangerous chemicals into the local river.
00:09:15.360 --> 00:09:20.000
Um, but then you move forward to just a few months ago and you're getting this level of quality.
00:09:20.080 --> 00:09:26.080
You'd have to really know your detail about birds to know that this wasn't a real bird.
00:09:26.240 --> 00:09:32.320
Um, but then you look at when Sora launched fairly recently, where we're now going from text to video.
00:09:32.799 --> 00:09:42.559
This again, this is the same prompt just a couple of months ago in creating real-time video essentially of that bird behaving uh in a typical bird-like fashion.
00:09:42.720 --> 00:09:46.720
So that rate of progress in just two years is absolutely phenomenal.
00:09:46.879 --> 00:09:56.480
Um, to give you some other examples in the space, you've got the prompt of a stylish woman walking down a Tokyo strait filled with warm, glowing neon and animated city signage.
00:09:56.639 --> 00:09:58.399
Again, looks really quite realistic.
00:09:58.480 --> 00:10:03.919
And actually, things have moved on fairly significantly from when this video first came out a few months ago.
00:10:04.080 --> 00:10:12.559
Um, you'd really have to be an art director to look at this and to see the little intricacies that would maybe give away that it's AI generated.
00:10:12.799 --> 00:10:21.759
And of course, something similar here when you look at more of a nature scene, a drone view of waves crashing against the rugged hills along Big Sur's Garay Point Beach.
00:10:22.000 --> 00:10:25.919
Um but this isn't just used for positive things.
00:10:26.159 --> 00:10:28.639
Of course, we're seeing deep fakes that are coming out.
00:10:28.799 --> 00:10:31.600
This is a deep fake that was created off uh Martin Lewis.
00:10:31.840 --> 00:10:34.960
Both the voice and the visual is a deep fake in this case.
00:10:35.120 --> 00:10:40.399
Um and I think for the first time I was working with a retail energy uh client at the time.
00:10:40.559 --> 00:10:55.679
And I think this was a real moment for them where they realized we don't have a capability within any of our departments, not just an AI capability, but within corporate comms or within PR or within marketing to respond to something like this coming out.
00:10:55.840 --> 00:11:03.360
So the risk profile uh within our organizations fundamentally changes as well as the opportunity space does as well.
00:11:03.840 --> 00:11:08.879
So that is a very rapid run through of where we've been over the last few months.
00:11:08.960 --> 00:11:19.039
And I think if you take anything from this, the key message is that AI isn't just a technology and data challenge, it's a strategic, operational, and cultural shift.
00:11:19.279 --> 00:11:26.960
Or as I often say, it's 10% algorithms, it's 20% technology, it's 70% people and processes.
00:11:27.200 --> 00:11:35.759
We're going to talk a bit more about this in the next section where we look at um how we automate, enhance, and consider new experiences.
00:11:36.000 --> 00:12:07.120
But to all of you as technologists, one thing that I would be saying here is we need to now, and this has been true before AI came out, but we need to now really be thinking about how we step up out of thinking of low-level implementation details when we're thinking about technology and instead start to think about the orchestration and the strategy and the operations at a much higher level above things, because a huge amount of what we've been doing for many years, and in some cases decades, um, there are big aspects of that now that can be automated.
00:12:07.279 --> 00:12:13.200
Um, so how we move into much more strategic space becomes a very important question.
00:12:13.919 --> 00:12:17.440
So that's what's been happening over the last couple of years.
00:12:17.679 --> 00:12:26.399
We'll now take a quick run through automate, enhance, and experience, and then after that, we'll get on to the QA side of things.
00:12:26.639 --> 00:12:37.919
So, automate, enhance, and experience is a framework that we uh we use at Owendale when we're looking to see where is AI going to be a useful contributor within a business.
00:12:38.240 --> 00:12:45.759
And there could be some very smart people on this call who potentially can think of something that doesn't fit within these three categories.
00:12:45.840 --> 00:12:55.600
Um, but so far, with all of our clients that we work with, these sum up every different area of the business in one way or other that AI has got an opportunity to play.
00:12:55.840 --> 00:13:11.679
So, if we think about automate, first of all, what we're really doing here is thinking about how we can focus human expertise on higher value work by eliminating the repetitive knowledge work that consumes much of what we've done over many years in our roles.
00:13:12.960 --> 00:13:26.399
Um, it's no surprise at the beginning of this year, Sam Altman announced that he believes that this is the first year that we're going to see AI join the workforce, not just as a tool, but essentially as a colleague.
00:13:26.559 --> 00:13:37.200
Um so this is when AI is able to join the organization and take on somewhat substantive areas of different um jobs or roles or activities that we do in our organization.
00:13:37.519 --> 00:13:46.559
Now, needless to say, the way our organizations are today, it isn't designed in a way that gives you a role that can wholesale handover to AI.
00:13:46.720 --> 00:13:55.519
And I think any organization that tries to push that message that we're going to automate everyone's roles, that they're probably selling your platform or selling your product or a service.
00:13:55.759 --> 00:14:13.600
In reality, to understand how AI is really going to make a difference within your organization, we need to take a look at the roles that we've got today and start unpacking what are the things within that role that have to remain human, what are the things within that role that potentially could be human and AI working in collaboration?
00:14:13.759 --> 00:14:24.000
And then separately, what are the things that potentially could be AI alone because it's perhaps got better safety rails around it, or it's a particularly well-defined repetitive task.
00:14:24.240 --> 00:14:35.200
By doing that, then we're able to get different aspects of these roles or activities that we can hand over more wholesale to AI whilst keeping humans focused on higher value tasks.
00:14:35.440 --> 00:14:38.559
And we're starting to see this in a number of different organizations now.
00:14:38.720 --> 00:14:57.919
So Tobias Lutka, for example, the CEO of Shopify, um, has released a memo to staff that says we won't be um approving budget to recruit new humans into the organization unless you can demonstrate that AI is incapable of performing all the constituent parts of a role.
00:14:58.159 --> 00:15:07.519
That's a significant shift in positioning because until now, organizations have been considering wouldn't it be nice if AI could, and then falling back on the human option.
00:15:07.759 --> 00:15:15.360
What Luke has done here is turned that in his head and said, prove that AI can't do it, otherwise, you're not going to get that budget.
00:15:15.600 --> 00:15:21.440
Now, many people would say that that is an overly strict or perhaps too harsh way of doing things.
00:15:21.600 --> 00:15:24.879
But in reality, what he's really doing here is he's driving change.
00:15:25.039 --> 00:15:37.600
Everybody's going to have to fundamentally think differently about the roles that they and their teams all perform and then start to really redesign how they collaborate and how the work works within their systems.
00:15:38.399 --> 00:15:48.639
Now, to give you an example of how we're doing this, pardon me, internally at Owendale, I'll call an example from uh from within our sales team.
00:15:48.799 --> 00:15:55.200
So we're at a stage of development just now where we've got a number of clients coming on, we want to continue that growth trajectory.
00:15:55.360 --> 00:15:59.759
Um, we had the option of growing out a large sales team.
00:15:59.840 --> 00:16:03.840
Uh, however, we thought it was important to essentially ether on dog food.
00:16:04.000 --> 00:16:10.879
So we wanted to be able to use technology internally to start automating all aspects of that sales outreach capability.
00:16:11.120 --> 00:16:16.639
So, what we did here is I'm sure many of the technologists in the call will have heard of a platform called Make.
00:16:16.879 --> 00:16:35.679
Make is essentially an orchestration platform and provides some out-the-box integrations with various different platforms, but it also has a lot of power for uh calling into APIs or endpoints and webhooks and so on that you might need to do different things that isn't uh natively supported within the application.
00:16:36.000 --> 00:16:42.799
So we've got a platform that we use called Apollo, that's where we identify the organizations that we would like to work with.
00:16:42.960 --> 00:16:52.720
Um what we've done essentially is we're using make as the orchestrator, but then calling into AI, which performs different roles that normally would be the role of the human.
00:16:52.879 --> 00:17:06.799
So we're using Make to call into often uh OpenAI's API, sometimes Anthropic, but that will go off and query Apollo as a platform that tells us what organizations are available to potentially work with.
00:17:06.960 --> 00:17:15.359
We can query all different things around the revenue, the size, the global footprint, the industry that they're in, uh, whether or not they've unlocked funding and so on.
00:17:15.440 --> 00:17:20.960
Um something that would normally be a very human task, uh, but this can now be done with AI.
00:17:21.359 --> 00:17:31.279
Um from there, it then pushes all of that information onto a second uh model from the OpenAI team, which does a review to prioritize who we want to work with.
00:17:31.680 --> 00:17:34.799
Um, it then goes out to a platform called Xpande.
00:17:35.440 --> 00:17:49.920
Uh and the combination of intelligence with the platform Expande, which essentially does LinkedIn automation, is able to then visit someone's profile, come back a while later and send a connection message, uh perhaps like a post or two.
00:17:50.079 --> 00:17:59.680
It's able to get into what looks like a human type conversation to start warming up with those target people within the organization that we want to speak with.
00:18:00.000 --> 00:18:05.359
Um from there, we go back to Apollo because we use that then as an email outreach platform.
00:18:05.519 --> 00:18:13.119
Again, all of the messaging is tailored towards the organization and the person that we're reaching out to directly.
00:18:13.279 --> 00:18:15.680
Um and from there, we take the next step.
00:18:15.759 --> 00:18:21.039
And this, I think, is where it really starts to show the power that's available within these platforms.
00:18:21.200 --> 00:18:25.599
Um, we then reach out to Twilio, which is uh essentially a VoIP platform.
00:18:25.680 --> 00:18:28.079
We're able to do outbound dialing.
00:18:28.160 --> 00:18:46.400
Uh and by combining that with a combination of 11 labs, voice models, and intelligence, and again, the intelligence that comes from ChatGPT, we're actually able to do uh telephone outreach and have a full conversation with a client to see if they're interested in having an introductory call with us.
00:18:46.640 --> 00:19:01.440
So, this process normally for a sales team would be a very onerous process, recognizing what um organizations, what people within the organizations, customizing messaging, reaching out on LinkedIn, going back to email, making a phone call.
00:19:01.599 --> 00:19:08.799
We're able to automate all of that just using technology and just using the skills that we have within our organization.
00:19:09.039 --> 00:19:19.519
Um to kind of polish this little part off, this is Kev, um poor unsuspecting Kev, who uh is one of our partners within Owendale, was sitting on his sofa one night.
00:19:19.599 --> 00:19:27.839
Um, I didn't tell him I was going to do this, and all of a sudden he got an outbound call uh from uh our Owendale sales advisor.
00:19:27.920 --> 00:19:29.200
And uh hopefully you can hear this.
00:19:29.359 --> 00:19:30.799
Lau, give me a nod if you're able to.
00:19:31.119 --> 00:19:33.759
Hi, Kev, it's David from Owendale Advisory.
00:19:33.920 --> 00:19:37.759
We're a specialist AI consultancy that works exclusively with senior leaders.
00:19:38.000 --> 00:19:39.759
I'm just following up on Gary's email.
00:19:40.000 --> 00:19:48.079
He asked me to reach out to see if you might be open to a short introductory call with him about what AI means for your business and how to get ahead of that shift.
00:19:49.039 --> 00:19:50.319
It's now a good time to talk.
00:19:53.119 --> 00:19:53.440
Great.
00:19:53.759 --> 00:19:56.319
Gary has already connected with you on LinkedIn and email.
00:19:56.880 --> 00:20:19.759
And he's keen to organize a quick I I won't play any more there because I think is fairly self-explanatory, but the point is that entire role essentially, where we would normally have assigned a team, we're able to use orchestration platforms, we're able to use a combination of node applications to glue things together with intelligence and various different platforms to automate huge swathes of different things that we would do internally.
00:20:20.240 --> 00:20:35.279
Um, the second uh part of automate enhancing experience is of course, how do we enhance uh the powers of the employees within our organization, you know, when they're focusing on those higher value tasks, because we've already automated out the repetitive tasks.
00:20:35.440 --> 00:20:39.759
Um, so this is obviously where we start to think about things like copilots and so on.
00:20:39.839 --> 00:20:46.640
Um, I'm sure for people on the call here, you're probably very experienced uh using tools like Cursor, for example.
00:20:46.799 --> 00:21:02.720
Um, in the previous example that I showed you there, um, I did mention that there was uh some connector glue essentially that hangs between Twilio and Eleven Labs, which is a node application, uh opens up some web sockets for the real-time communication and various different things.
00:21:02.880 --> 00:21:06.400
Now, I am uh I would call myself a reformed technologist.
00:21:06.480 --> 00:21:09.359
You wouldn't want me anywhere near your production code these days.
00:21:09.519 --> 00:21:12.640
Uh, but at the same time, I know what good looks like.
00:21:12.960 --> 00:21:26.240
So by jumping into Cursor and using that with a little bit of Claude in the background, and because I know what good looks like, I was able to build out all of that glue code along with a couple of other people in my team and really, really quickly.
00:21:26.559 --> 00:21:32.319
Now, would I launch that bit of software into a production environment for a client?
00:21:32.480 --> 00:21:34.079
No, I probably wouldn't.
00:21:34.400 --> 00:21:43.359
But the way AI is changing the economics around software means that not everything has to be 99.9999% uptime.
00:21:43.519 --> 00:21:48.559
You know, we don't need to think about how we engineer software in the exact same standard ways all the time.
00:21:48.799 --> 00:22:08.720
If you're competent with something like Cursor and you can get it to do something internally for you that actually is really valuable and takes a huge amount of work out of the system, then Then potentially there's some flex and how we think about the uptime and the robustness of different things, as long as it's not causing any catastrophic failures.
00:22:08.880 --> 00:22:22.799
And to give you an example of this, I've seen quite a few times over the last few months with some designers that we're working with, where Photoshop perhaps doesn't provide the capabilities that they want for the designs that they're working on.
00:22:22.960 --> 00:22:31.440
And these designers are now able to jump into tools like Cursor, craft out a little tool that's able to essentially allow them to explore something.
00:22:31.599 --> 00:22:42.319
So one that's in my mind at the moment is the one of the designers wanted a tool that would allow them to explore uh how dots would all interact together on a bit of motion on a website.
00:22:42.480 --> 00:22:52.160
So they created a little tool with sliders that would allow them to play with the density, the angle, the color, the size, um, various different chaos kind of functions within there.
00:22:52.319 --> 00:22:54.400
Um, and once it was done, they threw it away.
00:22:54.480 --> 00:22:56.480
They used it for a couple of hours and they threw it away.
00:22:56.640 --> 00:23:04.079
So we're in a position where aspects of software now are starting to become a little bit more like a shopping list that you would take to Tesco.
00:23:04.480 --> 00:23:07.440
You know, it performs a really important temporary role.
00:23:07.519 --> 00:23:10.400
Um, and once you're finished with it, you can throw it away.
00:23:10.480 --> 00:23:18.079
And it doesn't need to cost hundreds of thousands or potentially even millions of pounds to build and have that same level of rigor.
00:23:18.240 --> 00:23:27.359
There's lots of ways that we can rethink how we can use um use uh software internally and sometimes even externally in really interesting ways.
00:23:27.920 --> 00:23:30.880
Um, that extends into other areas of design as well.
00:23:31.039 --> 00:23:36.400
So I'm sure many of you are familiar with uh with planning in tools like Miro.
00:23:36.640 --> 00:23:40.240
It could be sprint planning, it could be roadmap planning and so on.
00:23:40.400 --> 00:23:54.319
These types of tools are now having AI embedded within them so that that difficult role of sorting and categorizing or planning or summarizing is actually taken out of your hands and made much, much simpler by the AI that's within the tool.
00:23:54.559 --> 00:24:04.000
Um and for anyone in the call that perhaps is thinking more along the design side of things, you know, you're also seeing very similar tools coming out in uh in things like Figma.
00:24:04.240 --> 00:24:14.160
Um, so one of the big challenges, of course, in creating great products is you're limited to the number of prototypes or the number of different things that you can experiment with.
00:24:14.559 --> 00:24:36.079
By using AI that's embedded within these types of platforms now, you can generate huge quantities of uh of different potential designs and really very rapidly test those things out uh before starting to align on where you need to go with something that actually becomes a fairly strong uh essentially wireframe, a kind of high fidelity wireframe to get you going.
00:24:36.480 --> 00:24:39.680
Um, so this is the the enhanced side of things.
00:24:39.759 --> 00:24:50.799
We're seeing AI coming into tools and we're seeing organizations creating custom tools that allow them to do things that they couldn't have done before, and because AI is giving that brand new capability.
00:24:51.839 --> 00:24:53.839
Um, some huge examples of this.
00:24:53.920 --> 00:24:56.000
I'm sure you're all familiar with Midjourney.
00:24:56.400 --> 00:25:01.920
Uh, Midjourney has grown to 200 million in revenue in two years with only 10 people.
00:25:02.400 --> 00:25:07.599
Uh the team at Cursor have done an incredible job with only 21 people in 21 months.
00:25:07.759 --> 00:25:15.359
Uh the Magnific team, the Upskiller team, uh, one year with two people, getting to that 10 million ARR point.
00:25:15.920 --> 00:25:21.759
Uh 11 Labs, which I mentioned before, provide really high quality um uh voice models.
00:25:22.079 --> 00:25:26.160
Um two years they got to 100 million with only 50 people.
00:25:26.319 --> 00:25:41.599
These are tiny, tiny teams, but they're able to move exceptionally quickly uh and you know, for want of an overused word, in a very agile way because they're enhancing how they work with AI as well as embedding it into the brand new tools they're creating.
00:25:41.759 --> 00:25:45.039
And the final example there, I'm sure many of you have heard of Lovable.
00:25:45.359 --> 00:25:50.960
Um, two months with 15 people, and they were up at$10 million in ARR.
00:25:51.200 --> 00:25:53.440
So really impressive progress.
00:25:53.680 --> 00:26:00.960
Now, the final section here, just before we round off to the QA's, um, it's one thing to think about what can we automate?
00:26:01.119 --> 00:26:07.680
Or it's a different thing to think about where we can use off-the-shelf tools or even our own crafted tools to enhance this internally.
00:26:07.920 --> 00:26:11.839
But what about for the people in the call that are perhaps building digital experiences?
00:26:12.000 --> 00:26:20.400
How can we integrate AI into those experiences in a meaningful way, in a sympathetic way that starts to add new value, not just novelty.
00:26:22.240 --> 00:26:32.880
So, here really we're thinking about how can AI build relationships with users and start to really simplify complex journeys and decisions that they need to make in the use of the digital products that we have.
00:26:33.680 --> 00:26:42.240
So, I think to really understand the impact that this has here, you probably have to go back more than 50 years ago to what I call the pre-digital era.
00:26:42.480 --> 00:26:46.160
Now, back in this time, our businesses ran with face-to-face connection.
00:26:46.319 --> 00:26:55.519
If you needed to get a bank loan, you'd go down to your local bank manager, and they would probably know you, your family, they'd know how creative you are.
00:26:55.680 --> 00:27:00.400
So you have a conversation about how you get your new startup idea off the ground.
00:27:00.559 --> 00:27:02.799
You know, that's real-time human intelligence.
00:27:02.880 --> 00:27:07.440
It's two humans face-to-face, figuring out exactly how we do things.
00:27:07.759 --> 00:27:11.440
Now, that was awesome and it really had the human touch.
00:27:11.599 --> 00:27:23.759
But what businesses found was that wasn't scalable because you had huge numbers of variations in how people would tackle different challenges and how they would go about things, not to mention the management overhead and coordinating at scale.
00:27:23.839 --> 00:27:26.559
Um so we came up with this idea of software.
00:27:26.799 --> 00:27:34.000
And with software, we're suddenly able to standardize and scale many of the aspects of our business.
00:27:34.240 --> 00:27:38.880
So this is what in the digital era I would call design time human intelligence.
00:27:39.039 --> 00:27:44.960
You still got a huge amount of intelligence in the system, but now it's moved to the point where you design the software.
00:27:45.039 --> 00:27:48.880
And that's the point where many of us have probably spent our entire careers.
00:27:49.039 --> 00:28:03.920
So you've got um, you know, you've got product owners or you've got BAs working with designers, working with developers, working with testers, you know, and you come up with the scenarios that you're going to handle, you also eradicate the scenarios that you're not going to handle.
00:28:04.079 --> 00:28:10.559
Um, and you get a very deterministic process that allows you to say at the end, if it does this, check, it works.
00:28:10.799 --> 00:28:15.200
Otherwise, it's barked and you've got to return it back to the devs to rework that thing.
00:28:15.359 --> 00:28:17.279
So a huge amount of intelligence.
00:28:17.519 --> 00:28:24.960
But what we sometimes forget when we think about software is that intelligence is a long way away from the customer experience.
00:28:25.200 --> 00:28:31.359
So quite often the decisions that we're taking are the best decisions for our business and for the software that we're building.
00:28:31.519 --> 00:28:36.640
They're not necessarily the best decisions for the users that are going to be using the software that we've created.
00:28:37.119 --> 00:28:39.440
We're now moving into an entirely new era.
00:28:39.599 --> 00:28:44.880
And this is one that I call the intelligence era, and this is where we have runtime digital intelligence.
00:28:45.039 --> 00:28:53.759
So you still have people that are building the software, but the difference now is we're moving into a world where you can embed the intelligence within that digital experience.
00:28:53.920 --> 00:29:01.200
So we no longer need to sanitize and throw out different important use cases for the user because we can't handle it or we don't want to handle it.
00:29:01.359 --> 00:29:10.079
Instead, you can start delegating to the intelligence at runtime to take better, more timely, more contextually aware decisions for our end users.
00:29:10.559 --> 00:29:14.480
I'll give you some examples of that and then we'll wrap up into the the QA.
00:29:14.960 --> 00:29:24.400
Um, so again, back in a pre-digit LERA, um, if any of you remember this, you would uh save up your pocket money on a Saturday, you'd you'd go down to the local record store.
00:29:24.480 --> 00:29:26.000
Uh, and in there they probably know you.
00:29:26.160 --> 00:29:31.440
So they say, Oh, hi Gary, I've got your new Rick Astley album here, Rickroll.
00:29:31.519 --> 00:29:40.000
Uh oh, did you know there's this other great band that I think you'll like because I know your tastes as another human who understands you, I think you're gonna love Right Said Fred.
00:29:40.319 --> 00:29:48.079
Um, and then you jump forward to a much more uh familiar time for many of us now, where you've got things like Spotify.
00:29:48.160 --> 00:29:54.640
Um now, Spotify, of course, gives us incredible access to music and allows us to push our boundaries and try new things.
00:29:54.880 --> 00:30:00.960
But in reality, most of what you experience with Spotify is design human intelligence.
00:30:01.119 --> 00:30:12.400
You're seeing the suggestions that it's giving you because a team of people building that software has decided there's an algorithm that makes you part of that cohort of one million people or however many.
00:30:13.039 --> 00:30:20.960
You look at what they're doing now, and as an audiophile, this sometimes makes me a little bit itchy, uh, but they've made some improvements recently, which are quite good.
00:30:21.119 --> 00:30:36.640
They've now come up with something called Spotify DJ, which is able to understand much more of your interests, of the music you like, and potentially even where you are and what you're doing, to be able to give you a personalized radio station just for you.
00:30:37.119 --> 00:30:38.880
Um, so that's a complete different shift.
00:30:38.960 --> 00:30:43.119
You're no longer part of that cohort of one million, you're in a cohort of one.
00:30:43.279 --> 00:30:44.960
And how are they able to do that?
00:30:45.200 --> 00:30:46.720
Well, it's really easy.
00:30:46.880 --> 00:30:57.599
There's no multi-year data projects, there's no uh teams of data scientists, they've got the Spotify personalization API, which knows what you've been listening to over the years.
00:30:57.839 --> 00:31:10.400
They pass that information into a large language model, and then they pass that into the Synatic, which is a business that um they bought a few years ago, that is an API that generates dynamic voice, and they play that back to you.
00:31:10.480 --> 00:31:16.880
So the DJ is able to say, back in 2022, you were listening a lot to this, these are the types of vibes that you listened.
00:31:17.039 --> 00:31:18.400
I also think you'll like this.
00:31:18.480 --> 00:31:21.839
And that is dedicated to me, it's a very personalized experience.
00:31:22.000 --> 00:31:25.599
Again, achieved with nothing more than API calls.
00:31:26.079 --> 00:31:30.079
Um, the second example I'll give you here is thinking more on the banking side of things.
00:31:30.160 --> 00:31:34.720
You know, spoken already about the bricks and mortar days of going down to your local bank.
00:31:34.960 --> 00:31:43.200
Then along came the idea of online banking and mobile banking, which allowed us to carry out transactions on our phones wherever we were.
00:31:43.440 --> 00:31:53.680
But we're now moving beyond that with platforms like Clio, where using open uh banking APIs, it's able to gather a view of my overall finances.
00:31:53.839 --> 00:31:59.759
I'm able to tell it that my financial ambitions is to take my kids to Disneyland in two years' time.
00:31:59.920 --> 00:32:05.279
And it's able to bring together a dedicated plan and coach me through that plan.
00:32:05.440 --> 00:32:09.200
So it's able to tell me, you know what, Gary, 12 McDonald's in one week.
00:32:09.359 --> 00:32:11.119
That's not going to get you to where you need to be.
00:32:11.759 --> 00:32:16.400
You cut back on the McDonald's, get a little bit healthier, and put this amount towards your savings.
00:32:16.559 --> 00:32:28.160
So again, it's a much more intelligent experience that understands me, understands how it needs to coach me, and gives much more intelligent feedback separate to enter a number and press transact.
00:32:28.559 --> 00:32:30.079
Again, how does this work?
00:32:30.319 --> 00:32:31.200
It's all APIs.
00:32:31.279 --> 00:32:39.759
You've got the open banking APIs that push into OpenAI's large language model, and this time we expose that intelligence out through a mobile app.
00:32:39.920 --> 00:32:42.400
For technologists, this is bread and butter stuff.
00:32:42.640 --> 00:32:46.000
You know, there's nothing unusual or strange or difficult in here.
00:32:46.240 --> 00:32:48.640
The big thing that's changed is the experience.
00:32:49.440 --> 00:32:51.599
Well, the final example, and we're on to the QM.
00:32:52.480 --> 00:33:17.759
This thing from the healthcare environment, and I've deliberately used disease and greater productivity, and we know that healthier systems like the NHS are really struggling.
00:33:18.400 --> 00:33:38.319
Digital over the years has made some help, but realistically, these have more been in the space of things like booking systems, unless you go into you know a very specific category of traditional ML where you're maybe using it to identify cancer years ago with a radio informatics.
00:33:38.559 --> 00:33:42.240
Um, but we're now seeing a new generation of software coming through.
00:33:42.400 --> 00:33:47.920
Um, this is from a company called Wobot Health, who have got a digital tool called Wobot.
00:33:48.079 --> 00:33:52.960
This is for people who are in significant um psychiatric breakdown.
00:33:53.039 --> 00:33:57.279
Essentially, for some reason, they can't get access to the care that they need or the medication that they need.
00:33:57.440 --> 00:34:00.319
But these people desperately need help in this moment.
00:34:00.480 --> 00:34:10.559
And what this is able to do is listen to what that patient's saying and then able to guide them gently and appropriately through the difficult scenario that they're in.
00:34:10.880 --> 00:34:18.480
Now, needless to say, doing the wrong thing at this stage for somebody in that level of stress could be absolutely catastrophic.
00:34:18.719 --> 00:34:31.679
But what the team there have done that I think is incredibly valuable, and I'd urge you all to think about this if you're considering where you can apply AI, is they've recognized that you don't always need to use what AI generates.
00:34:31.920 --> 00:34:36.559
You can just use it as an incredibly powerful interpreter of what the needs are.
00:34:36.719 --> 00:34:50.960
So here they're using large language models to listen to the patient, to categorize the type of challenge that that patient is experiencing, and then to select a predefined human-generated, physician-generated response that's appropriate to go back in that moment.
00:34:51.119 --> 00:35:04.400
So we're able to use that to work within the regulatory system to make sure that we've only got expert-generated responses, and we're not going to say something inappropriate, but to scale to meet the needs of the people who need our help.
00:35:04.639 --> 00:35:15.760
Once again, this is all about listening to the conversation and passing it to the AI, picking direct-approved messaging and going back out through that interface.
00:35:16.000 --> 00:35:18.400
Really simple technology stuff.
00:35:18.639 --> 00:35:22.960
It's the experience and how we think about the experience that's fundamentally changed.
00:35:23.199 --> 00:35:35.840
So the key message in that last one really is Gen AI scales our ability not just to generate, but to listen, to reason, and actually to communicate if you want to take that final step.
00:35:36.639 --> 00:35:46.719
So, just wrapping up now, that experience piece, AI fundamentally changes how companies think about growing and building long-term relationships with employees and customers.
00:35:46.880 --> 00:35:50.719
And as technologists, you need to think about your role within that system.
00:35:50.880 --> 00:36:08.400
We need to step out from low-level implementation detail to become part of thinking about the experience, thinking about the capabilities that this new generation of technologies can offer, and rethinking the roles that we have in contributing towards building digital products and digital services.
00:36:08.559 --> 00:36:11.679
So AI is much more than a technology and data challenge.
00:36:11.840 --> 00:36:24.079
It's strategic, it's operational, it's cultural, but that strategy, operations, and cultural shift needs to be part of your roles as technology now to give you more opportunities in your career moving forward.
00:36:24.239 --> 00:36:31.119
Like I say, 10% algorithms, 20% technology, 70% people and processes.
00:36:31.440 --> 00:36:36.960
So once a new technology rolls over you, if you're not part of that steamroller, you're part of the road.
00:36:37.119 --> 00:36:47.920
So now is the time to think about our roles, broaden them out, become more strategic, uh, and set ourselves up for a really exciting time as we've seen all of these technologies shift.
00:36:48.880 --> 00:36:50.239
And on to the QA.
00:36:50.400 --> 00:36:51.199
Thank you.
00:36:51.599 --> 00:36:52.320
Fantastic.
00:36:52.559 --> 00:36:53.760
Thank you so much for that, Gary.
00:36:54.000 --> 00:36:56.239
There's so much interesting stuff in that presentation.
00:36:56.400 --> 00:36:59.760
I'm sure um you've all got questions here, and we've got some.
00:36:59.840 --> 00:37:02.480
So I'll just um head straight into it given the time.
00:37:02.639 --> 00:37:12.000
So, one of the questions I was going to kick off with, Gary, was and somebody's mentioned when using AI, how do you see AI replacing people for workforce?
00:37:12.159 --> 00:37:17.920
And how will revenue come in when people won't be working with AI replacing the workforce?
00:37:18.320 --> 00:37:18.639
Yeah.
00:37:18.880 --> 00:37:19.199
Okay.
00:37:19.599 --> 00:37:23.920
So I think there's a lot of heated debate that's going on about this at the moment.
00:37:24.079 --> 00:37:28.000
Um, AI will remove a lot of jobs.
00:37:28.079 --> 00:37:30.639
Um, I'm I'm quite confident about that.
00:37:30.880 --> 00:37:35.360
Um, for many of the jobs that we have, I think it's more going to be about how we reshape them.
00:37:35.440 --> 00:37:46.400
Uh, and hopefully that's one of the key messages that that comes through um the talk is we need to, as technologists, proactively think about how do we retain our relevance.
00:37:46.559 --> 00:37:49.840
You know, our organizations need us and it needs our skill sets.
00:37:50.079 --> 00:37:58.559
But to do that, I think you need to not wait until somebody who's looking at a spreadsheet comes to try and change your role.
00:37:58.639 --> 00:38:01.679
You need to proactively think about how you evolve that role yourself.
00:38:01.920 --> 00:38:05.199
None of our roles can wholesale be handed over to AI.
00:38:05.360 --> 00:38:17.440
So if we proactively think about which parts of it can be, then we can tease them out and separate them and hand them over, you know, wholesale, whilst at the same time refocusing the things that we do on higher value tasks.
00:38:17.599 --> 00:38:27.280
And I think if we do that, that creates a huge opportunity to actually make much of our job more exciting, uh, more valuable, and much more interested in many ways.
00:38:27.440 --> 00:38:30.880
I think that shift is absolutely going to happen.
00:38:31.039 --> 00:38:39.840
Um, the choice that I think we all have in this call is whether or not we want to be part of reshaping it or we want to wait on that that train coming uh and and hitting us.
00:38:40.000 --> 00:38:42.480
Um, what was the second part of that question?
00:38:42.800 --> 00:38:46.559
Yeah, no, it was just um, I think you've answered that perfectly.
00:38:46.639 --> 00:38:48.079
Um to be honest, Gary.
00:38:48.239 --> 00:38:51.760
So um I've just got there's quite a few questions here, so we'll move on.
00:38:52.000 --> 00:38:54.800
Um so I think this is really interesting.
00:38:55.039 --> 00:39:05.440
You know, in your role, you've seen lots of AI use cases, and you spoke a little bit about this within your presentation, but what's the best transformation AI use case you've seen and through the kind of clients you work with?
00:39:05.599 --> 00:39:07.920
Because there seems to be a lot of kind of POCs out there.
00:39:08.320 --> 00:39:32.159
I I think the thing that's really exciting me at the moment, um, and it it's difficult to go into very specific details on it, but national park.
00:39:32.320 --> 00:39:35.199
Uh, last week we were down in London with the Natural History Museum.
00:39:35.360 --> 00:39:54.320
You know, these aren't necessarily organizations that you would typically think of as being at the forefront of digital technology, but what these organizations are finding is that it gives them um an opportunity to try new things and to think about this technology in a really exciting and completely new way.
00:39:54.480 --> 00:40:04.000
So it's not just about cost cutting, and you know, they're very purpose-driven organizations with a much higher kind of societal uh value and kind of uh focus.
00:40:04.159 --> 00:40:07.440
So it's really good to see those kind of things coming in.
00:40:07.679 --> 00:40:30.400
The second part of that, which is closely related, is we're finding repeatedly that actually quite often organizations that are more digitally mature, in the terms that we would have considered that over the last 10, 15 years or so, are actually at a slight disadvantage because they're so heavily invested in a particular direction or a particular tech stack or approach.
00:40:30.480 --> 00:40:37.119
Uh, with people whose careers are tied up in those approaches, they're finding it quite difficult to rethink things and change.
00:40:37.280 --> 00:40:51.679
So, in some cases, organizations that have been later to the table with digital technology, but they're coming to the table now with AI with a very open mind and a clean sheet, and we're seeing some incredible and very rapid progress in those spaces.
00:40:51.840 --> 00:41:08.639
And I think the two most interesting categories for me is automate, because we're actually rethinking the organization, we're rethinking the structures, the roles, and how you apply the technology internally, and then experience where you're really getting into the redesign of digital products and digital experiences.
00:41:08.800 --> 00:41:13.280
I think the co-pilot type enhances stuff in the middle is stuff that we're all good at.
00:41:13.440 --> 00:41:34.880
And if your organization's um AI policy isn't overly restrictive, we'll all do naturally a very good job of the question.
00:41:35.039 --> 00:41:44.480
So it really depends on the organization, it depends on the processes or the data that's that's being handled, obviously, for end users.
00:41:44.719 --> 00:41:52.559
Um the key thing I would call out here is AI for me, largely at the moment, is a design challenge more than a technology challenge.
00:41:52.639 --> 00:41:54.239
And I mean that in every sense.
00:41:54.320 --> 00:42:00.159
Uh it's organizational design, it's experience design, um, it's technology design.
00:42:04.480 --> 00:42:07.599
Very careful to not just take the low-hanging fruit.
00:42:07.760 --> 00:42:10.800
Sometimes there can be some pretty nasty gotchas and low-hanging fruit.
00:42:10.960 --> 00:42:26.719
We're quite careful to make sure we think through how we rethink the digital experiences or we rethink the internal processes to tease things out in ways that can be handled relatively safely and securely with relatively low risk with the AI.
00:42:26.800 --> 00:42:28.239
So that's one part of that.
00:42:28.400 --> 00:42:36.559
Um, the second part of that is obviously how you choose to work with these technologies from a more technical perspective is also very important here.
00:42:36.719 --> 00:42:42.639
You know, you could be calling into Anthropic or Mistral or OpenAI's APIs equally.
00:42:42.719 --> 00:42:48.800
You could be choosing to self-host and keep things entirely within your own ecosystem.
00:42:49.039 --> 00:42:57.119
Um, from more of an application security and application design perspective, um, adopting architectural patterns like air gapping.
00:42:57.280 --> 00:43:07.440
So, for example, when uh a message comes in from an end user, that message never actually gets to the large language model that's going to be uh performing the task.
00:43:07.519 --> 00:43:13.199
You know, it goes through different stages of sanitization, it goes through different stages of categorization.
00:43:13.360 --> 00:43:24.880
You know, we make sure that the thing that actually gets to the decision-making engine is something that's essentially been constructed internally from the context of post-sanitization that's come in from the end user.
00:43:25.039 --> 00:43:34.079
So we're still able to get a good response, but we're not potentially uh accidentally carrying out some prompt injection or any of those types of things.
00:43:34.320 --> 00:43:52.000
Um, application level design patterns.
00:44:00.320 --> 00:44:08.480
And that's something you need to be very aware of and obviously put the the right types of red team and stuff in place to do the testing off the back of that.
00:44:08.800 --> 00:44:09.119
Okay.
00:44:09.360 --> 00:44:09.679
Great.
00:44:09.760 --> 00:44:10.639
Thanks for that, Gary.
00:44:10.880 --> 00:44:11.760
Really detailed answer.
00:44:11.840 --> 00:44:12.960
So we appreciate that.
00:44:13.199 --> 00:44:14.239
That's it though, guys.
00:44:14.320 --> 00:44:14.880
Time is up.
00:44:15.280 --> 00:44:21.440
So a massive thank you to Gary for being my guest today on this webinar.
00:44:22.000 --> 00:44:25.280
So just to finish up, we are taking a break for the summer.
00:44:25.599 --> 00:44:35.280
We will be hosting our fourth Data NAI webinar on the 27th of August with Elizabeth Hollinger, where she'll talk about evolving skills in a data driven world.
00:44:35.440 --> 00:44:38.000
So look forward to seeing you all on the call then.
00:44:38.159 --> 00:44:40.719
Have a great summer and thanks again.
00:44:41.519 --> 00:44:42.320
Thanks everyone.
00:44:42.480 --> 00:44:42.880
Take care.