Parmit K. Chilana

Understanding usability practices in complex domains

Although usability methods are widely used for evaluating conventional graphical user interfaces and websites, there is a growing concern that current approaches are inadequate for evaluating complex, domain-specific tools. We interviewed 21 experienced usability professionals, including in-house experts, external consultants, and managers working in a variety of complex domains, and uncovered the challenges commonly posed by domain complexity and how practitioners work around them. We found that despite the best efforts by usability professionals to get familiar with complex domains on their own, the lack of formal domain expertise can be a significant hurdle for carrying out effective usability evaluations. Partnerships with domain experts lead to effective results as long as domain experts are willing to be an integral part of the usability team. These findings suggest that for achieving usability in complex domains, some fundamental educational changes may be needed in the training of usability professionals.

Acceptance of Commercially Available Wearable Activity Trackers Among Adults Aged Over 50 and With Chronic Illness: A Mixed-Methods Evaluation.

Background Physical inactivity and sedentary behavior increase the risk of chronic illness and death. The newest generation of “wearable” activity trackers offers potential as a multifaceted intervention to help people become more active. Objective To examine the usability and usefulness of wearable activity trackers for older adults living with chronic illness. Methods We recruited a purposive sample of 32 participants over the age of 50, who had been previously diagnosed with a chronic illness, including vascular disease, diabetes, arthritis, and osteoporosis. Participants were between 52 and 84 years of age (mean 64); among the study participants, 23 (72%) were women and the mean body mass index was 31 kg/m2. Participants tested 5 trackers, including a simple pedometer (Sportline or Mio) followed by 4 wearable activity trackers (Fitbit Zip, Misfit Shine, Jawbone Up 24, and Withings Pulse) in random order. Selected devices represented the range of wearable products and features available on the Canadian market in 2014. Participants wore each device for at least 3 days and evaluated it using a questionnaire developed from the Technology Acceptance Model. We used focus groups to explore participant experiences and a thematic analysis approach to data collection and analysis. Results Our study resulted in 4 themes: (1) adoption within a comfort zone; (2) self-awareness and goal setting; (3) purposes of data tracking; and (4) future of wearable activity trackers as health care devices. Prior to enrolling, few participants were aware of wearable activity trackers. Most also had been asked by a physician to exercise more and cited this as a motivation for testing the devices. None of the participants planned to purchase the simple pedometer after the study, citing poor accuracy and data loss, whereas 73% (N=32) planned to purchase a wearable activity tracker. Preferences varied but 50% felt they would buy a Fitbit and 42% felt they would buy a Misfit, Jawbone, or Withings. The simple pedometer had a mean acceptance score of 56/95 compared with 63 for the Withings, 65 for the Misfit and Jawbone, and 68 for the Fitbit. To improve usability, older users may benefit from devices that have better compatibility with personal computers or less-expensive Android mobile phones and tablets, and have comprehensive paper-based user manuals and apps that interpret user data. Conclusions For older adults living with chronic illness, wearable activity trackers are perceived as useful and acceptable. New users may need support to both set up the device and learn how to interpret their data.

How power users help and hinder open bug reporting

Many power users that contribute to open source projects have no intention of becoming regular contributors; they just want a bug fixed or a feature implemented. How often do these users participate in open source projects and what do they contribute? To investigate these questions, we analyzed the reports of Mozilla contributors who reported problems but were never assigned problems to fix. These analyses revealed that over 11 years and millions of reports, most of these 150,000 users reported non-issues that devolved into technical support, redundant reports with little new information, or narrow, expert feature requests. Reports that did lead to changes were reported by a comparably small group of experienced, frequent reporters, mostly before the release of Firefox 1. These results suggest that the primary value of open bug reporting is in recruiting talented reporters, and not in deriving value from the masses.

Design, discussion, and dissent in open bug reports

While studies have considered computer-mediated decision-making in several domains, few have considered the unique challenges posed in software design. To address this gap, a qualitative study of 100 contentious open source bug reports was performed. The results suggest that the immeasurability of many software qualities and conflicts between achieving original design intent and serving changing user needs led to a high reliance on anecdote, speculation, and generalization. The visual presentation of threaded discussions aggravated these problems making it difficult to view design proposals and comparative critiques. The results raise several new questions about the interaction between authority and evidence in online design discussions.

InterTwine: creating interapplication information scent to support coordinated use of software

