Software-as-a-service: Difference between revisions

no edit summary
No edit summary
No edit summary
Line 22: Line 22:
But common experience, when you finally get to play with it, is that these [[reg tech]] applications ''never quite do what you want them to''. Either ''your'' intended use isn’t ''quite'' the one the [[vendor]] had in mind — here the product can’t ''quite'' do what you want, and isn’t flexible enough for you to reconfigure it  so it can— call this a “'''misalignment'''” problem — or it ''can'', but to get the application to be of any use, it will need a good deal of energy, expertise and effort from ''your'' people to configure it; energy [[change adoption|they will be disinclined to provide]] — call this a “'''configuration'''” problem.
But common experience, when you finally get to play with it, is that these [[reg tech]] applications ''never quite do what you want them to''. Either ''your'' intended use isn’t ''quite'' the one the [[vendor]] had in mind — here the product can’t ''quite'' do what you want, and isn’t flexible enough for you to reconfigure it  so it can— call this a “'''misalignment'''” problem — or it ''can'', but to get the application to be of any use, it will need a good deal of energy, expertise and effort from ''your'' people to configure it; energy [[change adoption|they will be disinclined to provide]] — call this a “'''configuration'''” problem.


Misalignment and configuration are different problems, but most [[reg tech]] offerings suffer from both, because they both stem from the same fact of life: while there is an unquantifiably huge volume of [[tedium]] to be automated, ''no two instances of [[tedium]] are quite alike''. {{maxim|Tedium is particular, not generic}}. ''That is '''why''' it is [[tedious]]''. If the same instance of [[tedium]] were common to enough market participants that a glib [[SaaS]] solution could fix it, ''it would have been fixed by now''. Fixable tedium is not stable. Persistent tedium ''is'' stable. Notwithstanding breathtaking claims to the contrary from people who should really know better — who ''do'', in fact — this has been the story of technological progress in the legal industry in the last thirty years. ''Pace'' [[Allen & Overy]]’s [[thought-leader]]s there has been ''tons'' of legal technology. The [[BlackBerry]]. Citrix. Document comparison. Document management. Optical character recognition. Voice recognition. Cloud computing. Remote access. Working from home. Skype. Virtual deal rooms. e-Discovery. Legal process outsourcing. All things that effectively, quickly and cheaply solve generic problems, that are intuitive, that boost productivity from the get-go.
Misalignment and configuration are different problems, but most [[reg tech]] offerings suffer from both, because they both stem from the same fact of life: while there is an unquantifiably huge volume of [[tedium]] to be automated, ''no two instances of [[tedium]] are quite alike''. {{tedium is particular capsule}} Notwithstanding breathtaking claims to the contrary from people who should really know better — who ''do'', in fact — this has been the story of technological progress in the legal industry in the last thirty years. ''Pace'' [[Allen & Overy]]’s [[thought-leader]]s there has been ''tons'' of legal technology. The [[BlackBerry]]. Citrix. Document comparison. Document management. Optical character recognition. Voice recognition. Cloud computing. Remote access. Working from home. Skype. Virtual deal rooms. e-Discovery. Legal process outsourcing. All things that effectively, quickly and cheaply solve generic problems, that are intuitive, that boost productivity from the get-go.


====Misalignment====
====Misalignment====