How to Build a Fraud Signal-Sharing Strategy Across Teams and Vendors

WEBVTT

1
00:00:02.110 –> 00:00:13.399
Jerry Hoff: And welcome back to the Blueprint series. This is gonna be a fun one. This is how to build a fraud signal-sharing strategy across teams and vendors. So we’re going to dig deep.

2
00:00:13.400 –> 00:00:22.979
Jerry Hoff: Into what signals are in terms of fraud, and then we’re going to get into a whole bunch of logistics that you’re going to need to know in order to make

3
00:00:22.980 –> 00:00:30.840
Jerry Hoff: best use of signals and signal sharing. So today, I’ve got Jacob Sanchez. Jacob, how you doing today?

4
00:00:32.820 –> 00:00:34.410
Jacob Sanchez: I’m doing well, Jerry, how are you?

5
00:00:34.410 –> 00:00:51.449
Jerry Hoff: I’m doing great, I’m doing great. So, Jacob and I are going to get deep down into signal sharing, and we’re gonna get into… and Jacob is a trust and safety architect at SIFT. So, Jacob, let’s start off by the question, what is signal sharing? So, I mean, I think we all know what signals are, right?

6
00:00:51.450 –> 00:01:05.000
Jerry Hoff: pieces of data that are going to help us in our fraud analysis. But let’s dig into, you know, how do you see signal sharing and various signals as well? Maybe define signals to begin with, and then let’s get into signal sharing.

7
00:01:05.410 –> 00:01:17.660
Jacob Sanchez: Yeah, I think at its core, at its simple version, like, signals, in the context of a fraud team, or even, like, security and others, is, you know, pieces of information that help you do your job and help your program. So, think of things like.

8
00:01:17.660 –> 00:01:32.039
Jacob Sanchez: you know, potentially items of PII, or IP addresses, or device data, like, those are signals that, all put together, and with some strategy, really help you. But signal sharing is being able to take those signals and…

9
00:01:32.040 –> 00:01:45.569
Jacob Sanchez: kind of use them in different ways. So, within fraud teams, you can use them for your fraud prevention strategy or investigations. You can also use those same signals to help with security events and other, other teams’ initiatives and programs.

10
00:01:46.340 –> 00:02:05.170
Jerry Hoff: It makes sense. You know, Jacob, as you know, I come from an information security background, and it’s always interesting to me that various teams in a large corporation are going to have various signals, and they don’t necessarily share those signals. Not out of anything bad, just simply they might not realize that other teams have

11
00:02:05.170 –> 00:02:09.389
Jerry Hoff: pieces of data that they can be using as well. So…

12
00:02:09.889 –> 00:02:28.129
Jerry Hoff: you know, getting into signal sharing, just very briefly, I’d love to know, what are the various teams, usually, that have signals that are relevant to fraud detection? I mean, clearly the fraud team, right? But I would imagine IT, information security, do we ever get that crossover universe going on? And is it legal? Like, who…

13
00:02:28.130 –> 00:02:30.959
Jerry Hoff: Who… where do you get these universe of signals?

14
00:02:31.400 –> 00:02:55.040
Jacob Sanchez: Yeah, I’d say, like, short answer is you can probably share signals with any team in the organization. From my experience, like, the groups you just mentioned, IT, security teams, and legal, definitely wanted to hear, you know, about certain things, different kind of fraud trends. From a legal standpoint, there was requests for information that, you know, that we would share for either law enforcement requests or anything like that.

15
00:02:55.040 –> 00:03:18.229
Jacob Sanchez: And then I’ve seen it being used more strategically, and for growth initiatives within a company, like, you know, sharing data with commercial teams, or growth teams, and marketing and customer support. There are things that fraud teams or trust and safety teams often see that are either useful for other groups, or it’s the same data that the other groups are seeing, but perhaps it’s from a different vendor, or there’s just a different use case for it.

16
00:03:18.230 –> 00:03:25.000
Jacob Sanchez: And so, I think, the… the topic here is really important, I think, for…

17
00:03:25.000 –> 00:03:36.040
Jacob Sanchez: For Fraud and trust and safety practitioners to understand, because everybody’s so passionate about their area of focus and what they do, and trying to make their programs and teams better, that it’s often forgot that

18
00:03:36.040 –> 00:03:46.160
Jacob Sanchez: This stuff is useful everywhere, right, across the business, and it just… it takes a lot of, you know, strategic effort to make that work, and buy-in from the team and from leadership.

