Hoping the OCAU brains trust can help me on this one since it is so hard to network these days. I work in a large organisation where we have distinct technology teams request services from end users and from one another. I'm particularly interested in hearing about the experiences of tech team to tech team. Example of "tech-to-tech" requests that end users would never see could be: Requesting a DNS record change Setting up a new AD group for a new application Creating SCCM site boundaries These are all handled by separate IT teams due to segregation of duties. However, there isn't an unified way to raise requests for each of these teams - these could be through: Fully-fledged ITSM ticketing system (eg Remedy/ServiceNow) Simplified web interface that integrates into ITSM tooling JIRA Service Desk Email DLs/Teams channels Direct Teams messages/phone calls/walk-ups Help desk requests Attempts at fixing this include: Making help desk triage all requests (drowned our help desk team in emails) This was quickly followed by forcing all "tech folks" to raise an ITSM ticket and not contact help desk (which led to creating a "quick interface" for techies to raise/query tickets etc. without having to log in/fill in 50 fields Having a single Confluence webpage to direct tech users but these quickly become outdated Obviously this creates a lot of confusion for new starters who have no idea how to raise requests and rely on others to help navigate the maze that is our IT. I would love to hear how other companies tackle this problem. Apart from giving tech people admin rights to everything, how does "wayfinding" work for your company where segregation of duties are required? Does it work effectively? How have your techies reacted?