Meta: Data, Repeated Legal Cases and the Power of Defaults

The psychology and its limits

Eric Johnson and Daniel Goldstein’s 2003 paper examined defaults, including an experiment with hypothetical organ-donor decisions. The opt-in condition differed from the other conditions; opt-out and neutral conditions were not significantly different in that experiment. This was not a measurement of actual organ donations. [5]

A 2019 meta-analysis by Jachimowicz, Duncan, Weber and Johnson found substantial variation in default effects, including nonsignificant and negative findings. An average across studies cannot predict the result of your signup flow. [6]

For design, a default can appear to be a recommendation, preserve the status quo or save the effort of choosing. Which explanation applies depends on the situation. The research does not demonstrate that any particular Meta setting caused litigation or establish the company’s motives.

A practical six-step workflow

These are Maqtrix’s proposed applications to test, not outcomes established by the brand story or a promise of results.

1. List the decisions made by silence

   Walk through signup, checkout, notifications and account settings. Record what happens if a user accepts the screen without changing anything. Include less visible defaults such as preselected frequencies or permissions that persist from a previous visit.

2. Write the consequence in plain language

   Explain what the starting choice does at the moment it matters. A label such as “updates” can be too vague if it combines service messages with promotions. Describe the actual result rather than relying on a reassuring button colour.

3. Separate unrelated choices

   Do not bundle optional marketing preferences with a request for service simply because one combined checkbox is convenient. Decide which choices are necessary for the task and which deserve their own explanation. Check applicable consent requirements separately.

4. Make the alternative workable

   Ensure a person can change the choice without hunting through unrelated screens. The alternative should be readable, keyboard-accessible and understandable on a phone. An apparent choice with a broken or hidden route is not useful control.

5. Test understanding

   Ask a small group to explain what will happen next. Include people who leave the default unchanged and people who change it. Record misunderstandings before measuring acceptance. A high selection rate can coexist with poor comprehension.

6. Review downstream consequences

   Watch preference changes, complaints, unexpected messages and support contacts. A default that looks successful at signup may create frustration later. Keep a record of the wording and date so changes can be evaluated accurately.

A small-business example

Imagine a service business with an enquiry form. The visitor wants a reply about their request. That does not tell the business whether the person also wants a recurring promotional newsletter. A clear design can explain the enquiry response and handle optional marketing separately.

This is a proposed design principle, not individualized legal advice. The exact implementation should reflect the business’s actual data use and relevant obligations. Copying a large platform’s interface does not establish that the same choice is suitable for a small business.

What to measure

Assess whether people can correctly describe the setting, whether they can change it, and how often they later report an unexpected consequence. Track completion alongside comprehension and complaints. Do not optimize only for the number of boxes left selected; that can reward confusion rather than a useful experience.