19
00:03:46.860 –> 00:03:59.729
Jerry Hoff: You got me very intrigued with customer support being a source of data for fraud detection. I want to hear more about that, but let’s get to our first question. So this is a question for the audience.

20
00:03:59.730 –> 00:04:17.150
Jerry Hoff: How does your team currently share fraud signals across departments? Do you have a shared dashboard and reports? Slack email threads? We don’t, honestly, or what’s a fraud signal? Now, hopefully we’ve defined what’s a fraud signal, so hopefully we won’t get too many votes

21
00:04:17.149 –> 00:04:27.589
Jerry Hoff: on that one. But this is a great question, and this comes up in information security as well, which is, how do you share relevant information with the various parties involved?

22
00:04:27.950 –> 00:04:36.209
Jerry Hoff: Jacob, I mean, without putting your thumb on the scale in terms of the voting, what, what have you seen that works?

23
00:04:37.010 –> 00:04:45.520
Jacob Sanchez: Yeah, I’ve seen a… to be honest, and this is where, you know, this is a great candid conversation, I’ve seen a lot of it start to work and then kind of deteriorate or fail over time, and…

24
00:04:45.590 –> 00:05:04.480
Jacob Sanchez: I would say in today’s day and age, probably the answer lies between automation and some sort of, like, AI enablement for teams to share data easily, but also, like, have monitoring on the hygiene of that data, right? Is it going stale? Are people engaged? Are we sharing it the right way? Maybe, one channel’s good for

25
00:05:04.480 –> 00:05:09.360
Jacob Sanchez: Your legal team, but not for your marketing team, and figuring out how you share it is what matters.

26
00:05:09.600 –> 00:05:19.360
Jerry Hoff: That makes sense. So the votes have come back, and it’s interesting, so we got about 30% using shared dashboards and reports. We have 43%

27
00:05:19.360 –> 00:05:32.659
Jerry Hoff: with Slack or email threads, so it sounds like Slack and email is the winner here. And then 30% saying, we don’t, we don’t share. And fortunately, nobody said, what’s a fraud signal? So it looks like we did a good job of…

28
00:05:32.660 –> 00:05:33.770
Jacob Sanchez: Great job, awesome.

29
00:05:34.880 –> 00:05:48.739
Jacob Sanchez: Yeah, if I… this is great. I mean, kind of what I expected. I think this shows probably different maturity levels of programs and growth stages, but I think this is, you know, pretty accurate to what I was expecting of…

30
00:05:48.740 –> 00:06:03.800
Jacob Sanchez: Shared reports and reports… shared dashboard and reports can be something as simple as a CSV file kind of going back and forth. I’ve seen that plenty of times in my day. Dashboards are even better, because you get a central point where multiple teams can look at something and use it.

31
00:06:03.800 –> 00:06:18.560
Jacob Sanchez: And then the Slack and email threads. It’s great for quick, you know, interactions, but it’s not, you know, good for cross-team functionality or being able to have, kind of, more transparent information across your team and across the org.

32
00:06:19.050 –> 00:06:20.290
Jerry Hoff: Nice, nice.

33
00:06:20.350 –> 00:06:27.089
Jerry Hoff: Alright, so let’s move to the next slide. Where does signal sharing break down today? Now, you know, as,

34
00:06:27.140 –> 00:06:44.870
Jerry Hoff: you know, in my former life, I was head of information security for a large company, and I know, even within my group, you know, it was… like I was saying, this team might have signals that this other team might need to use, or vice versa, or sometimes you’ve got, you know, maybe the same

35
00:06:44.950 –> 00:06:53.010
Jerry Hoff: basic team, but you’ve got different geographical distributions, it’s not easy to get all of this plumbing working. So.

36
00:06:53.130 –> 00:07:07.140
Jerry Hoff: where does it break down? Like, you do a lot of effort, you go through, I guess you have the meetings, you set up, okay, Team A, you’re going to be sharing this data with Team B, Team B, you’re going to be sharing this with Team C, and then it degrades over time. Jacob, what happens?

37
00:07:07.430 –> 00:07:21.750
Jacob Sanchez: I think a lot of what has happened that I’ve seen is there’s breakdowns of, like, the simple things, right? People, process, and then, like, is this successful? And I think when it starts to not become successful or useful for you and your team.

38
00:07:21.750 –> 00:07:29.370
Jacob Sanchez: that’s when you start to kind of, like, bow out, and maybe slow down the sharing, or it’s not really helpful for you. But I think the best thing

