Fostering Continuous User Participation by Embedding a Communication Support Tool in User Interfaces

Abstract

This paper critically reviews previous IS literature on user participation and argues that the literature is mainly empirically or normatively oriented and lacks design research on developing system prototypes in order to foster continuous user participation. It then contributes to the current research by introducing a system prototype, a communication tool that enables users to participate while using their application systems in their work contexts. The prototype provides different communication channels for supporting user-designer communications and knowledge sharing among users with respect to application usage. When integrated in the interface of an application system, the tool can help to adapt and redesign the application. The initial evaluation of the communication tool within the context of an application system indicates its usefulness and usability.

Integración de pruebas remotas de usabilidad en Programación Extrema: revisión de literatura

“…El enfoque de desarrollo centrado en el usuario conocido en inglés como User Centered Development y referenciado en adelante como UCD ha sido combinado con metodologías ágiles, por medio de la integración de artefactos y roles como lo son usuarios, herramienta persona, pruebas unitarias, pruebas de usabilidad y evaluaciones de expertos de usabilidad (Wolkerstorfer, Tscheligi, Sefelin, Milchrahm, Hussain, Lechner & Shahzad, 2008). Así mismo, es importante fomentar la participación distribuida que proporcione infraestructura y canales de comunicación centrada en artefactos propios de cada metodología; además, fomentar valores de democracia en el lugar de trabajo, el conocimiento y la experiencia sustentados en reconocimiento, también el compromiso y aceptación de los involucrados (Yetim, Draxler, Stevens & Wulf , 2012).…”

“…¿Cómo integrar pruebas remotas de usabilidad en la metodología de desarrollo XP? es un tema que ha sido abordado por varios autores, los cuales han propuesto diferentes procesos conocidos también como enfoques combinados, lo que ha generado conceptos como pruebas de usabilidad ágil, desarrollo ágil y usable, prototipos para el extremo, donde además se propone que varios de los artefactos propios de las pruebas de usabilidad sean adaptados para el desarrollo extremo (Salgado, Amaral, Freire & Fortes, 2016;Sohaib, & Khan, 2010;Salah, Paige & Cairns, 2014;Wolkerstorfer, Tscheligi, Sefel, Milchrahm, Hussain, Lechner & Shahzad, 2008 ;Yetim, F., Draxler, Stevens, Wulf, 2012;Sohaib & Khan, 2010). Estos enfoques combinados han sido resumidos y documentados en la Tabla 3.…”

How Do Users Perceive a Design-in-Use Approach to Implementation? A Healthcare Case

“…Design in use serves the double purpose of responding to local circumstances in a manner that pursues planned ends and seizes the opportunities provided by emergent change [14]. To fulfill this purpose Markus [21] stresses the importance of troubleshooting and shakedown in the period immediately after go-live; Karasti et al [16] show the need to sustain designin-use processes for years or even decades; Yetim et al [45] propose to extend systems with an embedded tool for collecting design-in-use ideas; and Hertzum and Simonsen [15] catalog the competences needed locally to be able to configure systems and work practices for each other.…”

Towards sociable technologies

“…Examples for appropriation frameworks for software centered domains include the development and integration of a participative feedback tool into the Eclipse IDE [9,10] or attempts at formalizing a theoretical appropriation model focused on software [4]. The integration of appropriation frameworks directly in the IS which it is intended to support has been thoroughly investigated, tested and seems to have merit [25,33,38]. Traditionally, if hardware was involved in such studies, it is mostly considered in a systemic way in conjunction with software [6,19].…”