Introduction: Sensor-feedback systems can be used to support people after stroke during independent practice of gait. The main aim of the study was to describe the user-centred approach to (re)design the user interface of the sensor feedback system “Stappy” for people after stroke, and share the deliverables and key observations from this process. Methods: The user-centred approach was structured around four phases (the discovery, definition, development and delivery phase) which were fundamental to the design process. Fifteen participants with cognitive and/or physical limitations participated (10 women, 2/3 older than 65). Prototypes were evaluated in multiple test rounds, consisting of 2–7 individual test sessions. Results: Seven deliverables were created: a list of design requirements, a personae, a user flow, a low-, medium- and high-fidelity prototype and the character “Stappy”. The first six deliverables were necessary tools to design the user interface, whereas the character was a solution resulting from this design process. Key observations related to “readability and contrast of visual information”, “understanding and remembering information”, “physical limitations” were confirmed by and “empathy” was additionally derived from the design process. Conclusions: The study offers a structured methodology resulting in deliverables and key observations, which can be used to (re)design meaningful user interfaces for people after stroke. Additionally, the study provides a technique that may promote “empathy” through the creation of the character Stappy. The description may provide guidance for health care professionals, researchers or designers in future user interface design projects in which existing products are redesigned for people after stroke.
DOCUMENT
Deze handreiking is ontwikkeld voor designers en ontwikkelaars van AI-systemen, met als doel om te zorgen dat deze systemen voldoende uitlegbaar zijn. Voldoende betekent hier dat het voldoet aan de wettelijke eisen vanuit AI Act en AVG en dat gebruikers het systeem goed kunnen gebruiken. In deze handreiking leggen we ten eerste uit wat de eisen zijn die er wettelijk gelden voor uitlegbaarheid van AI-systemen. Deze zijn afkomstig uit de AVG en de AI-Act. Vervolgens leggen we uit hoe AI gebruikt wordt in de financiële sector en werken één probleem in detail uit. Voor dit probleem laten we vervolgens zien hoe de user interface aangepast kan worden om de AI uitlegbaar te maken. Deze ontwerpen dienen als prototypische voorbeelden die aangepast kunnen worden op nieuwe problemen. Deze handreiking is gebaseerd op uitlegbaarheid van AI-systemen voor de financiële sector. De adviezen kunnen echter ook gebruikt worden in andere sectoren.
MULTIFILE
Our study introduces an open general-purpose platform for the embodiment of conversational AI systems. Conversational User-interface Based Embodiment (CUBE) is designed to streamline the integration of embodied solutions into text-based dialog managers, providing flexibility for customization depending on the specific use case and application. CUBE is responsible for naturally interacting with users by listening, observing, and responding to them. A detailed account of the design and implementation of the solution is provided, as well as a thorough examination of how it can be integrated by developers and AI dialogue manager integrators. Through interviews with developers, insight was gained into the advantages of such systems. Additionally, key areas that require further research were identified in the current challenges in achieving natural interaction between the user and the embodiments. CUBE bridges some of the gaps by providing controls to further develop natural non-verbal communication.
LINK
This guide was developed for designers and developers of AI systems, with the goal of ensuring that these systems are sufficiently explainable. Sufficient here means that it meets the legal requirements from AI Act and GDPR and that users can use the system properly. Explainability of decisions is an important requirement in many systems and even an important principle for AI systems [HLEG19]. In many AI systems, explainability is not self-evident. AI researchers expect that the challenge of making AI explainable will only increase. For one thing, this comes from the applications: AI will be used more and more often, for larger and more sensitive decisions. On the other hand, organizations are making better and better models, for example, by using more different inputs. With more complex AI models, it is often less clear how a decision was made. Organizations that will deploy AI must take into account users' need for explanations. Systems that use AI should be designed to provide the user with appropriate explanations. In this guide, we first explain the legal requirements for explainability of AI systems. These come from the GDPR and the AI Act. Next, we explain how AI is used in the financial sector and elaborate on one problem in detail. For this problem, we then show how the user interface can be modified to make the AI explainable. These designs serve as prototypical examples that can be adapted to new problems. This guidance is based on explainability of AI systems for the financial sector. However, the advice can also be used in other sectors.
DOCUMENT
Purpose: The purposes of this study were, first, to (re)design the user-interface of the activity tracker known as the MOX with the help of input from elderly individuals living independently and, second, to assess the use of and experiences with the adapted Measure It Super Simple (MISS) activity tracker in daily life. Methods: The double diamond method, which was used to (re)design the user-interface, consists of four phases: discover, define, develop, and deliver. As a departure point, this study used a list of general design requirements that facilitate the development of technology for the elderly. Usage and experiences were assessed through interviews after elderly individuals had used the activity tracker for 2 weeks. Results: In co-creation with thirty-five elderly individuals (65 to 89-years-old) the design, feedback system, and application were further developed into a user-friendly interface: the Measure It Super Simple (MISS) activity. Twenty-eight elderly individuals (65 to 78-years-old) reported that they found the MISS activity easy to use, needed limited help when setting the tracker up, and required limited assistance when using it during their daily lives. Conclusions: This study offers a generic structured methodology and a list of design requirements to adapt the interface of an existing activity tracker consistent with the skills and needs of the elderly. The MISS activity seemed to be successfully (re)designed, like the elderly who participated in this pilot study reported that anyone should be able to use it.
DOCUMENT
Purpose: The aims of this study were to investigate how a variety of research methods is commonly employed to study technology and practitioner cognition. User-interface issues with infusion pumps were selected as a case because of its relevance to patient safety. Methods: Starting from a Cognitive Systems Engineering perspective, we developed an Impact Flow Diagram showing the relationship of computer technology, cognition, practitioner behavior, and system failure in the area of medical infusion devices. We subsequently conducted a systematic literature review on user-interface issues with infusion pumps, categorized the studies in terms of methods employed, and noted the usability problems found with particular methods. Next, we assigned usability problems and related methods to the levels in the Impact Flow Diagram. Results: Most study methods used to find user interface issues with infusion pumps focused on observable behavior rather than on how artifacts shape cognition and collaboration. A concerted and theorydriven application of these methods when testing infusion pumps is lacking in the literature. Detailed analysis of one case study provided an illustration of how to apply the Impact Flow Diagram, as well as how the scope of analysis may be broadened to include organizational and regulatory factors. Conclusion: Research methods to uncover use problems with technology may be used in many ways, with many different foci. We advocate the adoption of an Impact Flow Diagram perspective rather than merely focusing on usability issues in isolation. Truly advancing patient safety requires the systematic adoption of a systems perspective viewing people and technology as an ensemble, also in the design of medical device technology.
DOCUMENT
Background: Phantom limb pain is a frequent and persistent problem following amputation. Achieving sustainable favorable effects on phantom limb pain requires therapeutic interventions such as mirror therapy that target maladaptive neuroplastic changes in the central nervous system. Unfortunately, patients’ adherence to unsupervised exercises is generally poor and there is a need for effective strategies such as telerehabilitation to support long-term self-management of patients with phantom limb pain. Objective: The main aim of this study was to describe the user-centered approach that guided the design and development of a telerehabilitation platform for patients with phantom limb pain. We addressed 3 research questions: (1) Which requirements are defined by patients and therapists for the content and functions of a telerehabilitation platform and how can these requirements be prioritized to develop a first prototype of the platform? (2) How can the user interface of the telerehabilitation platform be designed so as to match the predefined critical user requirements and how can this interface be translated into a medium-fidelity prototype of the platform? (3) How do patients with phantom limb pain and their treating therapists judge the usability of the medium-fidelity prototype of the telerehabilitation platform in routine care and how can the platform be redesigned based on their feedback to achieve a high-fidelity prototype?
DOCUMENT
Deze casestudie geeft inzicht in verschillende soorten kennis die kenmerkend zijn voor applied design research. Er wordt onderscheid gemaakt tussen kennis over de huidige situatie, over wenselijke alternatieven en over effectieve oplossingen om daar te komen. Ofwel, kennis hoe het is, kennis over hoe het kan zijn en kennis over hoe het zal zijn als we effectieve oplossingen toepassen. Elk van deze soorten kennis heeft andere kwaliteitscriteria.
DOCUMENT
This exploratory study investigates the rationale behind categorizing algorithmic controls, or algorithmic affordances, in the graphical user interfaces (GUIs) of recommender systems. Seven professionals from industry and academia took part in an open card sorting activity to analyze 45 cards with examples of algorithmic affordances in recommender systems’ GUIs. Their objective was to identify potential design patterns including features on which to base these patterns. Analyzing the group discussions revealed distinct thought processes and defining factors for design patterns that were shared by academic and industry partners. While the discussions were promising, they also demonstrated a varying degree of alignment between industry and academia when it came to labelling the identified categories. Since this workshop is part of the preparation for creating a design pattern library of algorithmic affordances, and since the library aims to be useful for both industry and research partners, further research into design patterns of algorithmic affordances, particularly in terms of labelling and description, is required in order to establish categories that resonate with all relevant parties
LINK
In order to empower more people to become more selfreliant in society, interactive products and services should better match the skills and values of diverse user groups. In inclusive design, relevant end-user groups are involved early on and throughout the design and development process, leading to a better user experience. However, for IT businesses not operating in the academic domain, getting access to appropriate user research methods is difficult. This paper describes the design and prototype development of the Include Toolbox, in close cooperation with practitioners of small to medium sized enterprises (SMEs) in IT. It consists of an interactive app paired with a book. The app helps to find suitable research methods for diverse user groups such as older people, people with low literacy, and children. The book offers background information on the advantages of inclusive design, information on different user groups, and best practices shared by other companies.
DOCUMENT