39
00:07:29.370 –> 00:07:40.139
Jacob Sanchez: That you can do in that time of excitement, where this is a… maybe a new initiative, or a certain kind of fraud case popped up that triggered, you know, this thought across the business.

40
00:07:40.140 –> 00:07:51.640
Jacob Sanchez: It’s really about how do you map the signals, per function that matter to them, right? Between your fraud, your security team, your legal team, anybody else, have a kind of…

41
00:07:51.640 –> 00:08:16.569
Jacob Sanchez: a key of definitions and signal kind of index that you can reference, and then the teams can know what’s kind of available, and then you agree on, hey, maybe there’s two things here out of this list of 10 that we really want to focus on, so how can we make that the best that we can? And so if I can give a quick example, earlier in my career, when I was a web hosting company.

42
00:08:16.570 –> 00:08:18.499
Jacob Sanchez: There was an initiative to…

43
00:08:18.500 –> 00:08:39.539
Jacob Sanchez: really share data that we were gathering on fraudsters across the wider, kind of, web hosting industry. And so I was meeting with leaders with our, you know, of the space, and with our competitors, and there was a lot of excitement at the beginning, but it really started to only benefit a few players in that group.

44
00:08:39.539 –> 00:08:57.070
Jacob Sanchez: And so, the ones that it wasn’t benefiting started to back away, or just not submit anything, and then it deteriorated. We just kind of said, you know, I think it was good, a good pilot for what we had. We didn’t have the momentum to actually put it into practice and execute well on it, and it was kind of tabled within a few months, and…

45
00:08:57.070 –> 00:09:15.730
Jacob Sanchez: I think that was a good learning, because I think it definitely takes the people being bought in, having champions of that kind of initiative and process, and being able to understand, hey, is this working? And if it’s working, how can you make it better? If it’s not working, do you want to change it, or do you just want to kind of focus on something else? And so, I think that’s totally realistic for a lot of teams to face.

46
00:09:16.800 –> 00:09:28.520
Jerry Hoff: You know, I like what you said as well about, like, the motivation and so forth, and that, you know, certain signals maybe benefit just certain groups. Whenever you’re giving new responsibilities to teams.

47
00:09:28.600 –> 00:09:45.629
Jerry Hoff: you know, there’s always, like, the must-do and the nice to do, right? And if people are not properly motivated to make sure that, I guess, the sharing is a must-do, it’ll fall off the radar in times of when, you know, when things get busy.

48
00:09:45.800 –> 00:09:59.950
Jerry Hoff: Is there a motivation factor as well? Like, you tell this team, hey, you must share this data because otherwise this other team can’t function properly, and make it part of their KPIs, make it part of their performance review. That must go into the whole thing, right?

49
00:09:59.950 –> 00:10:17.839
Jacob Sanchez: Yeah, definitely, it’s part of, like, the, you know, preventing the breakdown of the signal sharing process. It’s aligning on certain, you know, data points that are relevant, and then aligning on success of this. And we’ll get into that, you know, as we go further through this webinar, but I think just having that

50
00:10:17.840 –> 00:10:37.610
Jacob Sanchez: personal buy-in and the team buy-in and leadership kind of sponsorship is really important and helpful. And look, I’ll kind of call it out, too, is like, we know that there’s economic pressure, there’s kind of layoffs happening around industries every day. It’s hard to do this when you lose the people that were fighting for certain initiatives, so…

51
00:10:37.610 –> 00:10:49.099
Jacob Sanchez: How do you kind of make that scalable and more, automated so that if you lose one key person, the whole thing doesn’t just kind of go, you know, out the door? You can maintain some of that integrity of the initiative?

52
00:10:49.390 –> 00:10:55.500
Jerry Hoff: which happens a lot, right? You… it’s interesting as well, because, yeah, when you have certain roles.

53
00:10:55.500 –> 00:11:11.330
Jerry Hoff: There’s, like, the documented responsibilities of that role, but there’s always a whole bunch of undocumented responsibilities. So when one person leaves the organization, there can be an invisible effect that isn’t obvious at first glance, and this is probably one of those. That’s very interesting.

54
00:11:12.010 –> 00:11:14.480
Jerry Hoff: Very good. Well, let’s get to the next…

55
00:11:14.590 –> 00:11:18.100
Jerry Hoff: Next slide. So this is another question for the audience.

56
00:11:18.330 –> 00:11:37.299
Jerry Hoff: what’s your biggest blocker to sharing fraud signals across teams? Is it data format mismatches? Is it trust and liability concerns? No shared owner, or leadership doesn’t prioritize that? Those are all very interesting. The data format mismatch

