Sounds so familiar Rob. Does the team have a backlog today? How is work triaged? How large is the function? How’s it structured? This sounds like a classic potential Team Kanban implementation from the blue book: could you start with where you are and visualise how work flows today? Or at the very least visualise the left hand side of the process.

Thank you once again for pointing me in the right direction @U01JWHPG4V6 - much appreciated. Will follow that approach. Also led me onto a couple of videos by David Anderson which has helped provide some additional detail on how I can move forward with this..

There’s some good information on team APIs/interfaces (across both humans and systems) in Team Topologies as well.

I think API patterns work really well for modelling teams and team interactions. By defining explicit purpose and expected inputs/outputs not only can it be shared externally, it shows when teams are trying to do too much or dealing with too much variability and complexity. I’d also suggest value stream mapping for that explicit purpose, usually there’s opportunities for generality to simplify or split teams effectively, which makes everyone happier.