What should a managed technology service actually own?
“Managed” is a scope, not a mood. It says what the service includes, what it leaves out, who owns each side, and how the work is reported and improved. Without that, it becomes a queue for whatever arrives next.
Write the boundary in plain language. Name the owners. Set the escalation route for work that sits outside the day-to-day queue. Agree what is monitored, how quickly someone responds, and what a response is expected to achieve. Reporting should describe the service, not only the number of tickets.
Keep running the service separate from changing it. Administration of what already exists is not the same job as a project, a supplier cutover or a design. Put them in one backlog and each one interrupts the other.
Then give the service a reason to improve. Look at what the reporting shows, decide what should change, and give that decision an owner. A managed service that cannot say what it will improve next is still only a support arrangement.