Choice Architecture
- •
What it is
- •
The deliberate design of how choices are presented to a user, structured so that the "easy" default path is the one that benefits the designer rather than the user — while still technically offering the user "control."
- •
- •
Why it matters
- •
It explains why privacy controls inside most apps feel like an illusion. A dashboard full of toggles looks like meaningful control, but rarely offers the option people actually want ("only use my data to help me"). Worse, it shifts blame onto the user — you "had the choice" and didn't take it — when the real issue is that the defaults and friction were engineered to push you toward agreeing.
- •
- •
Example
- •
A cookie consent form with a dense maze of sliders and checkboxes, next to one big "I Agree" button. Almost everyone clicks "I Agree" just to read the article — not because they evaluated and accepted the terms, but because the form was built to make the alternative exhausting.
- •
- •
Related
- •
- •