57
00:11:37.320 –> 00:11:50.939
Jerry Hoff: Well, it looks like most people were using Slack or email, so there’s not really a data format mismatch, unless it’s, like you said, people are trying to automate it, right? Putting it into some kind of a JSON format so it can be ingested by some other automated process.

58
00:11:51.200 –> 00:12:01.729
Jerry Hoff: What about that trust and liability concerns? Is it, like, trust among teams? Like, the legal’s like, well, I don’t know if we can trust IT, or vice versa. Is that… is that what you see, Jacob?

59
00:12:01.730 –> 00:12:03.480
Jacob Sanchez: I’ve definitely seen in my past, like.

60
00:12:03.520 –> 00:12:18.379
Jacob Sanchez: teams get, sensitive around certain things of, like, hey, we have this data for this use case. If it gets, you know, not in the wrong hands, but just, like, to a team or to people who shouldn’t be seeing this, then it gets tricky, right? And I think…

61
00:12:18.380 –> 00:12:41.070
Jacob Sanchez: there are some teams, some organizations that are just, you know, more strict with this kind of thing, and they’ll say, you know, you just don’t… we’re not going to give access to this, or we’ll give it to you, but it’ll be hashed, or it’ll be kind of anonymized, and sometimes that’s helpful, and then oftentimes, it can be, like, good to have, but not the best thing. So I’ve seen definitely different, levels of variety here.

62
00:12:41.070 –> 00:12:59.510
Jacob Sanchez: I would say legal teams tend to err on the side of, let’s keep things private and secure. Then, you know, the teams that want to move quick and get their things done will share things in a way that, you know, is still secure and trusted, but can go a lot faster and give more transparency.

63
00:13:00.930 –> 00:13:15.010
Jerry Hoff: Yeah, and I’ve seen that many, many times, especially when, like you just said, you’re involving legal, sometimes involving HR, like you just said, customer support, potentially. Then you’ve got IT, information security, and fraud, all kind of together.

64
00:13:15.010 –> 00:13:27.800
Jerry Hoff: And especially once you add the international component, right? Like, hey, because of GDPR, are we able to give this information to these other teams, etc? Or, hey, if it’s gonna cross a border, what’s the effect of that going to be?

65
00:13:27.800 –> 00:13:41.470
Jerry Hoff: So, yeah, those are all very complicated. So, the, the results are in. So, we got 25% saying data format mismatches, which means, I guess, there’s a lot of automation going on, I guess we can assume, right, Jacob?

66
00:13:42.240 –> 00:13:44.590
Jacob Sanchez: Yeah, it could be, like,

67
00:13:44.590 –> 00:14:08.759
Jacob Sanchez: either the teams across the initiative are okay with kind of the lowest level of format, and by that I mean, like, if it’s a CSV file, and your engineering team, your security engineering team is, like, okay with that, then that’s cool. They’re probably doing something else after the fact to make it easier for them to work on, but I think I’ve seen cases where it’s like, let’s keep the sophistication level low, just so we can get it going, and then we’ll improve

68
00:14:08.760 –> 00:14:10.399
Jacob Sanchez: Over time, so that makes sense.

69
00:14:10.730 –> 00:14:20.119
Jerry Hoff: Makes sense. So, the number one was trust and liability concerns, and that tracks very closely with what I’ve seen as well, working in large enterprises.

70
00:14:20.350 –> 00:14:24.510
Jerry Hoff: you’re just not sure, right? If you’re, like, supposed to share data and…

71
00:14:24.720 –> 00:14:35.030
Jerry Hoff: you share the wrong data, it could actually, you know, come back to bite the sharer, right? And so there’s liability and trust concerns.

72
00:14:35.390 –> 00:14:39.490
Jerry Hoff: That seems to be a big one. That probably tracks your experience as well, right, Jacob?

73
00:14:39.490 –> 00:15:03.130
Jacob Sanchez: Yeah, and it’s just a… you know, when there’s, like, a kind of an overarching view of, like, we won’t share things because it could lead to bad, you know, bad things happening. Right. That’s okay, and I think that’s totally realistic of, like, some teams just having that mindset, but there’s always a way, I would say, like, let’s figure out a way to do this, either with tools or certain…

74
00:15:03.130 –> 00:15:11.049
Jacob Sanchez: you know, user groups and permissions, like, there’s ways to do… to get things done, but I totally understand where the trust and liability concerns are very top of mind for everybody.

