82,891
edits
Service catalog: Difference between revisions
no edit summary
Amwelladmin (talk | contribs) No edit summary Tags: Mobile edit Mobile web edit |
Amwelladmin (talk | contribs) No edit summary Tags: Mobile edit Mobile web edit |
||
| Line 4: | Line 4: | ||
:“''Centralizing services also acts as a means of identifying service gaps and redundancies that can then be addressed by the enterprise to improve itself<ref>In other words, firing people.</ref>” | :“''Centralizing services also acts as a means of identifying service gaps and redundancies that can then be addressed by the enterprise to improve itself<ref>In other words, firing people.</ref>” | ||
In other words, you write down everything each machine, system, application or employee<ref>One of these kids is not like the others. One of these kids is not the same.</ref> is meant to do. It is a way of atomising and | In other words, you write down everything each machine, system, application or employee<ref>One of these kids is not like the others. One of these kids is not the same.</ref> is meant to do. It is a way of atomising, articulating and mapping every function in the organisation, with a view to [[operationalisation|operationalising]] every role. | ||
This will do two things: (1) | This exercise will do two things: (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 disposed]], on loyal grounds of ''preserving the integrity of the control environment'', to decline any invitation to take action or responsibility not explicitly assigned to them in the catalog. | ||
'''A [[service catalog]], that is to say, is the [[jobsworth's charter]].''' | '''A [[service catalog]], that is to say, is the [[jobsworth's charter]].''' | ||
It is hard to fault his logic. All my services cost something, and must be [[shredding|allocated]] back to a cost centre. The starting assumption must be that all valuable services have been catalogued and assigned to one function or another. I should not carry out an uncatalogued service. It is either ([[Q. E. D.]]) unnecessary and cannot be shredded, or it can be shredded, but only because it is in someone else's catalog and therefore it is their problem, not mine. In all lights, going “off catalog” is wasteful at best and liable to be risky. | |||
This is part of a wider thrust to [[operationalise]] the organisation and eliminate redundancies. You, dear [[subject matter expert]], cannot fight it, because ''you '''are''' the redundancy the thrust is designed to eradicate''. | The point at which a [[service catalog]] becomes irresistible is the [[tipping point]] where your organisation has become so sprawling that the potential [[redundancy|economies of scale]] outweigh the costs of disenfranchising all your local [[subject matter expert]]s by jamming them into a universal model that won’t ''quite'' fit ''any'' of their day-to-day experiences, and depriving them of the autonomy to use their subject matter expertise to make pragmatic decisions on the hoof to keep the organisation moving. | ||
This is part of a wider thrust to [[operationalise]] the organisation and eliminate - by which I mean ''make'' [[redundancies]]. You, dear [[subject matter expert]], cannot fight it, because ''you '''are''' the redundancy the thrust is designed to eradicate''. | |||
===Come the [[apocalypse]]=== | ===Come the [[apocalypse]]=== | ||