Service catalog: Difference between revisions

no edit summary
No edit summary
No edit summary
Tags: Mobile edit Mobile web edit
Line 9: Line 9:
:(1) excite the [[middle manager|management]] layer, who will regard it some kind of master key that unlocks all unrealised “[[redundancy|efficiencies]]”; and  
:(1) excite the [[middle manager|management]] layer, who will regard it some kind of master key that unlocks all unrealised “[[redundancy|efficiencies]]”; and  
:(2) licence [[jobsworth|those at the coalface]] who are so [[inclined]], on grounds of ''loyal preservation of the integrity of the control environment'', to decline any invitation to take action or responsibility not explicitly assigned to them in the catalog.  
:(2) licence [[jobsworth|those at the coalface]] who are so [[inclined]], on grounds of ''loyal preservation of the integrity of the control environment'', to decline any invitation to take action or responsibility not explicitly assigned to them in the catalog.  
:(3) cultivate a behaviour pattern of catalog parsing, to construe one’s own service commitments as narrowly and atomically as possible, even where — as all activities within  networked enterprise do — they form part of a wider process that can't be meaningfully articulated. These people will spend a large part of their day not checking the production line for themselves, but obtaining attestations from upstream neighbours that everything is in order, the line does not need to be checked for imperfections and, importantly, should any arise, they are categorically someone else’s fault.


A [[service catalog]], that is to say, is a jobsworth’s charter.
A [[service catalog]], that is to say, is a jobsworth’s charter. In this way so we see comprehensive operational responsibility for a process recede like an outgoing tide on a mudflat. As available human resources have been trimmed and it has become increasingly hard to carry out these roles, it is no wonder people should behave this way. They hardly have a choice.


It is hard to fault this logic, should logic be your constant and only frame of reference. All “services” must cost something, and so  must be [[shredding|allocated]] back to a cost centre. One should ''not'' carry out an uncatalogued service: it is either ([[Q.E.D.]])<ref>Ironic use of [[Q.E.D.]] here, by the way.</ref> unnecessary and, as such, unshreddible, or it ''is'' shreddible, but only because it is in someone ''else’s'' [[service catalog]] and is therefore ''their'' problem, not yours.  
It is hard to fault this logic, should logic be your constant and only frame of reference. All “services” must cost something, and so  must be [[shredding|allocated]] back to a cost centre. One should ''not'' carry out an uncatalogued service: it is either ([[Q.E.D.]])<ref>Ironic use of [[Q.E.D.]] here, by the way.</ref> unnecessary and, as such, unshreddible, or it ''is'' shreddible, but only because it is in someone ''else’s'' [[service catalog]] and is therefore ''their'' problem, not yours.