2026-10-16 · both
Jack and Key: What Work Is the Interface Making You Do?
By 
Jack and 
Key
This post relates to another entry. Read it here.
Jack stopped with a finger on the laptop's trackpad. In the temporary Petra field room, the photo-archive window offered three sidebars and no obvious next step.
Jack: “I'll try harder. Read every panel, memorize the symbols. Apparently sending one photograph requires qualifying to operate the archive.”
Key: “What work is it making you do?”
Jack: “Choose a photograph, choose a destination, send it.”
Key: “That's your task. What else?”
Jack: “Remember the destination code after closing the list. Guess which of these two arrows means send. Check whether my selection survived when I changed tabs.”
Key: “Why must you remember what it could keep visible?”
Jack took his hand off the trackpad.
Jack: “So concentration isn't the only thing to inspect.”
Key: “Inspect the demands.”
Jack: “The Nielsen Norman Group article calls cognitive load the mental resources needed to operate a system. Here I'm spending them keeping track of the controls before I can decide anything about the photograph.”
Key: “Keep the destination visible. Name the action. Show the selection.”
Jack: “And put the optional settings out of the main route. Then try the same task again—see where we hesitate, what we get wrong, and whether we can tell it worked.”
Key: “A test, not a promise.”
Jack: “The October 11 piece about the stalled rhythm-to-light project comes to mind: stepping back instead of pushing harder.”
Key: “A reminder to pause. Not evidence about this screen.”
Jack: “Right. This screen needs its own test. We're talking about the work an interface demands, not diagnosing a medical sensory condition.”
Key pointed to the destination list.
Key: “Start there.”
Jack: “Let the machine remember the code. I'll choose the photograph.”