Skip to main content

Week 4 Session: What the Button Promises

Every button is a promise about what will happen next, somewhere between trivial and irreversible — and some buttons lie about which end of that scale they're on.

15 March 2027

Week 3 asked whether a shape earns the right to look pressable. This week asks a different question about the same object: once a shape has earned that right, what is it actually claiming will happen if you press it?

Every button is a promise about a state change. “Like” claims a small, reversible change to a counter and a record somewhere that you did it. “Send” claims a message will leave your control and arrive somewhere you can no longer edit it. “Delete account” claims something closer to the opposite of “like” — a state that, depending on the application, may not come back.

The axis

Reversible sits at one end: pressing again, or pressing undo, restores the previous state at no real cost. Irreversible sits at the other: once pressed, the previous state is permanently unavailable, or recoverable only at a cost the button gave no warning of.

Most buttons sit somewhere between the two, and where they sit is not always visible in how they look. A button styled in quiet grey text can trigger something irreversible; a button styled in alarming red can trigger something you can undo in one click. The same mismatch Week 3 diagnosed between a shape and its behaviour shows up here between a button’s weight and its consequence.

Five buttons, one application

Pick one real application you use — pick the app, not five buttons from five different places. Choose five of its buttons and, for each:

  1. name the button as it’s labelled
  2. say in one sentence what state actually changes when it’s pressed
  3. place it on the reversible-to-irreversible axis, and say what “reversing” it would actually require, if anything
  4. note its visual weight — is it styled to match how consequential it is, understated, or overstated?

The mismatch

Somewhere in your five, or elsewhere in the same application, find at least one button whose visual or verbal presentation misrepresents its actual consequence — quieter than it should be, louder than it needs to be, or worded to sound reversible when it isn’t. Name the button, the mismatch, and which direction it runs.

Submit

The five-button table and the one flagged mismatch. Keep the table somewhere you can find it again — Week 10 returns to one of these five buttons.

The spec

What you bring to the session. Written so a reader can tell whether it has been met without asking you.

Teaching team