Managing User Integration

The importance of robotics and assistive technologies for healthcare is increasing. For their introduction into practical application, the continuous integration of the user perspective is crucial to ensure acceptance and usability. This can be achieved by the user-centered design approach. In an earlier publication, several problems with its functional implementation within research and development (R&D) projects were pointed out. This chapter discusses possible solutions to promote an effective integration of the user perspective in R&D projects based on six interviews with experts from Germany. The results can be summarized in three main requirements: first, the generation of a common understanding of the target group; second, a scientific research approach considering the context of technology usage; third, projectification, with a focus on efficient resource planning, the development of generic technologies, and technology evaluations with the user group. Leaders of innovative projects can benefit from implementing these strategies in the development process.

THE VALUE OF THE NON-USER: DEVELOPING (NON-)USER PROFILES FOR THE DEVELOPMENT OF A ROBOT VACUUM WITH THE USE OF THE (NON-)PERSONA

This contribution explores non-user integration in a product development context of the development of a vacuum robot in order to analyse users as well as non-users of a product. While user profiles like the persona have been part of product development and product design for years, the non-user has not been widely explored.Within this contribution the known concept of the persona is extended and further developed to the non-persona, a profile that describes non-users and why they do not use a certain product, in this case the vacuum robot. Including the non-user in product development offers the chance of addressing yet unidentified product requirements and therefore opening the product up to a bigger audience. This template works for both users and non-users and can be used to include both sides in a development project.

Triggering Local Innovation Processes for the Implementation of Sector Coupling Projects: An Integrated Approach

Local implementation projects for sector coupling play an important role in the transformation to a more sustainable energy system. Despite various technical possibilities, there are various barriers to the realisation of local projects. Against this backdrop, we introduce an inter- and transdisciplinary approach to identifying and evaluating different power-to-X paths as well as setting up robust local implementation projects, which account for existing drivers and potential hurdles early on. After developing the approach conceptually, we exemplify our elaborations by applying them to a use case in the German city of Wuppertal. It can be shown that a mix of several interlinked interdisciplinary methods as well as several participatory elements is suitable for triggering a collective, local innovation process. However, the timing and extent of end-user integration remain a balancing act. The paper does not focus on a detailed description of power-to-X (PtX) as a central pillar of the sustainable transformation of the energy system. Rather, it focuses on the innovative methodological approach used to select a suitable use path and design a corresponding business model. The research approach was successfully implemented in the specific case study. However, it also becomes clear that the local-specific consideration entails limitations with regard to the transferability of the research design to other spatial contexts.

Changing Role of Users—Innovating Responsibly in Digital Health

Despite the recognition of the importance of stakeholder inclusion into decisions about new solutions offered to society, responsible innovation (RI) has stalled at the point of articulating a process of governance with a strongly normative loading, without clear practical guidelines toward implementation practices. The principles of RI direct us to involve the user early in the innovation process. However, it lacks direction of how to involve users and stakeholders into this process. In this article, we try to understand how to empower users to become a part of innovation process though empirical cases. Based on 11 cases of firms innovating in digital health and welfare services, we look on firm practices for user integration into their innovation process, as well as how the user’s behavior is changing due to new trends such as availability of information and digitalization of services. We try to explore this question through lenses of responsible innovation in the emerging field of digital healthcare. Our findings indicate that users are not a homogenous group—rather, their willingness to engage in innovative processes are distributed across a spectrum, ranging from informed to involved and, at extreme, to innovative user. Further, we identified signs of user and stakeholder inclusion in all our cases—albeit in different degrees. The most common group of inclusion is with involved users, and firms’ practices varying from sharing reciprocal information with users, to integration through focus groups, testing or collecting a more formative feedbacks from users. Although user inclusion into design space is perceived as important and beneficial for matching with market demands, it is also a time-consuming and costly process. We conclude with debating some policy impacts, pointing to the fact that inclusion is a resource-consuming process especially for small firms and that policy instruments have to be in place in order to secure true inclusion of users into the innovation process. Our article sheds light on RI practices, and we also suggest some avenues for future research to identify more precisely whom to include, when to include and at what stage of the innovation process.

Changing Role of Users - Innovating Responsibly in Digital Health

Despite the recognition of the importance of stakeholder inclusion into decisions about new solutions offered to society, responsible innovation (RI) has stalled at the point of articulating a process of governance with a strongly normative loading, without clear practical guidelines toward implementation practices. The principles of RI direct us to involve the user early in the innovation process. However, it lacks direction of how to involve users and stakeholders into this process. In this article, we try to understand how to empower users to become a part of innovation process though empirical cases. Based on 11 cases of firms innovating in digital health and welfare services, we look on firm practices for user integration into their innovation process, as well as how user’s behavior is changing due to new trends such as availability of information and digitalization of services. We try to explore this question through lenses of responsible innovation in the emerging field of digital healthcare.

Co-Design in the Development of a Mobile Health App for the Management of Knee Osteoarthritis by Patients and Physicians: Qualitative Study

