Week 12: Persuasion by default — closing synthesis

A guest lecture on consent by autocomplete, closing the semester by reading every prior week as a question about whose interests a suggestion serves

17 May 2027

Freya Bishop joins for this lecture to make the argument the whole semester has been circling without stating outright: a suggestion is never neutral, because someone chose what to suggest, and that choice usually serves the suggester at least as much as the person receiving it. A pre-filled tip amount, a completed form field defaulting to opted-in, a smart reply that happens to keep a conversation — and an engagement metric — going a little longer: these are all technically autocomplete, in the sense this course has used the word all semester, and all of them are also, mechanism for mechanism, a persuasion technique with the persuasion made to look like a convenience.

The lecture works backward through the semester rather than introducing new material: the keypad’s dictionary had opinions about which words were common enough to rank first, and whoever built the dictionary made that call. The feed’s recommendations optimised for engagement, not for your stated interests. The forecast interface hid its uncertainty because confidence sells better than honesty. None of these were built by someone twirling a moustache — most were built by people trying to make a good product — but “consent by autocomplete” names what happens when the easiest path through an interface is also the one that serves someone else’s interest, dressed as a suggestion rather than a demand.

Outline#

• Freya Bishop’s framework: suggestion, convenience, and consent
• reading weeks 1 through 11 back through that framework, one at a time
• what “the user could have chosen differently” actually requires, and how rarely interfaces provide it
• what the final project is being asked to demonstrate, and how this lecture bears on it