Brukerskrevne

Brukerskrevne is a Norwegian adjective describing requirements, requests, or features that have been demanded or requested by users. The term is commonly used in product development, user experience design, and public service design to distinguish what developers or providers think is valuable from what users explicitly ask for.

In practice, brukerskrevne aspects are identified through user research such as interviews, surveys, feedback channels, and usage analytics. They are then prioritized in roadmaps or backlogs and translated into specific features, improvements, or changes in service processes. Examples include a software function requested by a significant portion of users or an accessibility enhancement mandated by user groups.

In software and digital services, brukerskrevne features are weighed against technical feasibility, security, and business goals. The concept aligns with user-centered design and user-driven development, but it is not a formal standard; it is a descriptive label for user-derived requirements rather than a standalone process.

Criticism notes that overemphasizing brukerskrevne requests can lead to feature creep or catering to vocal minorities. Effective governance requires gathering representative input and applying transparent prioritization, ensuring brukerskrevne requests are evaluated alongside factors such as performance, maintainability, and regulatory compliance.

Related terms include brukerdrevet utvikling, brukerorientert design, and user stories. The concept helps ensure products and services reflect actual user needs rather than solely technical considerations.