75
00:15:11.050 –> 00:15:25.399
Jerry Hoff: Yeah, well, that’s number one, and then number two was leadership doesn’t prioritize it, and that makes complete sense. It goes back to the motivation, right? If your direct boss, who’s going to give you your performance review, doesn’t prioritize it, well, you’re gonna…

76
00:15:25.400 –> 00:15:31.830
Jerry Hoff: Naturally do the things that they do prioritize, right? To make sure that you’re making your direct boss happy.

77
00:15:31.830 –> 00:15:36.179
Jerry Hoff: Yeah, and so that, that just makes sense. Okay, very good.

78
00:15:36.600 –> 00:15:48.390
Jerry Hoff: So, let’s go to the next slide, how you can encourage internal teams to share data. This is tricky. This gets into psychology, this gets into motivation, this gets into a whole can of worms.

79
00:15:48.540 –> 00:16:03.919
Jerry Hoff: I… I told you, I’ve done the same thing. Like, in information security, there’s lots of signals that can be used by the various teams, and it’s not always easy to get teams to share. Sometimes they’re threatened, right? They’re like, whoa, whoa, why do you want this data? Why do you want this?

80
00:16:03.920 –> 00:16:08.679
Jerry Hoff: Right? Sometimes it just, like you said, it’s not a priority. Sometimes…

81
00:16:08.690 –> 00:16:16.630
Jerry Hoff: Yeah, I guess there’s all sorts of reasons. So, encouraging them, overcoming them, Jacob, what have you seen that works?

82
00:16:17.240 –> 00:16:36.829
Jacob Sanchez: Yeah, I think the things that work are coming to the table with, hey, we have this idea to share a certain signal. Call it a, you know, either device kind of ID, or anything that would tie kind of a digital footprint to a user. I’ve seen, if you have alignment on, kind of.

83
00:16:36.980 –> 00:17:01.939
Jacob Sanchez: maybe one or a few things, that usually gets, you know, you kick the tires a bit of there’s buy-in on a certain signal that you want to share in a certain way, and here are the reasons for why it can work. And this is where you get into, hey, we can share a KPI, maybe there’s a KPI that you share between groups. Maybe there’s a metric that you’re tracking that is really only relevant to you, but the

84
00:17:01.940 –> 00:17:14.590
Jacob Sanchez: same signal helps drive performance on both sides or multiple sides of that initiative. So, really, it is about, you know, coming to alignment with the people and the program and the team of

85
00:17:14.589 –> 00:17:28.269
Jacob Sanchez: this is what we want to do, why we want to do it, how we’re going to do it, and this is how we’re going to measure success. And we’ll kind of take this in phases, and if it’s not working, we figure out, do we want to change it? And if you do, then you kind of keep going down the path of improvement.

86
00:17:28.270 –> 00:17:38.119
Jacob Sanchez: If it doesn’t work, then you can call and be like, hey, we tried something here. Maybe there’s a point in the future that it makes sense to do so. But I think, like, the thing that…

87
00:17:38.120 –> 00:17:55.049
Jacob Sanchez: typically works is, if the person asking, or the requester of, like, hey, I want to share this data, or I want you to share this data, if they have things kind of figured out in a way that makes the other party or party’s lives a little bit easier, where they don’t have to kind of brainstorm the whole thing.

88
00:17:55.050 –> 00:17:58.880
Jacob Sanchez: That goes a long way, and it just, I think, gets buy-in and trust pretty quickly.

89
00:17:59.790 –> 00:18:18.040
Jerry Hoff: That makes sense. So, you know, so I can visualize this. Is it mainly… is the most typical example, like, fraud going to IT, hat in hand, and saying, hey, we need these IP addresses? Or when there’s a brand new account created, we need to see these pieces of information. Geographical location, timestamps.

90
00:18:18.100 –> 00:18:22.549
Jerry Hoff: Activity, you know, you had mentioned before, I think we were talking about

91
00:18:22.660 –> 00:18:25.449
Jerry Hoff: It’s not just making the account, it’s…

92
00:18:25.690 –> 00:18:34.880
Jerry Hoff: suspicious activity once the account is made that sometimes will give an indication whether this is a fraudster or not. So.

93
00:18:35.140 –> 00:18:51.959
Jerry Hoff: Is the… is the concrete implementation, yeah, fraud going to IT, having a meeting, saying, we need this data, please send it over, and are these, like, ad hoc? Are these, like, we want you to make an automated system so we always have this data, or is it a little bit of all of those things?

