Challenges in participant recruiting for usability testing

Adult code cart redesign: Clinical implications.

Production test and device I/O characterization are different tasks. Measurements and analysis associated with these different tasks need quite different tools. 1 Serial Data Links -the future is “bright” The 2001 ITRS predicted serial datacom rates reaching 40 GBPS by this year, doubling within a decade - and 40 GBPS production devices now exist. A 12.5 ps unit interval is tiny by today’s standards; for reliable data transmission to reach these rates the challenges are daunting. Despite this, we can fully expect such serial data links. What is required for them to be producible? Quite simply: reliable design, consistent process technology, and solid production test capability. 2 Design Qualification vs Production Test It is absolutely necessary to distinguish clearly between design qualification/characterization and the sort of test necessary to guarantee that a particular device is manufactured properly. Yet to sort one from the other is no mean task. It only takes a few extra ohms of interconnect to marginalize a good design; these few extra ohms will displace a transition by a few but unacceptably large number of picoseconds. Each bit in a high-speed serial data stream can be characterized by two key parameters: unit interval and individual edge displacement, expressed as a fraction of unit interval. Edge displacement is often referred to as jitter. Jitter is an unfortunate term, as it masks what is actually going on. Yes, some edges are out of place, but why are they? Displaced edges are created by intersymbol interference, internal systematic path or propagation delay errors, clock phase error, and random noise. These errors must be identified and minimized during the design qualification phase; the design is acceptable if error rate is sufficiently below target unless the product is defective. Key point: “random noise” in semiconductors is not very large. RJ in excess of 1 ps is more likely to be instrumentation noise than true circuit noise, or else is uncorrelated systematic error. This error is likely to be correctable in design. Laboratory equipment is generally capable of acquiring the data necessary to characterize today’s I/O designs. However, it is a costly mistake to attempt to translate these characterization tasks into a production test requirement. Measuring “jitter” in a production test environment is unneeded. What might be measured (and compared to design minimum, nominal, and maximum) are bit-by-bit displacements focused specifically on the structure of the specific serializers or deserializers in the signal path. This requirement is derived from the concept of defect-based testing: each element in the circuit (whether transistor, passive component, or interconnect) has a target quality requirement; if it is not manufactured to this quality requirement then something - something specific - is wrong. Yet this overall approach is insufficient by itself. It misses the tight coupling of the serial data stream to its internal self-aligned clock. If this clock is too erratic, then perfect serializing or deserializing circuitry will break. Conclusion: production test has two requirements: qualify the clock and qualify the bit generators or extractors. There should be no need for long data streams, or concomitant long test times.

Usability testing is a widely used evaluation method for product design during and after the development. Conventional usability testing applies short and discrete test tasks and task scenarios that are based on the tasks the product is designed to support. Thus, conventional test task design relies heavily on the representations of the specified context of use and the specified user requirements of the proposed design solution. However, a premature commitment to the specified context, requirements and proposed solutions may limit the scope of usability testing in a manner that hinders its capability to elicit and validate new user requirements, which is one of the objectives of the evaluation phase in the iterative user-centered design process. In this paper, we introduce a user-centered task design approach, which allows test participants to follow their natural work flow and freely express their needs during a test session. The main idea of this open-ended task approach is to break the tight link between the produced design solutions and the tasks used in the usability test and in this way increase the probability that novel user needs can emerge during a test session. Empirical results from a case study are used to depict the approach and its prerequisites, strengths, and limitations are discussed.

