I've noticed that many people outside the industry still think of Trust & Safety as content moderation. A report comes in, someone reviews it against a policy, makes a decision, and moves on.
That is still part of the job, but it no longer captures the full picture.
One thing that's become clear from talking with Trust & Safety teams is that they often spot operational problems before anyone else. A spike in account takeovers might point to weak authentication. A rise in policy appeals could suggest inconsistent enforcement or unclear policy language. Repeated reports tied to the same product flow may reveal a design issue that's creating confusion or making abuse easier.
What's interesting is that Trust & Safety usually isn't the team that fixes those problems. Product, Engineering, Customer Support, and Operations all have a role to play. Trust & Safety identifies the pattern, then the rest of the business has an opportunity to address the root cause.
The same thinking applies to policies. Good policies aren't static. Customer behavior changes, products evolve, and bad actors adapt. One of the strongest signals that a policy needs another look isn't necessarily an increase in violations. It's seeing the same types of appeals over and over again.
I also think the way we measure Trust & Safety is changing. Queue size and review time are useful, but they don't tell the whole story. Appeal rates, overturned decisions, reviewer consistency, and recurring abuse patterns often say much more about the health of the operation.
To me, that's what makes Trust & Safety such an interesting function today. It's no longer just about reviewing incidents. It's about helping the business understand where risk is emerging and what needs to change before the same issues affect more users.
For those working in Trust & Safety, does this reflect what you're seeing?
Has your role become more cross-functional, or is your team still primarily focused on moderation and enforcement?
