1
00:00:00.080 --> 00:00:10.070
Welcome to the Data Strategy Gurus podcast. In this show, we bring together the brightest minds in the world of data strategy, data management, artificial intelligence, and disruptive technologies.
2
00:00:10.300 --> 00:00:17.100
Thought leaders and experts share their insights, knowledge, and experience on how to stay ahead of the game in an ever-evolving data landscape.
3
00:00:17.140 --> 00:00:23.740
Whether you're a data professional, a business leader, or simply someone who is passionate about the power of data, this podcast is for you.
4
00:00:23.800 --> 00:00:34.980
So sit back, relax, and join us on a journey to explore the world of data, analytics, artificial intelligence, tech, and beyond. Hi, and welcome to the Data Strategy Gurus podcast.
5
00:00:35.160 --> 00:00:44.200
Once again, we're at the Qlik World Conference in Las Vegas, and we're joined by Kevin Ryan, who's the director of business intelligence of Wolters Kluwer.
6
00:00:44.700 --> 00:00:58.870
Uh, Kevin, uh, can you explain, uh, director of business intelligence- Sure... what you are doing at Wolters Kluwer? Sure. My job is, um, sort of two, two main priorities. One is to be, um,
7
00:01:00.220 --> 00:01:13.120
take advantage of, in an ad hoc fashion, any question that might come to my team related to sales, uh, marketing, product, uh, development. Um, basically get like an order taker.
8
00:01:13.220 --> 00:01:23.000
So if someone has a question about, um, turnover or a question about finances, they come to my team, and we process those requests. That's about half of the work that we do.
9
00:01:23.480 --> 00:01:42.600
The other half is much more strategic in nature, and that involves, um, me and my team helping to design and implement a data strategy that, that exists, that can survive and be, um, pragmatic across, um, all of the divisions within Wolters Kluwer.
10
00:01:42.700 --> 00:01:55.310
So, um, one's sort of very tac- tactical, very tactical, and the other one is more, more strategic in nature. Yeah, I'm interested in, in the technical part where we say we get these ad hoc questions- Mm-hmm...
11
00:01:55.380 --> 00:02:02.380
and sometimes you get the same question five times again, and you're trying to do- Sure... the self-service- Sure... business intelligence. Yeah.
12
00:02:02.440 --> 00:02:12.840
So how do you take these type of questions and can keep up to the speed of, of the questions that are- Right... coming in? Yeah, I mean, in, in a practical sense, um,
13
00:02:15.160 --> 00:02:24.410
you can't necessarily, um, engineer an automated solution for everything, so that does, that, that's a reality. Um, but I will say that when we do
14
00:02:25.380 --> 00:02:34.420
start clustering, I suppose, um, requests that come into my team that seem to be, you know, fairly repetitive, that's when we start automating.
15
00:02:34.480 --> 00:02:49.880
That's when we start really trying to push, um, push the analyst out from my team and more into, um, into our stakeholder organizations, and that really is philos- a philosophy that we're trying to implement around, um,
16
00:02:50.820 --> 00:03:02.960
around the citizen analyst, really. Mm. If, if cen- if BI is centralized, it's my opinion that it's, it's difficult scaling out to really, uh, uh, um, accommodate the strategic needs of a whole organization.
17
00:03:02.970 --> 00:03:13.310
So, um, whether that's technology or with process or training of individuals, um, it's something that we've tried very hard on my team to start implementing, and it's been quite successful.
18
00:03:13.520 --> 00:03:23.040
Um Yeah, so you start in a central way, capturing the questions, and when you're looking into scaling that one, you, you take that acumen with the business analyst and put them- Correct...
19
00:03:23.100 --> 00:03:31.350
because you had BICC's a while ago. Yep. People have been trying to centralize, decentralize- Yeah... all these motions, and- Yeah... nothing seemed to work in a certain way. Correct.
20
00:03:31.630 --> 00:03:43.090
For some organizations, the BICC did work because you have centralized the knowledge on, on how you set everything up on a technical level, but as well on the company, uh, industry level. Absolutely. No, and I think that
21
00:03:44.060 --> 00:04:20.469
that centralization versus non-centralization, you know, I think that it's, it gets to, you know, a, one of the real struggles that I do have in, around culture, um, in that right now the culture of my organization is that, um, analytics questions can be centralized, and there, a lot of the, uh, resistance that I find in my job, it's around creating that culture where folks are more curious about accessing data, answering their own questions, providing insights, and then the inherent learning that happens when you self-discover a, a, a problem in the data, or you find something in the data that is- Yeah...
22
00:04:20.680 --> 00:04:31.960
inherently yours. Um, the momentum that that brings to, to any individual or organization is, is really impressive. Yeah, an interesting point, the, the data culture as we these- Mm-hmm... days call it.
23
00:04:32.500 --> 00:04:41.500
Uh, what, what are you trying to set up to, to create that real data culture- Right... where there is no people look at data, "Oh, data, data. Oh, technology"- Yeah...
24
00:04:41.510 --> 00:04:51.240
and they kind of get, get afraid of, of get, doing something- Yeah... with the data and really getting the value out of that? Yeah. Um, you know, I, I don't remember the guy's name. He's a,
25
00:04:52.360 --> 00:05:02.180
he's a social influencer, but he draws the... He has this anecdote about, um, dissemination of information. Um, and what I have found is that
26
00:05:04.820 --> 00:05:11.880
putting things out there, letting people volunteer to be, uh, you know, I wanna learn more about data and analytics.
27
00:05:11.920 --> 00:05:22.750
I wanna s- you know, I'm, I'm a classic marketer, or I, you know, I'm in, I've been doing the same sales job for, for a very long time. Asking people to raise their hand, who wants to learn a little- Yeah...
28
00:05:22.760 --> 00:05:32.570
bit about SQL? Who wants to learn a little bit about, you know, how we onboard data sources? How do we then visualize data? Um, getting those early adopters- Yeah...
29
00:05:32.580 --> 00:05:38.860
getting them bought into that culture, then they sort of, um... I don't know, it's something that I've just found to be,
30
00:05:39.820 --> 00:05:47.430
you know, it, it's starting to work well because eventually that momentum reaches a, a tipping point that, that I'm hoping, um- Yeah. You-...
31
00:05:47.440 --> 00:05:54.224
it should be much easier to change a culture than, than, than-Um, you know, than from, from scratch. So we're clo- we're getting there. We're getting there.
32
00:05:54.344 --> 00:06:04.554
Yeah, you're trying to find your champions within, within- Yeah... the company, in the business side if, well- Yeah... it's always, it's one company for me always. Yeah. Business IT, uh, try to not- Yeah...
33
00:06:04.644 --> 00:06:11.044
do that separation. And then, uh, try to find these people- Yeah... and, and help them in, in- Yeah... getting those, those, those skills then.
34
00:06:11.124 --> 00:06:18.884
Yeah, one point though, champions, from my experience, it usually involves a vice president or, or some- you know, someone with some kind of stature in their name.
35
00:06:18.914 --> 00:06:31.364
And the reality is that those people might support it, but to, to really build, to change a culture, you need to get people, you know, analysts level, manager level, um, employees that can get in with, get in with data, answer their own questions.
36
00:06:31.564 --> 00:06:42.334
Yeah. And that's how you really change that culture and slowly but surely, it's, it's, it's been working out. Yeah. And then you said as well, the, the strategic level, what, what, what you- Right... you're at?
37
00:06:42.404 --> 00:07:00.044
So, so that is less stakeholder, um, driven and more around, um, the hard problem after next. So right now, what we're trying to do, for example, is, you know, one, none of my stakeholders is asking for,
38
00:07:01.644 --> 00:07:09.654
um, segmentation based in customer lifetime value, for example. Um- Okay. Yep. But, but, um, it's an idea that we're working on,
39
00:07:10.684 --> 00:07:20.654
such that over the course, when, when the request comes from a stakeholder, the hard work's already done. So we're sort of like trying to foresee- Prepare, yeah... the next.
40
00:07:20.744 --> 00:07:28.094
Um, and it's just, you know, a lot of my job is engaging with stakeholders and understanding, and what I'm hearing now is that,
41
00:07:29.404 --> 00:07:39.364
you know, revenue might not be the best metric to be evaluating, um, a customer relationship. Are there ways to do differentiated treatment- Yeah...
42
00:07:39.374 --> 00:07:44.844
from a customer experience perspective, from a, um, a marketing perspective? So
43
00:07:45.764 --> 00:08:00.404
what that leads to in my mind is, you know, understanding, putting, being able to put, uh, you know, a, a, a metric on a specific customer and their, all their relationships and have that be able to differentiate how you treat that customer relative to other customers.
44
00:08:00.464 --> 00:08:12.673
So it's not being asked for right now, but that's, that's a lot of what we're trying to do is push, um, push, push the organization in areas where really advanced metrics and, and capabilities can answer hard questions that are coming- Yeah...
45
00:08:12.684 --> 00:08:20.464
down the pipe. So you're educating them. Well, educating is a hard word always- Sure... but to, to help them understand what you can do with data. Right.
46
00:08:20.584 --> 00:08:29.524
For me, it's kind of strange that, that a marketeer wouldn't know anything about customer lifetime value, but what you're, what you're saying, it is exactly like that.
47
00:08:29.644 --> 00:08:41.134
So I, sometimes it's a bit strange that the people from the tech side know more about that and, and can help them in such a way. Yeah. I, I think I f- I think what it is really is about understanding...
48
00:08:42.984 --> 00:08:54.964
Like if you've got a set of data and it, it contains usage data for a particular customer, um, you know, a stakeholder might look at that and, and be able to say, "Oh, that's interesting.
49
00:08:55.044 --> 00:09:01.444
That, that tells me what, what just happened. What just happened in the last quarter or the last month?" Where
50
00:09:02.344 --> 00:09:09.174
someone with understanding of technology can say, can look at that and say, "We can pull in other variables around retention." Mm-hmm.
51
00:09:09.174 --> 00:09:21.324
"And now we can do things like predicting, um, a customer's decision to retain or not retain based on a particular data signature in their usage-" Yeah... "or things like that." And that's, so that's how the kind of, um,
52
00:09:22.344 --> 00:09:32.074
you know, the technology, the technologists understanding our data kind of coordinate with our, with our stakeholders to come up with some, some interesting analytical solutions. Yeah.
53
00:09:32.104 --> 00:09:42.704
So yeah, they, they do understand what you can bring together, and that's not necessarily known by the people using- Correct... the data. Correct. Yeah. Okay. It, it, it's, um, it's just understanding, you know, really,
54
00:09:43.764 --> 00:09:50.354
you know, on a, on a time-based perspective, can you help me understand about the past or can you help me predict things about the future?
55
00:09:50.374 --> 00:10:01.884
And that's really what I'm trying to push towards is data is obviously in, you know, interesting being retrospective, but there's a ton of power- Yeah... in prospective and, and being able to be predictive.
56
00:10:02.004 --> 00:10:19.284
Um, and we're a B2B, um, firm, so it's a lot of the traditional playbooks kinda lack that idea of churn, the idea of cross, you know, cross-selling and upselling. But, um, it, it really is just, it's the same math.
57
00:10:19.344 --> 00:10:29.544
And if you have the data, you can, you can answer the same types of problems. And then again, it's about, um, getting a culture to adopt those, those recommendations and change for the better. Yeah.
58
00:10:29.584 --> 00:10:38.344
You mean, you mean in B2B, it's not the same when you talk about churn and, and, and everything. Correct. In B2C, it's, it's very prominent to do- Absolutely... cross-selling, upselling. Yes. Yeah.
59
00:10:38.784 --> 00:10:41.994
Yeah, I mean, it's, it's, you know, you know, a,
60
00:10:43.204 --> 00:10:55.254
a subscription business, a monthly subscription business like Netflix, something like that, they might have something like 4% per month where they have to, they're, they're const- so it's a constant, constant, um, problem.
61
00:10:55.404 --> 00:11:00.064
Our business is, you know, we retain, we retain 90 plus percent per year.
62
00:11:00.204 --> 00:11:11.264
So there's not the pressing imperative that's sort of built into your business where you need to, um, but it's obviously it's the retaining customers is the cheapest way to do, to do marketing, to grow your- Yeah...
63
00:11:11.304 --> 00:11:21.294
your footprint and things like that. So yeah, um, it, it's, it's amenable, it's amenable to, to, uh, all the great tricks of the trade, uh- Yeah...
64
00:11:21.294 --> 00:11:30.524
that, that exist in B2C, uh, you know, BI shops and things like that, [laughs] so. Yeah. And your, well, business intelligence, it feels like, uh, this is from ages ago.
65
00:11:31.044 --> 00:11:48.304
Uh, w- are you looking at artificial intelligence to, to apply that in, in your B2B space and at Wolters Kluwer? Yeah. I mean... So look, it, I have a pretty high threshold for what I would consider AI to be.
66
00:11:48.664 --> 00:11:54.264
Um, and I think for me, it's mostly around, um, a self-learning component, right?
67
00:11:54.384 --> 00:12:09.204
So being able to put-Say, a decision engine out into the market and have the decision, you know, engine surface recommendations for customers and then learn from when a, a recommendation was adopted or not.
68
00:12:09.864 --> 00:12:26.084
Um, so we are scratching the surface around that, I would say. Um, but you know, AI more so in, you know, finding, taking an entire corpus of data from, um, you know, a, uh,
69
00:12:27.874 --> 00:12:37.564
uh, our customer service agents- Mm-hmm... and, and putting that through a natural language processor. To being able to tell, you know, to really thin out the thematics, uh- Yeah...
70
00:12:37.604 --> 00:12:46.904
that, that are existing and then, you know, applying me- metadata to that and, and being able to analyze that. That's, that's I'd, I'd say the extent of the, um, the AI that we're, we're going for.
71
00:12:47.004 --> 00:12:55.224
But, you know, definitely trying to be, um, prescriptive in, in anything that we do. So finding out a customer that...
72
00:12:55.364 --> 00:13:08.544
We have, we've, uh, we have models called, uh, red alert models, which it's, um, it's a data-driven approach to proactively letting a sales rep know that they might have an issue. Is that AI? I don't know.
73
00:13:08.604 --> 00:13:14.784
It, it, it's, it's a, it's a, it's a, it's a, it's an evaluation of data and then making a recommendation and learning from that, so.
74
00:13:14.844 --> 00:13:22.444
Yeah, it's statistics and then the next level, it's AI, it's a model, and then you have your self-learning models- Yeah, yeah... like you say. It's, it's, it's, it's a thin line.
75
00:13:22.504 --> 00:13:30.854
I, I agree with you where you say very often people shout out, "It's AI," but it's kind of automated decision engine. It's... Right. Yeah. [laughs] Right. Right. Um. So, um,
76
00:13:31.784 --> 00:13:42.864
you know, I have, I have the utmost respect for folks that, uh, are actually building AI engines, and, and so I, I, I tend to be a little bit conservative of a- [laughs]... of applying, applying the label. Yeah, yeah.
77
00:13:42.964 --> 00:13:49.564
I'm, I'm, I'm following what you're saying, so I just sometimes challenge as well. Okay, AI, you know, just show me and, and what are you doing. Sure.
78
00:13:49.604 --> 00:13:58.964
So in, in that respect and in, in business intelligence solutions, and especially in AI where they think it's, it's, it's, it's smart enough for, for itself, it comes down to the data.
79
00:13:59.144 --> 00:14:11.964
What, what are the type, type of data problems, what you're facing on, on data quality level? Because AI is gonna be very helpful in, in, in supporting the data quality, uh, for toolings. Yeah.
80
00:14:12.024 --> 00:14:25.524
Not where we're just discussing AI at the end of the loop. Yeah. I look at it to help in the data management as well. No, I, I think that there's, you know, and I, I haven't seen a lot of...
81
00:14:26.804 --> 00:14:37.284
So, so whenever you do, when you ru- whenever you roll up your sleeves and you do kind of, um, programmatically trying to cleanse data, right? There's inherently a,
82
00:14:38.584 --> 00:14:50.444
a threshold with which you're willing to, um, say, um, I'm gonna, I'm gonna, I'm gonna crank up the interpretation of, of this algorithm.
83
00:14:50.564 --> 00:15:01.124
It's gonna change my data, and it might make some change in the data that I'm not gonna be able to find. But the balance of, of, of using a, an intelligent approach to a problem with data quality. Um,
84
00:15:02.204 --> 00:15:17.204
so in that regard, I think that there's a tremendous amount of potential for AI in data quality where it can sort of learn from, you know, an in- in an, a data set and make those modifications that need to be made, um, on a small scale.
85
00:15:17.984 --> 00:15:33.474
Um, we're fortunate enough that, you know, the data problems that we have are around, um, frankly classical organization of silos around how do you, how do you... What do you, um, you know, how do you define churn?
86
00:15:33.584 --> 00:15:43.514
How do you define retention- Yeah... one business to another? Yes. When is a customer, um, in that window of being, uh, a retention risk? Um, and those are easier problems to have- Mm-hmm...
87
00:15:43.524 --> 00:15:52.704
but you can't throw, uh, you can't throw technology at 'em. Yeah. No, it's really- Fortunately... the semantical meaning of, of, you say- Yeah... of, of your KPI, of, of what- Yeah... what churn means. Yeah.
88
00:15:53.124 --> 00:16:02.313
And do you use a kind of framework for that or anything that helps in getting that, that, that right? So we, so it, we take two approaches. Um, one,
89
00:16:04.464 --> 00:16:18.244
and, and really anything related to changing the, the data strategy of our organization, um, we tend to go top-down and set up, um, just committees of, you know, how, how are we gonna define a customer?
90
00:16:18.344 --> 00:16:21.134
How are we gonna... Who's gonna be responsible for making changes? Yeah.
91
00:16:21.144 --> 00:16:46.084
But then the other part that we do is, um, again, that sort of grassroots decentralized approach, is we're creating a lot of pilots where, specifically around data quality and data stewardship, where, you know, those decisions where you can't have, you know, an elegant AI, um, driven solution to data quality, you can outsource it to your business analysts- Yes...
92
00:16:46.094 --> 00:16:56.404
and have them, and bring them into the fold of, of data quality, you know, and making it more of a team sport. We've done a lot of work in that regard with our, with our partners at Talend, um, around,
93
00:16:57.664 --> 00:17:09.254
you know, using their, their kind of non-code based, drag and drop based- Mm-hmm... uh, solutions to quality to be able to do, you know, outsourcing some of the stuff to, to stakeholders.
94
00:17:09.664 --> 00:17:18.754
Because that to me is, is a concern in, in that, um, you know, to scale, to scale my organization or the data strategy- Mm-hmm...
95
00:17:18.764 --> 00:17:25.424
across the whole division, um, it's gonna need the, the amount of people that you have to do it is gonna have to stay lean.
96
00:17:25.624 --> 00:17:38.694
And it's gonna have to be very efficient, and it's gonna have to rely on, on stakeholders to participate because, you know, doubling the data responsibilities of a, of a BI team- Yeah. [laughs]...
97
00:17:38.704 --> 00:17:48.744
you know, it's difficult to then dig- to then say, "Well, I need you to double the size of my team as well." So we're sort of preparing for that as well. Yeah, just to fix the data quality issues. Yeah. Oh, for sure.
98
00:17:48.784 --> 00:18:02.044
[laughs] Yeah, for sure. So you're using Talend already. Mm-hmm. Uh, you're using QlikView. What do you think about now they're coming together? Um, will that make your life easier, um- So-... processing things?
99
00:18:02.684 --> 00:18:18.332
What I love about-QlikView a-and, and Talend. It's... To do... So I'm, I'm essentially trying to build a data strategy for an entire...
100
00:18:18.762 --> 00:18:32.852
Help, help build a d- a data strategy for a h- an entire enterprise. Mm-hmm. QlikView is an amazing product because it allows you to make a quick buy versus build decision. You know, if you have
101
00:18:34.152 --> 00:18:40.572
several different data sources and you just need BI out of the box- Mm-hmm... they are there for... They are there to support those organizations.
102
00:18:41.112 --> 00:18:55.442
And I think that it's a, it's a, it's a brilliant model to follow, um, because at the end of the day, like, once data is in a lake or a warehouse, it's agnostic technology, right? Yeah.
103
00:18:55.442 --> 00:19:08.752
So how it got from a source system into a data warehouse, Qlik, Talend, uh, Power BI, Azure, you know, writing, writing custom scripts in Python, it, it doesn't really matter.
104
00:19:08.832 --> 00:19:20.432
But once it's there, and it's well-documented, that's so... That to me is, is really where there's a cool place for a company like Qlik to exist right now, 'cause I think that's the...
105
00:19:20.852 --> 00:19:33.982
There's tons of, tons of, um, directors of BI like me out there that are struggling with, you know, FTP sites and struggling with email attachments and things like that, you know. [laughs] Yeah.
106
00:19:33.982 --> 00:19:43.772
You know, they're not, they're not massive, you know, Fortune 50, Fortune 500 companies, but they're of scale that they have data. Yeah. And that's where Qlik is, is a fantastic...
107
00:19:43.852 --> 00:19:53.352
Just walking around the floor and seeing some of the demos that they have right out of the box, that's the, that's the brilliance of their, of their positioning, I think. Yeah, and I see the partnership what they have.
108
00:19:53.412 --> 00:20:02.272
Uh, I, I saw some, some, some partners as well doing version control- Yeah... on QlikView, as well on Cognos and Power BI. Yeah. And then you think, yeah, they're doing...
109
00:20:02.292 --> 00:20:13.021
They know what is missing, but that is tackled by the partnerships, so. No, it is. It really is. And, and I think that, you know, I... There wasn't...
110
00:20:13.512 --> 00:20:20.192
Companies like Qlik didn't exist when I started my career, where you could just say, "Just get, procure the, procure some funds,
111
00:20:21.132 --> 00:20:30.452
you know, write the check for the software, a little bit of the services, and you could be up and running with visualizations in a matter of weeks." Yeah. It just, that, that to me is a, is a very cool,
112
00:20:31.412 --> 00:20:45.272
very cool differentiator, I think, for, um, for lots of different organizations out there, um, for sure. Yeah. Great one. Um, Kevin, besides data, music connects us as well. What is your favorite type of music or band?
113
00:20:46.952 --> 00:21:03.632
[sighs] Um, so that's a very, very big question. Um, you know, I think right now I'm listening to a lot of, um, Grateful Dead. I'm listening to a lot of Dead & Company.
114
00:21:04.232 --> 00:21:18.352
Trying to decide whether to go see Dead & Company in Philadelphia- Okay... in June. Um, but I, I run the gamut. We listen to hip hop in my house. We listen to- Okay... classic rock. Um, you know,
115
00:21:19.652 --> 00:21:29.792
we listen to, you know, uh, dan- mot- dance, you know, you name it. We're really... But right now, heavy rotation with Grateful Dead and Dead & Company- Yeah... I'd say. Okay. Great one.
116
00:21:30.312 --> 00:21:37.312
Kevin, it was nice talking to you. Very nice talking to you. Thanks for your time. And- Thank you very much... thank you very much. All right. Okay. Cheers. Cheers. Thank you very much.
117
00:21:37.852 --> 00:21:47.862
Thank you for joining us on this awesome podcast. As senior executives, data and analytics architects, and AI professionals, your time is valuable and we appreciate you choosing to hang out with us.
118
00:21:48.152 --> 00:21:54.432
If you liked what you heard, please give us a thumbs up. Hit the subscribe button, and leave a comment. We love hearing from our audience.
119
00:21:54.652 --> 00:22:10.152
Don't forget to spread the word on social media, and let's continue to drive innovation in the industry together. Thanks for listening, and we'll catch you on the next episode. [outro music]