Document assembly: Difference between revisions

Document assembly (view source)

Revision as of 11:21, 10 October 2022

53 bytes removed , 10 October 2022

no edit summary

Amwelladmin

Bureaucrats, Interface administrators, Administrators

82,891

edits

@@ Line 1: / Line 1: @@
 {{a|tech|
 [[File:Self-adjusting thank you letter.jpg|450px|thumb|center|[[nigel molesworth|Molesworth]]’s [[self-adjusting thank-you letter]], the first recorded instance of document assembly in legal history]]
-}}Not the [[Mediocre lawyer|lawyer]]-killing overwhelming disruptive tech that Darryl R Mountain thought it would be way back in 2006<ref>[https://doi.org/10.1093/ijlit/eal019 ''Disrupting Conventional Law Firm Business Models using Document Assembly''] International Journal of Law and Information Technology, Volume 15, Issue 2, Summer 2007, Pages 170–191. </ref>. Its capabilities are limited, it costs a lot (no one has figured out a sensible model for how to price it... by document? by structure? by user?) it is difficult to implement, and it ''really just isn’t very good''. Candidly, it has barely evolved past its original invocation, by [[noble, fearless and brave]] legal pioneer [[nigel molesworth]], whose first prototype is pictured at right.
+}}Not the [[Mediocre lawyer|lawyer]]-killing disruptive [[legaltech]] that [[thought leader|thought leaders]] thought it might be way back in 2006.<ref>[https://doi.org/10.1093/ijlit/eal019 Darryl R Mountain: ''Disrupting Conventional Law Firm Business Models using Document Assembly''] International Journal of Law and Information Technology, Volume 15, Issue 2, Summer 2007, Pages 170–191. </ref>
-It is specified by IT folk who don’t understand the business (legal) application, sold to (legal) users who don’t understand the technological benefits of automation, let alone the challenges sub-optimal legal language poses to that technical benefit — is there any more dispositionally Luddite a professional than a lawyer? — and is commissioned and configured by [[management consultant]]s who (a) don’t understand (that is, ''{{risk|fear}}'') the business application, (b) don’t trust (that is, ''{{risk|fear}}'') the legal users; and (c) are motivated to retain control of the process and quash any instinct for flexibility or creativeness by lawyers, whom they are trying to reconceptualise as mute users of overweening {{t|technology}} — that is to say, '''''[[user]]s'''''.
+Its capabilities are limited, it costs a lot (no one has figured out a sensible model for how to price it... by document? by structure? by user?) it is difficult to implement, and it ''really just isn’t very good''. Candidly, it has barely evolved past its original invocation, by [[noble, fearless and brave]] legal pioneer [[nigel molesworth]], whose first prototype is pictured at right.
+It is specified by [[IT department|IT folk]] who don’t understand the business application, sold to users who don’t understand the technological benefits of automation, let alone the challenges sub-optimal legal language poses to that benefit, and is commissioned and configured by [[management consultant]]s who (a) don’t understand (that is, ''{{risk|fear}}'') the business application, (b) don’t trust (that is, ''{{risk|fear}}'') the legal users; and (c) are motivated to retain control of the process and quash any instinct for flexibility or creativeness by lawyers, whom they are trying to reconceptualise as mute users of overweening {{t|technology}} — that is to say, '''''[[user]]s'''''.
 ===If document assembly is the answer...===