Background Despite a doubling of osteoarthritis-targeted mobile health (mHealth) apps and high user interest and demand for health apps, their impact on patients, patient outcomes, and providers has not met expectations. Most health and medical apps fail to retain users longer than 90 days, and their potential for facilitating disease management, data sharing, and patient-provider communication is untapped. An important, recurrent criticism of app technology development is low user integration design. User integration ensures user needs, desires, functional requirements, and app aesthetics are responsive and reflect target user preferences. Objective This study aims to describe the co-design process for developing a knee osteoarthritis minimum viable product (MVP) mHealth app with patients, family physicians, and researchers that facilitates guided, evidence-based self-management and patient-physician communication. Methods Our qualitative co-design approach involved focus groups, prioritization activities, and a pre-post quality and satisfaction Kano survey. Study participants included family physicians, patient researchers and patients with knee osteoarthritis (including previous participants of related collaborative research), researchers, key stakeholders, and industry partners. The study setting was an academic health center in Southern Alberta. Results Distinct differences exist between what patients, physicians, and researchers perceive are the most important, convenient, desirable, and actionable app functional requirements. Despite differences, study participants agreed that the MVP should be electronic, should track patient symptoms and activities, and include features customized for patient- and physician-identified factors and international guideline-based self-management strategies. Through the research process, participants negotiated consensus on their respective priority functional requirements. The highest priorities were a visual symptom graph, setting goals, exercise planning and daily tracking, and self-management strategies. The structured co-design with patients, physicians, and researchers established multiple collaborative processes, grounded in shared concepts, language, power, rationale, mutual learning, and respect for diversity and differing opinions. These shared team principles fostered an open and inclusive environment that allowed for effective conceptualization, negotiation, and group reflection, aided by the provision of tangible and ongoing support throughout the research process, which encouraged team members to question conventional thinking. Group-, subgroup-, and individual-level data helped the team reveal how and for whom perspectives about individual functional requirements changed or remained stable over the course of the study. This provided valuable insight into how and why consensus emerged, despite the presence of multiple and differing underlying rationales for functional requirement prioritization. Conclusions It is feasible to preserve the diversity of perspectives while negotiating a consensus on the core functional requirements of an mHealth prototype app for knee osteoarthritis management. Our study sample was purposely constructed to facilitate high co-design interactivity. This study revealed important differences between the patient, physician, and researcher preferences for functional requirements of an mHealth app that did not preclude the development of consensus.

THE USER-DRIVEN MINIMUM FEASIBLE PRODUCT – TOWARDS A NOVEL APPROACH ON USER INTEGRATION

User integration is a key aspect of new product development. When applying corresponding methods, however, there is a communication gap that needs to be overcome by the designer. Prototyping is a means to bridge this disjunction, yet brings its own set of hermeneutic limitations. Taking a closer look at the processual information exchange, we propose the concept of the user-driven minimum feasible product (UD-MFP). It describes the artefact generated by the users themselves in their specific context, which contains the essence of the problem's solution as a possible source of validation.

Co-Design in the Development of a Mobile Health App for the Management of Knee Osteoarthritis by Patients and Physicians: Qualitative Study (Preprint)

BACKGROUND Despite a doubling of osteoarthritis-targeted mobile health (mHealth) apps and high user interest and demand for health apps, their impact on patients, patient outcomes, and providers has not met expectations. Most health and medical apps fail to retain users longer than 90 days, and their potential for facilitating disease management, data sharing, and patient-provider communication is untapped. An important, recurrent criticism of app technology development is low user integration design. User integration ensures user needs, desires, functional requirements, and app aesthetics are responsive and reflect target user preferences. OBJECTIVE This study aims to describe the co-design process for developing a knee osteoarthritis minimum viable product (MVP) mHealth app with patients, family physicians, and researchers that facilitates guided, evidence-based self-management and patient-physician communication. METHODS Our qualitative co-design approach involved focus groups, prioritization activities, and a pre-post quality and satisfaction Kano survey. Study participants included family physicians, patient researchers and patients with knee osteoarthritis (including previous participants of related collaborative research), researchers, key stakeholders, and industry partners. The study setting was an academic health center in Southern Alberta. RESULTS Distinct differences exist between what patients, physicians, and researchers perceive are the most important, convenient, desirable, and actionable app functional requirements. Despite differences, study participants agreed that the MVP should be electronic, should track patient symptoms and activities, and include features customized for patient- and physician-identified factors and international guideline-based self-management strategies. Through the research process, participants negotiated consensus on their respective priority functional requirements. The highest priorities were a visual symptom graph, setting goals, exercise planning and daily tracking, and self-management strategies. The structured co-design with patients, physicians, and researchers established multiple collaborative processes, grounded in shared concepts, language, power, rationale, mutual learning, and respect for diversity and differing opinions. These shared team principles fostered an open and inclusive environment that allowed for effective conceptualization, negotiation, and group reflection, aided by the provision of tangible and ongoing support throughout the research process, which encouraged team members to question conventional thinking. Group-, subgroup-, and individual-level data helped the team reveal how and for whom perspectives about individual functional requirements changed or remained stable over the course of the study. This provided valuable insight into how and why consensus emerged, despite the presence of multiple and differing underlying rationales for functional requirement prioritization. CONCLUSIONS It is feasible to preserve the diversity of perspectives while negotiating a consensus on the core functional requirements of an mHealth prototype app for knee osteoarthritis management. Our study sample was purposely constructed to facilitate high co-design interactivity. This study revealed important differences between the patient, physician, and researcher preferences for functional requirements of an mHealth app that did not preclude the development of consensus.