Week 11 Session: The Button That's Lying to You
One real button whose wording, weight, or friction steers a choice, and what's lost when that leverage is removed.
3 May 2027
Three ideas from earlier weeks converge here. Week 4 said every button is a promise about a state change. Week 6 said a button can be built to reward repeated pressing regardless of whether the outcome matters. Week 10 said friction placed in front of a button can protect the person pressing it. All three can also be pointed the other way: a promise can be worded to obscure the state change, reward can be used to keep someone pressing past the point it serves them, and friction can be placed selectively — heavy on the choice you don’t want taken, absent on the one you do.
A button that does this isn’t broken like Week 7’s. It works exactly as built. The manipulation is in which choice it makes easy and which it makes costly, not in whether the mechanism functions.
Find one, honestly#
Find one real bounded button — not invented, not a vague composite — where the wording, size, position, timing, visual weight, or surrounding friction visibly pushes toward one option over another. Describe it accurately enough that the leverage is checkable: what it says, where the alternative option is, how it’s styled, whether accepting is one press and declining is several. If you can’t find or verify a public example, build and document your own instead of guessing at someone else’s.
Rebuild it honestly#
Rebuild the same button, changing only properties of the button and its immediate pressing interaction:
- wording
- size
- position
- timing
- visual weight
- confirmation or friction
Don’t change what the button actually does. Only change what it’s like to press.
Name the leverage#
Write one paragraph naming exactly what the original version was using against the person pressing it, and what specifically was lost — for that person, not in the abstract — once you removed it. If nothing was lost, say that too, and say what that tells you about whether the leverage was doing any real work.
The spec
What you bring to the session. Written so a reader can tell whether it has been met without asking you.
- you have found and accurately described one real bounded button whose wording, size, position, timing, visual weight, or confirmation friction pushes toward one choice — or documented your own example if a public one wasn't available
- you have rebuilt the same button honestly, changing only wording, size, position, timing, visual weight, or confirmation/friction, without changing what it does
- you have written one paragraph naming exactly what leverage the original used and what was lost, for the person pressing it, once you removed it
Teaching team
- Marisol Quaye — convenor