Designing interfaces for probabilistic answers

Twenty years of deterministic software taught people that what the screen says is true. Probabilistic systems break that contract, and the interface has to renegotiate it honestly.

Confidence is not a percentage

Showing users a raw confidence score transfers your calibration problem to them. Design the affordance instead: how easy is it to verify, to correct, to escalate?

Citations do more than cite

A visible source is a trust primitive. It converts "the system says" into "you can check" — and the checking almost never happens, which is exactly the point.

Latency is a design material

Streaming changes the perceived quality of an identical answer. So does showing the retrieval step. Users forgive slow far more readily than they forgive opaque.

Design the correction path first

Every probabilistic system will be wrong in front of a user. The interface that makes correction fast and dignified is the one people keep using.