Design principles: Difference between revisions
Jump to navigation
Jump to search
Amwelladmin (talk | contribs) No edit summary |
Amwelladmin (talk | contribs) No edit summary |
||
| Line 1: | Line 1: | ||
{{a|design|}} | {{a|design|}} | ||
In Don | In {{Author|Don Norman}}’s terms<ref>{{Br|The Design of Everyday Things}}</ref> design is comprised of [[affordance]]s, [[signifier]]s, [[mapping]] and [[feedback]], a taxonomy of which the design of legal products seems utterly ignorant. | ||
*[[Know your purpose]] | *[[Know your purpose]] | ||
*[[Assume there will be accidents]]: The role of the risk manager is to know where the risks are concentrated, not to be satisfied there are no risks. If your [[RAG status]] has been uniformly green at every [[opco]] for the last ten years you should [[get your coat]]. Because either there ''is no'' [[risk]], so what are you even doing chairing an [[opco]], or you are flat-out delusional, so someone ''else'' is needed. | *[[Assume there will be accidents]]: The role of the risk manager is to know where the risks are concentrated, not to be satisfied there are no risks. If your [[RAG status]] has been uniformly green at every [[opco]] for the last ten years you should [[get your coat]]. Because either there ''is no'' [[risk]], so what are you even doing chairing an [[opco]], or you are flat-out delusional, so someone ''else'' is needed. | ||
| Line 18: | Line 18: | ||
*{{br|The Design of Everyday Things}} | *{{br|The Design of Everyday Things}} | ||
*[[Blind spot assistance]] | *[[Blind spot assistance]] | ||
{{Ref}} | |||
Revision as of 11:51, 8 March 2021
|
The design of organisations and products
|
In Don Norman’s terms[1] design is comprised of affordances, signifiers, mapping and feedback, a taxonomy of which the design of legal products seems utterly ignorant.
- Know your purpose
- Assume there will be accidents: The role of the risk manager is to know where the risks are concentrated, not to be satisfied there are no risks. If your RAG status has been uniformly green at every opco for the last ten years you should get your coat. Because either there is no risk, so what are you even doing chairing an opco, or you are flat-out delusional, so someone else is needed.
- Design for average people: be realistic about your people’s capability: they will be, on average, average.
- Iterate
- Open source: don’t seek rent.
- Amplify signal, minimise noise
- Know your client ↔ Be personal
- Have excellent data
- Automation eliminates value but not risk
- Solve simple problems. Like Blind spot assistance. Leave the hard stuff to the experts.
Antifragile
- Be sceptical of models ↔ Don’t tick boxes ↔ watch out for proxies. Don't confuse simplistic models with simplicity.
- Decomplicate ↔ reduce complexity: do few things well, rather than everything fairly.
- Be antifragile