94
00:18:51.960 –> 00:19:11.470
Jacob Sanchez: It’s probably a little bit of all of those things, and I want to, yeah, double-click on that, and then kind of give an example that maybe is… I’ll call it, like, atypical, or just kind of a different take on it, but yes, when you’re, you know, implementing any tools, or you’re… maybe have internal tools and data that you’re writing rules and policies around.

95
00:19:11.470 –> 00:19:29.280
Jacob Sanchez: yes, getting that buy-in from the IT team, from the security team on, like, what and how you want to use it makes, you know, everybody’s lives easier when IT and security know exactly what you’re ingesting into your certain, you know, tools or your reports, and how you’re going to use that data.

96
00:19:29.280 –> 00:19:33.010
Jacob Sanchez: If there’s alignment there, great. And then even better, if they can help

97
00:19:33.010 –> 00:19:49.639
Jacob Sanchez: you know, kind of get your tools and your processes online with that trust of, like, this was built in the right way, and we’re not just kind of, like, cobbling pieces of data together in some Excel sheet that is, like, gonna fall apart and get, you know, too cumbersome to look at. That’s always great.

98
00:19:49.660 –> 00:20:00.049
Jacob Sanchez: I’ll say the… the interesting cases that I’ve seen of, kind of, signal sharing or data sharing, came from an example that,

99
00:20:01.140 –> 00:20:22.649
Jacob Sanchez: I have where I used certain pieces of data that we wanted to share with our growth team, like our commercial team. We wanted to drive sales, and we had a lot of things on the fraud side that could be useful, you know, to the marketing side or the growth side, and vice versa. So, there were things that we aligned on on certain, you know.

100
00:20:22.650 –> 00:20:45.229
Jacob Sanchez: volume of activity, like, user activity, are there things like multi-accounting, or kind of, like, promo abuse that’s hurting commercial gains? And so, yes, we were tracking that on our side as more of a fraud concern of, like, maybe people are using fake or stolen identities to create these, you know, these accounts, and they’re multi-accounting. And then on the growth of the marketing and commercial side, it was…

101
00:20:45.230 –> 00:21:08.440
Jacob Sanchez: hey, we’re seeing our kind of, like, promos get abused in a certain way, and we just don’t like that, because it’s hurting us from a dollar standpoint. And we’re like, hey, the two are very related, it’s the same problem, two sides of the same coin, and so you start to share, you know, different approaches to how you’re tracking it, kind of what abuse looks like, what fraud looks like, and then align on

102
00:21:08.440 –> 00:21:15.919
Jacob Sanchez: certain metrics and KPIs that make sense for both groups to march towards, and then you can kind of play with if there’s…

103
00:21:15.920 –> 00:21:28.950
Jacob Sanchez: Give and take on budget, if we’re over-indexing on, kind of, the fraud prevention. Can we balance that out to try to put more into the marketing spend and make it successful for both teams, or all teams, and your organization as a whole?

104
00:21:30.100 –> 00:21:32.870
Jerry Hoff: That’s really interesting, yeah, you kind of…

105
00:21:33.080 –> 00:21:49.240
Jerry Hoff: made me realize that these teams can have literally contradictory goals, right? So, if you have a growth team, and their goal is get as many new accounts as possible, and then you have the Fraud team that’s there to detect suspicious accounts, well, now all of a sudden.

106
00:21:49.540 –> 00:21:57.590
Jerry Hoff: one team might not… to, you know, make sure that the number is the biggest possible, they might not want to share data. Does that ever happen, in terms of…

107
00:21:57.740 –> 00:22:00.980
Jerry Hoff: Dragging one’s feet, or it’s never explicitly said like that?

108
00:22:01.190 –> 00:22:03.560
Jacob Sanchez: I mean, I think it definitely happens. There’s, like…

109
00:22:03.660 –> 00:22:12.079
Jacob Sanchez: again, I’ll go back to, like, the people, and then the team, and the program. It depends, right? Sometimes it’s, like, it starts off good, and then it doesn’t work anymore, and…

110
00:22:12.080 –> 00:22:12.570
Jerry Hoff: Interesting.

111
00:22:12.570 –> 00:22:23.099
Jacob Sanchez: Yeah, it just kind of has to be a consistent effort across all sides, and, you know, as long as you have alignment and goal setting, that will help drive performance and success.

112
00:22:23.500 –> 00:22:25.440
Jerry Hoff: Nice, nice. All right.

