Behøvebehov

Behøvebehov is a Danish term used in user experience design, product management, and related fields to describe the total set of needs that a user or stakeholder has for a product, service, or system. The concept emphasizes both expressed needs and latent or unarticulated needs that influence how a solution is perceived and used.

Etymology and scope: The word is a compound of behøve (to need) and behov (need), reflecting a focus on the underlying requirements that guide design and development. In practice, behøvebehov covers functional needs (what the product must do), usability needs (how easy and efficient it is to use), and emotional or relational needs (trust, satisfaction, comfort).

Application: Behøvebehov informs requirements gathering, prioritization, and design decisions. It helps teams distinguish between essential features and niceties, and between objective performance goals and subjective user impressions. Identifying these needs typically involves user research methods such as interviews, observations, diary studies, surveys, and usability testing, often integrated with persona development and journey mapping.

Frameworks and examples: Common frameworks used alongside behøvebehov include the Kano model (basic, performance, delight) and Jobs to be Done, which together help categorize needs. For a messaging app, functional needs might be reliable message delivery, while emotional needs could include privacy and trust. For a ride-sharing service, needs include availability, clear pricing, safety features, and straightforward instructions.

Relation to other concepts: The term is related to, and sometimes used interchangeably with, user needs and requirements, but it emphasizes a need-centered view in design. It is not universally standardized, and its exact interpretation can vary across organisations.

See also: User need, Jobs to be Done, Kano model, UX design.