PurposeThis paper details a usability testing case study on a simplified homepage for [Library]. The usability testing was completed in Spring 2017 to meet the needs of diverse user groups and shifting trends in Web design and development. At the conclusion of the usability testing, recommendations for change informed the design decisions and a new homepage was implemented in October 2018.Design/methodology/approachThe researcher performed eight usability tests with a combination of the different library user types; full-time faculty, students, an administrator and members of the public. The usability test consisted of 13 specific tasks. After testers completed the tasks, users filled out a 30-question Likert-scale questionnaire and answered a set of 8 open-ended questions.FindingsThis paper discusses the recommendations for change which the researcher discovered at the conclusion of the usability testing period. The research found the need to improve and include specific navigational, visual and easy-to-use elements to best meet the needs of the users in the usability tests. Changes were ranked and implemented on a scale of catastrophic to cosmetic.Research limitations/implicationsAs websites, technology and user preferences continually evolve, the homepage will need to be tested for usability again in the next several years. Researchers are encouraged to adapt the methods to their own institutions.Practical implicationsThis paper discusses findings specific to [Library], which in turn has proved to increase usage of certain features and functions by the user community.Originality/valueThis is the first time usability testing has been done for the [Library’s] website. It was the first time the design of the homepage was informed by real user preference. This paper is valuable to those looking to create a simple, easy-to-use homepage that best benefits their own unique community of users.

Usability testing is regarded as a key element in user-centered design. Several studies from the Standish Group have shown that usability testing increases the chance of developing usable software. Companies are faced with many challenges: their customers demand usable products at reasonable costs and the customer base is distributed and diverse. Unfortunately, usability testing is often perceived as impractical due to the remote and distributed location of users, limited access to representative users, or a work context that is difficult to reproduce in a laboratory setting. Additionally, for some companies, the cost of transporting users or developers to remote locations can be prohibitive. Interest in remote usability testing has grown in response to these concerns.As the user advocate, the Information Technology student needs to be provided not only with hands-on experience in usability testing, but also with its nuances. These include an understanding of the wide range of formats and options available such as remote usability testing. Moreover, a remote format may be a solution for universities that do not have the resources to set up formal laboratories. There is a need to understand how best to facilitate remote testing in a classroom environment.The focus of our study was to identify appropriate tools and define methodologies for efficient and effective remote testing environments. We investigated commercial tools to determine their usefulness and cost-effectiveness for the classroom and then conducted an empirical study to compare traditional and remote usability testing of a web site using one of these tools. This paper will report on advantages and disadvantages of various remote testing tools, modifications to procedures and protocols of traditional testing, and the project findings, including usability problem identification, which establish the effectiveness of remote usability testing. Recommendations will be made for providing a credible environment for remote testing.

Stimulated by regulations and standards as well as commercial imperatives, medical device manufacturers are striving to make medical devices safer by decreasing the potential for harmful use errors. Accordingly, manufacturers are observing and interviewing intended users about their interactions with devices en route to developing user interface requirements; applying human factors engineering (HFE) principles when designing user interfaces; and conducting formative and summative usability tests to improve and validate their devices’ interactive quality. This has represented significant work for manufacturers, particularly the majority who started with little HFE knowledge and experience. Today, the “awakening” to HFE in medical device development is essentially over—an established manufacturer who is just now discovering HFE has been out of touch. After all, the U.S. Food and Drug Administration (FDA) and AAMI conducted their first joint conference on HFE in 1995 when they previewed HFE expectations related to recent changes in quality system regulation (QSR). So, it has been 17 years since HFE entered the medical industry’s zeitgeist. HFE specialists working in the medical industry used to focus on making devices more usable (i.e., user friendly). Since the QSR change, use safety has become the primary focus, resulting in user interfaces that are less vulnerable to harmful use errors. It is rather obvious how HFE affects the safety of some medical devices. In the design of a surgical instrument, for example, HFE’s aim would be to reduce the chance of cutting anything other than the intended target. This goal could be accomplished by including a blade guard and a mechanical interlock that requires more than one deliberate action to enable cutting.

