Design principles: Difference between revisions

Revision as of 18:08, 30 August 2020

In which the curmudgeonly old sod puts the world to rights.

Index — Click ᐅ to expand: The Devil’s Advocate

Tell me more Sign up for our newsletter — or just get in touch: for ½ a weekly 🍺 you get to consult JC. Ask about it here.

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.
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.

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

@@ Line 1: / Line 1: @@
 {{a|devil|}}
 *[[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''.
 *[[Amplify signal, minimise noise]]