113
00:22:25.770 –> 00:22:44.479
Jerry Hoff: So, we have another question for the group. Does your fraud team currently share a KPI with any other department or vendor? Now, that’s interesting. Once you have the shared KPIs, now everybody is kind of going towards the same direction. So, yes, formally, informally, sort of.

114
00:22:44.480 –> 00:22:47.379
Jerry Hoff: Or, no, we operate independently.

115
00:22:47.380 –> 00:22:53.109
Jerry Hoff: This will be interesting to see what comes back. I think the KPI is really important.

116
00:22:53.130 –> 00:22:56.650
Jerry Hoff: Because, again, it puts everybody on the same page. If…

117
00:22:56.740 –> 00:23:03.650
Jerry Hoff: I’ve seen so many times, especially, like, you know, fraud, security, whatever it happens to be, There is, like.

118
00:23:04.130 –> 00:23:20.250
Jerry Hoff: one thing that you measure people’s performance on, which is, like, an actual formal KPI, and then there’s kind of, like, the informal stuff that people are told to do, but it’s never part of their review, or their bonus structure, or whatever, so it almost gives kind of contradictory

119
00:23:20.420 –> 00:23:30.470
Jerry Hoff: guidance to each person. Like, well, they told me to do X, but I’m gonna get bonused on Y. So which one am I supposed to do, right?

120
00:23:30.750 –> 00:23:39.250
Jacob Sanchez: Yeah, I would say that’s a story, you know, the life story of a fraud practitioner. It’s like, hey, my initiative here is to drive down loss, mitigate loss to the business.

121
00:23:39.250 –> 00:23:52.090
Jacob Sanchez: But you also care about your company’s growth and, like, your bonus and things like that, right? Like, those are all real things that you want to make sure you’re not just killing growth and, like, stopping fraud at all costs, and that’s where having, like, a shared KPI of

122
00:23:52.090 –> 00:24:08.209
Jacob Sanchez: perhaps, like, something, like, as simple as, like, a suspension rate. Like, we’re suspending these customers from doing a certain thing, but if there’s, like, a goal across teams that you’re trying to hit and try to strike a balance, that’s where you start to unlock the growth and the alignment across the company.

123
00:24:09.450 –> 00:24:12.479
Jerry Hoff: Well, I’ve got bad news. So, results are in.

124
00:24:12.640 –> 00:24:15.330
Jerry Hoff: And, Jacob, can you see the results, or only I can see the results?

125
00:24:15.330 –> 00:24:16.359
Jacob Sanchez: No, I can see them, yeah.

126
00:24:16.360 –> 00:24:17.970
Jerry Hoff: Okay, so number one.

127
00:24:18.350 –> 00:24:34.449
Jerry Hoff: No, we operate independently. So the number one 50… about 50% of the folks are saying they don’t share a KPI with any other department or vendor. So that’s definitely room for improvement, right? So if we agree that shared KPIs can go… can do a lot.

128
00:24:34.450 –> 00:24:43.419
Jerry Hoff: to formalize the, you know, the expectations the company has in these various teams, then if there aren’t any KPIs, that means

129
00:24:43.850 –> 00:24:47.570
Jerry Hoff: they’re leaving something on the table, right? It means there’s room for improvement.

130
00:24:48.010 –> 00:24:56.559
Jacob Sanchez: That’s right, yeah, or you’re doing it, you know, without anything in mind, just kind of, like, doing an activity, doing activity, and it leads to, you know, deterioration or,

131
00:24:56.700 –> 00:24:58.489
Jacob Sanchez: Been having an unsuccessful program.

132
00:24:58.710 –> 00:25:03.250
Jerry Hoff: Right, so it’s about 50% operating independently, and then 50-50 on the…

133
00:25:03.350 –> 00:25:07.999
Jerry Hoff: Or I guess 25-25, yes, formally or informally, sort of.

134
00:25:08.040 –> 00:25:19.109
Jerry Hoff: Very interesting, very interesting. Yeah, again, I hate to always make the parallels of information security, but it’s very similar. Like, we tell IT, hey, you must do these things securely.

135
00:25:19.110 –> 00:25:29.309
Jerry Hoff: But IT has really bonused on how fast they can do things, not so much on security, so it just becomes, mixed signals. So sharing KPI is definitely important.

136
00:25:30.460 –> 00:25:36.729
Jerry Hoff: All right, so moving on, bringing vendors into the signal-sharing loop. So this is interesting.

