82,891
edits
Service catalog: Difference between revisions
no edit summary
Amwelladmin (talk | contribs) No edit summary |
Amwelladmin (talk | contribs) No edit summary |
||
| 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>” | ||
The point at which a [[service catalog]] becomes irresistible is the [[tipping point]] where your organisation has so large and sprawling that the potential economies of scale outweigh the costs of disenfranchising all your local [[subject matter experts]] by jamming them into a universal model that won’t ''quite'' fit any of their local 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 | The point at which a [[service catalog]] becomes irresistible is the [[tipping point]] where your organisation has so large and sprawling that the potential economies of scale outweigh the costs of disenfranchising all your local [[subject matter experts]] by jamming them into a universal model that won’t ''quite'' fit any of their local 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. You cannot fight it because ''you are the redundancy the thrust is designed to eradicate''. | This is part of a wider thrust to [[operationalise]] the organisation. You, dear [[subject matter expert]], cannot fight it because ''you are the redundancy the thrust is designed to eradicate''. | ||
{{seealso}} | {{seealso}} | ||
*[[Playbook]] | *[[Playbook]] | ||