We treat interfaces as a matter of convenience — how easy is it to use? But an interface is where a person and a system meet, and every meeting of unequal parties is a negotiation. The interface is the settlement: it decides what the person is allowed to know, to question, to change, and to refuse.
What an interface hides is part of its design
Every interface shows some things and hides others, and the hiding is never neutral. A system that shows you a confident answer and hides its uncertainty has decided you are a recipient, not a participant. A system that shows you why, and lets you push back, has decided the opposite.
When a system can act on your behalf, the interface is the only place you can grant, withhold, or withdraw that authority. Designed only for smoothness, it will reduce your friction to zero — which is the same as reducing your control to zero.
The two questions
For any interface between a person and a system, ask what the person can see — not just outputs, but reasoning, confidence, and the alternatives not taken — and what they can do about it: correct, override, refuse, or leave, and at what cost. A good interface widens both.
Ease that removes your ability to say no is not a service. It is a transfer.
The page beneath this one goes into the fine mechanics of consent — where the smallest design choices decide whether a “yes” really means yes.