82,891
edits
General systems unit: Difference between revisions
no edit summary
Amwelladmin (talk | contribs) No edit summary |
Amwelladmin (talk | contribs) No edit summary |
||
| Line 21: | Line 21: | ||
Are you getting calls from contractors in Hyderabad? Rather than throttling legal demand by charging for it, why not do that structurally, but limiting who — what grade — is allowed to seek it? | Are you getting calls from contractors in Hyderabad? Rather than throttling legal demand by charging for it, why not do that structurally, but limiting who — what grade — is allowed to seek it? | ||
==The “product”== | ==The “product”== | ||
The product may not be what you think it is. The product is the task to be achieved; the problem to be solved. | |||
Thought experiment, to separate the essence of the product from its [[substrate]]: imagine all today’s limitations and technological, conceptual constraints no longer apply. Imagine you are an undefined point in the future where logistical problems have been ''solved'': you know, when there are flying cars, teleportation, we live in a virtual matrix and the analogue world has been conclusively proved to be an optical illusion. | |||
=== | You don’t need paper, you don’t need email, you don’t need humans — this is a thought experiment, remember: The [[AI]] embedded in the General Systems Vehicle ''Just Because You’re Paranoid Doesn’t Mean No-one’s Following You'' can automatically configure agreements by itself. | ||
*What is the problem: distinguish between problems and symptoms. Inanimate objects — like documents, and templates — are rarely problems: they are ''symptoms'' of problems. Formal structures are rarely problems (or even all that relevant). Problems arise in interactions For example: a crappy document | |||
Now: in that scenario, what would your process look like then? What, in other words, is its [[Platonic form|Platonic essence]], that cannot be reduced by optimising [[Legal services delivery|legal service delivery]]? That is your product. Once you know that, then, considering everything you know now, and all [[adjacent possibilities]], and recognising the infinite number of useful things you don’t know, that if you did know, might send you in a different direction, what practical step can you take ''today'' that would lead in the direction that today looks like the optimal one? | |||
What wasteful processes or componentry can you remove? | |||
What new processes can you instill that will make the machine run better? | |||
Tomorrow, having taken that step, ask yourself that question again, afresh, based on the information and the [[adjacent possibilities]] open to you tomorrow. | |||
Rinse, repeat. This is [[iteration]]; this is super-forecasting: continually cleansing, reconsidering and rebasing, based on currently understood state of affairs. | |||
What do we have available to us to imagine that future: | |||
''Tools'' and ''expertise''. Do not confuse tools and expertise. Tools ''facilitate'' expertise. They ''amplify'' expertise. They cannot replace it. | |||
=== Expertise === | |||
==== Lawyers ==== | |||
A [[lawyer]] is not the product. | |||
==== Knowledge ==== | |||
=== Tools === | |||
==== Documents ==== | |||
We call it work product but a legal ''document'' is not the product. It is evidence of the product. Likewise, a bad document is not the problem. It is a ''symptom'' of the problem. | |||
==== Technology ==== | |||
[[Technology]] is not the product. It is a tool for solving the problem, or delivering the product. Technology cannot replace expertise | |||
==The problem== | |||
*What is the problem: distinguish between problems and symptoms. Inanimate objects — like documents, and templates — are rarely problems: they are ''symptoms'' of problems. Formal structures are rarely problems (or even all that relevant). Problems arise in interactions For example: a crappy document | |||
*Is what we focus on really the problem? | *Is what we focus on really the problem? | ||
== | ==The general systems unit== | ||
*A source of knowledge on how to optimise ''human'' processes and systems. | *A source of knowledge on how to optimise ''human'' processes and systems. | ||
*In scope: use of language, legal, | *In scope: use of language, legal, | ||
| Line 37: | Line 67: | ||
*A plain-English drafting service | *A plain-English drafting service | ||
*A legal technology platform | *A legal technology platform | ||
{{Sa}} | |||