82,891
edits
Reg tech: Difference between revisions
no edit summary
Amwelladmin (talk | contribs) No edit summary |
Amwelladmin (talk | contribs) No edit summary |
||
| Line 2: | Line 2: | ||
:::''—{{author|Arthur C. Clarke}}’s Third Law'' | :::''—{{author|Arthur C. Clarke}}’s Third Law'' | ||
===Why is reg tech so disappointing?=== | ===Why is reg tech so disappointing?=== | ||
[[Document assembly]] has been around for a good 15 years — they thought it was “Lawyer-killing disruptive technology” in 2006<ref>See Darrel R Mountain’s OUP monograph on the subject from 2006 [https://academic.oup.com/ijlit/article-abstract/15/2/170/683915 “Disrupting Conventional Law Firm Business Models using Document Assembly”]</ref> and, well, the cockroaches — ''we'' cockroaches — are still here, ladies and gentlemen, and [[document assembly]] technology ''still'' | [[Document assembly]] has been around for a good 15 years — they thought it was “Lawyer-killing disruptive technology” in 2006<ref>See Darrel R Mountain’s OUP monograph on the subject from 2006 [https://academic.oup.com/ijlit/article-abstract/15/2/170/683915 “Disrupting Conventional Law Firm Business Models using Document Assembly”]</ref> and, well, the [[Mediocre lawyer|cockroaches]] — ''we'' cockroaches — are still here, ladies and gentlemen, and [[document assembly]] technology ''still'' doesn’t work very well. And nor, for all the promise, do many of the other heralded applications in the vanguard of the reg-tech revolution. The things that were supposed to revolutionise legal practice - put junior lawyers out of work — the chatbots; the natural language parsing; the data-extraction — these applications still seem to be eluding us. | ||
Why? | Why? | ||
If advanced technology is magic, then “magic” is in the eye of, and measured from the perspective of, the beholder. When the beholder in question inhabits the [[legal]] or [[compliance]] department the technology doesn’t have to be awfully advanced to seem magical. Especially in a [[proof of concept]]<ref>One could define the [[terms of reference]] of a successful [[POC]] as being extensive enough to show off the clever bits, but limited enough to conceal the rubbish.</ref>. Your [[sales]]guy airily drops “[[blockchain]]”, “[[chatbot]]”, “[[natural language processing]]”, “[[algorithm]]” and “[[AI]]” into his patter and he will sail through. | If advanced technology is magic, then “magic” is in the eye of, and measured from the perspective of, the beholder. When the beholder in question inhabits the [[legal]] or [[compliance]] department the technology doesn’t have to be awfully advanced to seem magical. Especially in a [[proof of concept]]<ref>One could define the [[terms of reference]] of a successful [[POC]] as being extensive enough to show off the clever bits, but limited enough to conceal the rubbish.</ref>. Your [[sales]]guy airily drops “[[blockchain]]”, “[[chatbot]]”, “[[natural language processing]]”, “[[algorithm]]” and “[[AI]]” into his patter and he will sail through. | ||
| Line 21: | Line 20: | ||
*'''Don't be a [[rentier]]''': How do I make money off something which is basically a simple idea that doesn’t require a lot of maintenance? The whole point of this tech is it is meant to be labour saving, right? I can’t do it per unit - the whole point is to eliminate the cost of having meatware do manual, repetitive tasks, and — once you have set it up — there is no actual cost to having a machine do it. So trying to act like a [[rentier]] is (a) a dick move and (b) is going to get you killed, because your big idea isn’t that flash, and someone will do it, and undercut you. See {{author|Roger Martin}}’s the {{br|The Design of Business: Why Design is the Next Competitive Advantage}} | *'''Don't be a [[rentier]]''': How do I make money off something which is basically a simple idea that doesn’t require a lot of maintenance? The whole point of this tech is it is meant to be labour saving, right? I can’t do it per unit - the whole point is to eliminate the cost of having meatware do manual, repetitive tasks, and — once you have set it up — there is no actual cost to having a machine do it. So trying to act like a [[rentier]] is (a) a dick move and (b) is going to get you killed, because your big idea isn’t that flash, and someone will do it, and undercut you. See {{author|Roger Martin}}’s the {{br|The Design of Business: Why Design is the Next Competitive Advantage}} | ||
*'''Remember the [[meatware]]''': If you convert your [[Meatware|user]] experience from “answering nuanced legal questions” into “completing a mandatory questionnaire”, you have lost. [[Document assembly]] applications: I’m talking to you. You are trying to make humans behave like machines. That is stupid. ''Humans aren’t good at emulating machines''. Humans are better than machines precisely because they aren’t machine-like. If you have reduced your process to a rules-based questionnaire, ''you don’t need humans at all''. Get a machine to do it - hook it up to the trading system directly. | *'''Remember the [[meatware]]''': If you convert your [[Meatware|user]] experience from “answering nuanced legal questions” into “completing a mandatory questionnaire”, you have lost. [[Document assembly]] applications: I’m talking to you. You are trying to make humans behave like machines. That is stupid. ''Humans aren’t good at emulating machines''. Humans are better than machines precisely because they aren’t machine-like. If you have reduced your process to a rules-based questionnaire, ''you don’t need humans at all''. Get a machine to do it - hook it up to the trading system directly. | ||
[[File:Tipp-Ex.jpg|thumb|left|For your monitor, sir.]] | |||
{{ref}} | {{ref}} | ||