This thesis provides insights into the feasibility of managing product requirements in a concept leveraging an object-centric information model. The aim of this concept is to provide efective management of product requirements in the context of rising volume and complexity of requirements. Firstly, benefts and challenges between the current document-centric way of managing requirements and the novel object-centric concept for managing requirements are mapped and presented. Secondly, the organizational prerequisites necessary for adopting the object-centric product requirement applicability concept are explored and insights into how this transition can be facilitated with knowledge management are generated. Thirdly, the accuracy of this novel concept is evaluated in terms of applying the correct requirements onto products and not more nor less. The methods in this thesis are of mixed nature and combine qualitative and quantitative data sets. The quantitative data was collected from the analysis of the requirement applicability concept and the previous tests of the same concept on diferent products at Company X. The analysis of quantitative data for concept accuracy revolved around interpreting the nature of negative- and positive delta values following an automatic application of requirements in the novel object-centric concept. The former of these delta values relates to relevant requirements missing onto products whereas the latter relates to non-relevant requirements being applied following the automatic application. The qualitative data was collected mainly through a comprehensive literature review, semi-structured interviews, a workshop, meetings, Company X documents and observations. The analysis of qualitative data was done via an adaptation of two frameworks: The Multi-Dimensional Framework for Digital Transformation by Hanelt et al, 2021 and The Process of Organizational Knowledge Creation by Nonaka, 1994. These adapted frameworks were leveraged to generate insights into the necessary organizational prerequisites for adopting the object-centric product requirement applicability concept. While benefts and challenges exist between the two diferent ways of managing requirements, these are not weighted and thus no defnitive conclusion on best practice is drawn. Instead these fndings provide organizations a reference point for evaluating each approach in relation to their own circumstances. Some of the prerequisites identifed as critical for adopting an object-centric product requirement applicability model are a digital library of requirement specifcations that are convertible to object-centric data format, and a suitable PLM strategy chosen by the Top Management Teams that is aiding the development of the concept. As for knowledge management in order to transition to the new concept, fndings show that standardized knowledge creation and knowledge exchange is necessary as well as developing centralized knowledge databases. Lastly, the quantitative fndings indicate that the applicability concept is accurate, but that there is a need for additional iterations with model improvements where the negative delta can be eliminated and the positive delta held at an acceptable level. / Den här studien ger insikter om genomförbarheten av att hantera produktkrav i ett koncept som utnyttjar en objektcentrerad informationsmodell. Syftet med detta koncept är att tillhandahålla efektiv hantering av produktkrav i samband med att de ökar i volym samt komplexitet. Studien kartlägger först fördelar och utmaningar mellan det nuvarande dokumentcentrerade sättet att hantera krav och det nya objektcentrerade konceptet. Även de organisatoriska förutsättningar som krävs för att införa det objektcentrerade produktkravskonceptet undersöks i samband med hur denna övergång kan underlättas med hjälp av kunskapshantering. Slutligen så utvärderas det objektcentrerade konceptet för kravapplicering beträfande hur exakt konceptet är i att applicera rätt krav på produkter. Metodiken i denna studie kombinerar kvalitativa och kvantitativa datamängder. Den kvantitativa datan samlades in från analys av kravappliceringskonceptet samt de tidigare testerna av konceptet på olika produkter som gjorts av Företag X. Analysen av kvantitativ data för hur exakt konceptet är i att applicera rätt krav kretsar kring att förstå grundorsakerna till de negativa och positiva deltavärden som uppkommit efter en automatisk applicering av krav i det nya objektcentrerade konceptet. Det negativa deltavärdet relaterar till nödvändiga krav som saknas på produkter, medan det positiva deltavärdet avser icke-relevanta krav som har applicerats efter en systemförfrågan och automatisk applicering av krav. Den kvalitativa datan samlades huvudsakligen in genom en omfattande litteraturstudie, semistrukturerade intervjuer, workshops, möten, dokument från Företag X och observationer. Analysen av kvalitativ data gjordes via en anpassning av två vetenskapliga ramverk: The Multi-Dimensional Framework for Digital Transformation av Hanelt et al, 2021 och The Process of Organizational Knowledge Creation av Nonaka, 1994. Dessa anpassade ramverk utnyttjas för att generera insikter i de nödvändiga organisatoriska förutsättningarna som krävs för att införa det objektcentrerade kravappliceringskonceptet i en organisation. Fördelar och utmaningar med de två olika sätten att hantera krav viktades inte i denna studie, därför dras ingen defnitiv slutsats om bästa praxis. Istället ger dessa fynd en referenspunkt till organisationer att utvärdera bästa praxis i förhållande till sina egna omständigheter. Några av förutsättningarna identiferade som kritiska för att tillämpa en objektcentrerad produktkravappliceringsmodell är ett digitalt bibliotek av kravspecifkationer som är konverterbara till objektcentrerat dataformat, samt en PLM-strategi införd av de högsta ledningsgrupperna som hjälper till med stödja det objekcentrerade konceptet för produktkravsapplicering. Vad gäller kunskapshantering för att övergå till det nya konceptet visar resultaten att standardiserad kunskapsskapande och utbyte av kunskap är nödvändigt, samt utvecklingen av centraliserade kunskapsdatabaser. Slutligen indikerar de kvantitativa resultaten att tillämpningskonceptet är noggrant, men att ytterligare iterationer med modellförbättringar behövs där den negativa deltan kan elimineras och där den positiva deltan hålls på en acceptabel nivå.

User retention is a key factor for Software as a Service (SaaS) companies to ensure long-term growth and profitability. One area which can have a lasting impact on a digital product’s user retention is its user onboarding experience, that is, the methods and elements that guide new users to become familiar with the product and activate them to become fully registered users. Within the area of user onboarding, multiple authors discuss “best practice” design patterns which are stated to positively influence the user retention of new users. However, none of the sources reviewed showcase any statistically significant proof of this claim. Thus, the objective of this study was to: Design and implement a set of commonly applied design patterns within a digital product’s user onboarding experience and evaluate their effects on user retention Through A/B testing on the SaaS product GetAccept, the following two design patterns were evaluated: Reduce friction – reducing the number of barriers and steps for a new user when first using a digital product; and Monitor progress – monitoring and clearly showcasing the progress of a new user’s journey when first using a digital product. The retention metric used to evaluate the two design patterns was first week user retention, defined as the share of customers who after signing up, sign in again at least once within one week. This was tested by randomly assigning new users into different groups: groups that did receive changes related to the design patterns, and one group did not receive any changes. By then comparing the first week user retention data between the groups using Fisher’s exact test, the conclusion could be drawn that with statistical significance, both of the evaluated design patterns positively influenced user retention for GetAccept. Furthermore, due to the generalizable nature of GetAccept’s product and the aspects evaluated, this conclusion should also be applicable to other companies and digital products with similar characteristics, and the method used to evaluate the impact of implementing the design patterns should be applicable for evaluating other design patterns and/or changes in digital products. However, as the method used for data collection in the study could not ensure full validity of it, the study could and should be repeated with the same design patterns on another digital product and set of users in order to strengthen the reliability of the conclusions drawn.