Dialog box: Difference between revisions

From The Jolly Contrarian
Jump to navigation Jump to search
No edit summary
Tags: Mobile edit Mobile web edit
No edit summary
 
(4 intermediate revisions by the same user not shown)
Line 1: Line 1:
{{a|design|}}Like the “[[polite notice]]”, a blight on our modern age. A ''canker''. an almost inevitable transgression of the [[JC]]’s [[seventh law of worker entropy]].  
{{a|design|{{image|Dialog|png|Are you sure you want to, like, do this? FOR THE TWO THOUSANDTH TIME.}}}}Ghastly things. Like the “polite notice”, a blight on our modern age. A ''canker''; an inevitable transgression of the [[JC]]’s [[seventh law of worker entropy]].  


Most [[dialogue box]]es are insentient, unwanted interruptions. They require your pointless intervention, before you can carry on the [[tedious]] task you were already occupied with. Dialog boxes can and do get buried under other pointless windows, files and dialogues, to the point where that can no longer be found. There they are the cause of many a crashed session.
Dialogue boxes are insentient, unwanted interruptions. They require pointless intervention before continuing the [[tedious]] task with which you were already occupied. They can and do get buried under windows, files and ''other'' pointless dialog boxes. They can be buried so deep as to be quite invisible, undetectable and unreachable. But they hang your session all the same, waiting obediently for reply that will never, and can never, come.


Ghastly things.
Dialog boxes are also, in their way, [[second-order derivative]] risk management tools. For what is one meant to achieve but an ''allocation of fault'', that can only play itself out upon, and not before, catastrophe?


Also, in their way, [[second-order derivative]] risk management tools. For what is is a dialogue box meant to achieve but allocation of risk, the can only play itself out upon and not before catastrophe. Does a dialogue box stop you from downloading a harmful worm from the internet in a suspicious attachment? Does a quarterly compliance attestation prevent the mischief thatcompliance in itself is designed to avoid? It's does not. Quite the contrary: it provides comfort –false comfort – that compliance is in hand, de-escalates whatever risk mitigation and minimisation processes might otherwise be available and instead provides a [[RAG status|green]] signal that the [[legible]] world is at peace.
Does a dialog box ''stop'' you from downloading that trojan worm? It does not. It just reminds you that it’s ''your'' posterior in the sling if you do. Does a quarterly [[compliance attestation]] that, say, you have not violated the employee share trading policy prevent anyone from doing so? Again, it does not. Quite the contrary: it provides comfort – ''false'' comfort – that compliance is in hand; it de-escalates whatever risk management process might otherwise be running and instead provides a [[RAG status|green]] signal that ''the [[legible]] world is at peace''.
 
This makes [[Middle management|management]] happy in the meantime, and gives it someone to point a finger at later. In this way, it resembles many of the protections afforded by a legal [[contract]] that do not target practical, day-to-day compliance or meaningfully go towards ensuring a robust system, but which merely allocate liability should the unthinkable — and since you’ve designed a sodding dialogue box for it, it’s not ''really'' unthinkable, is it? — happen.
 
The risks attested to by dialogue boxes fall into two categories: ''real'' ones and ''bullshit'' ones.
 
''Real'' ones, we think, will naturally weed themselves out in the same way that, as {{author|Rory Sutherland}} wryly suggested, a dishwasher does: if you want to make everything in your kitchen dishwasher-proof, ''just put everything in the dishwasher''. Within 3-weeks, hey presto! Everything left will be dishwasher-proof. In the same way, ''real'' risks addressed by salutary dialogue boxes, auto-generated email reminders and the like will surely present themselves from time to time, and it will be no surprise that this dumb, set-and-forget prophylactic will be singularly ineffective at preventing the risk realising itself. But it will provide management with a culprit: a bad apple; a weak gazelle, a [[root cause]]. The poor sod who missed it will doubtless pay the P45 price — don’t let the door smack you on the arse on your way out, friend — said smacked arse covering not its condemned owner, but the systemic failure that this “human error” conceals. {{author|Sidney Dekker}} rights persuasively about this in {{br|The Field Guide to Human Error Investigations}}.
 
''Bullshit'' risks, on the other hand, will remain, kludging up every employee’s day, burying themselves under open windows, causing system crashes, and doubtless full-time jobs employing and managing them to take account of whatever fantastical risks management is currently preoccupied with.


{{sa}}
{{sa}}
*{{br|Seeing Like a State}}
*[[Design principles]]
*[[Design principles]]
*[[Audit attestation]]
*[[Seventh law of worker entropy]]
*[[Seventh law of worker entropy]]

Latest revision as of 16:15, 3 January 2023

The design of organisations and products
Dialog.png
Are you sure you want to, like, do this? FOR THE TWO THOUSANDTH TIME.
Making legal contracts a better experience
Index — Click ᐅ to expand:

Comments? Questions? Suggestions? Requests? Insults? We’d love to 📧 hear from you.
Sign up for our newsletter.

Ghastly things. Like the “polite notice”, a blight on our modern age. A canker; an inevitable transgression of the JC’s seventh law of worker entropy.

Dialogue boxes are insentient, unwanted interruptions. They require pointless intervention before continuing the tedious task with which you were already occupied. They can and do get buried under windows, files and other pointless dialog boxes. They can be buried so deep as to be quite invisible, undetectable and unreachable. But they hang your session all the same, waiting obediently for reply that will never, and can never, come.

Dialog boxes are also, in their way, second-order derivative risk management tools. For what is one meant to achieve but an allocation of fault, that can only play itself out upon, and not before, catastrophe?

Does a dialog box stop you from downloading that trojan worm? It does not. It just reminds you that it’s your posterior in the sling if you do. Does a quarterly compliance attestation that, say, you have not violated the employee share trading policy prevent anyone from doing so? Again, it does not. Quite the contrary: it provides comfort – false comfort – that compliance is in hand; it de-escalates whatever risk management process might otherwise be running and instead provides a green signal that the legible world is at peace.

This makes management happy in the meantime, and gives it someone to point a finger at later. In this way, it resembles many of the protections afforded by a legal contract that do not target practical, day-to-day compliance or meaningfully go towards ensuring a robust system, but which merely allocate liability should the unthinkable — and since you’ve designed a sodding dialogue box for it, it’s not really unthinkable, is it? — happen.

The risks attested to by dialogue boxes fall into two categories: real ones and bullshit ones.

Real ones, we think, will naturally weed themselves out in the same way that, as Rory Sutherland wryly suggested, a dishwasher does: if you want to make everything in your kitchen dishwasher-proof, just put everything in the dishwasher. Within 3-weeks, hey presto! Everything left will be dishwasher-proof. In the same way, real risks addressed by salutary dialogue boxes, auto-generated email reminders and the like will surely present themselves from time to time, and it will be no surprise that this dumb, set-and-forget prophylactic will be singularly ineffective at preventing the risk realising itself. But it will provide management with a culprit: a bad apple; a weak gazelle, a root cause. The poor sod who missed it will doubtless pay the P45 price — don’t let the door smack you on the arse on your way out, friend — said smacked arse covering not its condemned owner, but the systemic failure that this “human error” conceals. Sidney Dekker rights persuasively about this in The Field Guide to Human Error Investigations.

Bullshit risks, on the other hand, will remain, kludging up every employee’s day, burying themselves under open windows, causing system crashes, and doubtless full-time jobs employing and managing them to take account of whatever fantastical risks management is currently preoccupied with.

See also