A default is a decision the product makes before the customer acts. Quantity selectors, delivery choices and notification settings all carry an initial answer. Leaving those settings unexamined does not make them neutral.
- 01Start with the customer’s task
- 02Make the initial choice visible
- 03Measure the whole outcome
Start with the customer’s task
Johnson and Goldstein's research examined how defaults affected organ-donation consent decisions. That finding is useful context for thinking about choice architecture; it is not a forecast of what changing a shopping basket will do.
One of my older agency notes describes an espresso-martini mix offer with one-, three- and six-bottle options, and a three-bottle default. The design question worth keeping is whether a bundle matches a plausible use occasion. The old performance figures need the underlying campaign records before they belong in a public case study.
Make the initial choice visible
A default should be easy to recognise and easy to change. Show the selected quantity, total cost and relevant conditions before checkout. A larger basket created by a customer overlooking a setting is a poor foundation for repeat business.
For a hypothetical event-supply store, a starter bundle might make sense when its contents serve a clear event size. A single-item option should remain straightforward. Explain the bundle in terms of the job it does, not simply because it is the option the business prefers to sell.
Measure the whole outcome
Record the existing selection pattern before changing anything. Then compare purchases, cancellations, support questions and customer feedback. Watch whether the bundle creates unused product or confusion about the total price.
A default has earned its place when it makes a common task easier while leaving the customer in control. Treat it as a service decision as well as a conversion experiment.