WEBVTT 1 00:00:00.172 --> 00:00:02.910 (dramatic music) 2 00:00:02.910 --> 00:00:05.598 If you look at the future of GenAI at scale 3 00:00:05.598 --> 00:00:08.790 and AI at scale and agentic workflows 4 00:00:08.790 --> 00:00:11.340 that are coming our way at speed, 5 00:00:11.340 --> 00:00:14.940 all of that relies on high-quality data 6 00:00:14.940 --> 00:00:17.580 at the right frequency, at the right granularity, 7 00:00:17.580 --> 00:00:20.730 in the right moment for the right user, 8 00:00:20.730 --> 00:00:22.680 and the the fascinating thing about it 9 00:00:22.680 --> 00:00:24.750 is when you start geeking out on it, 10 00:00:24.750 --> 00:00:26.850 you get into the guts of the business: 11 00:00:26.850 --> 00:00:28.410 how does the business work? 12 00:00:28.410 --> 00:00:31.293 I'm Vlad Lukic and you are not hallucinating. 13 00:00:32.132 --> 00:00:35.190 (upbeat music) 14 00:00:35.190 --> 00:00:37.830 It was fascinating for me now to see over the last, 15 00:00:37.830 --> 00:00:39.420 I would say last nine months or so, 16 00:00:39.420 --> 00:00:42.060 when you go through some of the data conversations 17 00:00:42.060 --> 00:00:43.320 with the executives 18 00:00:43.320 --> 00:00:46.710 and you see there's so much fancy terminology out there, 19 00:00:46.710 --> 00:00:48.810 data velocity, data fluidity, 20 00:00:48.810 --> 00:00:51.330 that is coming at speed at a lot of the techies 21 00:00:51.330 --> 00:00:53.070 that they're using that in their big meetings 22 00:00:53.070 --> 00:00:55.020 to add more gravity to it, 23 00:00:55.020 --> 00:00:57.420 but in the end, it obfuscates, right, 24 00:00:57.420 --> 00:01:00.000 the basic business conversations they need to have. 25 00:01:00.000 --> 00:01:02.700 So don't fall into the trap of those conversations 26 00:01:02.700 --> 00:01:04.380 without the clarity. 27 00:01:04.380 --> 00:01:07.170 As the CEO, you first need to articulate 28 00:01:07.170 --> 00:01:08.640 what are the business objectives 29 00:01:08.640 --> 00:01:10.320 and outcomes you're driving for, 30 00:01:10.320 --> 00:01:12.690 and that becomes a true north for anyone 31 00:01:12.690 --> 00:01:15.330 that touches or talks about data. 32 00:01:15.330 --> 00:01:17.130 You've got to follow the rhythm of the business 33 00:01:17.130 --> 00:01:18.690 and where the bottlenecks are, 34 00:01:18.690 --> 00:01:21.270 and then direct the effort of using the right data 35 00:01:21.270 --> 00:01:23.220 to solve those pain points. 36 00:01:23.220 --> 00:01:24.990 A lot of the executives don't do that 37 00:01:24.990 --> 00:01:28.110 because they start the meetings with their executive teams 38 00:01:28.110 --> 00:01:29.137 and their tech teams that say, 39 00:01:29.137 --> 00:01:31.380 "We need to approve the following tens of millions 40 00:01:31.380 --> 00:01:33.690 of dollars to build the following data lake. 41 00:01:33.690 --> 00:01:35.220 We need to build the following pipelines, 42 00:01:35.220 --> 00:01:37.530 and then there is this new solution from the cloud provider 43 00:01:37.530 --> 00:01:39.900 of your choice," et cetera, et cetera. 44 00:01:39.900 --> 00:01:43.680 And so as a result, people kind of get intimidated 45 00:01:43.680 --> 00:01:46.230 and they step back and they abdicate the thinking 46 00:01:46.230 --> 00:01:49.560 on the first principles, which are: What are we solving for? 47 00:01:49.560 --> 00:01:52.440 What is the business outcome we are driving? 48 00:01:52.440 --> 00:01:54.900 And my big message to all the executives 49 00:01:54.900 --> 00:01:57.090 is do not abdicate that conversation, 50 00:01:57.090 --> 00:02:00.584 because that becomes a true north for everything else. 51 00:02:00.584 --> 00:02:03.167 (gentle music)