It is all too common for products, such as consumer appliances, information systems, mobile apps, and websites, to cause trouble and frustration. For example, products are often difficult or dull to use, make tasks less flexible or more tedious, shift attention away from important or gratifying activities, and simply fail to deliver expected benefits or experiences. By identifying such trouble and frustration in the lab prior to widespread use, usability tests have proven a valuable method for informing redesign efforts. A usability test consists of having test users exercise a product and think aloud about their experience using it, while an evaluator observes the users and listens in on their thoughts. On this basis, the evaluator identifies usability problems and assesses the user experience. This book describes how to conduct usability tests. After providing context about concepts and testing, the main chapters of the book cover the steps involved in preparing for a usability test, executing the test sessions, and analyzing the test data. Throughout the chapters, concrete guidance is balanced against more complex issues with an impact on the robustness, validity, completeness, impact, and cost of a usability test. The book concludes with an outlook to variations of usability testing and alternatives to it.

Non-invasive ventilation (NIV) is assisted mechanical ventilation delivered via a facemask for people with chronic conditions that affect breathing. NIV is most commonly delivered via an interface (mask) covering the nose (nasal mask) or the nose and mouth (oronasal mask). The number of children in the UK requiring NIV is currently estimated to be around 5000. Mass-produced masks are available for both the adult and paediatric markets but masks that fit well are difficult to find for children who are small or have asymmetrical facial features. A good conforming fit between the mask and the patient’s face to minimise unintentional air leakage is essential to deliver the treatment effectively; most ventilators will trigger an alarm requiring action if such leakage is detected. We present an innovative use of 3D scanning and manufacturing technologies to deliver novel mask-face interfaces to optimise mask fit to the needs of individual patients. Ahead of planned user trials with paediatric patients, the project team trialled the feasibility of the process of creating and printing bespoke masks from 3D scan data and carried out testing of the masks in adult volunteers to select the strongest design concept for the paediatric trial. The evaluation of the process of designing a bespoke mask from scan data, arranging for its manufacture and carrying out user testing has been invaluable in gaining knowledge and discovering the pitfalls and timing bottlenecks in the processes. This allowed the team to iteratively refine the techniques and methods involved, informing user trials later on in the project. It has also provided indicative cost estimates for 3D printed mask prototype components which are useful in project decision making and trial planning. The value of the process extends to considerations for future implementation of the process within a clinical pathway.

Towards ensuring the reliability and dependability of vehicular crowd-sensing data in GPS-less location tracking

Teachers often test course materials by using them in class. Usability testing provides an alternative: teachers receive student feedback and revise materials before teaching a class. Case studies based on interviews and observations with two teaching assistants who usability tested materials before teaching introductory technical writing demonstrate how usability testing can make novice teachers more confident about and help them predict student experiences with their assignments. By helping to train teachers, usability testing can also help better serve students.

Distribution of gas hydrate reservoir in the first production test region of the Shenhu area, South China Sea

(1) COVID-19 pandemic restrictions caused a dramatic shift in research activities, forcing the adoption of remote practices and methods. Despite the known benefits of remote testing, there is limited knowledge on how to prepare and conduct such studies in the industrial context where the target users are experts and company employees. (2) In this article, we detail how we organized VR user tests in five industrial cases during the pandemic, focusing on practicalities and procedures. We cover both on-site testing, including disinfecting and other safety protocols, as well as remote and hybrid setups where both remote and on-site participants were involved. Subject matter experts from eight countries were involved in a total of 22 tests. (3) We share insights for VR user test arrangements relevant to the pandemic, remote and hybrid setups, and an industrial context, among others. (4) Our work confirms that with careful planning it is possible to organize user tests remotely. There are also some limitations in remote user testing, such as reduced visibility and interaction with participants. Most importantly, we list practical recommendations for organizing hybrid user tests with safety and disinfecting procedures for on-site VR use.

