How about “ownership” based?
I’m in a tech team. I own a few applications. It is my job to make sure they are maintained and supported. That “responsibility”/“ownership” includes a lot of fuzzy details that could be decided by top down management, but it rarely is:
1. When I need more headcount, it’s my job to defend the extra budget.
2. After there is budget, it is my job to make sure I get enough technical hands, in various geographical locations, to work on it. There are some “sought after” “junior devs” for whom I often need to fight with other app owners for. They only report to me on a dotted line basis. “Direct line reporting” is mostly irrelevant (except for performance discussion time).
3. After the *small*ish team is in place, it is my job to make sure the support structure stays in place no matter what. In practice, the “highly sought after dev”s get almost any weeks they want.in some of the more popular weeks, I have to stay on call for issues (I.e. no road trips), or do other such things. If I particularly strongly feel about a specific week, then I need to make sure everyone else knows about it well in advance (ie before others have put in their requests).
4. If there is a major clash where an application will not be supported from dev for a few days despite all efforts - we have one of two bad choices, wither work with the business stakeholders and tell them that issues will go unanswered for a day or two (I’ve done it once in 5 years), or have someone cancel his/her vacation (I’ve done it twice in 5 years, and one other junior developer once did it voluntarily so that I can go on a trip planned well in advance).