Cross-functional fraud collaboration: A field guide to working better with internal teams
Guest: Nate Kharrl
Today I’m digging into cross-functional fraud collaboration, because honestly, this is one of the most common pain points I hear from fraud leaders. A lot of them will tell you their biggest challenge is not always the criminals on the outside. It is the misalignment on the inside.
That is not exactly subtle.
Fraud teams often see risk in one part of the customer journey, while marketing sees growth, product sees conversion, operations sees volume, engineering sees roadmaps, and leadership sees competing priorities. None of those teams are wrong for caring about those things. The problem is that they are often working from different slices of the same customer story and using different success metrics to judge what matters most.
And that matters.
Because when departments are stuck in silos, they can end up arguing about symptoms instead of solving root causes. So in this episode, I sat down with Nate Kharrl from Spec to talk about what he has learned by working across dozens of companies and seeing how internal teams think, where they clash, and what fraud teams need to understand if they want stronger influence inside the business.
Here is what that means in practice:
- Cross-functional fraud collaboration gets much easier when teams can see the full customer journey instead of only their own section of it
- Fraud department silos often create unnecessary friction because each team thinks it has the clearest view of the customer
- Fraud metrics conflicts can quietly shape bad decisions when teams are rewarded for competing outcomes
- Internal stakeholder management matters because fraud team influence depends on being understood, not just being right
What you’ll hear in this episode:
- Why working with internal teams can be harder than fighting external fraud at times
- How fraud and marketing alignment, fraud and engineering collaboration, and fraud and operations teamwork often break down
- Why customer journey visibility and a common source of truth are so important for organizational fraud alignment
- What Nate has observed about the goals and pressures other departments are dealing with
- How fraud leadership strategy can improve when fraud teams understand what other teams care about most
You should listen to this episode if you:
- Work in fraud and feel like other departments do not fully understand your team’s role
- Want better cross-functional fraud collaboration without constantly fighting the same internal battles
- Need stronger fraud team communication and internal stakeholder management
- Care about customer journey analytics, cross-department fraud solutions, and better fraud team influence
- Are trying to build more durable organizational fraud alignment across product, marketing, operations, and engineering
If you liked this episode, be sure to subscribe and review the podcast on iTunes, Spotify, YouTube, or wherever you listen to podcasts. It really helps with getting the word out.
Episode notes & key takeaways
Why fraud teams so often feel at odds with other departments
Let’s break this down.
One of the biggest reasons fraud teams feel friction with other departments is that everyone is usually optimizing for something different. Marketing wants more approved customers. Product wants less friction. Operations wants speed. Engineering wants focus. Finance wants fewer losses. Fraud wants integrity. None of that is unreasonable on its own.
The problem is that those goals can collide fast.
And when they do, fraud teams are often put in the position of being the people saying no, slowing things down, or raising concerns nobody else wants to hear in the moment. That can make the fraud team look like the obstacle when really they are often just the first team seeing downstream consequences before anyone else does.
That usually does not feel great for anyone.
- Fraud metrics conflicts often come from teams being measured on different business outcomes
- Fraud team communication gets harder when other teams only see fraud as friction
- Working with internal teams requires understanding what they are protecting too
- Fraud leadership strategy is stronger when it starts with shared incentives, not just disagreement
Why customer journey visibility changes the conversation
This is where things get interesting.
A lot of internal conflict exists because each department sees only part of the customer journey and assumes that part is the most important part. Marketing may understand acquisition really well. Support may understand complaints really well. Product may understand flow behavior. Fraud may understand abuse patterns. But if nobody can see how those pieces connect, each team ends up defending its own truth instead of working from the full picture.
That is a problem.
Because cross-functional fraud collaboration becomes much harder when there is no common source of truth. Teams argue from partial visibility, and partial visibility almost always creates partial solutions.
This is exactly why customer journey visibility matters so much. Once teams can see the same story across the whole experience, the conversation gets a lot more productive. Not instantly easy. But much more grounded.
- Customer journey visibility helps teams move from assumptions to shared context
- A common source of truth reduces conflict caused by partial data and siloed perspectives
- Customer journey analytics are most useful when multiple teams can work from the same picture
- Cross-department fraud solutions work better when everyone can see where the real issue begins and where it spreads
Why fraud and other teams often talk past each other
Here’s what’s actually happening.
Fraud teams often communicate in the language of risk, abuse, downstream impact, and pattern recognition. Other teams may be thinking in the language of growth, user experience, engineering effort, campaign performance, or operational speed. So even when both sides are talking about the same customer behavior, they are often describing it through completely different priorities.
Right.
That is why so many meetings feel like people are missing each other by a few inches. Not because anyone is stupid. Not because anyone is malicious. Because they are translating the same reality through different stakes.
That is also why fraud and marketing alignment, fraud and engineering collaboration, and fraud and operations teamwork require more than just “better communication” in the abstract. Fraud teams need to understand what other teams are solving for, and other teams need help understanding what fraud sees before it becomes a bigger business problem.
- Fraud team communication improves when fraud leaders speak in terms other departments already care about
- Fraud and engineering collaboration gets stronger when fraud frames issues as system behavior, not only loss outcomes
- Fraud and marketing alignment works better when the discussion includes customer quality, not just customer quantity
- Internal stakeholder management depends on translation as much as expertise
Why a common source of truth creates stronger organizational alignment
This is one of the biggest takeaways from the conversation with Nate.
When companies have a true common source of truth around the customer journey, a lot of the internal tension starts to ease. Not because everyone suddenly agrees on everything, but because the debate becomes more honest. Teams can stop arguing over whose data is “right” and start talking about what the full story means.
And that matters.
Because organizational fraud alignment is a lot easier when the company can see how one team’s decision affects another team’s outcomes. A marketing push may change fraud volumes. A product change may shift support burden. An engineering shortcut may create new abuse paths. A fraud control may affect conversion in one segment and improve trust in another.
That is the kind of conversation mature teams need to be having.
- A common source of truth improves cross-functional fraud collaboration by reducing competing versions of reality
- Organizational fraud alignment gets stronger when teams can see cause and effect across the customer journey
- Fraud team influence grows when fraud is connected to the broader business picture
- Cross-department fraud solutions require shared visibility, not just shared meetings
Why fraud leaders need to understand what other teams care about
Honestly, this is the part that holds up for me.
Fraud teams spend a lot of time trying to get other departments to understand them. That makes sense. But one of the most useful ways to improve cross-functional fraud collaboration is to reverse that lens a little too. Understand what the other team is measured on. What pressure they are under. What they are trying to protect. What makes their day harder. What makes their success visible.
That is not giving up the fraud perspective. It is strengthening it.
Because once fraud leaders understand the motivations of other teams, they get much better at building real influence. They can frame risk in terms that land. They can propose solutions that feel workable. They can create stronger alliances instead of only raising objections.
The big takeaway from this episode is pretty straightforward. Cross-functional fraud collaboration improves when fraud teams stop assuming everyone else sees the same customer reality they do and start helping the company build a fuller, shared view of the journey. That takes better communication, stronger internal stakeholder management, and a common source of truth that cuts across departmental silos. That is where better alignment starts.
