Ownership vs. Usage

Products are purchased to be used. More features should mean more value—that's the logic behind feature lists. Yet customers pay for features they never use and remain dissatisfied. The question is: Why do purchase decisions and actual usage diverge so dramatically? What psychological mechanisms drive this gap, and what does the evidence tell us?

Studies

The MP3 Player Experiment

In 2017, Evan Polman and Sam Maglio conducted a study at the University of Wisconsin that systematically demonstrated the Having-Vs-Using Effect for the first time. They asked 145 students to choose between two MP3 players: Model A had 17 features and moderate user-friendliness, while Model B had only 7 features but excellent usability. Half of the participants were asked which player they would buy (the 'having frame'), while the other half were asked which one they would use (the 'using frame'). The results were striking: From the purchase perspective, 69% chose the feature-rich Model A. From the usage perspective, the preference reversed: 63% chose the simple Model B. The same people, the same products—but a different question fundamentally changed their choice.

The Vacation Planning Study

In a 2020 follow-up study, Polman and Maglio tested this effect with 312 participants making vacation decisions. Participants chose between two hotels: Hotel X offered extensive amenities (spa, three restaurants, fitness center, concierge) but average rooms, while Hotel Y had fewer services but exceptionally comfortable rooms and a quiet location. The researchers varied only the framing question: "Which hotel would you book?" versus "Which hotel would you prefer for your stay?" When asked about booking, 71% chose the service-rich Hotel X. When asked about staying, 58% preferred the comfortable Hotel Y. One week later, participants who had chosen from the booking perspective regretted their decision twice as often as those who had chosen from the stay perspective.

Principle

Which principle for Customer Experience Design can be derived from this? The core principle is: Sell for usage, not for ownership—value emerges from actual use, not from feature count. Companies should align their communication and product presentation with how the product feels and functions in everyday life, rather than focusing primarily on the number of available features. This approach is especially relevant for complex products or services where the gap between purchase expectations and usage experience is wide—such as software, technical devices, or digital platforms. For simple products with limited functions, this effect is less pronounced, since the ownership and usage perspectives align more closely. The following guidelines demonstrate how to implement this principle in practice.

Guidelines

Show usage context concretely

Show the product not in isolation, but in concrete usage situations. Use videos of people using it, screenshots of real workflows, and testimonials that describe everyday scenarios. The goal is to complement the ownership perspective of the purchase decision with actual usage impressions. Instead of saying "This CRM has 47 features," show "This is what a typical day with this CRM looks like."

Reformulating decision questions

Reframe decision aids from a usage perspective. Instead of asking "Which package would you like to purchase?" ask "Which of these features will you use regularly?" Rather than stating "Premium has more features," ask "For which of these tasks do you need daily support?" This reframing activates mental simulation of actual use and reduces feature overload.

Offer guided trial phases

Enable experience before purchase decisions through structured trial phases. Rather than simply offering a 'free trial,' provide guided onboarding sequences that allow users to work through real use cases. This approach lets potential customers experience the product from a usage perspective before making decisions from an ownership perspective, reducing the gap between expectation and reality.

Proactively managing usage expectations

Explicitly address post-purchase usage patterns: 'You've chosen the Premium package. Our data shows that most customers primarily use these 5 features. Would you like to start with these?' This approach prevents feature overwhelm and increases the likelihood that customers will actually derive value from the product rather than becoming lost in feature complexity.