Where does an “Agile Delivery Lead” fit in a Scrum team without overlapping the Scrum Master?

Lately I’ve been seeing more companies introduce a role called Agile Delivery Lead (sometimes even combined with “Value Manager”), and I’m trying to figure out how that actually fits within a Scrum setup.

In pure Scrum, the accountabilities feel pretty clear:
Scrum Master → process & team effectiveness
Product Owner → value & prioritization
Developers → delivery

But some orgs I’ve talked to are adding a Delivery Lead on top of that. From what I can tell, they handle things like cross-team coordination, timelines, stakeholder reporting, and sometimes tracking outcomes or value.

What confuses me is where the boundary is supposed to be.

Some of those responsibilities sound like Scrum Master territory. Others sound like Product Owner or even old-school Project Manager work. It feels like there’s a risk of overlap or stepping on toes if it’s not defined clearly.

At the same time, I can kind of see why bigger orgs might want someone focused on delivery across multiple teams.

For those working in Scrum environments:
Have you seen this role introduced?
Did it actually help, or just add extra process?
How did you avoid duplicating the Scrum Master/PO responsibilities?

Genuinely curious how people are making this work in practice.