137
00:25:36.950 –> 00:25:39.739
Jerry Hoff: The same thing, everybody has their own…

138
00:25:40.040 –> 00:25:52.989
Jerry Hoff: motivations, right? Vendors want to get renewals. Vendors want to get the contract in place, vendors want to keep out their rival companies, so bringing vendors into the signal-Sharing loop, how does that normally work, Jacob?

139
00:25:53.430 –> 00:26:15.740
Jacob Sanchez: Yeah, this is an interesting one. It’s very hard to achieve. I’ll say, like, the way that I’ve seen, you know, I work with a lot of teams here at CIF, a lot of Fraud teams across different industries, and really what people want to do is, like, make their programs better. And sometimes that means you’re getting multiple signals from multiple vendors, and you’re just trying to make sense of it all and, like, do the best for your team. And so.

140
00:26:15.740 –> 00:26:24.019
Jacob Sanchez: Vendors need to understand, like, that is a real thing that practitioners want to happen. And so, if we’re…

141
00:26:24.020 –> 00:26:34.690
Jacob Sanchez: too precious about how we share data, about what can be used, kind of, internally by… by that merchant. It does… it does become a very, like, tricky conversation, and so I would… I would encourage, like.

142
00:26:34.690 –> 00:26:58.009
Jacob Sanchez: you as a practitioner to have, like, open and honest conversations with your account team at different vendors. What are you trying to do? How are you trying to achieve it? And I think in this day and age, everybody is coming out with a version of, like, an MCP server or some sort of data share of the, you know, internal kind of vendor data to your, to the merchant kind of database. Can you do that in an elegant way that keeps things trusted and still

143
00:26:58.010 –> 00:27:11.689
Jacob Sanchez: proprietary in a way, but gives practitioners what they need to get their job done. And I think, hopefully a lot of vendors, you know, that resonates with them, and that they can help, you know, carve a path for that to actually happen and for teams to execute.

144
00:27:12.400 –> 00:27:27.819
Jerry Hoff: So the short answer is, vendors, be the good guys, right? Share the data, make sure that you’re working together with your customers to help them achieve their goals, and everything will work out. Yeah, very good, very good. And then, how do you measure whether your signal-sharing plan is working?

145
00:27:29.120 –> 00:27:54.079
Jacob Sanchez: Yeah, I think, it’s… if you have alignment on KPIs, on your goals, and, like, the way that you’re doing things, that should, you know, tell you that there’s success. A kind of intangible way to measure success is, is there engagement on… on… from the parties, right? From your other team that you’re sharing with, or other teams? If it starts to go quiet, that’s probably an indicator that things aren’t heading down the right path, so…

146
00:27:54.250 –> 00:28:16.869
Jacob Sanchez: measuring it, you know, are your… from a fraud standpoint, are you improving on certain metrics, like your kind of detection speed and suspension rate? Is that changing over time? And, kind of overall, like, bad debt, is that getting kind of driven down by certain things that you’ve put in place? So there’s, like, the traditional kind of measure on your KPIs and the shared KPIs you have with your partners here, but also, like.

147
00:28:16.870 –> 00:28:24.510
Jacob Sanchez: Do you have that trust? Is that being maintained over time? And are you iterating on how you’re sharing your signals with your partners?

148
00:28:25.010 –> 00:28:26.590
Jerry Hoff: I love it. I love it.

149
00:28:26.770 –> 00:28:36.070
Jerry Hoff: All right, well, we’re gonna skip the very last, we don’t have time for this, but how does your org currently measure signal-sharing success? So, folks who are watching, just kind of think about that.

150
00:28:36.070 –> 00:28:47.309
Jerry Hoff: And maybe reflect on that. Performance changes using KPIs, using usage rates by volume, volumes of alert dashboard, or we don’t measure yet. So obviously, you do want to measure.

151
00:28:48.010 –> 00:28:56.100
Jerry Hoff: And very last, we only have 10 seconds, so maybe speak 10 seconds to this, Jacob. Making the business case for signal-Sharing investment.

152
00:28:56.550 –> 00:29:06.240
Jacob Sanchez: Show that it matters, come in with data, you know, show where the potential is for savings or for growth, and that’ll go a long way with your organization.

153
00:29:06.560 –> 00:29:23.390
Jerry Hoff: Wonderful. Well, we’re gonna leave it there. Jacob, thank you so much. This was obviously a popular, popular topic. We had a giant audience, so thanks everybody who joined, and we will see you at the next Blueprint Series event. Thank you all very much. Have a wonderful rest of the day.