82,976
edits
Service catalog: Difference between revisions
no edit summary
Amwelladmin (talk | contribs) No edit summary |
Amwelladmin (talk | contribs) No edit summary |
||
| Line 19: | Line 19: | ||
The [[service catalog]] is also of a piece with the [[risk taxonomy]] in its conviction that the forward needs of the organisation are perfectly understood, anticipated, and pre-determined. There is nothing new under the sun. Unless we are on the brink of apocalypse - ''the'' [[apocalypse]] that is: the one with horsemen, not just any old calamity - logically, this view is wildly mistaken. As the [[JC]] never tires of reminding us, [[Risk]]s, challenges and opportunities present themselves from undetected crevices in the [[space-time continuum]]. They are not languishing in plain sight within the pages of your [[playbook]]. | The [[service catalog]] is also of a piece with the [[risk taxonomy]] in its conviction that the forward needs of the organisation are perfectly understood, anticipated, and pre-determined. There is nothing new under the sun. Unless we are on the brink of apocalypse - ''the'' [[apocalypse]] that is: the one with horsemen, not just any old calamity - logically, this view is wildly mistaken. As the [[JC]] never tires of reminding us, [[Risk]]s, challenges and opportunities present themselves from undetected crevices in the [[space-time continuum]]. They are not languishing in plain sight within the pages of your [[playbook]]. | ||
It is at just the moment when existential threats emerge, unbidden, from the poorly-sewn seams of your [[risk taxonomy]], that you ''don’t'' want your risk controllers going | It is at just the moment when existential threats emerge, unbidden, from the poorly-sewn seams of your [[risk taxonomy]], that you ''don’t'' want your risk controllers going “sorry, but according to the [[service catalog]], that's not my problem". | ||
===Machines, not [[meatware]] === | ===Machines, not [[meatware]] === | ||
As that earnest collaboration on Wikipedia quoted above notes, the idea of a service catalog originated in the software management. In any decent sized organisation, pitches for new software will come in from all sides, and carefully curating the the IT | As that earnest collaboration on Wikipedia quoted above notes, the idea of a service catalog originated in the software management. In any decent sized organisation, pitches for new software will come in from all sides, and carefully curating the the IT “estate" is profoundly important. | ||
But software is dumb. It follows rules. It can only do what it was bought to do. To augment or change the application to which your software is dedicated, to meet a new challenge or opportunity - that requires judgment. An executive decision. Only a person can make an executive decision.<ref>[[AI]] freaks who beg to differ : [mailto:enquiries@jollycontrarian.com mail me] if you want an argument. I'm game. </ref> | But software is dumb. It follows rules. It can only do what it was bought to do. To augment or change the application to which your software is dedicated, to meet a new challenge or opportunity - that requires judgment. An executive decision. Only a person can make an executive decision.<ref>[[AI]] freaks who beg to differ : [mailto:enquiries@jollycontrarian.com mail me] if you want an argument. I'm game. </ref> | ||