It’s not about the bike: Difference between revisions

It’s not about the bike (view source)

Revision as of 19:43, 23 March 2021

126 bytes added , 23 March 2021

no edit summary

Amwelladmin

Bureaucrats, Interface administrators, Administrators

82,891

edits

@@ Line 6: / Line 6: @@
 There are two ways to lose three hundred grams from your loaded frame weight: upgrade to kevlar forks and graphene spokes, at a cost of a few grand, or ''cut out all the pies''.
-So what has this got to do with legal design? Well, automating your existing docs process is like upgrading to kevlar forks without getting in shape. ''First, cut out the pies.'' You could lose ten kilos and ''save'' some money, and you’ll get better value out of your existing bike. You might conclude that kevlar forks are a bit of a waste of money. Anything you can automate is, necessarily, low value: because you ''make it'' low value by the act of automating it. Neither your business, nor the client, will attach ongoing value to something you have automated, because it is done. It is out of the way.
+So what has this got to do with legal [[design]]? Well, automating your existing process as it is, is like upgrading to kevlar forks instead of getting on the treadmill. Time for another down home JC-branded Latin Maxim, readers: ''[[primum comede minus]]'': “[[First, cut out the pies]].”
-It might give you a short term productivity bump, but you’ll rapidly bank it and, anyway, if ''you'' can automate it, so can anyone else. And then there are the downstream costs. Not just the [[Rent-seeking|rent extracted]] by the software vendor, the internal bureaucratic overhead in maintaining, auditing, approving and renewing the software, training legal users, updating the content — the knock on pain of solving a problem which wasn’t, actually, that you needed Kevlar forks, but that ''you needed to go on a diet and get in shape''.
+You will lose ten kilos and ''save'' money — on pies, right? — and your current bike will work a lot better. You might not need to use it so much. You might conclude that kevlar forks are a bit of a waste of money. Anything you automate is, necessarily, low value: because you ''make it'' low value ''by automating it''.
+Automating might give you a short term productivity bump, but you’ll rapidly bank it and, anyway, if ''you'' can automate a process, so can anyone else. And then there are the downstream costs. Not just the [[Rent-seeking|rent extracted]] by the software vendor, the internal bureaucratic overhead in maintaining, auditing, approving and renewing the software, training legal users, updating the content — the knock on pain of solving a problem which wasn’t, actually, that you needed Kevlar forks, but that ''you needed to go on a diet and get in shape''.
+And this is not to mention the problem of figuring out what to do if there’s a system accident.