Pressure from customers, the trade press, and the competition is causing companies to focus more on delivering usable products. But even when the commitment is there, companies still find it difficult to get their developers to believe in the results of usability tests and to make improvements based on them. The authors report on what Lotus has done to bring developers closer to the process, describing tools, techniques, and concepts to optimize user interfaces. They have found four approaches particularly valuable in getting developers and other members of the product team involved in usability testing: informal setups, sit-in sessions, usability nights, and videotapes. Their experience shows that these methods are more effective than conventional practices, in which developers merely receive reports of key problems from the test sessions. >

Use of the Internet for health promotion is increasing; however, the lack of published research regarding website usability suggests that health promotion websites are being developed without consultation with their users or formal evaluation. This study conducted usability testing of an existing health promotion website to inform modifications and to identify common usability themes that should be addressed by organisations developing or maintaining a health promotion website. A combination of qualitative and quantitative techniques were implemented during the usability testing sessions to gather data from users while completing tasks on the website. Techniques included performance measures (time taken), direct observation (participant observation) and subjective user preferences (questionnaire and interview). Improvements to the website were measured in terms of reduced problems reported, reduced time taken to complete tasks and increased subjective reports. Seven usability themes emerged from the data: design, feedback, format, instructions, navigation, terminology and learnability. This study demonstrates the application of usability testing to the design and modification of a health promotion website and illustrates the areas or themes that can be used as a framework for testing and modification.

Performance ImprovementVolume 41, Issue 10 p. 23-28 Article Staples.com: Focus on usability Tom McCann, Tom McCann Tom.McCann@Staples.com Tom McCann, Senior Manager Usability, Staples Business Delivery. Tom has experience across a wide range of human performance environments ranging from evaluation of man-machine systems for the Australian Military, the design of front and back-office bank branch processes and accompanying forms, evaluation and design of client-server and intranet systems for a telephone and communications firm and the evaluation and design of instructional systems for industry and education. Tom holds a BA (Psych) from the Australian National University and an MA (Psych) from the University of Sydney.Search for more papers by this authorColin Hynes, Colin Hynes Colin.Hynes@Staples.com Colin Hynes, Director Site Usability, Staples Business Delivery. Colin founded, built and currently leads the usability group at Staples that is responsible for information architecture, functional definition, and usability testing of online products. Previously, he led the user experience strategy of websites for FedEx, AT&T, Fidelity Investments, SmithKline Beecham, and many others. Colin holds an MS in human factors in information design, an MS in journalism, and a BA in corporate communications.Search for more papers by this author Tom McCann, Tom McCann Tom.McCann@Staples.com Tom McCann, Senior Manager Usability, Staples Business Delivery. Tom has experience across a wide range of human performance environments ranging from evaluation of man-machine systems for the Australian Military, the design of front and back-office bank branch processes and accompanying forms, evaluation and design of client-server and intranet systems for a telephone and communications firm and the evaluation and design of instructional systems for industry and education. Tom holds a BA (Psych) from the Australian National University and an MA (Psych) from the University of Sydney.Search for more papers by this authorColin Hynes, Colin Hynes Colin.Hynes@Staples.com Colin Hynes, Director Site Usability, Staples Business Delivery. Colin founded, built and currently leads the usability group at Staples that is responsible for information architecture, functional definition, and usability testing of online products. Previously, he led the user experience strategy of websites for FedEx, AT&T, Fidelity Investments, SmithKline Beecham, and many others. Colin holds an MS in human factors in information design, an MS in journalism, and a BA in corporate communications.Search for more papers by this author First published: 08 February 2007 https://doi.org/10.1002/pfi.4140411006 AboutPDF ToolsRequest permissionExport citationAdd to favoritesTrack citation ShareShare Give accessShare full text accessShare full-text accessPlease review our Terms and Conditions of Use and check box below to share full-text version of article.I have read and accept the Wiley Online Library Terms and Conditions of UseShareable LinkUse the link below to share a full-text version of this article with your friends and colleagues. Learn more.Copy URL Share a linkShare onFacebookTwitterLinkedInRedditWechat Volume41, Issue10November/December 2002Pages 23-28 RelatedInformation