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 20: | Line 20: | ||
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 | ==The “product”== | ||
'''What is your product?''' | ===The product may not be what you think it is=== | ||
'''What is your product?''' A ''document'' is not the product. A [[lawyer]] is not the product. [[Technology]] is not the product. The product is the task to be achieved; the problem to be solved. Documents are ''symptoms'' of the problem. | |||
==What will your product look like in 100 years=== | |||
This is a thought experiment to separate the essence from the [[substrate]]. Imagine all the accoutrements of today no longer apply: 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: 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 would your process look like then? What is its platonic essence? | |||
===what is 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 | *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? | ||
===What is the general systems unit?=== | ===What is 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. | ||