Legal technology: Difference between revisions

Revision as of 11:21, 7 February 2021

Redirect to:

@@ Line 1: / Line 1: @@
-{{a|Technology|}}No, not [[chat-bot]]s, {{t|AI}}, [[metadata extraction]], fuzzy logic or semantic syntactical parsing. That’s [[reg tech]], and it’s easy: the answer is [[blockchain]]. [[Legal technology]] is the real-life code that lawyers generate day in and day out: '''[[words]]'''.
+#redirect[[legal tech]]
-Should lawyers learn to code? My oath, they should. Because for the best paid professional writers on the planet, lawyers can't write for ''shit''.
-{{itstrategy}}
-===Addressing the barnacle risk===
-'''[[Strategic over tactical]]''': When drafting and updating templates *always* prioritise [[strategic over tactical]]. Say a new regulation has been introduced (I mean, just imagine!) which poses the question whether an existing form should be updated:
-*really, does it? Challenge whether any change is necessary
-**on economic grounds (could we lose money? How much? Realistically, how likely?)
-**on regulatory grounds (could we be in breach of the law? What are the consequences?)
-**on reputational grounds (could this affect the firm's franchise? How?)
-*If the issue is important look to do so in a way that shortens and simplifies:
-**take out specifics and render them as general statements
-**remove optionality and complexity – this is a tech and management imperative.
-{{sa}}
-*{{aiprov|A faster horse}}
-*{{br|Code: Version 2.0}}
-*[[Plain English]]
-{{plainenglish}}