82,891
edits
Service catalog: Difference between revisions
no edit summary
Amwelladmin (talk | contribs) No edit summary |
Amwelladmin (talk | contribs) No edit summary |
||
| Line 48: | Line 48: | ||
===Service catalogs and the high-modernist approach to management=== | ===Service catalogs and the high-modernist approach to management=== | ||
Service catalogs and risk taxonomies also suffer from the folly of [[reductionism]]. For what is a [[service catalog]] if it is not an attempted atomisation; an attempt to reduce an ineffable whole to a series of articulated components, each of which can be understood on its own terms, in management theory, without loss of fidelity? This will to trifurcate legal services into the “bespoke” (a proper subject for a real lawyer) the “standard” (suitable for outsourcing to some para-legal operational business with common sense but not possessing the higher sense of taste and style of a learned fellow) and programmatic ([[Chatbot]] fodder) | Service catalogs and risk taxonomies also suffer from the folly of [[reductionism]]. For what is a [[service catalog]] if it is not an attempted atomisation; an attempt to reduce an ineffable whole to a series of articulated components, each of which can be understood on its own terms, in management theory, without loss of fidelity? This will to trifurcate legal services into the “bespoke” (a proper subject for a real lawyer) the “standard” (suitable for outsourcing to some para-legal operational business with common sense but not possessing the higher sense of taste and style of a learned fellow) and programmatic ([[Chatbot]] fodder) — blame {{author|Richard Susskind}} for this easy categorisation; it was his idea — notwithstanding that almost ''any'' legal service worthy of a name has components of all three in it, and teasing them apart is often more trouble than it is worth. | ||
And, we think, it runs the risk of missing something that [[Emergence|emerges]] from their confluence that you lose when you descend into the weeds. At one level, it is simple ease of processing: you might carve the conclusion of something as dreary as a [[confidentiality agreement]] into its articulated parts: contract policy formulation; fallback creation; document assembly; web-service creation and maintenance; and of course the secondary range of bureaucratic quality control measures: procurement, management information and statistics, internal audit and so on. | |||
But the dispatch of an [[NDA]] takes twenty minutes, comes along once a month, and often provides a convenient diversion during that stakeholder check-in call. and that one, over-qualified lawyer, while handling all that micro-bifurcation, might just see something in the intersection of two roles she, according to management theory, ought not be doing. It does happen: sometimes it is just easier to think while typing than hand it off to a minute secretary. | |||
{{sa}} | {{sa}} | ||