Users often make continued and sustained use of online resources to complement use of a desktop application. For example, users may reference online tutorials to recall how to perform a particular task. While often used in a coordinated fashion, the browser and desktop application provide separate, independent mechanisms for helping users find and re-find task-relevant information. In this paper, we describe InterTwine, a system that links information in the web browser with relevant elements in the desktop application to create interapplication information scent. This explicit link produces a shared interapplication history to assist in re-finding information in both applications. As an example, InterTwine marks all menu items in the desktop application that are currently mentioned in the front-most web page. This paper introduces the notion of interapplication information scent, demonstrates the concept in InterTwine, and describes results from a formative study suggesting the utility of the concept.

From User-Centered to Adoption-Centered Design: A Case Study of an HCI Research Innovation Becoming a Product

As we increasingly strive for scientific rigor and generalizability in HCI research, should we entertain any hope that by doing good science, our discoveries will eventually be more transferrable to industry? We present an in-depth case study of how an HCI research innovation goes through the process of transitioning from a university project to a revenue-generating startup financed by venture capital. The innovation is a novel contextual help system for the Web, and we reflect on the different methods used to evaluate it and how research insights endure attempted dissemination as a commercial product. Although the extent to which any innovation succeeds commercially depends on a number of factors like market forces, we found that our HCI innovation with user-centered origins was in a unique position to gain traction with customers and garner buy-in from investors. However, since end users were not the buyers of our product, a strong user-centered focus obfuscated other critical needs of the startup and pushed out perspectives of non-user-centered stakeholders. To make the research-to-product transition, we had to focus on adoption-centered design, the process of understanding and designing for adopters and stakeholders of the product. Our case study raises questions about how we evaluate the novelty and research contributions of HCI innovations with respect to their potential for commercial impact.

Modern software product support processes and the usage of multimedia formats

Despite being an important channel for end-user assistance, few studies have directly investigated the interactions that occur in modern-day practice of software product support. We present results from a multi-dimensional analysis of product support activities at a leading design software company. We carried out a quantitative analysis of existing support requests, a survey with product support specialists, and follow-up interviews to understand the current practices in product support. In particular, we investigated the utility of different multimedia formats that modern web-based support systems enable. Our results showed that despite the value that these formats bring to support tasks, support specialists still face bottlenecks in remotely resolving software problems. We conclude by highlighting several opportunities in HCI for improving diagnosis and resolution of software issues over the web.

Understanding Conversational Programmers: A Perspective from the Software Industry

Recent research suggests that some students learn to program with the goal of becoming conversational programmers: they want to develop programming literacy skills not to write code in the future but mainly to develop conversational skills and communicate better with developers and to improve their marketability. To investigate the existence of such a population of conversational programmers in practice, we surveyed professionals at a large multinational technology company who were not in software development roles. Based on 3151 survey responses from professionals who never or rarely wrote code, we found that a significant number of them (42.6%) had invested in learning programming on the job. While many of these respondents wanted to perform traditional end-user programming tasks (e.g., data analysis), we discovered that two top motivations for learning programming were to improve the efficacy of technical conversations and to acquire marketable skillsets. The main contribution of this work is in empirically establishing the existence and characteristics of conversational programmers in a large software development context.

Designing for a billion users: a case study of facebook

Facebook is the worlds largest social network, connecting over 800 million users worldwide. The type of phenomenal growth experienced by Facebook in a short time is rare for any technology company. As the Facebook user base approaches the 1 billion mark, a number of exciting opportunities await the world of social networking and the future of the web. We present a case study of what it is like to design for a billion users at Facebook from the perspective of designers, engineers, managers, user experience researchers, and other stakeholders at the company. Our case study illustrates various complexities and tradeoffs in design through a Human-Computer Interaction (HCI) lens and highlights implications for tackling the challenges through research and practice.

Comparing bioinformatics software development by computer scientists and biologists: An exploratory study

We present the results of a study designed to better understand information-seeking activities in bioinformatics software development by computer scientists and biologists. We collected data through semi-structured interviews with eight participants from four different bioinformatics labs in North America. The research focus within these labs ranged from computational biology to applied molecular biology and biochemistry. The findings indicate that colleagues play a significant role in information seeking activities, but there is need for better methods of capturing and retaining information from them during development. Also, in terms of online information sources, there is need for more centralization, improved access and organization of resources, and more consistency among formats. More broadly, the findings illustrate a variety of information problems that end-user biologists and professional software developers face in developing bioinformatics software and how they are influenced by the level of domain knowledge and technical expertise.