My three laws of buttons:
1. If you display a button on the screen, I should be able to use it immediately. I should not have to wait for it to finish painting/fading in/whatever.
2. Buttons, once displayed, must not move of their own accord.
3. Clear visible feedback must be shown when I activate a button.
@flup fond happy fun memories of working in a dialysis clinic where every patient needed to be recorded as a hospital inpatient, in a records system with no concept of "routine inpatient", and delivered via a slow Citrix interface
I quickly memorised the flow and started clicking "No" on dialog boxes like "would you like to let Dr Mathew know that Dr Mathew has accepted their referral" and "would you like to print out an invite letter for the patient who's been sat behind you and receiving care for the last half hour already"... by pressing Alt-N before Citrix had even started rendering the dialog box
(I counted it once: eighty UI interactions to record four distinct facts per patient, times twenty to thirty patients each day. In my dreams, every CRM provides a bulk import feature that works equivalent to traipsing the UI)
@jackeric Jeez-oh. Reminds me of a month I spent working as tech support in a hospital lab around 2004. The test tracking system was text-based using some shonky terminal emulator, and was slow as hell -- the old hands could queue up a whole load of key sequences to enter test results way ahead of the system responding.
